F5F Stay Refreshed Hardware Desktop Frequent crashes happen without clear cause :( I don't know what's wrong.

Frequent crashes happen without clear cause :( I don't know what's wrong.

Frequent crashes happen without clear cause :( I don't know what's wrong.

N
NoxerPlays
Junior Member
15
05-03-2022, 01:10 AM
#1
Hey there, this was my first attempt (during lockdown), and it’s been a bit unstable. I went against my better judgment by choosing to buy a prebuilt Dell—there’s only one place to blame. Here’s the link to my build: https://ca.pcpartpicker.com/list/dhh7qm I just upgraded to a 1000w PSU gen 5 and an RTX 4090. The machine crashes under light stress in Unreal Engine. I’m seeing CLOCK_WATCHDOG and WHEA_UNCORRECTABLE errors. It looks like a processor issue, though I’ve replaced the chip before—probably a motherboard fault. All diagnostics pass except memory checks, which kept looping until I canceled them. I have an extended warranty on the motherboard, but to use it, I need to leave my workstation at Canada Computers for a few days to fix the problem. I wish I knew what tools they use so I can check ahead of time. Any thoughts on what might be wrong? Here’s an analysis of the MEMORY.dmp file from Microsoft ® Windows Debugger v10.0.25200.1003. AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump: Kernel address space is available, User address space may not be. ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNT, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff8025fc00000 PsLoadedModuleList = 0xfffff8026082a2b0 Debug session time: Thu Nov 24 12:04:38.297 2022 (UTC -5:00) System Uptime: 0 days 0:15:36.937 Loading Kernel Symbols ............................................................... .....Page fd434e not present in the dump file. Type ".hh dbgerr004" for details ........................................................... ................................................................ ................ Loading User Symbols PEB is paged out (Peb.Ldr = 000000d4...53199018). Type ".hh dbgerr001" for details Loading unloaded module list........ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff802`5fff92d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9f00`609cfc90=0000000000000101 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) A normal clock interrupt wasn’t received on a secondary processor in an MP system within the allowed time. This suggests the CPU is stuck and not handling interrupts. Details: Arg1: 000000000000000c, Clock interrupt timeout in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: ffff9f0060d48180 PRCB address of the hung processor. Arg4: 0000000000000009, index of the stuck processor. Debugging Info: Key values: Analysis.CPU.mSec 1702 Key Analysis.DebugAnalysisManager Value Create Key Analysis.Elapsed.mSec 1736 Key IO.Other.Mb 0 Key Memory.CommitPeak.Mb 0 Key Init.CPU.mSec 249 Key Init.Elapsed.mSec 4247 Key Memory.CommitPeak.MB 101 Key Bugcheck.Code.DumpHeader 0x101 Key Code.KiBugCheckData 0x101 Key Register 0x101 Key WER.OS.Branch vb_release Key WER.OS.Timestamp 2019-12-06T14:06:00Z Key OS.Version 10.0.19041.1 File in CAB: MEMORY.DMP BUGCHECK_CODE 101 BUGCHECK_P1: c BUGCHECK_P2: 0 BUGCHECK_P3: ffff9f0060d48180 BUGCHECK_P4: 9 FAULTING_PROCESSOR: 9 ProcessName: MsMpEng.exe ... Stack text: ffff9f00`609cfc88 fffff802`6005bdf2 ... More debug info available. ************ END ANALYSIS *** If you need further help, let me know.
N
NoxerPlays
05-03-2022, 01:10 AM #1

Hey there, this was my first attempt (during lockdown), and it’s been a bit unstable. I went against my better judgment by choosing to buy a prebuilt Dell—there’s only one place to blame. Here’s the link to my build: https://ca.pcpartpicker.com/list/dhh7qm I just upgraded to a 1000w PSU gen 5 and an RTX 4090. The machine crashes under light stress in Unreal Engine. I’m seeing CLOCK_WATCHDOG and WHEA_UNCORRECTABLE errors. It looks like a processor issue, though I’ve replaced the chip before—probably a motherboard fault. All diagnostics pass except memory checks, which kept looping until I canceled them. I have an extended warranty on the motherboard, but to use it, I need to leave my workstation at Canada Computers for a few days to fix the problem. I wish I knew what tools they use so I can check ahead of time. Any thoughts on what might be wrong? Here’s an analysis of the MEMORY.dmp file from Microsoft ® Windows Debugger v10.0.25200.1003. AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump: Kernel address space is available, User address space may not be. ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNT, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff8025fc00000 PsLoadedModuleList = 0xfffff8026082a2b0 Debug session time: Thu Nov 24 12:04:38.297 2022 (UTC -5:00) System Uptime: 0 days 0:15:36.937 Loading Kernel Symbols ............................................................... .....Page fd434e not present in the dump file. Type ".hh dbgerr004" for details ........................................................... ................................................................ ................ Loading User Symbols PEB is paged out (Peb.Ldr = 000000d4...53199018). Type ".hh dbgerr001" for details Loading unloaded module list........ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff802`5fff92d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9f00`609cfc90=0000000000000101 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) A normal clock interrupt wasn’t received on a secondary processor in an MP system within the allowed time. This suggests the CPU is stuck and not handling interrupts. Details: Arg1: 000000000000000c, Clock interrupt timeout in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: ffff9f0060d48180 PRCB address of the hung processor. Arg4: 0000000000000009, index of the stuck processor. Debugging Info: Key values: Analysis.CPU.mSec 1702 Key Analysis.DebugAnalysisManager Value Create Key Analysis.Elapsed.mSec 1736 Key IO.Other.Mb 0 Key Memory.CommitPeak.Mb 0 Key Init.CPU.mSec 249 Key Init.Elapsed.mSec 4247 Key Memory.CommitPeak.MB 101 Key Bugcheck.Code.DumpHeader 0x101 Key Code.KiBugCheckData 0x101 Key Register 0x101 Key WER.OS.Branch vb_release Key WER.OS.Timestamp 2019-12-06T14:06:00Z Key OS.Version 10.0.19041.1 File in CAB: MEMORY.DMP BUGCHECK_CODE 101 BUGCHECK_P1: c BUGCHECK_P2: 0 BUGCHECK_P3: ffff9f0060d48180 BUGCHECK_P4: 9 FAULTING_PROCESSOR: 9 ProcessName: MsMpEng.exe ... Stack text: ffff9f00`609cfc88 fffff802`6005bdf2 ... More debug info available. ************ END ANALYSIS *** If you need further help, let me know.

N
nameehasan
Member
231
05-03-2022, 07:11 AM
#2
Absolutely, you'll likely want to run some tests before shipping it off. They probably plan to check stability using just your motherboard and other reliable components. If the issue doesn’t repeat, they’ll probably assume it’s not the motherboard itself. If you dropped everything, the next step would be for the technician to run more detailed checks—possibly at an extra cost. For beginners, you probably don’t have the right tools to diagnose hardware problems properly. A place like CC can provide genuine parts and quickly replace components until the system works again.
N
nameehasan
05-03-2022, 07:11 AM #2

Absolutely, you'll likely want to run some tests before shipping it off. They probably plan to check stability using just your motherboard and other reliable components. If the issue doesn’t repeat, they’ll probably assume it’s not the motherboard itself. If you dropped everything, the next step would be for the technician to run more detailed checks—possibly at an extra cost. For beginners, you probably don’t have the right tools to diagnose hardware problems properly. A place like CC can provide genuine parts and quickly replace components until the system works again.

V
Vinger
Junior Member
11
05-04-2022, 04:37 PM
#3
Thanks for the feedback.
V
Vinger
05-04-2022, 04:37 PM #3

Thanks for the feedback.

P
PheonixMMC
Member
174
05-04-2022, 10:59 PM
#4
I recall reading about M.2 slots and their compatibility with different components. Some slots connect to the CPU, others to the GPU, and it seems certain configurations might lead to problems. I might have overlooked this, assuming it didn’t affect 11th generation CPUs like the Z590. Could this be related to the issues I’m experiencing? I checked CPUz and GPUz to see if anything unusual appeared. My GPU shows a PCIe 4.0 interface version 16, which appears correct.
P
PheonixMMC
05-04-2022, 10:59 PM #4

I recall reading about M.2 slots and their compatibility with different components. Some slots connect to the CPU, others to the GPU, and it seems certain configurations might lead to problems. I might have overlooked this, assuming it didn’t affect 11th generation CPUs like the Z590. Could this be related to the issues I’m experiencing? I checked CPUz and GPUz to see if anything unusual appeared. My GPU shows a PCIe 4.0 interface version 16, which appears correct.

S
SmartBoysFart
Member
211
05-06-2022, 10:55 AM
#5
S
SmartBoysFart
05-06-2022, 10:55 AM #5

C
CLUTCHOFFAME_
Junior Member
3
05-13-2022, 10:09 PM
#6
I'm not sure about the store warranty details for opening or reseating the PC. I hope the spare CPU resolves the problem, but I'm not sure what to do with the original CPU. Could you share photos of the bent pins?
C
CLUTCHOFFAME_
05-13-2022, 10:09 PM #6

I'm not sure about the store warranty details for opening or reseating the PC. I hope the spare CPU resolves the problem, but I'm not sure what to do with the original CPU. Could you share photos of the bent pins?