Windows 10: BSOD Driver power state failure

Hello @zbook
I have done the memtest for 9 passes and I didn't find any errors. There hasn't any BSOD or wifi disconnect since the driver change and the memtest was finished 3 days ago.

 

For Memtest86+ what were the troubleshooting steps that you made to get it to test? And which steps had prevented the testing? Please post as much detail as possible about each the Memtest 86+ software, USB, USB port, uefi or legacy bios, fast boot, secure boot, and csm.

Please post an undated zip: BSOD - Posting Instructions - Windows 10 Forums

 

Hello @zbook Here are the steps I followed to get my USB to boot into my bios.
for memtest86+: ASUS G551JW-----Press F2 to bios menu (ESC to boot menu)
1. I disabled the fast boot
2. I diasbled the secure boot control to get into CSM
3. I enabled the CSM and F10 to save and exit
4. Press F2 and in the boot menu we will find 4 options:
a) 2 for UEFI: boot manager, UEFI Flash disk
b) 2 for bios: boot manager, flash disk
5. Select the bios flash disk which will be the last option(fourth) and set it as primary boot device.
6. Press F10 to save and exit and wait for the memtest86+ to run.

 

The event logs and the windows error reporting display crashes on:
8/16
8/17
8/21
after the last bsod on 8/14/207.

Windows driver verifier is a tool that is used to find misbehaving drivers.
It will repetitively produce bsod until misbehaving drivers are fixed or until it is turned off.
For each windows driver verifier bsod there should be a mini dump file that can be debugged to find a misbehaving driver.
In order to use this tool you must know how to turn it off after each bsod and return to the desktop to fix misbehaving drivers.
There are 3 methods and all are done using windows recovery or windows advanced troubleshooting menu:
1) startup options (not startup repair) > select #6 safe mode with command prompt > type: verifier /reset
2) command prompt > Administrator X:\windows\system32\cmd.exe > type: verifier /bootmode resetonbootfail
3) restore
The steps should always be made in the above order. Using the restore method typically results in the loss of the bsod mini dump file and little progress would be made in the troubleshooting.

To get comfortable using the windows advanced troubleshooting menu open administrative command prompt and type shutdown /r /o /f /t 00

For each bsod you will need time to view the bsod window. There is typically a stop code driver verifier detected violation and sometimes it may display the misbehaving driver in the form *.sys. If you see the driver displayed please record it and post it into the thread.

Modify the system startup and recovery settings so that automatic restart is unchecked:
Microsoft Community

After each bsod you will turn off windows driver verifier and return to the desktop and run each Bluescreenview and Whocrashed. The misbehaving driver will be uninstalled. The driver can be reinstalled immediately after its uninstallation or after all misbehaving drivers are uninstalled. It is personal preference and the outcome should be the same.

Blue screen of death (STOP error) information in dump files.
Resplendence Software - WhoCrashed, automatic crash dump analyzer

After each bsod you can post a new zip and we will guide you through the process.

To turn on and customize the settings for windows driver verifier view this link:
Microsoft Community

View this link to learn the methods on turning off windows drive verifier:
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

Before turning on windows driver verifier make sure you perform the following steps:
1) make a brand new restore point.
2) backup all files
3) use Macrium to make a back up image
Macrium Software | Your Image is Everything
4) place the backup image onto another drive


Once all of the bsod have been fixed windows driver verifier will be run for 36 hours of typical computer use. If there are no longer any bsod troubleshooting and preventative maintenance will be completed.


Code: 8/22/2017 4:54 PM Windows Error Reporting Fault bucket 127958793500, type 5 Event Name: AppxDeploymentFailureBlue Response: Not available Cab Id: 0 Problem signature: P1: 80070003 P2: 16 P3: 1 P4: OSIM Host P5: 10.0.14393.1532 P6: 402 P7: P8: P9: P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_80070003_85c0a7efa2634422f3bc44a37399c33f408480e6_00000000_2f179abb Analysis symbol: Rechecking for solution: 0 Report Id: c0ca3483-873a-11e7-9d48-086266b6b749 Report Status: 0 Hashed bucket: 47ce340533ffc8ed355d8b483a75b46e8/22/2017 4:54 PM Windows Error Reporting Fault bucket 127958793500, type 5 Event Name: AppxDeploymentFailureBlue Response: Not available Cab Id: 0 Problem signature: P1: 80070003 P2: 16 P3: 1 P4: OSIM Host P5: 10.0.14393.1532 P6: 402 P7: P8: P9: P10: Attached files: \\?\C:\Windows\TEMP\AppXDeploymentServer_7E67D3B3-1A9B-0000-FE2B-697E9B1AD301.evtx \\?\C:\Windows\TEMP\AppXPackaging_7E67D3B3-1A9B-0000-FE2B-697E9B1AD301.evtx \\?\C:\Windows\TEMP\AppxErrorReport_7E67D3B3-1A9B-0000-FE2B-697E9B1AD301.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA85F.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_80070003_85c0a7efa2634422f3bc44a37399c33f408480e6_00000000_2f1797fc Analysis symbol: Rechecking for solution: 0 Report Id: 7ccfc5f7-873a-11e7-9d48-086266b6b749 Report Status: 0 Hashed bucket: 47ce340533ffc8ed355d8b483a75b46e[/quote] Code: Event[37829]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-08-21T11:35:31.962 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-K6IJU5N Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote] Code: Event[37829]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-08-21T11:35:31.962 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-K6IJU5N Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote] Code: Event[35566]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-08-17T20:13:36.854 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-K6IJU5N Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote] Code: Event[34114]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-08-16T12:15:02.869 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-K6IJU5N Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote]

 

There is no Problem with the nvidia driver. This information is from old bsod dump.

To shorten this here:

The wifi driver was/is the problem. The last two bsod dumps (which have an actual date) show this definitely

 

@vamsinaruto if you are satisfied that the original problem has been fixed then you should mark this thread as solved.

 

Hello @zbook
Sorry for the late reply. I read through your post and unfortuantely I have work for which I need the laptop. So, I will do the process you described as soon as I can when I am free.
The three methods you mentioned numbering 1,2,3 do I have to do all the three of them or just any one is enough with preference order being 1>2>3.

 

As BSODHunter typed the driver Netwbw02.sys was causing the bsod and was fixed.
The driver nvlddmkm.sys was from an older bsod.
After replacing Netwbw02.sys the logs no longer indicated any bsod.
After replacing Netwbw02.sys the logs indicated unexpected crashes without bugchecks (bsod).
Just 1 command that turns off windows driver verifier is needed.
Sometimes the command fails and then there are 2 additional methods to turn off windows driver verifier.
Philc43 typed that if you are satisfied you can mark the thread as solved.
So let us know whether you are or are not having unexpected crashes.
If you no longer have any unexpected crashes you can mark the thread solved.
If you continue to have unexpected crashes you can bring that to our attention when you have time to perform troubleshooting steps and we can guide you through the process.

 

Hello @zbook
Since I do not have any BSOD after changinf the network driver I will mark the thread as solved. Still, I will try to do the driver verifier when I am free just to make sure.
Thanks evreyone for the support. Thank you zbook.

 

Your welcome.
If you need any help please let us know.