Solved BSOD's on WakeUp for Randomly - Bug Check Code 0x00000050

[Chap9702]

Hello,

I have a custom built mid range gaming PC. I have overclocked her and run stability tests which have all passed. I sometimes get random BSOD's when closing chrome windows but mostly I get them when the PC is waking up from sleep. It BSOD's and then runs perfectly fine after restarting, so I can't really pinpoint the cause. It never BSOD's under load, running stress tests or while gaming so it is more of an inconvenience.

I assumed it was something to do with the overclock so in an effort find the cause I reset the PC to all stock settings in the BIOS and it has been running without issue for 2 days. Today it just did a BSOD again when waking up.

I have done some research and read the various forums here without being able to determine the cause. If you can take a look at the file I uploaded and give me some idea's it would be very much appreciated. Please let me know if you need more information.

The last BSOD was caused by "PAGE_FAULT_IN_NONPAGED_AREA - Bug Check Code 0x00000050"

The previous two BSOD's were two days apart (while still overclocked)
1. "SYSTEM_SERVICE_EXCEPTION - Bug Check Code 0x0000003b"
2. "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - Bug Check Code 0x0000007e"

Thanks,
Ryan

 

[essenbe]

Hello Chap, I've looked at your dump files and found this

BugCheck 50, {fffffa80635d2ea8, 0, fffff800023f83e0, 2}
 
Could not read faulting driver name
Probably caused by : [COLOR=red]memory_corruption[/COLOR] ( nt!MiGetWorkingSetInfo+2b0 )

lmvm avgidsdrivera
start             end                 module name
fffff880`038ff000 fffff880`03942000   avgidsdrivera T (no symbols)           
    Loaded symbol image file: avgidsdrivera.sys
    Image path: avgidsdrivera.sys
    Image name: avgidsdrivera.sys
    Timestamp:        Tue Jun 17 09:06:18 2014 (53A04B5A)
    CheckSum:         0003FA27
    ImageSize:        00043000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

AVG IDS Application Activity Monitor Driver

First I'd like you to disable that part of AVG. if that does not help, please uninstall it and install MSE.

The Memory Corruption is what I'm most concerned about. If you have faulty ram or dim slots, none of the dump files that we go by are reliable or accurate.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask​

 

[Chap9702]

Thanks for the reply I am uninstalling AVG with REVO and I have downloaded MSE. I already have MEMTEST and I have run it before successfully but perhaps not for that many runs so I will do that asap.

I'll let you know how it goes.

 

[essenbe]

Chap, I would guess it will take 9-10 hours to complete 8 passes, and yes I know what a pain it is. I've been there myself many times. Be glad you're not like me and have 16 GB of ram. The only reason I asked you to run it so early in the diagnosis is because of the dump files blaming memory corruption. Usually, if you have a memory fault, the computer will blame whatever driver is most in use at the time. That's why, the ram is so important. If the ram is not right, every dump file will be wrong. Dump files are what we use to debug, so it helps if they give us good info.

 

[Chap9702]

Hey Essenbe,

So just finished the 8 Memtest runs and no errors came up. AVG is uninstalled and I'me running MSE at the moment. No BSOD's since the original post, any idea of what to try next?

 

[essenbe]

Next open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

After you get through with that, Make a restore point first.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

What is Driver Verifier:
It puts stress on the drivers, and therefore it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How we know that DV is enabled:
It will make the system bit slow and sluggish.

   Warning

Before enabling DV, make it sure that you have created a restore point.
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.

 

[Chap9702]

Okay so I ran the scannow twice with one reboot and it came up with no integrity violations. I ran the verifier but windows BSODed immediately and I had to disable it in safe mode. It did create a dump file which I will attach here. Let me know what information you need next. Thanks for the help guys!

 

[essenbe]

As I am sure you realize, this is a trial and error system, but the best we have. We will just keep trying different things until we are at a point we can see what the real problem is. In this dump file it lists your Graphics card

lmvm nvlddmkm
start             end                 module name
fffff880`05c44000 fffff880`068d2000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 12:42:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update your graphics driver. The link I am going to give you will tell you where to download it from, how to uninstall your current drivers and how to install the new ones. Just download the new drivers first. I know it will look complicated, but it is really simple and the way I do mine every time. It will hopefully give you a very clean install and not install anything you don't need.
http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html

 

[Chap9702]

Okay ran it again just to see and this time it did start, got logged in and then Driver Verifier caught something. I'm attaching the new file for you guys to look at.

 

[Chap9702]

Okay I disabled the gdrv.sys driver and ran the verifier again. Windows started and is running with the verifier as I am typing this. I will go ahead and update GPU driver while I'm waiting and continue to run the verifier. If it BSODs I will let you know. Please let me know if you see anything else in the last file I uploaded, thanks again for helping out.

 

[essenbe]

That's an improvement. Good job. If you haven't started you may wait until we turn verifier off before installing the new GPU drivers. I'm not sure what effect verifier will have. If you've already done it, no problem. We'll just see what happens. Your last dump, you already have taken care of. You can uninstall it if you want to.

lmvm gdrv
start             end                 module name
fffff880`0c37f000 fffff880`0c388000   gdrv     T (no symbols)           
    Loaded symbol image file: gdrv.sys
    Image path: \??\C:\Windows\gdrv.sys
    Image name: gdrv.sys
    Timestamp:        Thu Mar 12 22:22:29 2009 (49B9D175)
    CheckSum:         000105CE
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The Gigabyte Easy Saver - mobo power utility driver

 

[Chap9702]

All right, GPU is updated and gigabyte easy saver is gone. I am restarting the verifier now at 9:05pm, we'll see how it goes.

 

[essenbe]

Good luck. Let me know.

 

[Chap9702]

Hey I have had no further BSOD's as of yet so I am going to shut down the verifier. I'll let you know if anything comes up again. Thanks for your help!

 

[essenbe]

Good luck. Just let us know if further problems come up. We're open 24/7.