Windows 10: Varios BSOD errors - Crash at any point

Hi everyone

I have had various BSOD errors over the past few weeks, occurring multiple times a day, I've just about had enough of it.

I believe these BSOD errors started occurring when I updated to the August Windows 10 patch. I tried to complete a system restore, but had no success. Either a BSOD or an error would appear.

I have tried running each stick of RAM individually, still had BSOD's. Also used Windows Memory Diagnostic, all ok. I have also checked my SSD, which has my OS on, using SanDisk software, and it shows it's health as normal. I have also tried various command prompts; SFC Scan, Health check, are there any others that you would advise doing?

As I had my files backed up, I decided to do a clean reboot of Windows 10 OS - Pro N. So right now I still have these BSOD's at sporadic times (I haven't noticed a pattern).

Have uploaded a zip, post reboot.

Any help would be greatly appreciated, so I can get back to gaming! *Biggrin

Thanks,



:)

 

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.

 

Flickering screen at startup, crashes, and BSOD after instaling new GPU

Here are some that are close to the BSOD crash time but i dont think they have to do anything with the BSOD.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.