Question Random BSOD crash ?

[Pixel.]

I dont know how to fix my bsod, i have tried nearly everything. My gpu, cpu and ram are at "default" settings no undervolt or overclock.
The crashes come at random, im not in control of them.

My specs

CPU: 7800x3d
GPU: 4090 suprim x
Mobo: Asrock x670E pg lighting
PSU: Corsair 1200 hx
RAM: G.Skill Trident Z5 Neo
OS: Windows 10

What i have tried:

• Turned off C-global states
• Enabled full control for nvlddmkm.sys
• Reinstalled windows
• disabled fast startup
• Used DDU in safe mode and reinstalled drivers
• Tried to disable MPO
• Newest windows update
• Updated all drivers

Here is the minidump:

******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************CLOCK_WATCHDOG_TIMEOUT (101)An expected clock interrupt was not received on a secondary processor in anMP system within the allocated interval. This indicates that the specifiedprocessor is hung and not processing interrupts.Arguments:Arg1: 000000000000000c, Clock interrupt time out interval in nominal clock ticks.Arg2: 0000000000000000, 0.Arg3: ffffe58024be4180, The PRCB address of the hung processor.Arg4: 0000000000000006, The index of the hung processor.Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1546 Key : Analysis.Elapsed.mSec Value: 3965 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 312 Key : Analysis.Init.Elapsed.mSec Value: 5697 Key : Analysis.Memory.CommitPeak.Mb Value: 144 Key : Bugcheck.Code.LegacyAPI Value: 0x101 Key : Failure.Bucket Value: CLOCK_WATCHDOG_TIMEOUT_IDLE_THREAD_INVALID_CONTEXT_nt!KeAccumulateTicks Key : Failure.Hash Value: {b37ea922-6ea8-0080-e849-451291ca96f3} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1BUGCHECK_CODE: 101BUGCHECK_P1: cBUGCHECK_P2: 0BUGCHECK_P3: ffffe58024be4180BUGCHECK_P4: 6FILE_IN_CAB: 073023-10093-01.dmpFAULTING_PROCESSOR: 6BLACKBOXBSD: 1 (!blackboxbsd)BLACKBOXNTFS: 1 (!blackboxntfs)BLACKBOXPNP: 1 (!blackboxpnp)BLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: Discord.exeSTACK_TEXT: fffff800`71a84c88 fffff800`6b843af6 : 00000000`00000101 00000000`0000000c 00000000`00000000 ffffe580`24be4180 : nt!KeBugCheckExfffff800`71a84c90 fffff800`6b686e3d : 00000000`00000000 fffff800`6961d180 00000000`00000246 00000000`00117173 : nt!KeAccumulateTicks+0x1bfed6fffff800`71a84cf0 fffff800`6b67dec1 : ffffa801`7cd44000 00000000`000a659d fffff800`6961d180 00000000`00000001 : nt!KiUpdateRunTime+0x5dfffff800`71a84d40 fffff800`6b681253 : fffff800`6961d180 00000000`00000000 fffff800`6c031528 00000000`00000000 : nt!KiUpdateTime+0x4a1fffff800`71a84e80 fffff800`6b688ae2 : ffff9b0c`297ee8d0 ffff9b0c`297ee950 ffff9b0c`297ee900 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3fffff800`71a84f30 fffff800`6b73ec85 : 00000029`968c9993 fffff800`6c0f3a60 fffff800`6c0f3b10 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2fffff800`71a84f60 fffff800`6b7fe05a : ffff9b0c`297ee950 fffff800`6c0f3a60 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5fffff800`71a84fb0 fffff800`6b7fe827 : 00000000`00000000 fffff800`6c12f240 ffffe580`24889078 fffff800`6b6eae5a : nt!KiInterruptSubDispatchNoLockNoEtw+0xfaffff9b0c`297ee8d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37SYMBOL_NAME: nt!KeAccumulateTicks+1bfed6MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.19041.3208STACK_COMMAND: .cxr; .ecxr ; kbBUCKET_ID_FUNC_OFFSET: 1bfed6FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_IDLE_THREAD_INVALID_CONTEXT_nt!KeAccumulateTicksOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {b37ea922-6ea8-0080-e849-451291ca96f3}Followup: MachineOwner---------


help is appreciated

 

[Darkbreeze]

Current motherboard BIOS version?

Approximate age of that HX power supply?

4090 firmware version?

EXACT model of your Trident Z sticks?

 

[ubuysa]

That bugcheck code cannot be analysed from a minidump, we need the kernel dump. You'll find it in the file C:\Windows\Memory.dmp, please upload that to the cloud somewhere (it will be large) and post a link to it here. Please remember to make the file public.

 

[Pixel.]

Current motherboard BIOS version?

Approximate age of that HX power supply?

4090 firmware version?

EXACT model of your Trident Z sticks?

Bios version 1.24

My psu is max a half year old

My gpu firmware is 1.2 i had the same problem with 1.1

This is the exact model of my ram : https://www.gskill.com/product/165/393/1661410171/F5-6000J3038F16GX2-TZ5N

 

[Darkbreeze]

Memory kit IS validated for that board, so no worries there.

I'd recommend updating the BIOS to version 1.28. "Notes" on BIOS updates don't always include all changes that are addressed via newly released firmware.

Just to be sure we aren't overlooking something obvious, exactly which slots are your DIMMs installed in?

Did you update your drivers directly from the motherboard and/or AMD product page or did you rely on Windows update or a third party driver updater for them?

Finding and uploading the kernel dump as suggested by ubuysa would be a good idea too.

 

[scout_03]

you could use whocrashed to see if it find any minidump files it will read them in plain text .

 

[Pixel.]

Memory kit IS validated for that board, so no worries there.

I'd recommend updating the BIOS to version 1.28. "Notes" on BIOS updates don't always include all changes that are addressed via newly released firmware.

Just to be sure we aren't overlooking something obvious, exactly which slots are your DIMMs installed in?

Did you update your drivers directly from the motherboard and/or AMD product page or did you rely on Windows update or a third party driver updater for them?

Finding and uploading the kernel dump as suggested by ubuysa would be a good idea too.

I have my ram in slot 2 and 4

Yeah i updated from the product pages, didnt do them over windows.

I have this link with all my dumps: https://onedrive.live.com/?authkey=!ANqKFR0QDA76Ha8&id=5634BEED8AE227AE!3291&cid=5634BEED8AE227AE

Thanks for helping

 

[Randi Poling]

Sounds like a CPU issue with "watchdog" Its either getting too much voltage or not enough... Maybe try a newer BIOs revision if available? Or even an older one? I would also check the CPU to make sure youre not having any issues on the bottom of it where the contacts are (bulging) and check the pins in the socket.

 

[Darkbreeze]

I would HIGHLY recommend resetting the BIOS to the default settings, and starting over. AND, if that means doing a hard reset of the BIOS

BIOS Hard Reset procedure

Power off the unit, switch the PSU off and unplug the PSU cord from either the wall or the power supply.

Remove the motherboard CMOS battery for about three to five minutes. In some cases it may be necessary to remove the graphics card to access the CMOS battery.

During that five minutes while the CMOS battery is out of the motherboard, press the power button on the case, continuously, for 15-30 seconds, in order to deplete any residual charge that might be present in the CMOS circuit. After the five minutes is up, reinstall the CMOS battery making sure to insert it with the correct side up just as it came out.

If you had to remove the graphics card you can now reinstall it, but remember to reconnect your power cables if there were any attached to it as well as your display cable.

Now, plug the power supply cable back in, switch the PSU back on and power up the system. It should display the POST screen and the options to enter CMOS/BIOS setup. Enter the bios setup program and reconfigure the boot settings for either the Windows boot manager or for legacy systems, the drive your OS is installed on if necessary.

Save settings and exit. If the system will POST and boot then you can move forward from there including going back into the bios and configuring any other custom settings you may need to configure such as Memory XMP, A-XMP or D.O.C.P profile settings, custom fan profile settings or other specific settings you may have previously had configured that were wiped out by resetting the CMOS.

In some cases it may be necessary when you go into the BIOS after a reset, to load the Optimal default or Default values and then save settings, to actually get the BIOS to fully reset and force recreation of the hardware tables.





Or just selecting the Optimized default settings from the Exit screen in the BIOS, then I'd do it. At least then you know you are at square one and any remaining problems aren't do to some of the questionable configuration choices you've elected to incorporate.