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.
Last edited by zbook; 07 Jan 2018 at 11:44.
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 :)
See post #8 as XxChrisxX initially suggested to stress test the GPU.
Eliminating drivers, then GPU, will help to identify the problem.
While it's not been the whole 48 hours of uptime yet, I've gone about 36 hours with driver verifier on, and no BSODs have occured. At this point I'm almost entirely sure that it's the PSU- I'm in the process of getting my hands on a 750 watt one, which should be enough. I'll definitely have to learn not to trust PC Part Picker's wattage estimate going forward, lol. Assuming that the test with that PSU works, once I have my hands on it, I'll just mark this as solved. If not, I'll have to GPU stress test. Thank you guys!
Quote
