How to fix random and frequent shutdowns?

Dylan Schulze 20 Reputation points
2024-08-04T14:05:17.91+00:00

Hi I have had random unclean shut downs for a while, with no rhyme or reason (Sometimes during workload, sometime during idle) . These have been giving Kernal 41 errors with no log dumps.

  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />

  <EventID>41</EventID>

  <Version>8</Version>

  <Level>1</Level>

  <Task>63</Task>

  <Opcode>0</Opcode>

  <Keywords>0x8000400000000002</Keywords>

  <TimeCreated SystemTime="2024-08-03T17:13:51.4098973Z" />

  <EventRecordID>47926</EventRecordID>

  <Correlation />

  <Execution ProcessID="4" ThreadID="8" />

  <Channel>System</Channel>

  <Computer>DESKTOP-L7IRFO7</Computer>

  <Security UserID="S-1-5-18" />

  </System>

  • <EventData>

  <Data Name="BugcheckCode">292</Data>

  <Data Name="BugcheckParameter1">0x10</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">false</Data>

  <Data Name="SystemSleepTransitionsToOn">0</Data>

  <Data Name="CsEntryScenarioInstanceId">0</Data>

  <Data Name="BugcheckInfoFromEFI">true</Data>

  <Data Name="CheckpointStatus">0</Data>

  <Data Name="CsEntryScenarioInstanceIdV2">0</Data>

  <Data Name="LongPowerButtonPressDetected">false</Data>

  </EventData>

  </Event>

I have also received other errors which are driver related:

<Provider Name="VBoxNetLwf" />

  <EventID Qualifiers="49156">12</EventID>

<Provider Name="volmgr" />

  <EventID Qualifiers="49156">161</EventID>

<Provider Name="Netwtw10" />

  <EventID Qualifiers="49152">5010</EventID>

What I have tried:

  • Replacing GPU and PSU
  • Updated motherboard BIOS to latest version
  • Keep GPU drivers up to date
  • Updating system log location
  • Reinstalling Windows
  • Running drive tests and corrupt file checks

Nothing so far has worked and I have been experiencing this for a long time. I have also not found any good relevant information on other Microsoft forums and was recommended to come over here.

Here is msinfo32.exe file as well as application and system event logs:

https://drive.google.com/drive/folders/1OORYTroZVhrftEfQ3D0rI_JjoNpm9-Hh?usp=drive_link

I appreciate any help or advice! If you need anymore information I am more than willing to provide it

Windows for business Windows Client for IT Pros User experience Other
{count} votes

Accepted answer
  1. Gary Nebbett 6,216 Reputation points
    2024-08-10T09:32:36.7+00:00

    Hello Dylan,

    No minidump will be generated in your case since the component that seems to be encountering a problem is the "Samsung SSD 970" drive (probably the place where a crash dump would have been written).

    If you convert the RawData hex string to binary data and examine that, you should find a "Common Platform Error Record" which mentions STORPORT, stornvme and "Samsung SSD 970".

    Gary

    User's image


1 additional answer

Sort by: Most helpful
  1. Wesley Li 11,245 Reputation points
    2024-08-08T07:30:03.52+00:00

    Hello

    Please check whether there is any dump file in C:\Windows\minidump or C:\Windows\memory.dmp.

    If there is any dump created, we could refer to the following link to open it. Or you could upload the dump here, we will try to analyze it for you.

    How to Open and Analyze Windows Crash Dump (.DMP) Files (wikihow.com)

    I tried to check the event, there is a parameter "BugcheckCode">292".

    It could be hardware issue. You may consider to ask for help from the device manufacturer website since you have tried a clean installation.

    Here is a link for reference:

    BSOD kernel error 41 BugcheckCode 292 - Microsoft Community


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.