BSOD every few days on wake up. Help translate dmp files.

[Pcfreak123]

I am getting random BSODs upon wakeup of my PC every few days and I am not exactly to sure what is causing them. I have went through my dmp files but I need help translating what is exactly causing them.

Need the help of you pros please.

 

[koolkat77]

Please test ram first.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Memtest should be done overnight.

 

[Pcfreak123]

Please test ram first.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Memtest should be done overnight.

Hi Kat,

So I did everything you told me and the memory has passed with no errors and I ran it for at least 10 passes. Could this issue be pointing to something else from what you see in the dumps?

Also I was wondering...is it possible for memory to only have/generate errors when coming out of sleep only? Does this make it faulty or why is it only after sleep? If it had something wrong wouldn't programs/games and other things not work smoothly?

 

[Pcfreak123]

Okay so Idk what is going on....I just bsod 2 more times today with PAGE_FAULT_IN_NONPAGED_AREA - ntoskrnl.exe 0x00000050 and SYSTEM_SERVICE_EXCEPTION - ntoskrnl.exe 0x0000003b.

Any ideas what could be causing all these errors?

 

[Pcfreak123]

Here are my updated reports. Please take a look. This is making me lose my mind literally. I have been searching through these forums like a mad man for a remedy.

 

[Pcfreak123]

I don't get it ....does anyone know something ? Is this just a common issue with windows 7? Should a computer not sleep? How about maybe because it is in hybrid mode?

 

[Arc]

The BSODs are pointing to memory error, consistently. If the RAM is free from errors, it may be that some drivers are passing bad info to the memory.

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.

 

[Pcfreak123]

The BSODs are pointing to memory error, consistently. If the RAM is free from errors, it may be that some drivers are passing bad info to the memory.

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.

Archie,

Thank you for the response...Driver Verifier has been running and nothing yet. I will continue to let it run...but while it does I was wondering if you knew....why is that only out of sleep this is happening? Can memory cause errors only out of sleep? Or does a driver cause errors out of sleep as well? It is just boggling my mind why this occurs coming out of sleep?

 

[Arc]

During sleep, there are power transitions. Some devices go inactive, some drivers goes to rest.

If is very often seen that there are various BSOD issues appear during sleep. Stop 0x9F and Stop 0xF4 are very common during sleep. But, your bugchecks are not very common.

What you may try is to put the computer to sleep when DV is enabled. There is a great chance that it will BSOD and will point out a failing driver there.

One more set of things may cause this sleep-wakeup related BSOD is the startup items. And you hav a few there, and out of them some are very vulnerable (like killer network manager). Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Try these two ... see how it goes. Let us know. Some further troubleshooting may be needed depending on the situation.

 

[doctore]

It could well be a graphic driver. Did you change video card or update drivers lately? When did this start happening?

 

[Pcfreak123]

It could well be a graphic driver. Did you change video card or update drivers lately? When did this start happening?

This pretty much has been occurring since the build took place about a month ago. But I literally have went through and made sure the proper graphics driver was in place for the integrated one and the stand alone one.

 

[Pcfreak123]

During sleep, there are power transitions. Some devices go inactive, some drivers goes to rest.

If is very often seen that there are various BSOD issues appear during sleep. Stop 0x9F and Stop 0xF4 are very common during sleep. But, your bugchecks are not very common.

What you may try is to put the computer to sleep when DV is enabled. There is a great chance that it will BSOD and will point out a failing driver there.

One more set of things may cause this sleep-wakeup related BSOD is the startup items. And you hav a few there, and out of them some are very vulnerable (like killer network manager). Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Try these two ... see how it goes. Let us know. Some further troubleshooting may be needed depending on the situation.

I am running DV but it has not BSOD out of sleep yet, I suppose I will keep trying. When it happens it's usually every few days sometimes everyday. My errors you say are not the common ones that usually happen when waking up but how come they relate to the memory? Can the start up issue you stated and passing bad info to the drivers cause such errors that I am having (memory errors). Just wondering.

 

[Arc]

Can the start up issue you stated and passing bad info to the drivers cause such errors that I am having (memory errors). Just wondering.

Yes, obviously.

My errors you say are not the common ones that usually happen when waking up but how come they relate to the memory?

