BSOD when waking laptop up from hibernate

[Buddyz]

Hello everyone,

With help from this forum, I fixed very frustrating BSOD issues while waking up the laptop from hibernate a while ago.
Unfortunately the issue is back now, with a different error. I did not get the chance to write down the code, but I have the dumpfile, which I have included in the attachment of this message.

If you need more information, please let me know.
Thank you very much for your help again!

 

[axe0]

There is a problem, you've used Ccleaner about 6 minutes after the crash what makes that we can't find out what exactly happened in the logs before the crash.
I recommend that you temporary remove Ccleaner to prevent this from happening while troubleshooting.
Although it isn't a big problem, the deleted logs could have been useful.

Event[0]:
  Log Name: System
  Source: Microsoft-Windows-Eventlog
  Date: 2016-04-18T16:03:26.476
  Event ID: 104
  Task: Logboek wissen
  Level: Informatie
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-3271328833-2471730391-1089612805-1001
  User Name: MADlab\MAD
  Computer: MADlab
  Description: 
Logboekbestand System is gewist.

Please make sure that all software that ASUS provides is removed just in case it gives any trouble.

Diagnostic Test

DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.


Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.


Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.


If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[Buddyz]

Hi,

Thanks for your reply.
I've turned off CCleaner's log cleaning, and today a new BSoD occurred, with the "DRIVER_POWER_STATE_FAILURE".
The dumpfile is attached to this post.

Thanks again!

 

[axe0]

Only a generic power problem is saved, but nothing about a BSOD.

From experience with the 0x9F it is that it is often caused by USB drivers/devices, remove all USB devices and see how it goes.

 

[Buddyz]

Hi there,

I had another one on my laptop today. This time it should've saved the dumpfile.
I've included the logs in the attachment.

Thanks again in advance!

 

[axe0]

You've created a new thread for the issue, please continue there.

 

[Buddyz]

Hi,

Assuming you're referring to THIS thread: these are two different systems, with two different operating systems. One is a laptop (this thread), the other one is my desktop PC.

 

[axe0]

Alright,

Again there is no dump file saved, what was the BSOD bugcheck?

 

[Buddyz]

Hello,

Oh, that is very weird then. What do you mean with bugcheck? The error it gave on the blue screen?
I did let it finish collecting all information, so I wonder why it did not create a dumpfile.
Next time I'll double-check whether there's a new dumpfile added, before posting. Sorry about that.

 

[axe0]

The error code the BSOD gives has various names, lately I'm calling it bugcheck

A BSOD is also known by many other names:
- Blue Screen of Death (hence the BSOD acronym)
- STOP error
- Crash dump
- Memory dump
- Bug Check
- BCCode

There are some reasons why a dump wasn't saved,

• memory corruption, the system checks the memory before it creates a dump of it so if the memory is too heavily corrupted no dump can be created,
• hard drive corruption, if the hard drive is also too heavily damaged in any sort of ways the dump cannot be saved
• improper startup & recovery settings,
• system corruption,
• no page file present or not large enough, it must be larger than the physical amount of memory,
• register settings improper.

Is there also no dump present in the %systemroot% directory?

 

[Buddyz]

Is there also no dump present in the %systemroot% directory?

There is, but it's an older one. I'm not sure if it's the one we're looking for.
I've included it in the attachment.

 

[axe0]

In the %systemroot% there is normally a memory.dmp present after a BSOD system crash which takes up a few 100MBs to a GB, given the size of your upload it isn't the one I meant.

 

[Buddyz]

Hi again,

Today I had a BSoD again. Fortunately a dumpfile was created this time.
I've included it in the attachment.

Thanks again!

 

[axe0]

Is there any reason why Driver Verifier is enabled?

Perhaps this is in either of your previous threads explained, but why is the Nvidia driver not from ASUS?

