Home build: crash after waking up from "sleep mode"


  1. Posts : 4
    Windows 10 Home
       #1

    Home build: crash after waking up from "sleep mode"


    Greetings All,

    First off, thank you for helping with these issues - I think what you guys (and gals) do is awesome and I wish I had the same troubleshooting skills.

    I have recently completed a new home build with the following specs:

    Processor: i7-6700k
    Motherboard: Gigabyte GA Z170X Gaming GT
    Memory: Corsair Vengence LPX DDR4, 2666
    GPU: Sapphire Radeon R9 Fury
    SSD: Intel 750 Series, 1.2 TB
    PSU: Corsair RM Series 750 Watt
    Case: Corsair Carbide Series Air 540
    OS: Windows 10 Home

    The build went fairly well and the computer seems rather stable (and very, very quiet). But the main problem I am having is that after the computer wakes up from sleep mode, it crashes a few seconds later and re-boots. The event log will be riddled with entries upon reboot, but one critical event in particular catches my attention:

    Event ID: 41, Kernel-Power

    There are also a number of Errors that show up; not sure if they are normal or not but I suspect errors should not typically occur. I've updated all of my device drives but that didn't really seem to help the issue. I also tried changing the power settings and un-selecting "Fast Startup" as per a recommendation I read on a different forum but that had no effect. To prevent the system crash, I've simply been shutting down my computer after I am done using it which isn't a bad thing, but I'd like to have the option of using sleep mode. Attached below is a screen shot of my event log:

    Home build: crash after waking up from "sleep mode"-event-log.png

    Also, for what it's worth, I remember having a bitch of a time with sleep mode with RAID 0 on my old computer, so perhaps Windows does not yet adequately support "sleep mode" with PCI-E controllers.

    Thanks again,

    Michael
      My Computer


  2. Posts : 13,848
    Win10 Version 22H2 Pro and Home, Win11 Pro and Home
       #2

    Double posting? Not nice. You also posted in the proper section called BSOD Crashes and Debugging.
      My Computers


  3. Posts : 4
    Windows 10 Home
    Thread Starter
       #3

    Berton said:
    Double posting? Not nice. You also posted in the proper section called BSOD Crashes and Debugging.

    Did you read the response I had in BSOD section from axe0? Clearly not as it instructed me to post in Performance and Maintenance.
      My Computer


  4. Posts : 39
    Microsoft Windows 10 Home 64-bit 10240 Multiprocessor Free
       #4

    Although technically it is a double post, if you look through his other thread, you will see that he doesn't actually get a BSOD, so the "double post" was because he didn't post it in the right section the first time.
      My Computer


  5. Posts : 14,901
    Windows 10 Pro
       #5

    Berton said:
    Double posting? Not nice. You also posted in the proper section called BSOD Crashes and Debugging.
    Hi Berton,

    I ask some people who create a thread in the BSOD section to create a new thread in other sections.
    The reason for this is that those threads do not belong in the BSOD section.
    If they copy/paste the content, that is fine for once because the content explains the problem and nobody wants to rewrite the content twice.
      My Computers


  6. Posts : 13,848
    Win10 Version 22H2 Pro and Home, Win11 Pro and Home
       #6

    I can only go with what I got chastised for doing some time back, once scolded I tend to believe the scolder and assume others should abide by the same.
      My Computers


 

  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 23:26.
Find Us




Windows 10 Forums