Windows 10: Computer Randomly Restarting Without BSOD in Wolfenstein II

3.3 Voltage: 3.328
5 Voltage: 5.040
12 Voltage: 12.192

CPU Frequency: 3.60 ghz
CPU Voltage: 1.192v

As for that log collector, do you want the entire folder of the results, or any specific files within?

 

Please run the log collector then post a zip into the thread for troubleshooting (all files)

 

DESKTOP-0AFCLF7 (1-5-2018 4 25 PM).zip Here it is!

 

For all tests /steps please post images into the thread.
For problems posting images please use one drive or drop box share links.

1) open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

6) In the left lower corner search type: clean > open disk cleanup > scroll up and down > post images into the thread

7a) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
7b) > on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
7c) > on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread

8) Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
http://www.resplendence.com/whocrashed
9) Click analyze > look at the results for dead or deaddead > post the results into the thread

10) Run the DM log collector after all of the above steps and post a zip into the thread:BSOD - Posting Instructions - Windows 10 Forums
BSOD - Posting Instructions - Windows 10 Forums

11a) Open device manager > click view > show hidden devices > expand all rows > look for any row with a yellow triangular icon with a black exclamation mark > post an image into the thread.
11b) Post an image of network adapters

12) Open the website for the computer's drivers > post a URL or hyperlink into the thread.



This was displayed as a problem device:
Code: WAN Miniport (IP) SWD\MSRRAS\MS_NDISWANIP 56[/quote] Code: Event[514]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5003 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Could not find a network adapter.Event[515]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[516]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[517]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[518]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[519]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[520]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[521]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[522]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[523]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[524]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[525]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[526]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[527]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[528]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[529]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5002 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly.Event[530]: Log Name: System Source: Netwtw04 Date: 2017-12-30T16:01:52.259 Event ID: 5005 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Intel(R) Dual Band Wireless-AC 8260 : Has encountered an internal error and has failed.[/quote] Code: Event[2499]: Log Name: System Source: Volsnap Date: 2018-01-04T23:55:20.870 Event ID: 24 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: There was insufficient disk space on volume C: to grow the shadow copy storage for shadow copies of C:. As a result of this failure all shadow copies of volume C: are at risk of being deleted.[/quote] Code: Event[2513]: Log Name: System Source: storahci Date: 2018-01-05T11:59:02.739 Event ID: 129 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Reset to device, \Device\RaidPort0, was issued.[/quote] Code: Event[2512]: Log Name: System Source: Disk Date: 2018-01-05T11:58:32.812 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: The IO operation at logical block address 0x24101a8 for Disk 1 (PDO name: \Device\00000032) was retried.[/quote] Code: Event[1830]: Log Name: System Source: Display Date: 2018-01-01T19:48:37.267 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-0AFCLF7 Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: Event[2450]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2018-01-04T23:52:29.245 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-0AFCLF7 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]

 

upgrading your PSU would be the best option.. 850w at least.. 500w is holding back your PC.

 

So, quick warning: Firefox was unable to save any of the copy+pasted text from the first steps when I closed it to do that crash test. I'll post logs that I was able to get after doing step 9, but the original logs are in screenshot.

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\Windows\system32> dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Image Version: 10.0.16299.192

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\Windows\system32> chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
251648 file records processed.
File verification completed.
4950 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
275 reparse records processed.
318810 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
275 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
33582 data files processed.
CHKDSK is verifying Usn Journal...
39936520 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

244196351 KB total disk space.
182265696 KB in 163804 files.
122620 KB in 33583 indexes.
0 KB in bad sectors.
366263 KB in use by the system.
65536 KB occupied by the log file.
61441772 KB available on disk.

4096 bytes in each allocation unit.
61049087 total allocation units on disk.
15360443 allocation units available on disk.
PS C:\Windows\system32>


Now here's the WhoCrashed logs:

On Fri 1/5/2018 6:46:24 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010518-4953-01.dmp
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19B16B9E, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\Windows\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.



On Fri 1/5/2018 6:46:24 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19B16B9E, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\Windows\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.


And finally, here comes the screenshots, where I took them/where they apply. I'm using a google drive sharable link, since that's easiest for me (given I currently haven't set up dropbox or onedrive), but if you'd rather I use another hosting service I'll see what I can do.
Screenshots - Google Drive

There is definitely an issue with my network adapter in some way, that much is certain. I didn't see any other devices with the little triangle, even after showing hidden devices.

 

1) For startup and recovery > system failure > un-check automatically restart
2a) For the WAN mini port with yellow triangle and black exclamation mark > right click > left click properties
2b) > left click driver tab > left click driver details > post an image into the thread.
2c) > left click details tab > under properties scroll to Hardware Ids > post an image into the thread.