Yes, those are not very common bugchecks for sleep issue. But they are mostly memory related errors.

Let us know how the computer behaves during sleep - wake up after removing the startup items.

 

[Pcfreak123]

Can the start up issue you stated and passing bad info to the drivers cause such errors that I am having (memory errors). Just wondering.

Yes, obviously.

My errors you say are not the common ones that usually happen when waking up but how come they relate to the memory?

Yes, those are not very common bugchecks for sleep issue. But they are mostly memory related errors.

Let us know how the computer behaves during sleep - wake up after removing the startup items.

I have done everything you told me and today when I woke up and went to wake up the computer it blue screened again.

It mentions BugCheck 1E (KMODE_EXCEPTION_NOT_HANDLED) along with process name being nvbackend.exe and Module Name to be fileinfo.sys.

I attached the new reports as 1-21 being the most recent (22651-01.dmp). Gosh I want to figure this out so bad.

 

[Pcfreak123]

When I reinstalled drivers nvbackend (geforce experience) was in startup (msconfig) . I just disabled it again and made sure start up is clear again like you said. I don't know if that's what is causing it because this is first time it was pertaining to nvbackend. But in my previous errors I have seen fileinfo.sys before. So I guess it's a waiting game again will see. Something must be generating these weird BSODs. Just insane.

 

[Arc]

When I reinstalled drivers nvbackend (geforce experience) was in startup (msconfig) . I just disabled it again and made sure start up is clear again like you said. I don't know if that's what is causing it because this is first time it was pertaining to nvbackend. But in my previous errors I have seen fileinfo.sys before. So I guess it's a waiting game again will see. Something must be generating these weird BSODs. Just insane.

OK, let us wait and see.

 

[Pcfreak123]

Arc,

As we wait..I have a couple questions real quick...this usually happens every 2-3 days...how is a driver going "bad" on wake up or passing such bad info on a wake-up if it has already been running? It is just keeping me up all night.

 

[Arc]

When a computer goes to sleep or hibernate, there is a power transition, from working state to sleep/hibernation state. During sleep/hibernation, devices (mostly the PnP devices; sometimes all the devices depending on the sleep/hibernation settings) go inactive.

The devices are configured by some device drivers. Now, some device drivers may fail to react (and it fails very often) with the power state change within the due time (a very small quantum of time). Here arises the problem. That particular device remains in a different power state than the entire computer. So the conflict arises, and the BSOD causes.

The startup items also play a role here. During wake-up (as during startup) some of them try to be active before the computer itself. That also causes the issues.

Clear now? If not, I will try to explain it more elaborately. Good questions are always welcome.

 

[Pcfreak123]

That was pretty clear, thank you! If you want to elaborate more I am open to it. I like learning more and more . So such power transitions causes memory errors and causes ntoskrnl.exe to be the fault alongside another module if any?

Also since this occurs is the only work around to turn off such start-up items? Does this still allow them (the drivers) to load if they are disabled in start up/services (how I have them now)? I have read some people do not let their computer sleep for this reason, but I definitely would like mine to sleep so its quiet and sleeping when I am.

 

[Arc]

So such power transitions causes memory errors and causes ntoskrnl.exe to be the fault alongside another module if any?

ntoskrnl.exe is never failing. Rather it is the kernel on which the crash took place. When the crash dump recording mechanism fails to detect any failing module, it blames the kernel itself; which is not the true situation.

Also since this occurs is the only work around to turn off such start-up items? Does this still allow them (the drivers) to load if they are disabled in start up/services (how I have them now)? I have read some people do not let their computer sleep for this reason, but I definitely would like mine to sleep so its quiet and sleeping when I am.

Some people who dont let their computer to go to sleep are all desktop users. Portable computers like laptops, notebooks and netbooks run on stored battery power. So the conservation of power is very urgent for those computers. But a desktop runs from direct power, so saving (and so sleep/hibernate) is not any must for it.

All the programs are installed in your computer. You will not loss any of them by disabling startup items. Whenever you need them, go to Start> All Programs and call them. But this rule has three limitations.

Touchpad driver for laptops
Antivirus
Any other special program used for customization, like rainmeter.
​

Besides all discussed above, some other driver (either auto or manual) also may cause BSODs during sleep. In that case we may find them out and take the proper actions for them.