BSOD Memory_Management & Page_Fault_In_Nonpaged_Area

[tomato500]

Hello everyone,

I made my own PC (not too long ago, probably March) with Windows 7 Professional 64 bits. I've recently installed some games (SimCity, Need for Speed: Most Wanted, Minecraft) and sometimes it's been crashing occasionally while I've been playing (oftentimes just an application crash, occasionally a BSOD). The bluescreens kept becoming more and more common, and sometimes it happens while I do other stuff (i.e. browsing web, system idling). It's getting annoying and the bluescreens alternate between MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA. Using BlueScreenViewer, I can see that it is coming from the files "ntoskrnl.exe" and "fltmgr.sys". There has been, I'd say, probably around 6 or 7 crashes, but those minidump files have been deleted with Disk Cleanup, although I know they are the same types of BSODS. Please help if you can! I am getting annoyed with this! Can I not just play my games and use the internet? Is that too much to ask?

 

[tomato500]

Oh yeah, almost forgot about this.

View attachment 263528

 

[Arc]

Your crash dumps are not showing any finite probable cause for the BSODs.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it comes clean, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

BTW, which antivirus do you use? Scan the system for possible virus infection, too.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

________________________________________________________________________________
BSOD ANALYSIS:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[URL="http://www.carrona.org/bsodindx.html#0x00000050"]BugCheck 50[/URL], {fffff683fb7e91a0, 0, fffff80002e52607, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+11b )

Followup: MachineOwner
--------------------------------------------------------------------------------------------------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[URL="http://www.carrona.org/bsodindx.html#0x0000001A"]BugCheck 1A[/URL], {41287, 18, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+454f5 )

Followup: MachineOwner
---------

 

[tomato500]

OK Arc, I will try your recommendation.
My antivirus is Microsoft Security Essentials, and I had already scanned it after the BSODs showed up.
I don't really want to run Norton or anything, because I already have it on my other PCs running Windows XP and it runs VERY slow, especially when it runs background scans.
Thanks! I will try Driver Verifier and Memtest86+ and report back.

 

[Arc]

Worried about TDSSKiller?

It will not install anything, will perform a standalone scan only. Also the scan is needed, as Windows Defender Offline is also needed. MSE or any other AV does not csan some areas like BIOS, and you need to scan it.

 

[tomato500]

TDSSKiller says that there is no threats on the PC, nor does Windows Defender Offline. Driver Verifier did not cause a crash.
However, I tried a version of Memtest that my IT friend recommended (actually runs in Windows, I don't have any blank CD/DVDs or spare USB drives and I don't have a floppy disk drive) and it reported many, many errors, saying that my RAM could not store data accurately. So I am going to switch out the RAM and exchange it. I hope that is the end of my problems. Well, I'm fine with reinstalling Windows since I have almost nothing on the machine except for the games.

 

[Arc]

Yeah a failing physical memory was the prime suspect here. Wish it will work good with the replacement RAM.
Let us know how it works after the change is done.

A request .... share the link of the version of the memtest that runs within windows please?

 

[tomato500]

Yeah a failing physical memory was the prime suspect here. Wish it will work good with the replacement RAM.
Let us know how it works after the change is done.

A request .... share the link of the version of the memtest that runs within windows please?

So I just installed the new RAM, and it seems to be working just fine right now.
Oh, and here's the Memtest that runs within Windows:

http://hcidesign.com/memtest/

 

[Arc]

First of all, thanks for the link I hope it will help many other people.

Now let the computer run for a few days. Observe how it is doing. Update the thread with the results

 

[tomato500]

Hey, I ran Memtest again on the PC (with the new replacement RAM) overnight and it detected 535 errors on the RAM. Crap. Have I gotten another faulty RAM or is it something else?

 

[Arc]

Follow the Part 3: If You Have Errors: of http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

It will make the situation clear.