Question "Driver-Power-State-Failure" BSOD occurs on my laptop due to graphics card... AGAIN

[enlightener]

So a few months ago, I had this problem where I'd get BSOD'd every time my GPU showed up in my device manager. I was able to somewhat "solve" the problem, and I left it at that. Well, that very same problem is back. I looked at the previous question I asked about the same problem I had a while ago (https://forums.tomshardware.com/thr...rs-on-my-laptop-due-to-graphics-card.3749217/) and tried using the answer I got from @Colif but to no avail. I used his solution several times, but the same BSOD error still popped up. Did the fast startup stuff too.

Specs:
Laptop Model: Asus ROG GU501GM
Processor: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz 2.21 GHz
Installed RAM: 32.0 GB
GPU: GTX 1060

 

[Colif]

We will need the dumps as usual. Hopefully this time we fix it

right click start button

choose powershell (admin)

copy/paste this command into window:

Repair-WindowsImage -Online -RestoreHealth

and press enter

Then type SFC /scannow

and press enter

Restart PC if SFC fixes any files as some fixes require a restart to be implemented

First command repairs the files SFC uses to clean files, and SFC fixes system files

SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11

 

[enlightener]

Alright, I did all of that, and both commands did not prompt me to restart (screenshot - https://prnt.sc/nmwxSFMFykkn). So, I shut down my computer to start the GPU up, and a few minutes later I got BSOD'd. I ran the commands in PowerShell again and I was given the same result. Anything else?

 

[Colif]

wow, i must be tired.

wrong instructions - sorry, I didn't notice... slaps self.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

 

[enlightener]

No worries my friend! Here's the link to the minidump zip file - https://1drv.ms/u/s!Ao5YPPaH-zsdqW4Uc36xJyRTqbb9?e=ezUom8

 

[enlightener]

Also, I have a question - how do you check the .dmp files from the minidump to know what the problem could be?

 

[gardenman]

how do you check the .dmp files from the minidump to know what the problem could be

Sometimes, on rare occasions, the results from WinDbg will name the driver that caused the crash. Then you look up that driver filename to determine what it belongs to, and update or rollback that driver. But most of the time (like 1 of the below dump files) it just leaves you guessing.

I ran the dump files through the debugger and got the following information: https://jsfiddle.net/rLxkb5cs/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	061722-7406-01.dmp (Jun 17 2022 - 01:40:11)
Bugcheck:	DRIVER_POWER_STATE_FAILURE (9F)
Probably caused by:	pci.sys (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 35 Sec(s)

File information:	061622-7359-01.dmp (Jun 16 2022 - 21:52:31)
Bugcheck:	DRIVER_POWER_STATE_FAILURE (9F)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 10 Min(s), and 56 Sec(s)

File information:	061622-7312-01.dmp (Jun 16 2022 - 23:32:53)
Bugcheck:	DRIVER_POWER_STATE_FAILURE (9F)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 34 Sec(s)

File information:	061622-6765-01.dmp (Jun 16 2022 - 23:00:03)
Bugcheck:	DRIVER_POWER_STATE_FAILURE (9F)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process running at time of crash: MsMpEng.exe)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 28 Sec(s)

File information:	061622-7359-02.dmp (Jun 17 2022 - 00:47:03)
Bugcheck:	DRIVER_POWER_STATE_FAILURE (9F)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 36 Sec(s)

Comment: 2 or more types of RAM are installed.

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

System: GU501 Laptop

ROG GU501 - Support

www.asus.com

You already have the latest BIOS (316).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

Apr 16 2018	nvvhci.sys	Nvidia Virtual USB Host Controller driver http://www.nvidia.com/
Aug 22 2018	nvvad64v.sys	Nvidia Virtual Audio driver http://www.nvidia.com/
Dec 11 2018	nvlddmkm.sys	Nvidia Graphics Card driver http://www.nvidia.com/

So those drivers that are installed are newest on the Asus website? As its what I suggested here - https://forums.tomshardware.com/thr...p-due-to-graphics-card.3749217/#post-22608127

Shame we don't know how old the ones you had installed were in the last thread.

I would run DDU again and grab the newest drivers from Nvidia and see if any better.

If we still get same error, I would start to think its the GPU itself.

 

[enlightener]

Welp, I've tried everything. I ran DDU several times, installed the newest drivers from Nvidia's website, and the newest ones from Asus, and let windows install the drivers for me, but I didn't get anywhere. Sometimes though, I wouldn't get the BSOD if I didn't do anything, but instead, if I just played a game and closed it, I would get BSOD'd after some time has passed. Or if I minimized the game's screen, the game would stop responding, I would get a BSOD shortly after. I retrieved more .dmp files (https://1drv.ms/u/s!Ao5YPPaH-zsdqXgGwZ5xOafCkvU6?e=tJ7ujV) since the crashes were a little bit different, but at this point, I don't know what else to do.

 

[enlightener]

Another thing, my GPU always turns off after a restart or after using DDU when it becomes the Microsoft Basic Display Adapter in the device manager. I always have to shut my computer down for up to an hour before it shows up again. Do any of you know why?

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://jsfiddle.net/avp82oer/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	062022-7734-01.dmp (Jun 20 2022 - 12:08:54)
Bugcheck:	DRIVER_POWER_STATE_FAILURE (9F)
Probably caused by:	pci.sys (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 39 Min(s), and 46 Sec(s)

File information:	061922-7968-01.dmp (Jun 19 2022 - 18:21:05)
Bugcheck:	DRIVER_POWER_STATE_FAILURE (9F)
Probably caused by:	pci.sys (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 06 Min(s), and 27 Sec(s)

File information:	061922-7250-01.dmp (Jun 19 2022 - 21:29:11)
Bugcheck:	DRIVER_POWER_STATE_FAILURE (9F)
Probably caused by:	pci.sys (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 35 Sec(s)

File information:	061922-7031-01.dmp (Jun 19 2022 - 18:32:21)
Bugcheck:	DRIVER_POWER_STATE_FAILURE (9F)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	dxgkrnl.sys (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 03 Min(s), and 13 Sec(s)

File information:	061922-7171-02.dmp (Jun 19 2022 - 19:36:34)
Bugcheck:	DRIVER_POWER_STATE_FAILURE (9F)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	dxgkrnl.sys (Process running at time of crash: System)
Uptime:	0 Day(s), 0 Hour(s), 39 Min(s), and 53 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

Welp, I've tried everything. I ran DDU several times, installed the newest drivers from Nvidia's website, and the newest ones from Asus, and let windows install the drivers for me, but I didn't get anywhere.

those are about only 3 options I normally offer.

Another thing, my GPU always turns off after a restart or after using DDU when it becomes the Microsoft Basic Display Adapter in the device manager. I always have to shut my computer down for up to an hour before it shows up again. Do any of you know why?

I wonder if its a hardware fault.

One thing that makes me question either way is fact it recognises the drivers. I have seen it refuse to install drivers before and that usually means its hardware... but yours recognises drivers and still crashes.

it being a laptop makes it hard to just swap a GPU out.

try running this and see if any new Intel drivers, might help = https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

 

[enlightener]

those are about only 3 options I normally offer.


I wonder if its a hardware fault.

One thing that makes me question either way is fact it recognises the drivers. I have seen it refuse to install drivers before and that usually means its hardware... but yours recognises drivers and still crashes.

it being a laptop makes it hard to just swap a GPU out.

try running this and see if any new Intel drivers, might help = https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

I went to the site you provided and it said something went wrong with trying to scan. Also, just an update - my whole screen now freezes before I get a BSOD. I can still move my mouse and stuff but can't do anything else. Then a few seconds later, a BSOD. It happens randomly. Sometimes I'm able to use my computer for long periods of time before it happens, and sometimes I'm not. Know anything else?

 

[Colif]

Strange Intel updater didn't work.

you might need to get it repaired. I don't like sound of the freezing part.

You don't need Advanced System care... curious, does it include a driver updater? If so, do you use it? This isn't a suggestion to run it. I don't think its the cause.

did laptop come with 32gb of ram or did you install 16gb? just curious. I may have asked this before.

 

[enlightener]

The original laptop owner added 16Gb of ram to the laptop before I bought it from them, and I used to have a driver updater. Coincidentally - I had the driver updater when the first issue started. I have since deleted it. But, do you think the ram could be the problem?