F5F Stay Refreshed Hardware Desktop Have trouble ending a computer crash?

Have trouble ending a computer crash?

Have trouble ending a computer crash?

Pages (3): 1 2 3 Next
D
DatDrop
Member
190
06-14-2021, 05:40 PM
#1
Hi guys, I recently updated my Motherboard and CPU, however its only giving crashing on me all the time! Hardware overview: - Asus RPG STROX Z590-E Gaming WiFi ( NEW ) - I9-11900K ( NEW ) - WD Black sn850 1TB m.2 ( NEW ) (installed OS) - Corsair 850 Watt supply - Samsung NVME SSD 1TB - MSI 2080TI - Noctua NH-D15 cooler I am getting some weird errors/crashes: I use digital out for my headphone after a few minutes/hours it just suddenly sends out insane noise and no audio output. When i mute the PC it goes away. The PC randomly crashes. Sometimes my pc just freezes, sometimes the screen turns black and the fans spin up. I get a BSOD with the message: "CLOCK_WATCHDOG_TIMEOUT", i read it is oc related. However i turned all the automatic OC off and am running everything on default settings (as far as i know) Does someone have any clue what i can do to solve this? Thanks!
D
DatDrop
06-14-2021, 05:40 PM #1

Hi guys, I recently updated my Motherboard and CPU, however its only giving crashing on me all the time! Hardware overview: - Asus RPG STROX Z590-E Gaming WiFi ( NEW ) - I9-11900K ( NEW ) - WD Black sn850 1TB m.2 ( NEW ) (installed OS) - Corsair 850 Watt supply - Samsung NVME SSD 1TB - MSI 2080TI - Noctua NH-D15 cooler I am getting some weird errors/crashes: I use digital out for my headphone after a few minutes/hours it just suddenly sends out insane noise and no audio output. When i mute the PC it goes away. The PC randomly crashes. Sometimes my pc just freezes, sometimes the screen turns black and the fans spin up. I get a BSOD with the message: "CLOCK_WATCHDOG_TIMEOUT", i read it is oc related. However i turned all the automatic OC off and am running everything on default settings (as far as i know) Does someone have any clue what i can do to solve this? Thanks!

L
lizzard89
Senior Member
707
06-14-2021, 07:33 PM
#2
Turn off XMP if enabled. Please upload all crash dump files so I can analyze them.
L
lizzard89
06-14-2021, 07:33 PM #2

Turn off XMP if enabled. Please upload all crash dump files so I can analyze them.

A
aicontepig
Member
57
06-15-2021, 04:07 AM
#3
Have you verified your temperatures?
A
aicontepig
06-15-2021, 04:07 AM #3

Have you verified your temperatures?

M
MorielM
Member
69
06-15-2021, 11:24 AM
#4
I did my best. The computer ran warm and I upgraded a few fans and adjusted the fan settings for better airflow. I believe the CPU reached around 70s and the GPU hit low 80s. Checking temperatures during crashes isn’t possible at the moment.
M
MorielM
06-15-2021, 11:24 AM #4

I did my best. The computer ran warm and I upgraded a few fans and adjusted the fan settings for better airflow. I believe the CPU reached around 70s and the GPU hit low 80s. Checking temperatures during crashes isn’t possible at the moment.

A
awsomeness2518
Junior Member
14
06-15-2021, 05:09 PM
#5
Use CoreTemp and GPUTemp for live CPU and GPU temperatures. Ideal tools to own.
A
awsomeness2518
06-15-2021, 05:09 PM #5

Use CoreTemp and GPUTemp for live CPU and GPU temperatures. Ideal tools to own.

I
Ikarus_ORG
Member
226
06-16-2021, 08:30 AM
#6
I set XMP to XMP II and have options: Auto, XMP, or XMP II. I located the memory.dmp file, but it’s only 2GB. I’m not sure if that matches what you intended.
I
Ikarus_ORG
06-16-2021, 08:30 AM #6

I set XMP to XMP II and have options: Auto, XMP, or XMP II. I located the memory.dmp file, but it’s only 2GB. I’m not sure if that matches what you intended.

C
callme_crybaby
Junior Member
41
06-24-2021, 03:57 AM
#7
Your system is configured to generate full crash logs, which is too much data to send. Adjust it to create smaller memory snapshots by referring to this guide: https://www.tenforums.com/tutorials/5560...-bsod.html (look for the small memory dump option). For XMP, enable Auto if there’s no way to disable it.
C
callme_crybaby
06-24-2021, 03:57 AM #7

Your system is configured to generate full crash logs, which is too much data to send. Adjust it to create smaller memory snapshots by referring to this guide: https://www.tenforums.com/tutorials/5560...-bsod.html (look for the small memory dump option). For XMP, enable Auto if there’s no way to disable it.

X
xNJW
Junior Member
22
06-25-2021, 11:44 AM
#8
I enabled auto XMP and saw a manual version available. I ran the Cinebench multicore test and it performed well. When I began playing Civilization 6, the computer restarted immediately without any warning. I tried several settings: 1) Auto XMP, started CIV after one crash; 2) Manual XMP, started after one crash; 3) XMP II, started right after a crash. File attached: 042021-22453-01.dmp. Edited April 20, 2021 by Joint_PK.
X
xNJW
06-25-2021, 11:44 AM #8

I enabled auto XMP and saw a manual version available. I ran the Cinebench multicore test and it performed well. When I began playing Civilization 6, the computer restarted immediately without any warning. I tried several settings: 1) Auto XMP, started CIV after one crash; 2) Manual XMP, started after one crash; 3) XMP II, started right after a crash. File attached: 042021-22453-01.dmp. Edited April 20, 2021 by Joint_PK.

F
Flashwing006
Member
217
06-27-2021, 04:57 AM
#9
This restart usually indicates a weak power source, though it isn't always the case. I'll review the crash log and provide an update soon.
F
Flashwing006
06-27-2021, 04:57 AM #9

This restart usually indicates a weak power source, though it isn't always the case. I'll review the crash log and provide an update soon.

X
XLucarioPVP
Member
50
06-28-2021, 11:19 PM
#10
I’ll share some key points from the crash dump and then share my thoughts at the end.
The system detected a clock interrupt failure on a secondary processor in an MP setup. The expected interrupt wasn’t received within the set time frame, suggesting the processor became idle and wasn’t handling interrupts.
Details include: address ffffc88196fe3180, processor index 7, and a timestamp of 101.
The PRCB address points to the hung core, which was likely handling a noise-canceling task.
The BUGCHECK_CODE is 101, with several related checks failing.
My guess is an audio driver or related software might be outdated and needs updating.
X
XLucarioPVP
06-28-2021, 11:19 PM #10

I’ll share some key points from the crash dump and then share my thoughts at the end.
The system detected a clock interrupt failure on a secondary processor in an MP setup. The expected interrupt wasn’t received within the set time frame, suggesting the processor became idle and wasn’t handling interrupts.
Details include: address ffffc88196fe3180, processor index 7, and a timestamp of 101.
The PRCB address points to the hung core, which was likely handling a noise-canceling task.
The BUGCHECK_CODE is 101, with several related checks failing.
My guess is an audio driver or related software might be outdated and needs updating.

Pages (3): 1 2 3 Next