Windows 10: Frequent apparently random bluescreening; possibly driver-related dumps included

I'm having frequent sudden bluescreening sometimes twice or three times a day, that seems to be driver-related, but I'm struggling to pin it down. I've done the following things:- run chkdsk; came back with no issues- did a memory check; came back with no issues- turned on Driver Validation, which caused the computer to always instantly bluescreen on boot before I went in and shut it off again via Safe ModeHowever, Driver Validation's bluescreen message never identified a particular driver as being the issue though it did clearly say DRIVER VALIDATION RETURNED EXCEPTION or whatever it is ev

:)

 

Frequent bluescreens with no apparent reason

Hello Rutger,

Most blue screen errors are caused by faulty or out-of-date drivers, or memory problems which seems to be true based on the minidumps you provided in your original post.

At this point in time, what we want to do is perform troubleshooting to further isolate the issue and identify what's causing the blue screen errors so that we can find a permanent fix. We suggest running the Memory Diagnostic Tool to help us check for possible
memory problems in your PC, use the Driver Verifier to find faulty drivers, and run the System File Checker (SFC.exe) to automatically find and fix corrupted system files.

To run Windows Memory Diagnostics:

• Click on Start, Search, or Cortana, and then type
  memory.
• Click on Windows Memory Diagnostics Desktop app.
• If you choose Restart now and check for problems, make sure that you have saved any work in progress in your PC. If you don't have free time, you can choose
  Check for problems the next time I start my computer to run the tool the next time your start your PC.

To use the Driver Verifier, refer to this forum article by ZigZag3143 (MS-MVP)
for the steps.

To use the System File Checker tool, refer to this support article for the steps.

Additionally, it would also help if you could remove peripherals when starting your PC. Peripherals such as external hard drives, dongles, or USBs are also known to cause blue screen errors due to their built-in drivers.

Let us know how it turns out.

 

Frequent bluescreens with no apparent reason

Hello Rutger,

Most blue screen errors are caused by faulty or out-of-date drivers, or memory problems which seems to be true based on the minidumps you provided in your original post.

At this point in time, what we want to do is perform troubleshooting to further isolate the issue and identify what's causing the blue screen errors so that we can find a permanent fix. We suggest running the Memory Diagnostic Tool to help us check for possible
memory problems in your PC, use the Driver Verifier to find faulty drivers, and run the System File Checker (SFC.exe) to automatically find and fix corrupted system files.

To run Windows Memory Diagnostics:

• Click on Start, Search, or Cortana, and then type
  memory.
• Click on Windows Memory Diagnostics Desktop app.
• If you choose Restart now and check for problems, make sure that you have saved any work in progress in your PC. If you don't have free time, you can choose
  Check for problems the next time I start my computer to run the tool the next time your start your PC.

To use the Driver Verifier, refer to this forum article by ZigZag3143 (MS-MVP)
for the steps.

To use the System File Checker tool, refer to this support article for the steps.

Additionally, it would also help if you could remove peripherals when starting your PC. Peripherals such as external hard drives, dongles, or USBs are also known to cause blue screen errors due to their built-in drivers.

Let us know how it turns out.

 

Constant bluescreens - still not fixed

I don't think you understood my issue - my bluescreens are random, so I can't do a clean boot and provoke a bluescreen. I am not sure what the steps you suggested have anything to do with my problem and it is not clear how it will help. The PC does boot
up normally, it just crashes randomly during the day.

I am pretty sure the issue is related to a driver that could be incompatible with Win 10. Please check the older threads to further understand the issue.

Thank you.