Question PC hangs constantly. Occasional BSOD

Cybereyes

Distinguished
Nov 21, 2013
30
0
18,530
I built a computer a couple of years ago and it’s started to act up. I think I’ve narrowed it down to potentially being my graphics card or the CPU of all things. Neither are outcomes I’m happy for but I’m almost certain this is hardware related and those are the most likely culprits.

Motherboard: MEG X570 ACE
CPU: AMD Ryzen 9 5950x
RAM: Gskill DDR4 4000Mhz 2x32. (I had 4x32 but two sticks died)
SSD: 970 EVO 2000GB x3
SATA hard drive 8000GB
Graphics: Nvidia GeForce RTX 3080ti

It started out as the PC not waking up the next day when I went to log on. All the lights were flashing like as if it was in a sleep mode but nothing woke it up except a hard reset. This happened once before after a windows update and eventually I got it sorted out but honestly don’t recall how. Anyway this time nothing helped. Eventually the PC started hanging while I was one it. It would just freeze completely and nothing would help but a hard reset. Occasionally it would BSOD with either a DPC watchdog violation or a driver verifier problem. I turned off driver verifier, not sure how it was even on anyway, but it was faster after that. I thought it was fixed but then it just froze again.

I’ve updated the BIOS, ran MEMtest, ran OCCT tests, ran self tests on all 3 of the SSDs I have, and even did a full Windows reinstall on a different partition. I also did a Windows reinstall on the regular partition. Nothing has worked or identified the problem. All tests come back perfect. I even replaced the coolant in my system thinking it may be causing heating problems even though all my systems checks say the temps are great. It’s a complete mystery to me.

The only thing I have left is analyzing the .dump files which I’m honestly clueless about. I’m about to learn as much as I can about reading dump files if I can ever get this thing fixed. I downloaded winDmp and this program called everything. Also a program called blue screen view. I can’t make heads or tails out of it. I do have a lot of data and sure the problem is in the .dmp data but I need some help. I have the data from two dumps I will display below.

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.468 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 43

Microsoft (R) Windows Debugger Version 10.0.27793.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\031425-19828-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff801`65c00000 PsLoadedModuleList = 0xfffff801`6682a2b0
Debug session time: Fri Mar 14 01:10:33.438 2025 (UTC - 4:00)
System Uptime: 0 days 2:24:33.040
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols

Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`65ffbca0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8d81`b39b6e20=0000000000000133
13: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff801668fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x18561b, File: 0x1857e3 - C:\ProgramData\Dbg\sym\BTHport.sys\70388B82185000\BTHport.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1281

Key : Analysis.Elapsed.mSec
Value: 2297

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 218

Key : Analysis.Init.Elapsed.mSec
Value: 16427

Key : Analysis.Memory.CommitPeak.Mb
Value: 92

Key : Analysis.Version.DbgEng
Value: 10.0.27793.1000

Key : Analysis.Version.Description
Value: 10.2410.02.02 amd64fre

Key : Analysis.Version.Ext
Value: 1.2410.2.2

Key : Bugcheck.Code.LegacyAPI
Value: 0x133

Key : Bugcheck.Code.TargetModel
Value: 0x133

Key : Failure.Bucket
Value: 0x133_ISR_nt!KeAccumulateTicks

Key : Failure.Hash
Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Key : Stack.Pointer
Value: ISR

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff801668fb320

BUGCHECK_P4: 0

FILE_IN_CAB: 031425-19828-01.dmp

