Windows 10: Getting BSOD once in a day. It is frustrating. It would be great if someone can help

Details from the whocrashed Application


On Sat 26-12-2020 7.02.16 PM your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\122620-12859-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5780
Bugcheck code: 0x9F 0x3, 0xFFFFD98C7E18D360, 0xFFFF938891CCF750, 0xFFFFD98C9457C050
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 16-12-2020 3.19.43 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121620-10468-01.dmp
This was probably caused by the following module: watchdog.sys watchdog+0x3AD0
Bugcheck code: 0x113 0x19, 0x2, 0x10DE, 0x1C8C
Error: VIDEO_DXGKRNL_FATAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the dxg kernel has detected a violation.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 09-12-2020 11.08.45 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120920-12375-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5780
Bugcheck code: 0x154 0xFFFF960788027000, 0xFFFFE400607AEF30, 0x2, 0x0
Error: UNEXPECTED_STORE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the store component caught an unexpected exception.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 28-11-2020 5.07.36 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112820-11578-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0x9F 0x3, 0xFFFFCA0200A03060, 0xFFFFEE0D14C2F750, 0xFFFFCA0217F078B0
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time.
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 23-11-2020 10.37.28 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112320-10046-01.dmp
This was probably caused by the following module: watchdog.sys watchdog+0x3AD0
Bugcheck code: 0x113 0x19, 0x2, 0x10DE, 0x1C8C
Error: VIDEO_DXGKRNL_FATAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the dxg kernel has detected a violation.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


Link for the dumpfiles : https://drive.google.com/file/d/1yQu2IO6qJ3p3hhzLKb5piG_2f0XEq_8D/view?usp=sharing

:)

 

OMG I am back after a day of total frustration

I believe you, it is ideed frustrating. Then again everything that involves calling support is frustrating. Is your problem solved by now or what will be the next steps?

 

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.

 

help to remote connect

not sure how to use both programs u 2 suggested, i need more helpful steps thanks