3: kd> !irp ffffe001`550eaca0
Irp is active with 8 stacks 4 is current (= 0xffffe001550eae48)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0 10 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe0014fa7c060 00000000 fffff80226b0e24c-ffffd001efb667e0 Success Error Cancel pending
	       \Driver\pci	nt!ViFilterGenericCompletionRoutine
			Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e0 ffffe0015334a040 00000000 fffff80152831590-ffffd001efb66860 Success Error Cancel 
	       \DRIVER\VERIFIER_FILTER	dxgkrnl!DpiFdoPowerCompletionRoutine
			Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e0 ffffe00153488040 00000000 fffff80226b0e24c-ffffd001efb66b50 Success Error Cancel 
	      *** WARNING: Unable to verify timestamp for [COLOR="#FF0000"]nvlddmkm[/COLOR].sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 \Driver\nvlddmkm	nt!ViFilterGenericCompletionRoutine
			Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe00153487de0 00000000 fffff8022659d75c-ffffe001550f9f08 Success Error Cancel pending
	       \DRIVER\VERIFIER_FILTER	nt!PopRequestCompletion
			Args: 00000000 00000001 00000001 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffe001550f9f08    

			Args: 00000000 00000000 00000000 00000000

Irp Extension present at 0xffffe001550eafb0:

3: kd> !devobj ffffe00153487de0
Device object (ffffe00153487de0) is for:
 InfoMask field not found for _OBJECT_HEADER at ffffe00153487db0
 \DRIVER\VERIFIER_FILTER DriverObject ffffe0014fa9e2b0
Current Irp 00000000 RefCount 0 Type 00000023 Flags 00002004
DevExt ffffe00153487f30 DevObjExt ffffe00153487f98 
ExtensionFlags (0xc0000000)  DOE_BOTTOM_OF_FDO_STACK, DOE_DESIGNATED_FDO
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) ffffe00153488040 \Driver\[COLOR="#FF0000"]nvlddmkm[/COLOR]
Device queue is not busy.

3: kd> !devobj ffffe0015334a040
Device object (ffffe0015334a040) is for:
 InfoMask field not found for _OBJECT_HEADER at ffffe0015334a010
 \DRIVER\VERIFIER_FILTER DriverObject ffffe0014fa9e2b0
Current Irp 00000000 RefCount 0 Type 00000032 Flags 00000000
DevExt ffffe0015334a190 DevObjExt ffffe0015334a1f8 
ExtensionFlags (0xd0000000)  DOE_BOTTOM_OF_FDO_STACK, DOE_DESIGNATED_FDO
                             Unknown flags 0x10000000
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffe00153488040 \Driver\[COLOR="#FF0000"]nvlddmkm[/COLOR]
AttachedTo (Lower) ffffe0014fa7c820 \Driver\ACPI
Device queue is not busy.

3: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff801`52a18000 fffff801`53734000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR="#FF0000"]Fri May 20 03:25:49 2016[/COLOR] (573E679D)
    CheckSum:         00CD7F80
    ImageSize:        00D1C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.​

How to fill in your system specs:

 

[Buddyz]

Hello again,

Uh oh. Thank you for that! I totally forgot that I turned on Verifier a while back, and never turned it back off.
That might explain many of the vague BSoDs.

As for your question about the NVIDIA driver; a better question might be: is there any specific reason why I should use heavily outdated GPU drivers provided by ASUS? Their latest (and only) driver dates back to January 2015, see HERE.
I should mention that I did have some weird issues with the NVIDIA drivers a while back; the PC would give a BSoD every time I tried to use the auto-updater from the NVIDIA Experience program. (Which always worked fine before that)
Eventually I ended up downloading the drivers manually, and installing them manually again, like the good ol' days.
I'll try doing a completely new/clean installation of the NVIDIA drivers now.

I've updated my profile with my laptop's specifications.
Please let me know if you need more information, and thanks again.

 

[axe0]

The answer to the 'better question':
Many laptop manufacturers alter their drivers they provide for customers, this kinda forces the user to only install those drivers.
It doesn't mean that you cannot install drivers from other sources, but if drivers from other sources are being installed the user can expect problems because the altered part that is designed for the hardware isn't included.

The drivers from ASUS aren't that much outdated though, my laptop used drivers that are from 2013/2014.

 

[Buddyz]

The answer to the 'better question':
Many laptop manufacturers alter their drivers they provide for customers, this kinda forces the user to only install those drivers.
It doesn't mean that you cannot install drivers from other sources, but if drivers from other sources are being installed the user can expect problems because the altered part that is designed for the hardware isn't included.

Hi again,

I'm aware of that, but what's the point of buying a high-end laptop, with a high-end graphics card, and then using over 1-year old drivers? That way you'll miss all special Game Ready drivers that are released for modern games.
The original NVIDIA drivers should work just fine, and saying that you "can expect" problems is not entirely true. I've been using original NVIDIA drivers ever since I started working with laptops. (Which is many many years)
Anyway, the above will be an endless discussion.

I did a full clean installation of the NVIDIA drivers. Today I got another BSoD when trying to run Unreal Tournament. Fortunately a log was saved this time, I've included it in the attachment.
Can you confirm that it is indeed caused by the NVIDIA drivers this time (too)? If so, I'll try the stock NVIDIA drivers from ASUS for testing purposes and then report back.

 

[axe0]

saying that you "can expect" problems is not entirely true

That is your opinion, but facts & experience state different. The fact is that if you install drivers from a different source you miss the part where the drivers are better optimized for your hardware what is the alter part, missing this can cause problems because Nvidia & AMD & Intel cannot provide drivers that are optimized for a laptop that has a small difference setup that the laptop manufacturer installs.

Anyway, the above will be an endless discussion.

Indeed, I'm not going to argue about it.
However I would like to say that all those who have said the same as you have ultimately saw their issues solved simply by installing drivers from the manufacturer instead of the direct source of the drivers.

You do not need drivers that are frequently updated, you need drivers that keep your system stable and are properly optimized for your system. Laptop manufacturers are late with driver updates, but that shouldn't matter as long as a system runs stable, this shouldn't be a reason why one would start installing drivers from a different source. It would be better to have drivers that are proper at once but a bit late than drivers that aren't proper but frequent updates are released to solve endless occuring problems.

If you do not want to follow my suggestions, no problem for me, but please do not try to argue about why I suggest something or why I say something that according to you is not true or you don't believe it or whatever. I've helped more than enough people to say what is good for stability, stability comes before performance in the case of BSODs, and if someone says something different then I'll ask him/her to continue with what I started.

 

[axe0]

I've included it in the attachment.
Can you confirm that it is indeed caused by the NVIDIA drivers this time (too)? If so, I'll try the stock NVIDIA drivers from ASUS for testing purposes and then report back.

Please try to include the zip again, I do not see a new one.

 

[Buddyz]

Hi again,

saying that you "can expect" problems is not entirely true

That is your opinion, but facts & experience state different. The fact is that if you install drivers from a different source you miss the part where the drivers are better optimized for your hardware what is the alter part, missing this can cause problems because Nvidia & AMD & Intel cannot provide drivers that are optimized for a laptop that has a small difference setup that the laptop manufacturer installs.

Like I said too, it was not an opinion, it it based on many years of experience using (and fixing issues with) laptops.
My point was that you are saying that you "can expect" problems, which suggests that you will always run into issues like this at some point, no matter what. That is simply not true.

Indeed, I'm not going to argue about it.

Yet you continue anyway.

You do not need drivers that are frequently updated, you need drivers that keep your system stable and are properly optimized for your system. Laptop manufacturers are late with driver updates, but that shouldn't matter as long as a system runs stable, this shouldn't be a reason why one would start installing drivers from a different source. It would be better to have drivers that are proper at once but a bit late than drivers that aren't proper but frequent updates are released to solve endless occuring problems.

Can you name one laptop manufacturer that actually tries to/does keep their GPU drivers up-to-date? I've never seen one, because they simply don't bother. Look at the drivers for my laptop, there is only one GPU driver, and that is the one that was released with the laptop itself. I can guarantee you that they will not update the GPU drivers ever again.
While you might not care about up-to-date drivers, some people like me do. Why else would they release Game Ready drivers? Like I said, they have all worked on my system just fine for so long. A possibility is that those drivers are indeed incompatible with the software/games I'm currently using.

If you do not want to follow my suggestions, no problem for me, but please do not try to argue about why I suggest something or why I say something that according to you is not true or you don't believe it or whatever. I've helped more than enough people to say what is good for stability, stability comes before performance in the case of BSODs, and if someone says something different then I'll ask him/her to continue with what I started.

Technically you never suggested something, you asked me why I was not using the stock drivers, not that I should use the stock drivers. I just answered your question.

And obviously you should not get me wrong here, I highly appreciate your and everyone else's help here. I'm not questioning your knowledge in any wayI don't have much BSoD knowledge, hence I always come here since I found this forum.

Please try to include the zip again, I do not see a new one.

After posting I found out that I forgot to include the attachment. A few minutes after that I edited the post and added the attachment. Can you still not see it?
I had another BSoD in the meantime, so I've included the logs for that one in the attachment of this post. (It also includes the older logs)

Thank you for your time and help.