This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I could use some help. PC becoming unusable, Constant BSODs. It's only a year and a half old, and it did initially ship with a broken GPU. I have performed a full reset, updated rivers, ran scan sfc now and chkdsk, it basically began happening out of nowhere with 0 warning. Here's my specs:
IBuyPower Creator RDY IWBG209
Case iBUYPOWER InWin 305 Tempered Glass RGB
Processor Intel® Core™ i9-11900KF Processor (8X 3.50GHz/16MB L3 Cache)
Processor Cooling iBUYPOWER 360mm Addressable RGB Liquid Cooling System
Memory 32GB [16GB x 2] DDR4-3200MHz RGB
Video Card GIGABYTE AORUS XTREME GeForce RTX 3090 - 24GB GDDR6X (VR-Ready)
Storage 1TB MSI M470 PCIe Gen4 NVMe SSD + 2TB Seagate HDD
Motherboard ASUS TUF GAMING Z590-PLUS WIFI
Power Supply 850 Watt - CORSAIR RM850 80 PLUS Gold, Full Modular
Internal Wireless Network On-Board Wireless Network
Operating System Windows 10 Pro
Keyboard iBUYPOWER RGB Gaming Keyboard
Mouse iBUYPOWER Gaming Optical Mouse
Log from WhoCrashed:
System Information (local)
Computer name: DESKTOP-LRI81AF
Windows version: Windows 10, 10.0, version 2009, build: 19044 (x64)
Windows dir: C:\WINDOWS
Hardware: ASUS, ASUSTeK COMPUTER INC., TUF GAMING Z590-PLUS WIFI
CPU: GenuineIntel 11th Gen Intel(R) Core(TM) i9-11900KF @ 3.50GHz 8664, level: 6
Processor count: 16 logical processors, active mask: 65535
RAM: 32623.1MB
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Fri 10/7/2022 6:07:29 PM your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\MEMORY.DMP (Kernel memory dump)
Bugcheck code: 0x101(0xC, 0x0, 0xFFFFAB802025F180, 0x7)
Bugcheck name: CLOCK_WATCHDOG_TIMEOUT
Driver or module in which error occurred: intelppm.sys (intelppm+0x138f)
File path: C:\WINDOWS\System32\drivers\intelppm.sys
Description: Processor Device Driver
Product: Microsoft® Windows® Operating System
Company: Microsoft Corporation
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues
A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.
On Fri 10/7/2022 3:12:10 PM your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\100722-14796-01.dmp (Minidump)
Bugcheck code: 0x101(0xC, 0x0, 0xFFFFDE81CE840180, 0x4)
Bugcheck name: CLOCK_WATCHDOG_TIMEOUT
Driver or module in which error occurred: intelppm.sys (intelppm+0x138f)
File path: C:\WINDOWS\System32\drivers\intelppm.sys
Description: Processor Device Driver
Product: Microsoft® Windows® Operating System
Company: Microsoft Corporation
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues
A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.
On Fri 10/7/2022 2:45:55 PM your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\100722-14156-01.dmp (Minidump)
Bugcheck code: 0x101(0xC, 0x0, 0xFFFF99818705F180, 0x7)
Bugcheck name: CLOCK_WATCHDOG_TIMEOUT
Driver or module in which error occurred: intelppm.sys (intelppm+0x138f)
File path: C:\WINDOWS\System32\drivers\intelppm.sys
Description: Processor Device Driver
Product: Microsoft® Windows® Operating System
Company: Microsoft Corporation
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues
A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.
On Fri 10/7/2022 6:07:29 PM your computer crashed or a problem was reported
Crash dump file: C:\WINDOWS\Minidump\100722-9562-01.dmp (Minidump)
Bugcheck code: 0x101(0xC, 0x0, 0xFFFFAB802025F180, 0x7)
Bugcheck name: CLOCK_WATCHDOG_TIMEOUT
Driver or module in which error occurred: intelppm.sys (intelppm+0x138f)
File path: C:\WINDOWS\System32\drivers\intelppm.sys
Description: Processor Device Driver
Product: Microsoft® Windows® Operating System
Company: Microsoft Corporation
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues
A full memory dump will likely provide more useful information on the cause of this particular bugcheck. The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.
Conclusion
4 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the suggestions displayed in the bugcheck analysis above.
The analysis process took 0:00:07 (h:mm:ss).
Event Viewer is telling me it's a Kernel-Power 41 issue.
Please help!
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
That appears to be the output from WhoCrashed.
Can you provide the actual minidump files?
Also if possible this file:
C:\Windows\MEMORY.DMP
The memory.dmp file will be quite large, you could zip and compress the memory.dmp file with a third party application such as 7-Zip.
Copy any .dmp file to another location such as the Desktop prior to zipping/uploading to overcome any permission issue.
https://1drv.ms/u/s!AvRgzlFXd_CxkH6acuXHI4XHf8b3?e=QdR0R2 Is this what you need?
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
Hi,
Can you provide the minidump files via a public folder on OneDrive or similar site.
