Random weekly BSODs even after reset, CRITICAL_PROCESS_DIED

Hi mezameta,

Please open powershell and copy/paste the following code into powershell to create a textfile report of the chkdsk result.

Code:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

Copy everything in chkdskresults.txt and paste it in your next post.

Just to confirm, I assume you ran MemTest86 - Official Site of the x86 Memory Testing Tool

I don't think you need to scan the other drives/partitions for now.

Do you know if the BSOD crashes of the previous onces, before reinstalling Windows, were the same or different?

Because there isn't a lot of information regarding the crashes, I'd like to go a bit of a different path than I usually do. I would like you to run driver verifier so we can get a direction/confirmation on any suspicion. If the first dump caused by driver verifier shows no driver, hardware is the probable cause. If there is a driver, update/reinstall/remove the driver and run driver verifier again, this happens at least a few times to see if different drivers cause problems or the same driver is causing the problem repeatedly. Different drivers is an indication of hardware problems.

Due to risks involved with driver verifier there is another option, safe mode, but it will take more of your time. If any problem in safe mode occurs, it is very likely hardware is the cause.

Please let me know which option you'd like to do.

Sorry, I thought I had included the risks.

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.


Please note, driver verifier needs to run for a reasonably extended period of time, see the quote below for all information regarding configuring driver verifier and what to do in situations where the system crashes.

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

That's correct. You do not select Microsoft drivers.