Kernel Power 41; Computer Shutting Down Unexpectedly


  1. Posts : 4
    Windows 10
       #1

    Kernel Power 41; Computer Shutting Down Unexpectedly


    Hello all, I have been experiencing this particular issue for several years now. To be clear, I am not getting a BSOD...the computer simply powers off as if it was unplugged from the wall, only to turn back on a few seconds later.

    The oldest record currently on my machine states September 2019 with the most recent time occurring today. I don't know if this issue occurred prior to upgrade to my current GPU/PSU (I don't remember if I was OC'd prior to that either). From my experience, it seems to happen while playing certain video games. My CPU is overclocked but runs prime95 and other stress tests without issues.

    When the overclock is gone, the computer doesn't seem to experience this issue but struggles with fps in games. However, since I am running on an old rig, I have found it to be a requirement to have my CPU overclocked in order to play modern games.

    I look forward to any help that can be offered as I have been unable to figure it out. Sometimes I can go a day or two without issues and other times, my computer shuts off multiple times a day.

    Windows Version: 1903 (OS Build 18362.900)
    Kernel Power 41; Computer Shutting Down Unexpectedly Attached Files
      My Computer


  2. Posts : 13,955
    Windows 10 Pro X64 21H1 19043.1503
       #2

    As the header of the forum says: Please do not post anything other than Windows 10 Blue Screen Of Death problems in this section.

    Sounds like you already know the cause of the problem which is overclocking your CPU sounds like you need to upgrade your CPU.

    I'll ask one of the Admins to move your post to a more appropriate forum.
      My Computers


  3. Posts : 4
    Windows 10
    Thread Starter
       #3

    Thanks Ztrucker, I thought this was still the appropriate forum for debugging the issue. I don't understand why an overclocked CPU runs stress tests fine but then falls apart doing less intensive things.

    Edit: Additionally, why would the computer shut off only during some games, and its perfectly fine doing other games when overclocked?
      My Computer


  4. Posts : 13,955
    Windows 10 Pro X64 21H1 19043.1503
       #4

    Well, turns out you did have a couple BSODs. I should have looked rather than take your word for it.

    Zbook found these:

    Code:
      Event[1293]:
      Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2020-05-24T14:09:50.465
      Event ID: 1001
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-H6LE8KI
      Description: 
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0x0000000000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff80413313604). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 01d171cd-692c-4296-8318-cf66a5c5050a.
    Code:
        Event[2033]:
          Log Name: System
          Source: Microsoft-Windows-WER-SystemErrorReporting
          Date: 2020-05-28T09:02:50.404
          Event ID: 1001
          Task: N/A
          Level: Error
          Opcode: N/A
          Keyword: Classic
          User: N/A
          User Name: N/A
          Computer: DESKTOP-H6LE8KI
          Description: 
        The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffb1874351c028, 0x00000000be000000, 0x0000000000800400). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 168111de-f18c-42b6-a7e9-67fe7295cda2.
    We can work it here rather than moving it back to the BSOD forum, sorry.

    Let's see what zbook has to say on this.
      My Computers


  5. Posts : 4
    Windows 10
    Thread Starter
       #5

    I am glad we found something at least!

    When you mention "lets see what zbook has to say" is there something that I need to do? or provide?

    - - - Updated - - -

    crashed again today and attached new logs here
    Kernel Power 41; Computer Shutting Down Unexpectedly Attached Files
      My Computer


  6. Posts : 13,955
    Windows 10 Pro X64 21H1 19043.1503
       #6

    Dump shows probable CPU error:

    Code:
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffb1874351c028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value
    0: kd> !errrec ffffb1874351c028
    ===============================================================================
    Common Platform Error Record @ ffffb1874351c028
    -------------------------------------------------------------------------------
    Record Id : 01d635077757d365
    Severity : Fatal (1)
    Length : 936
    Creator : Microsoft
    Notify Type : Machine Check Exception
    Timestamp : 5/28/2020 15:49:13 (UTC)
    Flags : 0x00000000

    ===============================================================================
    Section 0 : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor @ ffffb1874351c0a8
    Section @ ffffb1874351c180
    Offset : 344
    Length : 192
    Flags : 0x00000001 Primary
    Severity : Fatal

    Proc. Type : x86/x64
    Instr. Set : x64
    Error Type : Micro-Architectural Error
    Flags : 0x00
    CPU Version : 0x00000000000206a7
    Processor ID : 0x0000000000000000

    ===============================================================================
    Section 1 : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor @ ffffb1874351c0f0
    Section @ ffffb1874351c240
    Offset : 536
    Length : 128
    Flags : 0x00000000
    Severity : Fatal

    Local APIC Id : 0x0000000000000000
    CPU Id : a7 06 02 00 00 08 10 00 - bf e3 9a 1f ff fb eb bf
    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

    Proc. Info 0 @ ffffb1874351c240

    ===============================================================================
    Section 2 : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor @ ffffb1874351c138
    Section @ ffffb1874351c2c0
    Offset : 664
    Length : 272
    Flags : 0x00000000
    Severity : Fatal

    Error : Internal timer (Proc 0 Bank 3)
    Status : 0xbe00000000800400
    Address : 0x00003802522fe5b9
    Misc. : 0x000000000003ffff

    Since removing the OC resolves the problem I'd say you need to replace the CPU, especially since you say Prime95 doesn't show any problems.
    Your specs say you have a Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz which is a nice CPU that should be good enough to run most games without OCing.

    Remove all OCing and run Prime95 again.
    ===================================================

    Follow this tutorial to stress test your CPU:

    Test with the Intel Processor Diagnostic Tool.
    Also run Prime95 - Stress Test Your CPU - Windows 10 Forums
    Also try OCCT: OCBASE / OCCT

    For the above, read the instructions carefully and watch your system when testing.
    If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

    For Intel CPUs (32 and 64 bit): Intel® Processor Diagnostic Tool

    The purpose of the Intel® Processor Diagnostic Tool is to verify the functionality of an Intel® microprocessor. The diagnostic tool checks for brand identification, verifies the processor operating frequency, tests specific processor features, and performs a stress test on the processor.

    Maybe test your RAM and see if that is contributing to the problem:

    ===================================================
    Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
    DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review

    Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They will verify that:
    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses

    They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.

    If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    Both of these diagnostics has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ or 4+4 passes of Memtest86 is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run it overnight, starting just before you go to bed and leave it overnight.

    Take a picture when done and post in the forum please.

    Also run Driver Verifier to see if it shows any driver problems that contribute to the problem as well:

    Run Driver Verifier

    Driver Verifier-- tracking down a mis-behaving driver.

    Following the instructions in the above link will check for problems in all non-Microsoft drivers.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

    To check if verifier is active, open a Command Prompt and enter:

    verifier /query

    If not active it will respond with

    No drivers are currently verified.

    If you have questions, see this additional tutorial which may help to clear things up.

    Enable and Disable Driver Verifier in Windows 10


    If none of this helps you may have to replace the CPU. How old is it? Any chance it's still under warranty?
      My Computers


  7. Posts : 4
    Windows 10
    Thread Starter
       #7

    So far I have run Prime95 (with it overclocked still) at 3 hours with no errors. Intel Diagnostic Tool also passed. I will work on OCCT and memtest86 later.

    Thanks!
    Kernel Power 41; Computer Shutting Down Unexpectedly Attached Files
      My Computer


  8. Posts : 504
    Windows 10
       #8

    If youre going to overclock, keep the RAM in sync with the CPU. Forget dividing the memory because all that will do is cause errors.
    Find FSB or QPR of CPU. Then adjust RAM to run at half the speed of the FSB

    Forgot to add say,

    CPU at 1066mhz, I would run ram at 533mhz
    CPU at 1333mhz, i would run ram at 667mhz
    CPU at 1600mhz, i would run ram at 800mhz

    Hope that helps bud Good luck
    Last edited by Pluginz; 18 Jun 2020 at 14:17.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 15:59.
Find Us




Windows 10 Forums