Windows 7: ntoskrnl.exe+70600 BSOD, At my wits end.

yanquiuxo · 02 Jul 2010

Hello all! I built a computer almost a couple years ago with an ASUS P5Q Pro Mobo, Intel Core 2 Quad Q6600 Processor, 4 GB of Corsair PC800 RAM, EVGA Nvidia 9800GT 512MB Graphics

I have always gotten BSODs ever since I put it together that were somewhat bothersome but have been really irritating and more frequent as of late....I've replaced the hard drive a bunch, changed out for a new 9800GT, ran extensive tests with Memtestx86 with no errors. I am seriously out of options other than scrapping the whole thing, my friends won't let me come to them anymore for help because they all think I annoy them too much! Please help...

I'll attach all my BSOD minidumps from May, since that's the last time I reinstalled windows (all in all i've proabably installed windows fresh about 20 times since I've gotten the computer...

I've also tried multiple operating systems, It has happened with XP 32Bit, Vista, and 7 64. I don't think it's the RAM because memtest ran with no errors and I've already sent the mobo back to ASUS for repair under the warranty and they didn't find anything wrong with it!

I've looked at the minidumps, and it's always something different but the one constant is ntoskrnl.exe+70600 as the bad driver...a couple were ntfs driver errors. ANYONE'S INPUT WOULD BE APPRECIATED GREATLY, I AM REALLY OUT OF OPTIONS

reventon · 02 Jul 2010

Hi,

Latest 5 BSODs

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul  2 14:08:13.970 2010 (GMT+12)
System Uptime: 0 days 3:42:14.547
BugCheck 3B, {c0000046, fffff80002cb0ef8, fffff880089c08c0, 0}
*** WARNING: Unable to verify timestamp for pcouffin.sys
*** ERROR: Module load completed but symbols could not be loaded for pcouffin.sys
Probably caused by : pcouffin.sys ( pcouffin+9a80 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  ConvertXtoDvd.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul  1 11:57:01.404 2010 (GMT+12)
System Uptime: 0 days 1:13:58.371
BugCheck 3B, {c0000005, fffff80002f3e8bd, fffff880060b5080, 0}
Probably caused by : ntkrnlmp.exe ( nt!EtwpRundownNotifications+19 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WmiPrvSE.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 21:05:07.091 2010 (GMT+12)
System Uptime: 0 days 4:01:04.057
BugCheck 1E, {ffffffffc0000005, fffff80002cd8493, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiComputeStartingOffset+13 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 00:30:00.161 2010 (GMT+12)
System Uptime: 0 days 6:26:26.127
BugCheck 4A, {7fefdb160aa, 2, 0, fffff8800971ad60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
PROCESS_NAME:  explorer.exe
BUGCHECK_STR:  RAISED_IRQL_FAULT
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun 25 17:24:08.318 2010 (GMT+12)
System Uptime: 0 days 3:41:31.097
BugCheck 3B, {c0000005, fffff80002d86d5f, fffff8800672fef0, 0}
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+8f )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Only 3rd party driver mentioned as a cause is pcouffin.sys which is part of VSO's ConvertXtoDvd update from here and if that does not work then uninstall it.

Other drivers to be updated/removed:

Code:


adfs.SYS     Fri Jun 27 08:52:37 2008 (48640195)

AsIO.sys     Mon Dec 17 22:11:49 2007 (47663D55)

sptd.sys     Mon Mar 23 01:35:35 2009 (49C63097)

adfs.SYS - Adobe File System Driver - update any Adobe products that you have from Adobe

AsIO.sys - Asus Motherboard Driver - Updating instructions: Asus mobo utility driver updates - Windows Live

sptd.sys - Notorious for causing BSODs; remove Daemon Tools, then use this SPTD uninstaller: DuplexSecure - Downloads

Regards,
Reventon

yanquiuxo · 02 Jul 2010

Thanks for the response and tips! I've always used to DAEMON tools, so that is great advice to uninstall it. ConvertX was never on the computer until a week ago, so I don't think that would be it but going to uninstall anyway. As for the mobo, I have updated the BIOS to the most recent version which was summer 09 according to ASUS' site, so I'm not sure what other motherboard drivers there would be...or why it would say I have the 07 driver... interesting...

reventon · 02 Jul 2010

Rest of your BSODs:

Code:


BugCheck A, {fffffac04685eec0, 2, 0, fffff80002d83a2f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff80002d3ad5f, fffff88006e9eef0, 0}
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+8f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000007E, {ffffffffc0000005, fffff80002cdfba8, fffff8800330f888, fffff8800330f0f0}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+6a8 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {ffffffffc0000005, fffff80002f88f35, 0, ffffffffffffffff}
Probably caused by : win32k.sys ( win32k!GreSelectVisRgnInternal+1c8 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff80002d32a5f, fffff88008086cb0, 0}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff80002c4e90b, fffff88006132e60, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExQueryPoolUsage+e0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 24, {1904fb, fffff880031854f8, fffff88003184d60, fffff80002cbcc1e}
Probably caused by : fileinfo.sys ( fileinfo!FIStreamCleanup+4a )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 24, {1904fb, fffff88003928ba8, fffff88003928410, fffff80002c2e8eb}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushVolume+436 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {ffffffffc0000005, fffff80002c4954c, 0, ffffffffffffffff}
Probably caused by : win32k.sys ( win32k!xxxFreeWindow+1021 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000007E, {ffffffffc0000005, fffff8800ff26e1b, fffff88002befeb8, fffff88002bef720}
Probably caused by : nvlddmkm.sys ( nvlddmkm+e0e1b )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 19, {22, 40000000000000, 0, 0}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGDEVICE::DestroyAllocations+715 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff88001567ebf, fffff88006185b70, 0}
Probably caused by : cng.sys ( cng!DetermineFunctionInterface+3d8 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000007E, {ffffffffc0000005, fffff80002c80497, fffff880031d2958, fffff880031d21c0}
Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+47 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {ffffffffc0000005, fffff80002cdd765, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+265 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1000007E, {ffffffffc0000005, fffff80002c960ba, fffff880031fc6f8, fffff880031fbf60}
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireFastMutex+1a )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {ffffffffc0000005, fffff80002cf5a5f, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Interesting range - looking at that I would suspect a hardware fault; but lets get the drivers out of the way first and see what happens.

reventon · 02 Jul 2010

Quote:

I've also tried multiple operating systems, It has happened with XP 32Bit, Vista, and 7 64. I don't think it's the RAM because memtest ran with no errors and I've already sent the mobo back to ASUS for repair under the warranty and they didn't find anything wrong with it!

Ah, it is almost certainly hardware.

Memtest is not 100% accurate - try booting with only one stick at a time and see what happens.

yanquiuxo · 02 Jul 2010

i have booted with single sticks, both work on their own. I guess I will leave memtest running with more passes tonight and see what happens... And when encountering the BSODs, I always had DAEMON tools installed, even on XP, so I'm crossing my fingers that uninstalling the sptd driver and daemon will fix everything. I recently bought and tested a new PSU, but it failed to fix the problem. Let's hope for the best, unless you can find something hidden and magical in the minidumps... Thanks again for all the help!

yanquiuxo · 03 Jul 2010

DARNIT! A smooth day of no problems and then another BSOD. Here it is, if someone could look and tell me what they think I would really appreciate it!!! I've looked and this one is a little different but still ntoskrnl.exe

reventon · 03 Jul 2010

Code:


BugCheck 1000007E, {ffffffffc0000005, fffff80002e7b870, fffff88003316678, fffff88003315ee0}
Probably caused by : ntkrnlmp.exe ( nt!ObFastReferenceObject+10 )

Still looks like hardware.

I see that you have taken care of sptd.sys which is good. However the following driver is still present and out of date:

Code:


AsIO.sys     Mon Dec 17 22:11:49 2007

If you cannot find an update you might want to completely remove the application from your system.

yanquiuxo · 03 Jul 2010

thanks for the advice...I grabbed that last update...

I am using corsair 1066mhz ram model 8500c5d, and have been reading people having similar issues with this memory with asus motherboards...I went into my bios and tweaked the settings manually (everything was previously set to auto) to corsair's specs...havent had a bsod yet, but not getting my hopes up.

could it be the power supply possibly? mine is 80plus so it shouldnt be a problem

any advice you have is much appreciated.

thanks again

reventon · 03 Jul 2010

Hopefully changing the RAM voltage fixed it. PSU sounds ok - I take it it is 550W or greater?