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

Pcfreak123 · 19 Jan 2015

doctore said:

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 · 19 Jan 2015

Arc said:

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.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
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 · 20 Jan 2015

Pcfreak123 said:

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.

Pcfreak123 said:

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 · 21 Jan 2015

Arc said:

Pcfreak123 said:

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.

Pcfreak123 said:

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 · 21 Jan 2015

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 · 21 Jan 2015

Pcfreak123 said:

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 · 22 Jan 2015

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 · 22 Jan 2015

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 · 22 Jan 2015

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 · 23 Jan 2015

Pcfreak123 said:

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.

Pcfreak123 said:

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.