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.
http://www.resplendence.com/whocrashed
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
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.
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.
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.
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
Note
