ntoskrnl.exe+70600 BSOD, At my wits end.

Y

yanquiuxo

New member
Local time
10:29 AM
Messages
8
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 :cry:
 

My Computer My Computer

At a glance

Windows 7 64-bit
Computer Manufacturer/Model Number
ASUS P5Q PRO
OS
Windows 7 64-bit
Hi,

Latest 5 BSODs

Code: 
[font=lucida console]
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 : [COLOR=Red][B]pcouffin.sys[/B][/COLOR] ( 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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/font]

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: 
[font=lucida console]
[B]adfs.SYS [/B]    Fri Jun 27 08:52:37 [COLOR=Red]2008[/COLOR] (48640195)
[B]
AsIO.sys [/B]    Mon Dec 17 22:11:49 [COLOR=Red]2007[/COLOR] (47663D55)

[COLOR=Red][B]sptd.sys[/B][/COLOR]     Mon Mar 23 01:35:35 2009 (49C63097)
[/font]

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
 

My Computer My Computer

At a glance

Windows 7 x64, Windows XP SP3, Fedora
OS
Windows 7 x64, Windows XP SP3, Fedora
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...
 

My Computer My Computer

At a glance

Windows 7 64-bit
Computer Manufacturer/Model Number
ASUS P5Q PRO
OS
Windows 7 64-bit
Rest of your BSODs:


Code: 
[font=lucida console]
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 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

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.
 

My Computer My Computer

At a glance

Windows 7 x64, Windows XP SP3, Fedora
OS
Windows 7 x64, Windows XP SP3, Fedora
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!
Click to expand...

Ah, it is almost certainly hardware.

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

My Computer My Computer

At a glance

Windows 7 x64, Windows XP SP3, Fedora
OS
Windows 7 x64, Windows XP SP3, Fedora
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!
 

My Computer My Computer

At a glance

Windows 7 64-bit
Computer Manufacturer/Model Number
ASUS P5Q PRO
OS
Windows 7 64-bit
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
 

My Computer My Computer

At a glance

Windows 7 64-bit
Computer Manufacturer/Model Number
ASUS P5Q PRO
OS
Windows 7 64-bit
Code: 
[font=lucida console]
BugCheck 1000007E, {ffffffffc0000005, fffff80002e7b870, fffff88003316678, fffff88003315ee0}
Probably caused by : ntkrnlmp.exe ( nt!ObFastReferenceObject+10 )
[/font]

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: 
[font=lucida console]
[B]AsIO.sys [/B]    Mon Dec 17 22:11:49 [COLOR=Red]2007[/COLOR]
[/font]

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

My Computer My Computer

At a glance

Windows 7 x64, Windows XP SP3, Fedora
OS
Windows 7 x64, Windows XP SP3, Fedora
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
 

My Computer My Computer

At a glance

Windows 7 64-bit
Computer Manufacturer/Model Number
ASUS P5Q PRO
OS
Windows 7 64-bit
Hopefully changing the RAM voltage fixed it. PSU sounds ok - I take it it is 550W or greater?
 

My Computer My Computer

At a glance

Windows 7 x64, Windows XP SP3, Fedora
OS
Windows 7 x64, Windows XP SP3, Fedora
yup. thermaltake 550watt psu. tweaked dram settings to 2.1v @ 1066mhz...if i get another blue screen, ill take it down to 800mhz, and if that doesn't work i'll have to replace the ram entirely...

