Windows 10: BSOD error keeps occuring.

2: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************UNEXPECTED_KERNEL_MODE_TRAP 7fThis means a trap occurred in kernel mode, and it's a trap of a kindthat the kernel isn't allowed to have/catch bound trap or thatis always instant death double fault. The first number in thebugcheck params is the number of the trap 8 = double fault, etcConsult an Intel x86 family manual to learn more about what thesetraps are. Here is a *portion* of those codes:If kv shows a taskGate use .tss on the part before the colon, then kv.Else if kv shows a trapframe use .trap on that valueElse .trap on the appropriate frame will show where the trap was taken on x86, this will be the ebp that goes with the procedure KiTrapEndifkb will then show the corrected stack.Arguments:Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULTArg2: ffffa201bda86e70Arg3: 0000000000000000Arg4: ffff91830e51d676Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2092 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-LHOVPK3 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 3502 Key : Analysis.Memory.CommitPeak.Mb Value: 75 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 7fBUGCHECK_P1: 8BUGCHECK_P2: ffffa201bda86e70BUGCHECK_P3: 0BUGCHECK_P4: ffff91830e51d676TRAP_FRAME: ffffa201bda86e70 -- .trap 0xffffa201bda86e70NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000002rdx=ffffed063a1ee980 rsi=0000000000000000 rdi=0000000000000000rip=ffff91830e51d676 rsp=0000000000000000 rbp=ffffed063a1edf30 r8=0000000000000000 r9=ffffa201bd701180 r10=ffff91830548b1c0r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl zr na po ncffff9183`0e51d676 c3 retResetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXWINLOGON: 1PROCESS_NAME: SystemSTACK_TEXT: ffffa201`bda86d28 fffff804`499efa29 : 00000000`0000007f 00000000`00000008 ffffa201`bda86e70 00000000`00000000 : nt!KeBugCheckExffffa201`bda86d30 fffff804`499ea843 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69ffffa201`bda86e70 ffff9183`0e51d676 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c300000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff9183`0e51d676SYMBOL_NAME: nt!KiDoubleFaultAbort+2c3MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 2c3FAILURE_BUCKET_ID: 0x7f_8_nt!KiDoubleFaultAbortOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {d1f8395a-8c58-45da-6ebf-e8bb4aad2fc5}Followup: MachineOwner---------

:)

 

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 issue after fixing another BSOD error

Hi Williams,

There are several reasons why BSOD occur, which has different resolution. To check for any corruption or the integrity of your computer's Windows, we suggest that you perform a
Check Disk by following these steps:

• Type cmd in the search bar.
• Right-click on the Command Prompt, then Run as administrator.
  
• Type chkdsk x: /r, the /r command will fix errors found on the disk.

Let us know if you need further assistance.

 

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.