Share via

BSOD Kernel-Power 41

Anonymous
2019-05-13T16:29:12+00:00

This started a few days ago where PC will crash and after reboot, i find this in event viewer:

Log Name:      System

Source:        Microsoft-Windows-Kernel-Power

Date:          13/05/2019 16:48:11

Event ID:      41

Task Category: (63)

Level:         Critical

Keywords:      (70368744177664),(2)

User:          SYSTEM

Computer:      Venator

Description:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event Xml:

<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>6</Version>

    <Level>1</Level>

    <Task>63</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000400000000002</Keywords>

    <TimeCreated SystemTime="2019-05-13T15:48:11.414077800Z" />

    <EventRecordID>33686</EventRecordID>

    <Correlation />

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

    <Channel>System</Channel>

    <Computer>Venator</Computer>

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

  </System>

  <EventData>

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

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

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

  </EventData>

</Event>

Not good with this stuff, anyone know how to help fix this?

Windows for home | Windows 10 | Performance and system failures

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 No comments

8 answers

Sort by: Most helpful
  1. Anonymous
    2019-05-17T12:28:39+00:00

    Update 7: I tried going back to pre-2019 patchs for windows and still got BSOD so decided to try and reset while keeping personal files, Windows reset failed.

    After leaving the PC for awhile I once again booted it back up to take another shot at it (at some point I may have blown my extra internal case fans oops), But this time some different happened...

    The PC booted fast like as in the first time i booted it fast, loaded into window account fast and so far no signs of crashing yet will let this post sit for a day or two before closing incase the cause of BSOD is just hiding.

    Maybe I fixed it, Maybe it's hiding we'll see.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-05-16T16:20:30+00:00

    Update 6: new audio driver installed still getting BSOD issue seems like every step forward I take, I now have to system restore and start again.

    Might trying going back 2-3 months with next restore to see if its and issue with recent windows update.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-05-14T19:17:52+00:00

    Update 1: After finding out about bluescreenview, I looked at my dump file and saw "ntoskrnl.exe" was the cause of all BSOD's which can possibly be a memory driver error so I ran windows memory diagnostics tool.

    Update 2: Windows memory diagnostic showed no memory errors detected, gonna start checking individual drivers.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-05-13T16:53:12+00:00

    Here's the link: 

    https://1drv.ms/u/s!AhOdom\_lh0huiHthso9RXkH-Am2r

    I trowed in everything that could help.

    Was this answer helpful?

    0 comments No comments
  5. DaveM121 891.6K Reputation points Independent Advisor
    2019-05-13T16:33:12+00:00

    Hi Venator(GV) BSOD's are generally caused by a corrupt or incompatible device driver, to diagnose the underlying issue, I need to analyse your Mini-dump file(s):

    Open Windows File Explorer

    Navigate to C:\Windows\Minidump

    Zip up the contents of that folder

    If you have problems zipping those files, copy them out onto your Desktop and zip them from there

    Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

    Then post a link here to the zip file, so we can take a look for you . . .

    Was this answer helpful?

    0 comments No comments