Why does my computer keep crashing?

Question

Why does my computer keep crashing?

Anonymous

Hi Microsoft Community. So last month my brother and I built a new computer to host some gaming servers. We finally managed to get the servers up and running successfully but in the last couple of weeks, my computer has crashed 3 times around midnight (while I'm asleep) which obviously not ideal for my gaming community who is playing at that time. The most recent being last night.

Below i'll share what i'm pulling from event viewer which i know is not very helpful according to the other threads and forums i've read about event 41, kernel-power critical errors. So far, i have verified my GPU driver is updated, my components are not overheating (although I'm not on at that time but from what i can see there have been no spikes), my SSD and HHD diagnostics show no errors, and my power supply is sufficient. What i have not done and don't want to unless i have to, due to how many hours it takes to run and subsequently how long our servers would need to be down, is run a memory diagnostic on all 256 GBs of RAM. I did start to but after an hour it was at 1% so I decided i'd wait to see if this was necessary. Note, I also have no recent dmp files to share - nothing since the crashes began. I do however have an extracted MSINFO32 file with all of my system information. I'll paste that below.

Oh, also when the computer does crash i come back to my bios screen and it is extremely difficult to get out of. ESC, Save and Quit, nor restarting will get me out. The only thing that seems to work is when i reset setting to default UEFI 5 or 6 times. Eventually this will bring me back to windows login. I tried to change boot sequence / priority but when i have to hit reset it just changes it back.

Event Viewer:

<Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">
<System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" /><EventID>41</EventID><Version>10</Version><Level>1</Level><Task>63</Task><Opcode>0</Opcode><Keywords>0x8000400000000002</Keywords><TimeCreated SystemTime="2024-12-17T12:44:00.1580373Z" /><EventRecordID>11165</EventRecordID><Correlation /><Execution ProcessID="4" ThreadID="8" /><Channel>System</Channel><Computer>DESKTOP-LMH0K2L</Computer><Security UserID="S-1-5-18" /></System>
<EventData> <Data Name="BugcheckCode">239</Data><Data Name="BugcheckParameter1">0xffffe1823081a080</Data><Data Name="BugcheckParameter2">0x0</Data><Data Name="BugcheckParameter3">0x0</Data><Data Name="BugcheckParameter4">0x0</Data><Data Name="SleepInProgress">0</Data><Data Name="PowerButtonTimestamp">0</Data><Data Name="BootAppStatus">0</Data><Data Name="Checkpoint">0</Data><Data Name="ConnectedStandbyInProgress">true</Data><Data Name="SystemSleepTransitionsToOn">0</Data><Data Name="CsEntryScenarioInstanceId">16</Data><Data Name="BugcheckInfoFromEFI">true</Data><Data Name="CheckpointStatus">0</Data><Data Name="CsEntryScenarioInstanceIdV2">16</Data><Data Name="LongPowerButtonPressDetected">false</Data><Data Name="LidReliability">false</Data><Data Name="InputSuppressionState">0</Data><Data Name="PowerButtonSuppressionState">0</Data><Data Name="LidState">3</Data><Data Name="WHEABootErrorCount">0</Data></EventData> </Event>

MSINFO32 System Information:

System Information report written at: 12/17/24 12:20:52

System Name: DESKTOP-LMH0K2L

[System Summary]

Item Value

OS Name Microsoft Windows 11 Pro

Version 10.0.26100 Build 26100

Other OS Description Not Available

OS Manufacturer Microsoft Corporation

System Name DESKTOP-LMH0K2L

System Manufacturer To Be Filled By O.E.M.

System Model WRX80D8-2T

System Type x64-based PC

System SKU To Be Filled By O.E.M.

Processor AMD Ryzen Threadripper PRO 3975WX 32-Cores, 3501 Mhz, 32 Core(s), 64 Logical Processor(s)

BIOS Version/Date American Megatrends International, LLC. 10.27, 5/5/2022

SMBIOS Version 3.3

Embedded Controller Version 255.255

BIOS Mode UEFI

BaseBoard Manufacturer ASRockRack

BaseBoard Product WRX80D8-2T

BaseBoard Version

Platform Role Desktop

Secure Boot State Off

PCR7 Configuration Binding Not Possible

Windows Directory C:\WINDOWS

System Directory C:\WINDOWS\system32

Boot Device \Device\HarddiskVolume1

Locale United States

Hardware Abstraction Layer Version = "10.0.26100.1"

User Name DESKTOP-LMH0K2L\Dillion

Time Zone Eastern Standard Time

Installed Physical Memory (RAM) 256 GB

Total Physical Memory 256 GB

Available Physical Memory 120 GB

Total Virtual Memory 294 GB

Available Virtual Memory 128 GB

Page File Space 38.0 GB

Page File C:\pagefile.sys

Kernel DMA Protection Off

Virtualization-based security Running

Virtualization-based security Required Security Properties Base Virtualization Support

Virtualization-based security Available Security Properties Base Virtualization Support, DMA Protection, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control

Virtualization-based security Services Configured Hypervisor enforced Code Integrity

Virtualization-based security Services Running Hypervisor enforced Code Integrity

App Control for Business policy Enforced

App Control for Business user mode policy Off

Automatic Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable

A hypervisor has been detected. Features required for Hyper-V will not be displayed.

[System Drivers]

Name Description File Type Started Start Mode State Status Error Control Accept Pause Accept Stop

[Environment Variables]

Variable Value User Name

[Print Jobs]

Document Size Owner Notify Status Time Submitted Start Time Until Time Elapsed Time Pages Printed Job ID Priority Parameters Driver Print Processor Host Print Queue Data Type Name

[Network Connections]

