BSOD often at Desktop with PAGE_FAULT_IN_NONPAGED_AREA

[nanogenesis]

I have had the same hardware since the past 8 months. Recently I received a replacement of my 560Ti from RMA, and this is the only new piece of hardware in my system. One day I took apart my PC for cleaning. After putting it back, windows did not boot and I had to reformat. After reformatting, I started getting BSODs at the desktop just after 4-5 minutes.

At this point I googled for a solution, the most recommended was memtest. I ran it for 15hrs and 8 passes with no errors. After this test I tried to boot into Windows and in the short time window I was able to schedule a chkdsk on C:, it completed successfully. But the BSODs did not disappear.

I thought of reformatting, and after completion, when I reached the desktop, I got a BSOD with IRQL_NOT_LESS_OR_EQUAL. Because it was just after a fresh format, I wasn't able to collect the dmp file associated with this BSOD.

At this point, I was in rage. I removed 3 sticks of ram, and the new 560Ti from my system. I also replaced the SATA cable of my HDD.

After this I reformatted and have been able to spend a significant amount of time in Windows without any errors.

Right now I've only installed some of my motherboard drivers, and Waterfox for browsing. I haven't even installed video card drivers yet. I have a USB modem so installed the appropriate software to be able to run it.

My system was overclocked prior to this, and after the first BSOD I dialed back the settings. My system specs are as follows:
AMD Phenom II x4 955 Black Edition (Aftermarket CPU cooler applied)
MSI N560GTX-Ti Twin Frozr II/OC x2 SLI
ASUS M5A99X EVO
4x2Gb Kingston DDR3 1333Mhz
1Tb Seagate 7200RPM 32Mb Cache
Corsair TX850V2

All the components I disconnected are still disconnected. I'm attaching the dmp files I collected together in a zip file. I will reconnect them once I can pinpoint the problem with my setup.

View attachment 235065

Other than PAGE_FAULT_IN_NONPAGED_AREA I saw another error, MEMORY_MANAGEMENT

Also, I have Windows 7 Ultimate x64

Thank you.

 

[Arc]

Welcome aboard, nanogenesis.

All your latest crashes say that those are stop 0x50, with a probable cause of memory corruption. Whereas it may happen for some other reasons like Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS etc. (Source: Carrona.org)

Befoer blaming the memory (RAM) as the main cause, let us do two more things.

1. Enable Driver verifier: Driver Verifier - Enable and Disable
2. Upload the MSINFO.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[nanogenesis]

In order to recreate the problem on my fresh installation of Windows, I believe I will have to plug in all the components. I have done so and attached the generated ms32info.
View attachment 235091

I shall run driver verifier and report back my findings.

Right now due to work, I am limited to only 12hrs of running the PC at a stretch. If there are no errors while running for a total of 48hrs, can I be assured the issue is no more?

 

[Arc]

That's good. Will check the msinfo file comparing with the subsequent dumps.

 

[nanogenesis]

I have ran for a significant amount of time, with no BSODs. driververifier is still running.
The problem seems to have been resolved, but the fact that it arised puts me in tension.

 

[Arc]

You may disable driver verifier now.

If there are subsequent crashes, probably we know where to search for the reason behind those.

 

[nanogenesis]

Thank you, if I have any sort of problems again, I know where to ask