FAULTING_THREAD: ffffc00afa568080

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffd38881d49d90 -- (.trap 0xffffd38881d49d90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=df0a50bb35640000
rdx=00000000000c00e1 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80165ebfd06 rsp=ffffd38881d49f20 rbp=0000000000000002
r8=000000000000082f r9=00000000000000e1 r10=0000fffff80165ef
r11=ffffd38881d49ef0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KeFlushMultipleRangeTb+0x166:
fffff801`65ebfd06 85c0 test eax,eax
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8d81`b39b6e18 fffff801`66043814 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`668fb320 : nt!KeBugCheckEx
ffff8d81`b39b6e20 fffff801`65e813c3 : 00001adc`353d5ed8 ffff8d81`b39c0180 00000000`00000000 ffff8d81`b39c0180 : nt!KeAccumulateTicks+0x1bfbf4
ffff8d81`b39b6e80 fffff801`65e80eaa : ffffc00a`fa4d9900 ffffd388`81d49e10 ffffc00a`fa44b000 ffffffff`ffffffff : nt!KeClockInterruptNotify+0x453
ffff8d81`b39b6f30 fffff801`65f3e965 : ffffc00a`fa4d9900 fffff801`65f22fb7 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1a
ffff8d81`b39b6f60 fffff801`65ffdc3a : ffffd388`81d49e10 ffffc00a`fa4d9900 00000000`00000003 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff8d81`b39b6fb0 fffff801`65ffe407 : 00000000`757c9565 ffff8d81`b39c3088 ffffd388`81d49ec1 ffe9c440`ea4fb804 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd388`81d49d90 fffff801`65ebfd06 : 00000000`00000000 00000000`00000002 00000000`00000002 fffff2da`807a1000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd388`81d49f20 fffff801`65eea10f : ffffd388`81d4a520 00000000`00000000 ffffd879`6d403d00 ffffd388`81d4a520 : nt!KeFlushMultipleRangeTb+0x166
ffffd388`81d49fc0 fffff801`65e6dd2d : 00000000`00000004 00000000`00000000 ffff8d81`b85c1100 81000001`10788843 : nt!MiAgeWorkingSetTail+0xef
ffffd388`81d4a000 fffff801`65e6d94b : ffffd86c`00000000 ffff8d81`b85c1100 00000000`00000000 ffffd388`81d4a570 : nt!MiWalkPageTablesRecursively+0xc6d
ffffd388`81d4a0a0 fffff801`65e6d94b : ffffd86c`361e5b50 ffff8d81`b85c1100 00000000`00000001 ffffd388`81d4a580 : nt!MiWalkPageTablesRecursively+0x88b
ffffd388`81d4a140 fffff801`65e6d94b : ffffd86c`361e5000 ffff8d81`b85c1100 00000000`00000002 ffffd388`81d4a590 : nt!MiWalkPageTablesRecursively+0x88b
ffffd388`81d4a1e0 fffff801`65e6a94b : 00000000`00000000 ffff8d81`b85c1100 ffffd388`00000003 ffffd388`81d4a5a0 : nt!MiWalkPageTablesRecursively+0x88b
ffffd388`81d4a280 fffff801`65e6a231 : ffffd388`81d4a520 00000000`00000000 00000000`00000001 00000000`00000000 : nt!MiWalkPageTables+0x36b
ffffd388`81d4a380 fffff801`65e69cae : ffff8d81`b85c1100 ffffd388`81d4aa00 00000000`00000080 00000000`00000000 : nt!MiAgeWorkingSet+0x3d1
ffffd388`81d4a890 fffff801`65e690e7 : 00000000`00000000 ffffd388`81d4aa40 ffffd388`81d4aa00 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0x73e
ffffd388`81d4a980 fffff801`65e663b0 : fffff801`66850c00 ffffd388`81d4aa40 00000000`0000215a ffff8d81`00000281 : nt!MiProcessWorkingSets+0x227
ffffd388`81d4aa20 fffff801`65fb8837 : 00000000`00000003 00000000`00000003 00000000`ffffffff ffff8d81`b33d8180 : nt!MiWorkingSetManager+0x110
ffffd388`81d4aae0 fffff801`65f265f5 : ffffc00a`fa568080 00000000`00000080 fffff801`65fb86e0 c9334528`244c2148 : nt!KeBalanceSetManager+0x157
ffffd388`81d4abd0 fffff801`660048d8 : ffff8d81`b35c9180 ffffc00a`fa568080 fffff801`65f265a0 0f444024`54b70f00 : nt!PspSystemThreadStartup+0x55
ffffd388`81d4ac20 00000000`00000000 : ffffd388`81d4b000 ffffd388`81d44000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nt!KeAccumulateTicks+1bfbf4

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.2965

STACK_COMMAND: .process /r /p 0xffffc00afa4a3040; .thread 0xffffc00afa568080 ; kb

BUCKET_ID_FUNC_OFFSET: 1bfbf4

FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

DUMP2

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff890f964918c0, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000baa00000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000000080b, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

Mini Kernel Dump does not contain unloaded driver list
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
Mini Kernel Dump does not contain unloaded driver list
Mini Kernel Dump does not contain unloaded driver list

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1281

Key : Analysis.Elapsed.mSec
Value: 8623

Key : Analysis.IO.Other.Mb
Value: 7

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 21

Key : Analysis.Init.CPU.mSec
Value: 484

Key : Analysis.Init.Elapsed.mSec
Value: 25696

Key : Analysis.Memory.CommitPeak.Mb
Value: 87

Key : Analysis.Version.DbgEng
Value: 10.0.27793.1000

Key : Analysis.Version.Description
Value: 10.2410.02.02 amd64fre

Key : Analysis.Version.Ext
Value: 1.2410.2.2

Key : Bugcheck.Code.LegacyAPI
Value: 0x124

Key : Bugcheck.Code.TargetModel
Value: 0x124

Key : Dump.Attributes.AsUlong
Value: 0x18

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: LKD_0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

Key : Failure.Hash
Value: {f59f17e7-f24e-04f5-3f16-e9425b2acba5}


BUGCHECK_CODE: 124
 
Last edited by a moderator:
Welcome to the forums, newcomer!

Pass on the .dmp files for us to go through. You forgot to mention the make, model and age of your PSU. For the sake of relevance, you should mention the BIOS version you're on for your motherboard.

By any chance are you on Windows 10 20H1? If so, you should be on version 22H2.