New
#1
BSOD Memory
I just want to verified that does BSOD are caused by memory.
I just want to verified that does BSOD are caused by memory.
I agree with Ken. A RAM test is in order. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
I notice a Stop 0x124 error, which is a hardware error. Please read this article on it: https://www.sevenforums.com/crash-loc...-what-try.html
As for the old drivers Ken is referring to:That belongs to Asus PC Probe. Please remove PC Probe, or install the latest version from the Asus support site: ASUSTeK Computer Inc.-Support-Code:AsIO.sys Mon Dec 17 04:10:20 2007
BSOD BUGCHECK SUMMARYCode:Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Debug session time: Mon Jun 14 09:29:09.621 2010 (UTC - 4:00) System Uptime: 0 days 0:00:13.885 BugCheck 1000008E, {c0000005, 82a5b62f, 8f2d3704, 0} Probably caused by : ntkrpamp.exe ( nt!CmpKcbCacheLookup+6bd ) BUGCHECK_STR: 0x8E PROCESS_NAME: svchost.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Debug session time: Sun Jun 13 14:47:30.975 2010 (UTC - 4:00) System Uptime: 0 days 0:00:07.224 BUGCHECK_STR: 0xc0000221 PROCESS_NAME: System ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Debug session time: Sun Jun 13 16:28:21.131 2010 (UTC - 4:00) System Uptime: 0 days 0:00:07.396 BugCheck 124, {0, 86208024, 0, 0} Probably caused by : hardware BUGCHECK_STR: 0x124_AuthenticAMD PROCESS_NAME: System ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
I got a 2 Error in Test 8 after second pass, does this mean the ram is no good?
Possibly.
At this point,if I were you, I would double check the bios settings.
Make sure the RAM is set properly,according to the specs.
It's possible the "Auto" voltage was set too low or the timings are set wrong.
While not likely, as it it normally defaults to rather relaxed settings, its possible.
If all of that is OK, follow Jonathan Kings advice & the suggested link for the stop code.
Did you run memtest86+ one stick at a time and alternate the slots?
I running it again, I think its because of poor ventilation... since when did ram gets so senstive to heat ...
running both rams with memtest, no problems yet..