How to Find Drivers for Unknown Devices in the Device Manager


There were 18 crashes between 12/31/2017 and 1/5/ 2017.

Code: 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] The test dump displayed an extra software driver in the crash.

The plan is to eliminate hardware and software drivers and hardware as best as possible and isolate the PSU as the cause of the unexpected crashes. So this would be a process of elimination.

With the automatic restart off any BSOD will be much clearer.

3) backup all files to another drive or to the cloud
4) make a backup image using Macrium:
Macrium Software | Macrium Reflect Free
5) place the backup image onto another drive or into the cloud
6) make a brand new restore point
7) Make sure that there is no over clocking
8) To ensure that there are no improper bios settings please reset the bios.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

9) These are links on Windows driver verifier:
Read the links but do not turn on the tool until it is communicated in the thread.
The methods to turn off Windows driver verifier are done through the Windows advanced troubleshooting menu.
To view the menu you can get there by using administrative command prompt and typing: shutdown /r /o /f /t 00
or by clicking the left lower corner windows icon > power > restart (while holding down the shift key)
Please learn the 3 methods to turn off Windows driver verifier using the Windows advanced troubleshooting menu.
The first link is for the test settings
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
The second link is for the methods on how to turn off Windows drive verifier
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

10) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:Speccy - Free Download - Piriform: Speccy - System Information - Free
Speccy - System Information - Free Download
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

11) Change power plan to high performance



The computer graphics are Nvidia GTX 1070.
Nvidia GeForce GTX 1070 review - Hardware Setup | Power Consumption

The current BIOS for MB:
Manufacturer Micro-Star International Co., Ltd Product B350M PRO-VH PLUS(MS-7B07)
BIOS Version/Date American Megatrends Inc. 2.00, 6/22/2017

Please check for an upgraded bios:
Support For B350M PRO-VH PLUS | Motherboard - The world leader in motherboard design | MSI USA

The computer has version 20 > upgrade to new version 22


Code: Name NVIDIA GeForce GTX 1070PNP Device ID PCI\VEN_10DE&DEV_1B81&SUBSYS_85A01043&REV_A1\4&1C3D25BB&0&0019Adapter Type GeForce GTX 1070, NVIDIA compatibleAdapter Description NVIDIA GeForce GTX 1070Adapter RAM (1,048,576) bytesInstalled Drivers C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvldumdx.dllDriver Version 23.21.13.8871INF File oem13.inf (Section136 section)Color Planes Not AvailableColor Table Entries 4294967296Resolution 1920 x 1080 x 60 hertzBits/Pixel 32Memory Address 0xFC000000-0xFCFFFFFFMemory Address 0xE0000000-0xEFFFFFFFMemory Address 0xF0000000-0xF1FFFFFFI/O Port 0x0000E000-0x0000E07FIRQ Channel IRQ 54I/O Port 0x000003B0-0x000003BBI/O Port 0x000003C0-0x000003DFMemory Address 0xA0000-0xBFFFFDriver c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_d37ca5c2cde53609\nvlddmkm.sys (23.21.13.8871, 16.24 MB (17,028,552 bytes), 12/31/2017 11:58 AM)[/quote]

 

There are the two screenshots you asked for, and as for the link on finding drivers, when I went to Properties, instead of error 28 I got: "Windows is still setting up the class configuration for this device. (Code 56)"

I'm working on moving some data on an external hard drive and reformatting it so I can move my backup there, I'll post again once that's all done.

 

Okay! Here are the images:






And as for everything else: the BIOS has been updated, power plan was changed to High Performance, Speccy was installed, and I've done some reading on the driver verifier.

 

1) Make another brand new restore point
2) Make sure files are backed up and that you have made a backup image using Macrium.
3) Review these methods to turn off Windows driver verifier: (they are all done using the windows advanced troubleshooting menu)
a) startup options (not startup repair) > click restart > select #6 safe mode with command prompt > type:
verifier /reset
b) command prompt > Administrator: X:\Windows\system32\cmd.exe > Sources X: > type:
verifier /bootmode resetonbootfail
c) system restore
The steps should be done in the above order and advanced to the next step only if the prior method failed. Using system restore often leads to a loss of the mini dump file and little progress is made in the troubleshooting.
4) If you are comfortable with all of the above then turn on Windows driver verifier and plan to run the tool for 48 hours. During the use of the tool the computer can become sluggish. After the last BSOD the tool will be run for an additional 36 hours of typical computer use.
For each BSOD submit a new zip: log collector v2-beta06.zip

 