and if THAT doesn't work, then honestly it's just going to be time for a new board :(
 

My Computer My Computer

At a glance

Windows 7 64-bit
Computer Manufacturer/Model Number
ASUS P5Q PRO
OS
Windows 7 64-bit
taking another look, it's only a 70% effeciency; but i still don't think it should be a problem...
 

My Computer My Computer

At a glance

Windows 7 64-bit
Computer Manufacturer/Model Number
ASUS P5Q PRO
OS
Windows 7 64-bit
It could be, but personally I think the fault lies somewhere in your CPU/RAM/Motherboard.

I run a similar (Q6600, GTS250, 4gig Corsair RAM) system on a Corsair 80+ 750W - but that is a bit of overkill.
 

My Computer My Computer

At a glance

Windows 7 x64, Windows XP SP3, Fedora
OS
Windows 7 x64, Windows XP SP3, Fedora
I've made another discovery...

I've always ran the ASUS EPU-6 Engine that came with my P5Q PRO mobo... I eventually updated to a newer version than what came with it. But the auto mode I had it running on, and the program in general is actually notorious for causing problems and blue screens with ASUS boards, go figure.

I always liked the software because the different settings allowed you to tweak CPU clockspeed/fanspeed/etc with a simple GUI, and was cool to do depending on hard I was pushing the comp....
but I now suspect that this has been the source of my problems from the very beginning.

I've uninstalled it and haven't had a problem yet; from what I've been reading I'd recommend for anyone who has EPU-6 and gets BSODs to uninstall it asap..I'll bump this if anything comes up...
 

My Computer My Computer

At a glance

Windows 7 64-bit
Computer Manufacturer/Model Number
ASUS P5Q PRO
OS
Windows 7 64-bit
reventon said:

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

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

The above driver (mentioned in my 1st post) is the ASUS EPU-6 Engine driver. I always recommend an update first, but thinking about it now this is not the first time I have seen it at fault. I will recommend immediate removal in future.

Glad to hear that your BSODs seem to have stopped.
 

My Computer My Computer

At a glance

Windows 7 x64, Windows XP SP3, Fedora
OS
Windows 7 x64, Windows XP SP3, Fedora
Hello I was suffering the BSOD HELLL since I built my lil PC. Memory_Management was the common failure. When I looked at the dump log discovered ntoskrnl.exe failure or similar. I searched and searched over days .. only by chance a few days ago stumbled upoun your page. After reading through the remarks re Bios "auto mode" etc I decided to have a fiddle with it. Instead of the bios handling the speeding up or down of RAM , CPU speeds etc , I went in and manually set it to a slower speed(800Mhz) than subsequently the standard default for the RAM (1066). I must say, fingers CROSSED. So far NO BSOD ... Yay. Apart from ASUS Motherboards, I suspect a lot of the bios software which promises to speed up and squeeze that extra millicycle from your CPU or RAM might actually be counterproductive. I have also run memtest86+ and it certainly shows one address error in a RAM stick. So I will be RMA'ing the set back to crucial. But I must stress , despite this error showing up on the test, overall now, my PC certainly is ROCK SOLID stable compared to the problems I was getting prior to tweaking BIOS setting....... THANKS :) :) :) PS - I thanks - I must add .. I have the gigabyte bios and mb .. so I think this may be a generic fault with all speeding up bios softwares .. Take care .. Regards to all :)
 

My Computer My Computer

At a glance

Windows 7 64bitIntell I5 (Something )Crucial Ballistic 4gb (soon to be exchanged)ATI 5400
OS
Windows 7 64bit
CPU
Intell I5 (Something )
Motherboard
Gigabyte P55A-UD3R
Memory
Crucial Ballistic 4gb (soon to be exchanged)
Graphics Card(s)
ATI 5400
Monitor(s) Displays
HP ZR24w
Hard Drives
Samasung 1.5TB
minotaur1967 said:
Hello I "was" suffering the BSOD HELLL since I built my lil PC. Memory_Management was the common failure. When I looked at the dump log discovered ntoskrnl.exe failure or similar. I searched and searched over days .. only by chance a few days ago stumbled upoun your page. After reading through the remarks re Bios "auto mode" etc I decided to have a fiddle with it. Instead of the bios handling the speeding up or down of RAM , CPU speeds etc , I went in and manually set it to a slower speed then the standard default for the RAM. I must say, fingers CROSSED. So far NO BSOD ... Yay. Apart from ASUS Motherboards, I suspect a lot of the bios software which promises to speed up and squeeze that extra millicycle from your CPU or RAM might actually be counterproductive. I have also run memtest86+ and it certainly shows one address error in a RAM stick. So I will be RMA'ing the set back to crucial. But I must stress , despite this error showing up on the test, overall now, my PC certainly is ROCK SOLID stable compared to the problems I was getting prior to tweaking BIOS setting. THANKS :) :) :)
Click to expand...

Glad to hear you have it solved.

Make sure you also do not install/use the EPU-6 Engine otherwise you will be coming back here for more help.
 

My Computer My Computer

At a glance

Windows 7 x64, Windows XP SP3, Fedora
OS
Windows 7 x64, Windows XP SP3, Fedora
You must log in or register to reply here.

Similar threads

BSODs since March and I am COMPLETELY at my wits end. PLEASE help.
Replies
5
Views
1K
LDbro92
L
at my wits end with apphelp.dll errors!
Replies
3
Views
2K
Mellon Head
Mellon Head
Looking for help, Multipul BSOD, at my wits end.
Replies
7
Views
2K
Arc
Arc
Solved At wits end with BSOD's
Replies
17
Views
4K
sygnus21
sygnus21
Solved At my wits end with windows
Replies
8
Views
2K
DavidE
DavidE
Back
Top