Question PC BSOD when hitting high CPU usage in launching Minecraft ?

[decrypto]

My main problem is that this has been happening pretty much on and off for a while now, whenever I tend to try and launch Minecraft my computer reaches around 100% CPU usage and then freezes and BSODs. I get the error Clock_Watchdog_Timeout or something like that and I don't know why it's even happening. This has really only happened with MC and it's worked fine before.

Specs:
OS: Windows 10
GPU: Strix 980
CPU: i7-4790k
PSU: Corsair CX-650W
Motherboard: MAXIMUS VII HERO
RAM: 32GB 1600HZ

DMP file : https://1drv.ms/u/s!Ag9btMa_OVV5gQAtmLa3ck7xV55Y?e=tc1Jfn

 

[Colif]

won't know if it helped until you do.

 

[decrypto]

still bluescreened sadly.

 

[Colif]

share the dumps as one might show something useful like a driver name, beats trying to work it out from clues.

 

[decrypto]

https://1drv.ms/u/s!Ag9btMa_OVV5hmTCNThhKuv8SlX3?e=pVUAlT

 

[Colif]

conversion of dump file

report - click run as fiddle to see

File: 111522-8390-01.dmp (Nov 15 2022 - 19:57:10)
BugCheck: [CLOCK_WATCHDOG_TIMEOUT (101)]
Probably caused by: Unknown_Image (Process: msedge.exe)
Uptime: 0 Day(s), 0 Hour(s), 27 Min(s), and 53 Sec(s)

looks about same, John might see more.

 

[johnbl]

hang was due to a filter driver trying to talk to some process running on another cpu core. the second core did not respond. windows tried to flush the cpu cache
to recover but could not before the very short time out (18 clock ticks)