Just a few questions before I get going- I wanna be sure I understand it all, since this looks easy enough to mess up.


1. It looks like, according to one of the links you posted, I may be able to just turn it off by deleting settings in the driver verifier menu itself- if I'm able to, I assume I should do that before doing the methods in startup recovery?

2. While I run it for 48 hours, I assume it should stay on the whole time?

3. And with "for each BSOD submit a new zip," you mean that I should do it after the computer restarts, right? And should I just start a 36 hour timer and reset it after every BSOD, or what?

Finally, I saw mentioned that I might want to try and produce BSODs by doing what was happening when errors previously occured (eg, playing Wolfenstein or other problematic games.) Should I do that, or stay away from things that might cause restarts like that?

Sorry if these questions seem really simple, I just want to be sure that I have everything done right before I start this. Thanks!

 

The tool Windows driver verifier is part of Windows.
When it is turned on it will stress the non-Microsoft drivers.
It will repetitively produce BSOD until all misbehaving drivers are fixed or until the tool is turned off.
Each time it produces a BSOD there should be a dump file.
The debugging of the dump file may disclose a misbehaving driver.
With more the files and more the debugging the more likely any misbehaving driver will be fixed.
The test settings for the tool can be modified. The greater the number of drivers being stressed at any one time and the greater the number of active test settings at any one time the more likely it can produce a sluggish computer. Sometimes the typical method to turn off the tool fails. So there are additional methods to turn off the tool up to system restore. However system restore often leads to a loss of the dump file and little progress is made in the troubleshooting.
For each BSOD you will see a windows displaying the bugcheck. Sometimes the misbehaving driver is displayed in the form *.sys. If you see the misbehaving driver displayed please record it and post it into the thread.
After each BSOD you must turn off Windows driver verifier and return to the desktop. In order to do this you will need to use one of the commands. The typical command is verifier /reset when using the windows advanced troubleshooting menu. When you are back on the desktop you will run Whocrashed. It should display some information and if it displays the misbehaving driver you can uninstall it and the turn on windows driver verifier again to find the next misbehaving driver.
The process can be repeated over and over again until all misbehaving drivers are uninstalled. An alternative method is to reinstall drivers immediately after they have been uninstalled. Either method, waiting until all misbehaving drivers are uninstalled, or reinstalling drivers immediately after they were uninstalled should end up with the same result. All misbehaving drivers will be uninstalled and new drivers will be installed.
The tools that we use are more powerful than Whocrashed at finding misbehaving drivers as we can run commands on the dump files. So after each dump you will submit a new zip for debugging and we can guide you with the treatment of the misbehaving drivers.

You can start running the tool and uninstall misbehaving drivers after identifying them with Whocrashed.
Windows driver verifier is run for approximately 48 hours.
Then after the last misbehaving driver is identified it is run for an additional 36 hours of typical computer use.
This should be sufficient time to identify misbehaving drivers.

Computer crashes are typically caused by misbehaving hardware and software drivers, and malfunctioning hardware. The windows driver verifier tool will produce BSOD by stressing the drivers. Then when all of the misbehaving drivers are removed from the picture you be able to see whether there is an impact on the frequency of the crashes. If the crashes continue to occur then you likely have an under powered PSU and would want to swap it to see if a higher power PSU eliminates the crashes. If the crashes no longer occur after fixing misbehaving drivers then you know that any of the changes that were made in the thread fixed the computer environment. For over clocking you may want a higher powered PSU so that there is no bottle necking.

 

Okay, I've turned on driver verifier, used verifier /querysettings to make sure it's on, and I'll be sure to update you if any BSODs occur. If not, I'll come back in a few days time, but that'd mean it's almost definitely time for a new PSU.

 

By eliminating misbehaving drivers as a cause of unexpected shutdowns and reboots you will have narrowed the problem.
Calculations can be made for power requirements of the PSU needed for the computer hardware components.
That appears to have already been done earlier in the thread.
If there is a BSOD please post a zip: log collector v2-beta06.zip

 

Just to say if the mobo battery is on its way out this can cause time shifts and random restarts *Smile