Windows 10: Out of ideas what causing my BSOD errors...

Hello everybody,


So I’ve got a problem that persists for two years now, but as it didn’t get worse I could live with it. Now I’ve got time so I’m trying to figure out what the hell is going on with my PC.

The symptoms:

Rare BSOD errors, very unpredictable without any consistency. What I mean by that is it doesn’t matter if I play some game on ultra graphics Project Cars, GTA 5, Watch Dogs sometimes it crashes in the first 5 seconds or after 10 minutes or I play 2 hours without an issue. Sometimes I play 4 hours and when I’m back at the desktop it crashes immediately. But it is not connected to only gaming although it is more frequent then, I might just browse in Chrome, or I’m working in the house and only Spotify is playing… There are times when it happens every other day, a couple of times a day and then nothing for a month.

Logs, memory dump, other debugging results:

Just to be clear before I did a windows clean install I’ve got all sorts of error messages when BSOD occurred, after that I get a lot fewer kinds. Running WhoCrashed on the dumps:


This was probably caused by the following module:ntoskrnl.exe nt+0x3F3EA0

Bugcheck code: 0xD1 0xFFFFF8027AD07CE7, 0xFF, 0xC4, 0xFFFFF8027AD07CE7

Error:DRIVER_IRQL_NOT_LESS_OR_EQUAL


This was probably caused by the following module:ntkrnlmp.exe nt!setjmpex+0x8279

Bugcheck code: 0xD1 0xFFFFF8027AD07CE7, 0xFF, 0xC4, 0xFFFFF8027AD07CE7

Error:DRIVER_IRQL_NOT_LESS_OR_EQUAL


This was probably caused by the following module:ntoskrnl.exe nt+0x3F3EA0

Bugcheck code: 0xD1 0xFFFFF80280078DD7, 0xFF, 0xE4, 0xFFFFF80280078DD7

Error:DRIVER_IRQL_NOT_LESS_OR_EQUAL


This was probably caused by the following module:ntoskrnl.exe nt+0x3F3EA0

Bugcheck code: 0x7F 0x8, 0xFFFF8600321DCE50, 0x321C7D1F, 0xFFFFF8021151BF4C

Error:UNEXPECTED_KERNEL_MODE_TRAP


This was probably caused by the following module:ntoskrnl.exe nt+0x3F3EA0

Bugcheck code: 0x9C 0x80000001, 0xFFFFBF8058FF8B10, 0x0, 0x0

Error:MACHINE_CHECK_EXCEPTION


There were a couple of WHEA_UNCORRECTABLE_ERROR as well, but haven’t saved the dumps from them.

The whole dumps uploaded to onedrive:
https://1drv.ms/u/s!Am86NGE33yonbkDJn43uB5d3x4Q?e=1FscG0

PC specs:

Motherboard: ASRock Z170 Extreme4

CPU: Intel Core i7 6700K

RAM: Corsair Vengeance 16GB DDR4 2x8GB

Graphics card: Gigabyte GTX 970 4GB

Power: FSP 650W Raider 80

SSD: Kingston 120GB SATA3

HDD: 1TB WD 3.5" Caviar Blue SATA3 WD10EZEX


More details in CPU-Z report: https://1drv.ms/u/s!Am86NGE33yoncyXFJGLOYYM1MMQ


Temperature and voltage data:

I’ve logged a couple of values with SpeedFan to see if there is anything suspicious before a crash, you can find them here:

https://docs.google.com/spreadsheets/d/1mupygfoMQROR7vnqZjYkEXh4mdbyN2_nn-H4XLQR9wQ/edit#gid=1426000315


I’ve started the logs right before I started playing F1 2018, and some 20 minutes later I’ve got a BSOD, I don’t see any anomalies.

Attempts to fix it:

• 
  First off, I’ve updated every driver, nothing changed
  
  
• 
  Moved my graphics card to different PCI slot and also moved around with the RAM sticks tried every permutation, with one RAM, two RAMs in every slot
  
  
• 
  Ran chkdisk, sfc /scannow all good
  
  
• 
  Windows was up-to-date
  
  
• 
  Updated the BIOS
  

After that I’ve realized that I need a to go deeper, so I’ve continued with these steps:

• 
  Made a completely clean install of Windows
  
  
• 
  Ran MemTest86, 4 passes, all tests free version, each stick separately, no errors found
  
  
• 
  Removed the CMOS battery for 3 hours to reset BIOS
  
  
• 
  Checked both SSD and HDD with Crystal Disk Mark and both are in good condition
  
  
• 
  Ran Mark3D benchmarking, with no issues, no BSOD
  
  
• 
  Ran Prime95 torture test for 4 hours, with no problems
  

Other things might worth mentioning:

• 
  I’ve never overclocked anything
  
  
• 
  The PC is protected by Nod32 Internet Security from day 0
  
  
• 
  Switching parts wasn’t an option as I didn’t want to mess around with that during COVID
  

Soo… yes, this is it in a nutshell, I’m pretty much out of ideas so if anyone has any idea I would be grateful for some help here. Thank you.

:)

 

BSOD Hardware Caused???

they do weird things like that, which all seem like something else is failing.
One of the worst things to diagnose, they seem to only quit when they want to.

Memtest is a good next step, if you rule out RAM and Power Supply make sure you disconnect all unnecessary peripherals and try to start the system with as little hardware as possible, if it works then, you can narrow down the culprit by trial and error.

the follow was taken from some website:

It's very difficult to determine if a failure is caused by the CPU because many other components can cause the same symptom when they fail.

1. System fails to boot
2. System re-boots intermittently
3. General Protection Fault
4. Illegal Operation
5. Stop Error, or BSoD (Blue Screen OfDeath)

Actually, CPUs rarely fail, and about the only way to determine if the CPU is causing the failure is to swap it out with a known working CPU of the same type and speed. Since this is difficult, the best bet is to first rule out every other possibility.

Before suspecting the CPU, rule out all the possibilities listed below.

1. The Operating System
2. A peripheral port device
3. A bad memory module
4. The hard disk drive
5. The power supply
6. The motherboard

If you have ruled out out all the other possibilities, investigate the items listed below.

1. Overheating
2. A short circuit
3. ESD

 

BSOD - Registry Error

Your BSOD code is 0X000000051

Here's the Google search I did for it: https://www.google.com/search?q=0x0...j5.399j0j7&sourceid=chrome&es_sm=122&ie=UTF-8

There is a hotfix available that might help, https://support.microsoft.com/en-us/kb/810558

This thread makes a few good suggestions too: http://www.sevenforums.com/bsod-hel...dows-7-pro-sp1-registry-error-0x00000051.html

+1 to listing your full system specs, OS version, etc. I did only look at your BSOD log file.

Run a Diskchk /R (I know you already ran one, so you can skip this)

Run SFC /SCANNOW

Report back.

 

BSOD Hardware Caused???

It is not overheating - CPU runs 60*C in games.
Short Circuit - EXTREAMLY UNLIKELY