Daily BSODs - different minidump causes, bsod when not in use

Hi Gangel77,

Sorry for the delay in response.

Do you still need help?

Please run the V2 log collector again, upload a new zip to dropbox and post a share link.

I have currently two guesses as to what may be going on.

My first guess, there are one or more drivers terrible at synchronizing with the rest of the system.

My second guess, there is something else going on.

I am personally opting for the first guess currently after having a look at the stack, though one of them didn't exactly tell much. For now I'd like you to run driver verifier as well as look out for a very specific crash. I'll provide the driver verifier instructions below, for this very specific crash if you see it occurring I need you to upload the C:\Windows\Memory.dmp file because it'll be necessary as the minidump itself won't be sufficient. This specific crash is the 0x133, its what is best described as its 'sub-type' (parameter 1 = 1) indicates that one or more drivers caused problems and a full kernel memory dump is required to analyze that one.

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)

1. In normal mode open an administrator command prompt and enter the below command
2. In safe mode open an administrator command prompt and enter the below command
3. 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
   
   
4. Boot with the recovery media, see above 4 steps in option 3.
5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier

Code:

verifier /reset

Crashed when running driver verifier

1. Reset driver verifier
2. Boot in normal mode if necessary
3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs

Extra information about driver verifier
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

Code:

verifier /query

If the command gives a result similar to this, it means driver verifier is running.

gangel77 said:

- Weird about driversCloud.. I dont install this cr&p on my comp so i have no idea how it got there!

Could have come bundled with other software, it is common for software to come bundled with other software that the user unknowingly installs. Even if you are careful with this and go thoroughly through each step of the installation to prevent such software from unknowingly being installed, you can still end up with such programs installed simply because people make mistakes.