New
#11
Did you let it complete?
I just rerun the log collector again just in case something went wrong and attached to this thread.
Something was wrong yes, most of the interesting files were missing.
The strange thing is that the dumps report the system's uptime to be ~2 seconds, which means the system crashed after 2 seconds of getting online. That does not fit with your description, because it's in the boot process (hence the 'BOOT error' you see in the dump), so I asked for logs to see if they could clarify things, but unfortunately there's quite a gap of like an hour before the system crashed.
It appears the same crash (I assume) happened a month ago as well, does it only happen under the described circumstances?
I see. Yes about a month ago, i did encounter the same crash but i am unable to reproduce the problem. The previous crash happened a month ago was when I was playing Company of Hero game. It froze while I was playing and then I hit the restart button on my computer.
The past few days it crashes often was when I am using Excel. I have a lot of formula running on it. The formula uses a lot of Rand() function. I noticed on the power usage on the Task Manager, it gets extremely high and then suddenly it froze.
The following is just to rule out software related boot issues.
Please run driver verifier using the following settings for 48 hours.
- Special Pool
- Force IRQL checking
- Pool Tracking
- Deadlock Detection
- Security Checks
- Miscellaneous Checks
- Power framework delay fuzzing
- DDI compliance checking
Warning: driver verifier could cause boot issues and/or performance issues.
- Make sure that you have recovery media, if needed you can create it.
- Configure a restore point prior enabling driver verifier.
Resetting driver verifier options (recommended in this order)
- In normal mode open an administrator command prompt and enter the below command
- In safe mode open an administrator command prompt and enter the below command
- On 3 boot failures, you'll boot automatically to the recovery options,
- click Troubleshoot
- go to the advanced options
- choose command prompt
- enter the below command
- Boot with the recovery media, see above 4 steps in option 3.
- Via the recovery options or recovery media, select a restore point prior enabling driver verifier
Code:verifier /reset
Crashed when running driver verifier
- Reset driver verifier
- Boot in normal mode if necessary
- Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs
This is something I wrote last week about driver verifier explaining the most significant sign of driver verifier running.
When you run driver verifier, there are two things you're looking out for
1. Driver verifier won't find any driver violating something and thus in the time you need to run it there won't be a crash
2. Driver verifier will find a driver violating something and thus the system will crash.
The end result of driver verifier is either of the two, but when driver verifier finds something your system will BSOD.
Driver verifier essentially validates selected drivers on selected actions, this validation adds some delay to actions performed in the background which results in a performance decrease that many people notice. This is called stress testing drivers and depending on quite a few factors this performance decrease is worse for some than for others, and some won't even notice a difference.
Depending on the drivers selected, it is possible that some of the selected drivers are so-called 'boot' drivers, meaning they load when your system is booting. If these drivers don't pass a validation check, your system will crash, but since the drivers are loading at boot, your system will basically be in a boot loop. That is one of the risks involved and the most important one. Of course, there are various methods to recover from it.
If you want visual confirmation that driver verifier is actually running, copy/paste the following command in powershell or command prompt
If the command gives a result similar to this, it means driver verifier is running.Code:verifier /query