to debug this you would have to provide a kernel memory dump to see what was running on the second cpu core. (cpu #2)

as a guess you might consider uninstalling /reinstalling microsoft xbox gaming services (only if you really need it)
and make sure you have not plugged in a xbox 360 controller into the system
if you have installed one then unplug it, go to windows control panel device manager, find the option to show hidden devices then delete all hidden device from all ports.

otherwise you will want to change the memory dump type to kernel and provide memory.dmp file to see what this problem is.

 

[Colif]

Can you follow option one on the following link - here - and then do this step below: Kernel Memory dumps.

this creates a dump in Memory.dmp after a BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Memory.dmp
3. Copy the dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

 

[decrypto]

https://1drv.ms/u/s!Ag9btMa_OVV5hmXOfyawKaRd37Dj?e=ZtiU43

 

[johnbl]

https://1drv.ms/u/s!Ag9btMa_OVV5hmXOfyawKaRd37Dj?e=ZtiU43

looks like the pagefile was turned off when the bugcheck happened.
the memory dump is not usable. system up time was 3 minutes

 

[decrypto]

https://1drv.ms/u/s!Ag9btMa_OVV5hnkezAMQ7RDqePIc?e=plvWMM this one work?

 

[johnbl]

basicaly some network code is not working correctly. most of your cpu cores are attempting to do some network call and it is all blocked and each core is waiting for a response from the other cores. most likely they are all waiting for some software lock to be released. looks like the discord.exe is the owner of the thread that is blocking everything.
looks like it is in a STANDBY state which might mean it can not run.
maybe update or remove discord.exe

you might turn off the NortonSecurity.exe that was running on CPU 7
something called a terminate process

bunch of the network code was called by
Messenger.exe



0: kd> !dpcwatchdog
Not a DPC_WATCHDOG_VIOLATION issue

All durations are in seconds (1 System tick = 15.625000 milliseconds)

Circular Kernel Context Logger history: !logdump 0x2
DPC and ISR stats (total since boot): !intstats /d
DPC and ISR stats (during DPC watchdog period): !intstats /w

--------------------------------------------------
CPU#0
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function
0: Normal : 0xfffff8040d020ee0 0xfffff8040c6dbf10 nt!PpmCheckPeriodicStart
0: Normal : 0xfffff8040d031ee0 0xfffff8040c72c870 nt!KiBalanceSetManagerDeferredRoutine
0: Normal : 0xfffff8040ad54868 0xfffff8040c753340 nt!KiEntropyDpcRoutine


--------------------------------------------------
CPU#1
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function
1: Normal : 0xffffe68fc3374260 0xfffff80412abebc0 tcpip!TcpPeriodicTimeoutHandler
1: Normal : 0xffffd1808c0b3868 0xfffff8040c753340 nt!KiEntropyDpcRoutine
1: Normal : 0xffff8f8c7b7af600 0xfffff8040c673380 nt!PopExecuteProcessorCallback


--------------------------------------------------
CPU#2
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function
2: Normal : 0xffff8f8c7b334600 0xfffff8040c673380 nt!PopExecuteProcessorCallback
2: Normal : 0xffffd1808c16d290 0xfffff8040c6d1650 nt!PpmPerfAction
2: Normal : 0xffffe68fc33743f8 0xfffff80412abebc0 tcpip!TcpPeriodicTimeoutHandler


--------------------------------------------------
CPU#3
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function
3: Normal : 0xffffd1808c1e7290 0xfffff8040c6d1650 nt!PpmPerfAction
3: Normal : 0xffffe68fc3374590 0xfffff80412abebc0 tcpip!TcpPeriodicTimeoutHandler


--------------------------------------------------
CPU#4
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function
4: Normal : 0xffffd1808c2a1868 0xfffff8040c753340 nt!KiEntropyDpcRoutine
4: Normal : 0xffffe68fc3374728 0xfffff80412abebc0 tcpip!TcpPeriodicTimeoutHandler


--------------------------------------------------
CPU#5
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function
5: Normal : 0xffffe68fc33748c0 0xfffff80412abebc0 tcpip!TcpPeriodicTimeoutHandler
5: Normal : 0xffffd1808c39d868 0xfffff8040c753340 nt!KiEntropyDpcRoutine


--------------------------------------------------
CPU#6
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function
6: Normal : 0xffffe68fc3374a58 0xfffff80412abebc0 tcpip!TcpPeriodicTimeoutHandler
6: Normal : 0xffffd1808c448868 0xfffff8040c753340 nt!KiEntropyDpcRoutine


--------------------------------------------------
CPU#7
--------------------------------------------------
Current DPC: No Active DPC

Pending DPCs:
----------------------------------------
CPU Type KDPC Function
7: Normal : 0xffffe68fc3374bf0 0xfffff80412abebc0 tcpip!TcpPeriodicTimeoutHandler
7: Normal : 0xffffd1808c508868 0xfffff8040c753340 nt!KiEntropyDpcRoutine


7: kd> !irp
Free build - use !irpfind to scan memory for any active IRPs
7: kd> !ipi
IPI State for Processor 0

As a sender, awaiting IPI completion from processor(s) 2, 3.

TargetCount 1 PacketBarrier 1 IpiFrozen 0 [Running]


IPI State for Processor 1

As a sender, awaiting IPI completion from processor(s) 2, 3.

TargetCount 1 PacketBarrier 1 IpiFrozen 2 [Frozen]


IPI State for Processor 2

As a receiver, unhandled requests are pending from processor(s) 0, 1, 4, 5, 7.

TargetCount 0 PacketBarrier 0 IpiFrozen 5 [Target Freeze]

From processor 0, active request of type: flush multiple range
Flush Count 58 Flush List ffffffc7c63e27c0 (dp ffffffc7c63e27c0 l58)
From processor 1, active request of type: flush multiple range
Flush Count 58 Flush List ffffffc7c63fe7b0 (dp ffffffc7c63fe7b0 l58)
From processor 4, active request of type: flush multiple
Flush Count 0 Flush List ffffffc7c63f31b8 (dp ffffffc7c63f31b8 l0)
From processor 5, active request of type: flush multiple
Flush Count b0 Flush List ffffffc7c63d222b (dp ffffffc7c63d222b lb0)
From processor 7, active request of type: flush multiple
Flush Count a0 Flush List ffffffc7c63df09f (dp ffffffc7c63df09f la0)

IPI State for Processor 3

As a receiver, unhandled requests are pending from processor(s) 0, 1, 4, 5, 7.

TargetCount 0 PacketBarrier 0 IpiFrozen 5 [Target Freeze]

From processor 0, active request of type: flush multiple range
Flush Count 58 Flush List ffffffc7c63e27c0 (dp ffffffc7c63e27c0 l58)
From processor 1, active request of type: flush multiple range
Flush Count 58 Flush List ffffffc7c63fe7b0 (dp ffffffc7c63fe7b0 l58)
From processor 4, active request of type: flush multiple
Flush Count 0 Flush List ffffffc7c63f31b8 (dp ffffffc7c63f31b8 l0)
From processor 5, active request of type: flush multiple
Flush Count b0 Flush List ffffffc7c63d222b (dp ffffffc7c63d222b lb0)
From processor 7, active request of type: flush multiple
Flush Count a0 Flush List ffffffc7c63df09f (dp ffffffc7c63df09f la0)

IPI State for Processor 4

As a sender, awaiting IPI completion from processor(s) 2, 3.

TargetCount 1 PacketBarrier 1 IpiFrozen 2 [Frozen]


IPI State for Processor 5

As a sender, awaiting IPI completion from processor(s) 2, 3.

TargetCount 1 PacketBarrier 1 IpiFrozen 2 [Frozen]


IPI State for Processor 6
TargetCount 0 PacketBarrier 0 IpiFrozen 2 [Frozen]


IPI State for Processor 7

As a sender, awaiting IPI completion from processor(s) 2, 3.

TargetCount 1 PacketBarrier 1 IpiFrozen 2 [Frozen]

7: kd> !locks
** DUMP OF ALL RESOURCE OBJECTS **
KD: Scanning for held locks.....

Resource @ 0xffffe68fc3489aa0 Shared 1 owning threads
Threads: ffffe68fc3d6b5c0-01<*>
KD: Scanning for held locks...............................................................................................

Resource @ 0xffffe68fca0ee010 Exclusively owned
Contention Count = 318054
NumberOfSharedWaiters = 1
NumberOfExclusiveWaiters = 15
Threads: ffffe68fd0560080-01<*> ffffe68fcadd70c0-01

Threads Waiting On Exclusive Access:
ffffe68fcb699080 ffffe68fcadc1080 ffffe68fcee0a080 ffffe68fd1279600
ffffe68fce718080 ffffe68fcade5080 ffffe68fd0974080 ffffe68fceb020c0
ffffe68fd2496080 ffffe68fd0cf4080 ffffe68fcee0c080 ffffe68fd0525080
ffffe68fce0cc080 ffffe68fcfa4c080 ffffe68fcadbd080
KD: Scanning for held locks......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

Resource @ 0xffffe68fd1b4b200 Shared 2 owning threads
Contention Count = 4
Threads: ffffe68fcc5a8080-01<> ffffe68fce0ef080-01<>
KD: Scanning for held locks.....................................................................................................................................................................................................................................................................................................................................................................

Resource @ 0xffffe68fcee899b8 Exclusively owned
Threads: ffffe68fc3d6b5c0-01<*>
KD: Scanning for held locks...........
38648 total locks, 4 locks currently held

7: kd> !thread ffffe68fd0560080
THREAD ffffe68fd0560080 Cid 2cfc.08ec Teb: 000000000037d000 Win32Thread: ffffe68fd0476a20 STANDBY
Not impersonating
DeviceMap ffff9481eaa0d940
Owning Process ffffe68fcf48c080 Image: Discord.exe
Attached Process N/A Image: N/A
Wait Start TickCount 8344 Ticks: 451 (0:00:00:07.046)
Context Switch Count 41244 IdealProcessor: 1
UserTime 00:00:00.031
KernelTime 00:00:00.171
Win32 Start Address 0x0000000063ceacc0
Stack Init ffff8f8c7f1d8c90 Current ffff8f8c7f1d7da0
Base ffff8f8c7f1d9000 Limit ffff8f8c7f1d3000 Call 0000000000000000
Priority 15 BasePriority 8 PriorityDecrement 80 IoPriority 2 PagePriority 5
Child-SP RetAddr : Args to Child : Call Site
ffff8f8c7f1d7de0 fffff8040c6130b0 : 0000000000000008 fffff804ffffffff 0000020200000000 ffffe68fcd7e0158 : nt!KiSwapContext+0x76
ffff8f8c7f1d7f20 fffff8040c6125df : ffffe68fd0560080 ffff8f8c7f1d82c0 ffff8f8c7f1d80e0 0000000000000000 : nt!KiSwapThread+0x500
ffff8f8c7f1d7fd0 fffff8040c611e83 : 0000000000000080 0000000000000000 0000000000000000 ffffe68fd05601c0 : nt!KiCommitThreadWait+0x14f
ffff8f8c7f1d8070 fffff8040c614d5d : ffff8f8c7f1d8258 000000000000001b 0000000000000000 ffffe68fd01b3200 : nt!KeWaitForSingleObject+0x233
ffff8f8c7f1d8160 fffff8040c6106d0 : ffffe68fca0ee010 ffff8f8c7f1d8240 0000000000010224 fffff8040c761e30 : nt!ExpWaitForResource+0x6d
ffff8f8c7f1d81e0 fffff8040c60f8dc : fffff8040c763ce0 0000000000000001 0000000000000001 0000000000000000 : nt!ExpAcquireResourceExclusiveLite+0x320
ffff8f8c7f1d82b0 fffff9dfb683f96a : 0000000000000000 0000000000989680 0000000000000001 ffffe68fd0476a20 : nt!ExEnterCriticalRegionAndAcquireResourceExclusive+0x3c
ffff8f8c7f1d82f0 fffff9dfb6c0ad6b : fffff98b065d2600 fffff98b065d2620 0000000000000001 0000000000000000 : win32kbase!EnterCrit+0x8a
ffff8f8c7f1d8410 fffff9dfb6b33e1f : fffff98b065d2620 fffff98b065d2620 ffff8f8c7f1d8b80 0000000000000004 : win32kfull!LeaveEnterCrit::~LeaveEnterCrit+0x17
ffff8f8c7f1d8440 fffff9dfb6b32846 : fffff98b065d2620 ffff8f8c7f1d0000 0000000000000001 fffff98b00000000 : win32kfull!xxxRealSleepThread+0x36f
ffff8f8c7f1d8560 fffff9dfb6b31032 : ffff8f8c7f1d8a78 0000000011ebe701 0000000000000000 0000000000000000 : win32kfull!xxxRealInternalGetMessage+0x15d6
ffff8f8c7f1d8a30 fffff9dfb72d6275 : ffffe68fd0560080 00007ffc50b13970 0000000000000020 000000000037d000 : win32kfull!NtUserGetMessage+0x92
ffff8f8c7f1d8ac0 fffff8040c80caf8 : 0000000000000000 0000000000000001 0000000011f3f840 0000000011ebe6d0 : win32k!NtUserGetMessage+0x15
ffff8f8c7f1d8b00 00007ffc50b20014 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28 (TrapFrame @ ffff8f8c7f1d8b00) 0000000011ebe728 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffc50b20014

 

[johnbl]

guess you should confirm Messenger.exe is not malware. It was running 96 threads on almost all of the cpu cores. (running network code)

Sorting by NonPaged Pool Consumed


NonPaged Paged
Tag Allocs Used Allocs Used

ismc 2 35635200


I think ismc is the pool tag for the Rapid Storage Technology driver.
It is using an extreme amount of a limited resource. You might want to look to see if you can get a updated driver.
your version is old
\SystemRoot\System32\drivers\iaStorA.sys Mon Apr 10 06:06:24 2017
look for update from here:
Intel® Driver & Support Assistant

this could be a root cause of the failure

 

[decrypto]

I use messenger for facebook messaging and I downloaded it from microsoft store, no updates found using intel driver support and assistant

 

[johnbl]

I use messenger for facebook messaging and I downloaded it from microsoft store, no updates found using intel driver support and assistant

well, that leaves discord.exe you can remove it or update it and see if helps

 

[decrypto]

Weird, Discord is my main communication platform that I use to talk to friends, no updates available. This is my latest kernal dump, I just crashed on another game, same error.

https://1drv.ms/u/s!Ag9btMa_OVV5hnkezAMQ7RDqePIc?e=X6lQrv

 

[johnbl]

Weird, Discord is my main communication platform that I use to talk to friends, no updates available. This is my latest kernal dump, I just crashed on another game, same error.

https://1drv.ms/u/s!Ag9btMa_OVV5hnkezAMQ7RDqePIc?e=X6lQrv

dump is corrupted.
all I can see is a 18 clock tick watchdog timeout with cpu core 2 hung.

I would remove the intel storage driver and use the microsoft generic storage driver.

the procedure is something like this: (cut from a old post)

window key+x then m to bring up device manager
find ide ata/atapi controllers
click to expand, highlight the intel storage driver, right mouse click to bring up properties
select driver tab
select update driver button
select browse my computer for driver
select let me pick from available drivers

select standard sata ahci controller
select next or apply to save the setting.
it will ask to reboot your machine. do the reboot
then start control panel again and go to programs uninstall
find the intel storage driver installer and uninstall the software
this will remove the various services that try to talk to the driver and prevent a errors being put into your error log.

--------
reasons to make change: memory dump keeps getting corrupted, this could be a bug in the driver. driver is using very large amount of non page pool. (something is really wrong with the driver) Driver is very old, there have been many bug fixes for this driver including one where the pagefile.sys gets corrupted after several sleep/wake cycles.
You might change the system to delete your pagefile.sys after each reboot if you can get a fix. The microsoft storage driver will be automatically updated with windows updates. The intel driver will not.

watchdog timeouts are set by firmware, so I guess I should also stress that you want to have updated the bios to the most recent version. Also apply any cpu firmware updates.

fyi: watchdog info specification in http://MSDN.microsoft.com/en-us/windows/hardware/gg463320.aspx.