BSOD - 'Page fault in nonpaged area' - while surfing on chrome

Lerdeif · 13 Aug 2014

Hello

I started getting Blue screen of Death all of a sudden the last week. It seem to happen when I'm surfing using Chrome (Has happened 4-5 times so far).

I dont know if it's connected, but my computer also seem to be slowing down and freezing alot lately (without BSOD) forcing me to reboot. This often happens right after I've turned it on, but not always.

I've even experienced it freezing in the 'startup-menu' after a reboot (where you're asked if you want to start windows in safe-mode or normally)

I hope you can help me (at least with the BSOD)- and I've uploaded the file from option one in your BSOD posting intruction guide and attached it to this post.

Best regards,
Mikkel from Denmark

Arc · 14 Aug 2014

Hi Lerdeif.

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 start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, 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.
_________________________________________

Code:

BugCheck 50, {fffff8800e375450, 1, fffff800032b2f32, 2}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

Lerdeif · 16 Aug 2014

Hi Arc - and thanks for the quick response

I've tested my RAM as instructed, but no errors were found after running 8 passes over 20 hours.

Then I ran the Verifier. During 24 hours I didn't get any BSOD's, but after two I got a black screen which resulted in my computer booting itself. I've uploaded/attached a new .zip with the .dmp from this crash.

(I started thinking, and please correct me if I'm wrong as I'm very far from being a computer-wiz, but could the problem be related to my harddisk - and perhaps lack of free space on it? Some time ago my computer started slowing down alot (at that time I had only 125 GB out of a 1000 free). It should be noted that it slowed down and froze some times, but never gave me any BSOD's back then. I then deleted some stuff and doubled the amount of free space, which seemed to solve the problem. Atm I have around 200 GB free space, so I was wondering if some windows-setting might demand more than that, and cause the issues?)

- Mikkel

tehsaccade · 16 Aug 2014

Guys - if you check out my problem, and the problem of two other guys here - lots of people are getting BSOD's from chrome while streaming, which persist even when chrome is not in use.

I'm finding it hard to believe that hardware failure is going to be the cause - I think it is some invasive google action that windows haven't caught up with yet.

tehsaccade · 16 Aug 2014

Lerdeif - please will you post the reports from option 2 for me to examine..?

If yours have the same reads as me and the other guys - then it may lead somewhere.

It may be also the same that your network drivers are in need of repair, and that windows index and perhaps USN journal and file allocation table of your HDD might need looking at...

Arc · 16 Aug 2014

The BSOD is DV enabled for sure.

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

Still it is accusing the display hardware as the probable cause.

Code:

BugCheck 7A, {fffff6fc4007ebf0, ffffffffc00000b5, 20737a860, fffff8800fd7eb50}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : hardware ( nvlddmkm+90fb50 )

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

If you have any overclocking, set everything to stock settings.

Then Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the result.

Lerdeif · 16 Aug 2014

@tehsaccade - I've followed option 2 and attached the .zip as you requested. (I was also streaming on chrome (while playing Pro Cycling Manager 2014 in windowed mode at the same time) at least one of the times I got BSOD. But other times surfing on chrome without playing any games seems to be enough).

@Arc - I'm dont have any overclocking. I ran the Furmark stress test for 40 minutes and reached 92 max degress. No 'artifacts' or crashes though.

- Mikkel

Arc · 17 Aug 2014

40 minutes are long enough.

Now you may do one more thing. Uninstall your display driver using DDU and install a driver version that previously worked good for you.