BSOD Windows 7 64-bit 0x1E & 0xBE

3278 Views 5 Replies 2 Participants Last post by Jonathan_King, Mar 12, 2011

Nessquick

Discussion Starter · Mar 11, 2011

Hi, I have a strange issue with BSOD that occur only after my first boot up of the day, it shows either of the 2 but more of the first
-0x0000001E
-0x000000BE ( An attempt was made to write to read-only memory )

After this appears i turn off my computer and do a quick power cycle and it boots up just fine. However it is annoying and I am afraid it might do further damage in the future. I've checked the error on many debugging programs and just don't understand or can find a solution. Bugcheck Analysis gives me this after both BSOD's: "Probably caused by : ntkrnlmp.exe" I also have done memory diagnostics and memtest86+ and get no errors. Really Frustrated! If anyone could please help it'd be greatly appreciated, maybe there is something i am over looking or just don't know enough of. here are my crash dump logs and system specs. Thank you

Phenom™II X4 970 Black Edition
Asetek 510LC Liquid Cooling System 120MM Radiator & Fan
640GB SATA-III 6.0Gb/s 64MB Cache 7200RPM HDD
4GB (2GBx2) DDR3/1600MHz Dual Channel Memory Module (A-Data Gaming Series)
Asus M4A87TD EVO AMD 870 Chipset
750 Watts - Corsair CMPSU-750TX 80 Plus Power Supply
AMD Radeon HD 6950 2GB GDDR5 16X PCIe Video Card

Save

Status: Not open for further replies.

1 - 6 of 6 Posts

Jonathan_King

· #2 · Mar 11, 2011

Hello,

Try running Memtest86 immediately upon booting up for the first time in the morning.

...Summary of the dumps:

Code:

[font=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri Mar 11 12:52:22.032 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:04.687
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4237e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xBE
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xBE_nt!_??_::FNODOBFM::_string_+4237e
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Thu Mar 10 12:39:14.607 2011 (UTC - 5:00)
System Uptime: 0 days 0:03:25.261
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+381ba )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!_??_::NNGAKEGL::_string_+381ba
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

See less See more

Save

Nessquick

Discussion Starter · #3 · Mar 12, 2011

I ran memtest this morning and what do you know, errors galore. does this mean certain bad Ram? could it be the mobo? just wanna make sure that I RMA the right component in this issue, Thanks for the help!

Save

Jonathan_King

· #4 · Mar 12, 2011

I suppose one can never be 100% sure; as soon as I assured you it was the RAM, the Powers That Be would all join forces and set out to prove me wrong.

I will just give my advice that if you start out by replacing the RAM, you shouldn't regret it.

Save

Nessquick

Discussion Starter · #5 · Mar 12, 2011

haha ya i understand but i really think it is the RAM, off to replacing it.... this should be fun.. anyways thanks a lot for your help and quick responses!

Save