[SOLVED] BSODs since new GPU install.

nlj223 · Apr 8, 2013

· OS - Windows 7 64bit
· What was original installed OS on system? Windows 7 64bit
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM
· Age of system (hardware) All OEM parts of varying age. Oldest is 5 year old HDD. Mobo is next oldest at 3 years old.
· Age of OS installation - have you re-installed the OS? 6 months was the last time I reformatted, it's installed on an SSD, while all other data/programs is kept on another SDD and an HDD

· CPU intel I7 980x
· Video Card Nvidia 680gtx
· MotherBoard EVGA x58 Classified3
· Power Supply - 850watt modular Antec Quattro 850

· System Manufacturer OEM self built
· Exact model number (if laptop, check label on bottom)

I didn't start getting any BSODs until I installed the 680. Not sure if it's a faulty card, or just because the drivers are so new. About 7 months ago I had some BSOD issues with my Harddrives, due to them being in AHCI mode where my OS thought they were in IDE, but since then BSODs have been very rare and far between.

They've occurred while playing games, or just while browsing the internet. My system can run fine for 10 hours, or BSOD after 5 minutes. It's not an over heating issue, as the the temp on the card never goes above 62c, even when fully stressed. Harddrives and solidstates have given me issues in the past, but. Hoping for an answer. Thanks!

What I've tried so far:

Fresh driver installs on everything from the GPU to the mobo. Reseated the GPU in another PCI slot and changed out the power cables with new ones. Stress tested the GPU with furmark for 2 hours, no BSOD. Tested memory for 10 passes, no issues there. Restored bios to default settings.

Just about everything except a reformat, as Im trying to avoid it if it won't fix the issues. Formatting 3 harddrives is a pain, but I'll do if it deemed necessary.

jcgriff2 · Apr 8, 2013

Hi -

The 7 BSODs were inconclusive at best. Video does seem to be involved in at least 3 BSODs.

Any chance this is a checked build? One bugcheck indicated the possibility.

Run - https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html

Regards. . .

jcgriff2

BSOD SUMMARY

Code:

[font=lucida console]
Debug session time: Mon Apr  8 01:24:18.794 2013 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040813-23821-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 0:34:44.104
Probably caused by : ntkrnlmp.exe ( nt!PspReturnResourceQuota+51 )
BugCheck A, {0, 2, 1, fffff8000349ce99}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000000A]IRQL_NOT_LESS_OR_EQUAL (a)[/url]
Bugcheck code 0000000A
Arguments: 
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000349ce99, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!PspReturnResourceQuota+51
MaxSpeed:     3330
CurrentSpeed: 3316
BiosVersion = 6.00 PG
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Apr  8 00:48:34.560 2013 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040713-24024-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 13:51:05.870
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BugCheck 1, {751d2e09, 8, 0, fffff8800cc6fca0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000001]APC_INDEX_MISMATCH (1)[/url]
Bugcheck code 00000001
Arguments: 
Arg1: 00000000751d2e09, address of system function (system call)
Arg2: 0000000000000008, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 0000000000000000, Thread->KernelApcDisable
Arg4: fffff8800cc6fca0, Previous KernelApcDisable
BUGCHECK_STR:  0x1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  X64_0x1_nt!KiSystemServiceExit+245
MaxSpeed:     3330
CurrentSpeed: 3316
BiosVersion = 6.00 PG
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Apr  7 10:56:22.090 2013 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040713-20030-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 1:02:11.415
Probably caused by : ntkrnlmp.exe ( nt!PpmPerfRecordUtility+18e )
BugCheck A, {48, 2, 0, fffff8000358916e}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000000A]IRQL_NOT_LESS_OR_EQUAL (a)[/url]
Bugcheck code 0000000A
Arguments: 
Arg1: 0000000000000048, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000358916e, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!PpmPerfRecordUtility+18e
MaxSpeed:     3330
CurrentSpeed: 3316
BiosVersion = 6.00 PG
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Apr  5 18:42:07.984 2013 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040513-18969-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 2:14:12.324
Probably caused by : dxgmms1.sys ( dxgmms1!DXGFASTMUTEX::Acquire+1a )
BugCheck 1000007E, {ffffffffc0000005, fffff88005557eea, fffff8800390c3f8, fffff8800390bc50}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x1000007E]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/url]
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88005557eea, The address that the exception occurred at
Arg3: fffff8800390c3f8, Exception Record Address
Arg4: fffff8800390bc50, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!DXGFASTMUTEX::Acquire+1a
MaxSpeed:     3330
CurrentSpeed: 3316
BiosVersion = 6.00 PG
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Apr  5 16:27:00.331 2013 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040513-21060-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 0:49:13.283
Probably caused by : ntkrnlmp.exe ( nt!KeRundownQueueEx+180 )
BugCheck A, {2010102, 2, 0, fffff8000348e660}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000000A]IRQL_NOT_LESS_OR_EQUAL (a)[/url]
Bugcheck code 0000000A
Arguments: 
Arg1: 0000000002010102, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000348e660, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  rifterrorhandl
FAILURE_BUCKET_ID:  X64_0xA_nt!KeRundownQueueEx+180
MaxSpeed:     3330
CurrentSpeed: 3316
BiosVersion = 6.00 PG
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Apr  5 15:35:49.916 2013 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\040513-21855-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 1:03:39.241
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec )
BugCheck 1E, {ffffffffc0000005, fffff880045417ac, 0, 8}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880045417ac, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000008, Parameter 1 of the exception
BUGCHECK_STR:  0x1E
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  rift.exe
FAILURE_BUCKET_ID:  X64_0x1E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+fec
MaxSpeed:     3330
CurrentSpeed: 3316
BiosVersion = 6.00 PG
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Mar 21 17:02:22.183 2013 (GMT-4)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\032113-23478-01.dmp]
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 0 days 5:43:06.524
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+b8 )
BugCheck 1000007E, {ffffffffc0000005, fffff88004821008, fffff88002e26698, fffff88002e25ef0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x1000007E]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/url]
Bugcheck code 1000007E
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004821008, The address that the exception occurred at
Arg3: fffff88002e26698, Exception Record Address
Arg4: fffff88002e25ef0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+b8
MaxSpeed:     3330
CurrentSpeed: 3316
BiosVersion = 6.00 PG
BiosReleaseDate = 06/30/2010
SystemManufacturer = OEM
SystemProductName = OEM
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


         
       [color=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
             
           [url=http://mvp.microsoft.com/profiles/Griffith][color=#000055][u][url]https://mvp.support.microsoft.com/profile/Griffith[/url][/u][/color][/url]   

           [url=https://www.sysnative.com][color=#000033][u][url]www.sysnative.com[/url][/u][/color][/url]
             
           [url=http://jcgriff2.com][color=#000055][u][url]www.jcgriff2.com[/url][/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

Wrench97 · Apr 8, 2013

When was the card changed there are BSOD's going back to June of last year?

nlj223 · Apr 8, 2013

Wrench97 said:
When was the card changed there are BSOD's going back to June of last year?

Card was changed about 30 days ago. The BSODs from june were due to issues with my harddrives. But between that time and now, BSODs have been very rare, and mostly due to adjusting overclock settings.

I'm just going to reformat and do a fresh install of windows. I'll get back to you guys if the problems continue.

Wrench97 · Apr 8, 2013

Remove any OC first and see if that helps at all.

nlj223 · Apr 8, 2013

Wrench97 said:
Remove any OC first and see if that helps at all.

Posting from laptop as I'm currently in the process of re-installing windows. I reset my bios to default settings two days ago, and it still didn't help at all. CPU and ram were both at stable stock settings, and I'm pretty sure it wasn't the OC settings causing the blue screens in the first place, as I stress tested the CPU, ram and GPU for a number of hours without a single bsod. Hopefully things will be looking up with this OS re install.

writhziden · Apr 8, 2013

The first thing to do when the system starts being unstable is to remove the overclock. Overclocking degrades hardware lifespans and can cause hardware to fail prematurely. If you test it initially and it is stable, that does not mean it will always be stable with the settings imposed. As soon as the system stops being stable, remove the overclock and see if it becomes stable.

If removing your overclock still does not provide stability, install a fresh Windows installation and see if problems persist. If problems continue with a clean install of Windows (and the overclock still removed, of course), it is likely the overclock damaged a hardware component and that component will need to be diagnosed and replaced.

nlj223 · Apr 12, 2013

writhziden said:
The first thing to do when the system starts being unstable is to remove the overclock. Overclocking degrades hardware lifespans and can cause hardware to fail prematurely. If you test it initially and it is stable, that does not mean it will always be stable with the settings imposed. As soon as the system stops being stable, remove the overclock and see if it becomes stable.

If removing your overclock still does not provide stability, install a fresh Windows installation and see if problems persist. If problems continue with a clean install of Windows (and the overclock still removed, of course), it is likely the overclock damaged a hardware component and that component will need to be diagnosed and replaced.

My system was stable for a good number of months, and nothing is over volted. IT's all OCed on default voltage. Really safe stuff.

So since reinstalling my OS, I got two BSODs which I chalked up to a network driver I hadn't installed. I have since fixed that, and was stable for a good 4 days. However, as of today I got another BSOD. Don't have any over clocking, not even running an XMP profile on my memory.

So I'm not really sure what the culprit is.

jcgriff2 · Apr 13, 2013

Hi. . .

Did you by any chance have ZCinema running? It is video related & showed up in the dump:

Code:

6: kd> [B]lmvm ZCinema_SRS_amd64[/B]
start             end                 module name
fffff880`0af29000 fffff880`0af2cf80   ZCinema_SRS_amd64   (deferred)             
    Image path: \SystemRoot\system32\drivers\[COLOR=#ff0000]ZCinema_SRS_amd64.sys[/COLOR]
    Image name: ZCinema_SRS_amd64.sys
    Timestamp:        Wed [COLOR=#ff0000]Aug 15[/COLOR] 15:28:11 [COLOR=#ff0000]2007[/COLOR] (46C353CB)
    CheckSum:         00012B74
    ImageSize:        00003F80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please note that it did not show up as a probable cause in the dumps - just a guess on my part.

Check for update - http://www.sysnative.com/drivers/driver.php?id=ZCinema_SRS_amd64.sys

Please run - https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html

Regards. . .

jcgriff2

`

nlj223 · Apr 14, 2013

jcgriff2 said:
Hi. . .

Did you by any chance have ZCinema running? It is video related & showed up in the dump:

Code:

6: kd> [B]lmvm ZCinema_SRS_amd64[/B] start end module name fffff880`0af29000 fffff880`0af2cf80 ZCinema_SRS_amd64 (deferred) Image path: \SystemRoot\system32\drivers\[COLOR=#ff0000]ZCinema_SRS_amd64.sys[/COLOR] Image name: ZCinema_SRS_amd64.sys Timestamp: Wed [COLOR=#ff0000]Aug 15[/COLOR] 15:28:11 [COLOR=#ff0000]2007[/COLOR] (46C353CB) CheckSum: 00012B74 ImageSize: 00003F80 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please note that it did not show up as a probable cause in the dumps - just a guess on my part.

Check for update - http://www.sysnative.com/drivers/driver.php?id=ZCinema_SRS_amd64.sys

Please run - https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html

Regards. . .

jcgriff2

`

I've had driver verifier running all day since that crash, but I haven't crashed since then either forunately or un-fortunately.. Zcinema is my really old pair of speakers, I'll think about replacing them. I'll report back if verifier catches a crash.. THanks for the help though.

jcgriff2 · Apr 14, 2013

No need to replace the speakers, just check for an updated driver.

Keep Driver Verifier running; use system as you normally do.

Regards. . .

jcgriff2

nlj223 · Apr 21, 2013

I ran the verifier for 2 days, and didn't BSOD, although my OS did freeze up once and didn't get a dump out of it.

But, I think I'm good at the moment. I haven't had a BSOD in probably 5 or 6 days now. Here's all the things I did, although I'm not entirely sure which one fixed it.

I inquired on the EVGA forums (manufacturer of my GPU and mobo) about similar problems with my particular model of GPU. They told me 3 things, Update bios(Which I did), don't use an XMP profile on the ram as it acts weird with the card, and disable the SATA 3 onboard controller, because it does strange things to the PCI slots and the power they get, which messed with the card.

So I did those things, and now I'm A-okay.

Thanks for all the help with narrowing it down! This forum and the people behind it are invaluable resource in trouble shooting.

writhziden · Apr 22, 2013

That's great news! Don't forget to disable Verifier if you have not already done so now that you're done troubleshooting. :-}

[SOLVED] BSODs since new GPU install.

nlj223

Member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Wrench97

Administrator, Hardware Expert

nlj223

Member

Wrench97

Administrator, Hardware Expert

nlj223

Member

writhziden

Administrator, .NET/UWP Developer

nlj223

Member

Attachments

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

nlj223

Member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

nlj223

Member

writhziden

Administrator, .NET/UWP Developer

[SOLVED] BSODs since new GPU install.

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Administrator, Hardware Expert

Member

Administrator, Hardware Expert

Member

Administrator, .NET/UWP Developer

Member

Attachments

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Member

Administrator, .NET/UWP Developer

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)