Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Memory Related BSODs?
New Posts  All Forums:Forum Nav:

Memory Related BSODs?

post #1 of 5
Thread Starter 
Alright Folks.. woke up this morning to one of those "windows has recovered from an unexpected shutdown.." messages. I went into the event viewer and found it said something about kernel power, not exactly sure.. i'm away from my PC atm.

So then.. I tried proceeding with my business, (installing my new steam purchases) and then BSOD. Memory_Management

Went into the BIOS, adjust the DRAM frequency from auto to 1333MHz..

7 boots up.. then PAGE_FAULT_IN_NONPAGED_AREA BSOD..

Went back into the BIOS, set it back to Auto.. and then it was "okay" for there on.

Little while ago, I began a memtest 86 run, how many passes should i do? I'm almost at 10 as i'm typing this thread, and hope to do at least 20 by the time i wake up tomorrow.

Now heres the odd part. All christmas break.. I've been happily gaming and using my PC.. I put a LOT of time into Fallout New Vegas with no hitches.

However.. I have seen these BSODs before. when I had a faulty drive these BSODs appeared as well, among other hard drive related ones too.. Replaced the drive and i was fine.

Then there was an isolated incident, where i was just browsing the internet on opera,steam, and aim.. my system began to be REALLY irresponsive.. so i turned it off..

It boots up, but then the resolution is screwed up, running at 800x600 and theres green lines across my screen.

I go into the device manager, windows reports that it wasn't working correctly, and gave me the code 43.

It then proceeds to BSOD, Memory Management Error, something along those lines. It restarts itself and the resolution is fine, no green lines and windows device manger reports it is working fine.

That incident was two weeks ago.I didn't have any BSODs/Problems until this morning.

Now I'm not sure if this is software related, so i uninstalled some software i recently installed in the past 24 hours, MSI Afterburner / Kombuster.. 3D Mark Vantage.. and i believe one other.

So whats the ideal amount of passes on Memtest 86 with both of my dimms inserted, for it to rule it out as a memory problem?

Also, does Prime95 test the stability of your memory? If so.. I'll run that too, and approximately how long should i run it?

Would it be safe running it with a stock cooler as well?

Could a video driver cause this? If so, I'll try upgrading to a newer driver.

I hope someone can shed some light upon this, sorry for the long post too lol

Your feedback is greatly appreciated.
post #2 of 5
Thread Starter 
Bump. 31 passes of memtest86 and no errors.

I ran WhoCrashed, and it said that Memory_Management and PAGE_FAULT_IN_NONPAGED_AREA BSODs were related to a Kernel or Driver problem.. thing is.. it doesn't tell me what driver(s) that could be causing the crash.

Can anyone shed some light upon this?
post #3 of 5
Thread Starter 
Looks like it did again.. woke up in the middle of the night (12AM) and i got that same windows has recovered from an unexpected shutdown... didn't check the event log yet... if someone could give me a hand.. i'd really appreciate it at this point
post #4 of 5
whats the number in the stop codes below the wall of text? that is quite important.

if you have manually set voltages, your VTT may be too low if your RAM is already underclocked and timings are loosened.
The 775 Legend
(13 items)
 
  
CPUMotherboardGraphicsRAM
E8600 @ 5.8 -- 1.736v Rampage Formula! GTX550ti Vmod! OCZ D9's @ 1200+ cas 5 
OSMonitorPowerCase
XPEEEEEEEEEEEEEEEEEEEEEEE XGA 800x600 TR2-RX 850W Neoprene sheet 
  hide details  
Reply
The 775 Legend
(13 items)
 
  
CPUMotherboardGraphicsRAM
E8600 @ 5.8 -- 1.736v Rampage Formula! GTX550ti Vmod! OCZ D9's @ 1200+ cas 5 
OSMonitorPowerCase
XPEEEEEEEEEEEEEEEEEEEEEEE XGA 800x600 TR2-RX 850W Neoprene sheet 
  hide details  
Reply
post #5 of 5
Thread Starter 
Thanks man for posting But no, i have not touched my voltages in the BIOs, everything is set to Auto and default, but heres the crash dump from WhoCrashed.


On Mon 1/3/2011 3:44:13 AM GMT your computer crashed
crash dump file: C:\\Windows\\Minidump\\010211-16036-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xE3 (0xFFFFFA8004D2FE90, 0xFFFFFA800424D660, 0x0, 0x2)
Error: RESOURCE_NOT_OWNED
file path: C:\\Windows\\system32\
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread tried to release a resource it did not own.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 1/3/2011 3:44:13 AM GMT your computer crashed
crash dump file: C:\\Windows\\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xB7A3)
Bugcheck code: 0xE3 (0xFFFFFA8004D2FE90, 0xFFFFFA800424D660, 0x0, 0x2)
Error: RESOURCE_NOT_OWNED
file path: C:\\Windows\\system32\\drivers\
tfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a thread tried to release a resource it did not own.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 1/1/2011 2:32:00 PM GMT your computer crashed
crash dump file: C:\\Windows\\Minidump\\010111-17050-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFA80325743AB, 0x0, 0xFFFFF80002EDD53B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\\Windows\\system32\
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 1/1/2011 2:15:43 PM GMT your computer crashed
crash dump file: C:\\Windows\\Minidump\\010111-23290-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x5003, 0xFFFFF780C0000000, 0x4554, 0xFFFFF9800DF10009)
Error: MEMORY_MANAGEMENT
file path: C:\\Windows\\system32\
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 1/1/2011 10:34:32 AM GMT your computer crashed
crash dump file: C:\\Windows\\Minidump\\010111-20935-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800210E250, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\\Windows\\system32\
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 12/12/2010 8:43:26 PM GMT your computer crashed
crash dump file: C:\\Windows\\Minidump\\121210-13712-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800210EB20, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\\Windows\\system32\
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

What is this ntoskrnl.exe? I'm guessing its the culprit.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Memory Related BSODs?