Local Name Remote Name Type Status User Name

[Running Tasks]

Name Path Process ID Priority Min Working Set Max Working Set Start Time Version Size File Date

[Loaded Modules]

Name Version Size File Date Manufacturer Path

[Services]

Display Name Name State Start Mode Service Type Path Error Control Start Name Tag ID

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.

0 comments

2 answers

Answer 1

Hey Bob,

Thank you so much for the response. Last night the computer crashed twice more so I've been following this and making more adjustments. Here is what i've done today so unknown whether or not these helped.

I was using a battery back up so i've disconnected that and now have the PC plugged straight in. My power supply is an RM850x and according to a few different performance apps i'm using, the PC is pushing just over 100w so it should be more than enough.
By default, the motherboard allowed overclocking / performance boosts. This kept my cpu running at 4250 ghz consistently but now it's disabled and running at stock 3500.
I verified cpu and motherboard (including bios) drivers are up to date. Although, there are multiple drivers available on manufacturer website for my model and windows so i don't know if i need all of them. Motherboard manual and website doesn't say.
I tested RAM memory with OCCT program and found no errors. I also used this application to conduct a stability and stress test and everything came back good.
There are not many power options available in my control panel. Just power plans which is set to AMD Ryzen Balanced. Inside of the plan i did notice that it was set to turn off hard disk after a few mins so i changed this to 65.

I'm really hoping that one of these will do the trick.

Answer 2

Hello, Shay Patton

Welcome to the Microsoft Community.

Hello and thank you for reporting your problem here, it looks like you are experiencing a Kernel-Power Event 41 error, which usually indicates that the computer is shutting down or restarting without warning, usually due to a power-related issue, hardware failure, or driver problem. Since the crash occurred when the server was running at night, it could have been a resource-intensive issue due to a long load, but there are other factors that could have caused the problem.

Here are the possible causes and some troubleshooting steps you can try to find the problem:

The power supply is faulty

Even though you mentioned that the power supply is adequate, power-related failures are still one of the common causes of this error. Event 41 is usually associated with a sudden loss of power or an unstable power supply unit (PSU). You can try the following steps:

Check the power load: Make sure your power supply unit has enough power to support the system, especially when running a game server, the CPU and GPU can be very demanding.

Consider load testing: Test system stability under high loads using tools to verify the performance of the power supply unit under high loads.

Check cable connections: Make sure all power cables, especially the power connections to the motherboard and graphics card, are secure.

The memory is faulty

Since you mentioned that the system has 256GB of RAM, it is possible that one of the memory strips malfunctioned causing the system to crash. While it may take a little longer to fully test 256GB of RAM, you can try the following:

Run basic memory tests: Instead of testing all 256GB of memory at once, you can use the tool to test memory block by block to quickly identify faulty memory bars.

Reinstall the memory bar: Sometimes the memory bar may not be installed correctly. You can shut down the computer and reinstall all memory sticks to make sure they are inserted correctly.

The system and drivers are unstable

Problems with the graphics card driver or other system drivers may cause the system to crash.

Check for outdated drivers: Although you mentioned that the graphics card drivers have been updated, also check for updates to the chipset drivers, as these drivers can also affect power management.

Check for Windows updates: Make sure your system has the latest Windows patches installed, especially those related to power management.

Configure BIOS/UEFI

Since your system often enters the BIOS interface after crashing, it may be a problem caused by the BIOS Settings. You can try the following:

Update BIOS: Check the motherboard manufacturer's website to see if there are BIOS updates for stability or power management.

Reset BIOS Settings: You have tried to reset BIOS Settings, but you can also check if quick boot or secure boot is disabled, as these features can sometimes cause system boot problems.

Check boot order and UEFI Settings: Make sure your boot order and UEFI Settings are correct. If the BIOS resets these Settings frequently, it may indicate that there is a problem with the CMOS battery or that the BIOS Settings are corrupted.

Heat dissipation management and system load

Although you checked for overheating, a high load for a long time (such as running a game server) can still cause instability in the system, especially if the thermal paste ages or lacks heat dissipation.

Monitor system temperature: Use software to continuously monitor CPU and GPU temperature, even when you are not present. This can help confirm if the system is overheating under occasionally high loads.

Improve heat dissipation: Check whether the chassis fan, CPU heat sink, and graphics card heat sink are working properly.

The storage or hard disk is faulty

You mentioned that you have checked the SSD/HDD diagnostics, which is a good start, but sometimes bad sectors or problems with the hard drive can still cause the system to crash.

Check for file system errors: Use the chkdsk tool to check your hard disk to make sure there are no file system errors.

Check for disk errors in the Event Viewer: Check the event viewer for disk-related errors, especially disk controller problems that sometimes trigger Kernel-Power errors.

Disclaimer: Running chkdsk can check the file system and file system metadata of a volume for logical and physical errors. To avoid any trouble for you, do not cancel or interrupt chkdsk, and back up important data.

More information please refer to this chkdsk | Microsoft Learn.

Connect standby mode and sleep state

According to you provide the event data, "ConnectedStandbyInProgress" is true, this shows that the system may be to enter or exit a power state. This can cause problems if the hardware does not support this state.

Disable connection standby: Some systems have problems in sleep mode. Try disabling Mixed Sleep and Quick Start in Control Panel > Power options to see if that fixes the problem.

You can try it out by referring to the steps above, and after that, give some feedback and I will further support you.

Disclaimer: Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party linked sites or any support related to technology.

If you are going to modify BIOS Settings, please back up all your personal files first to ensure you do not lose data.

Best regards

Bobhe | Microsoft Community Support Specialist

Share via

Why does my computer keep crashing?

2 answers