Windows 10: 2 BSOD's and a Hardware Error

I have recently received two BSOD's and Hardware error's, I'm an unsure of what is the overall cause of these.




First Error:


Source

Windows


Summary

Shutdown unexpectedly


Date

‎2/‎5/‎20213:55 AM


Status

Reportsent


Problem signature

[COLOR=rgba0, 0, 0, 1]Problem Event Name: BlueScreen[/COLOR]

Code: a

Parameter1: 0

Parameter2: 2

Parameter3: 1

Parameter4: fffff8000924c1f0

OS version: 10_0_19042

ServicePack: 0_0

Product: 768_1

OSVersion: 10.0.19042.2.0.0.768.101

LocaleID: 1033


Extra information about the problem

[COLOR=rgba0, 0, 0, 1]Bucket ID: AV_nt!KiTryLocalThreadSchedule[/COLOR]


Second Error:

Source


Windows



Summary

Shutdown unexpectedly



Date

‎2/‎5/‎20214:25 AM



Status

Reportsent



Problem signature

Problem Event Name: BlueScreen

Code: 124

Parameter1: 0

Parameter2: ffff890f51f8c028

Parameter3: b2000000

Parameter4: 30005

OSversion: 10_0_19042

ServicePack: 0_0

Product: 768_1

OS Version: 10.0.19042.2.0.0.768.101

LocaleID: 1033



Extra information about the problem


Bucket ID: 0x124_0_GenuineIntel_PROCESSOR_Mae_BANK0_MSCOD0003_MCACOD0005_PCC_UC_IMAGE_GenuineIntel.sys



Hardware Error:

Source


Windows



Summary

Hardwareerror



Date

‎2/‎6/‎20213:41 AM



Status

Reportsent



Description

A problem with your hardware caused Windows to stop workingcorrectly.



Problem signature

Problem Event Name: LiveKernelEvent

Code: 117

Parameter1: ffffbf8945c73050

Parameter2: fffff8026a7f71c0

Parameter3: 0

Parameter4: 5f8

OSversion: 10_0_19042

ServicePack: 0_0

Product: 768_1

OSVersion: 10.0.19042.2.0.0.768.101

LocaleID: 1033



Extra information about the problem

Bucket ID: LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys_Turing


Serverinformation: d4328416-5ec9-482b-9296-c5dad06885e3

:)

 

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???

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

 

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.