Kernel-Power 41 BSOD Error

[PortableHighGround]

Hello and thanks for taking the time to help me out!

First the stuff outlined in the BSOD post requirements:

Spoiler

No dump files have been created in the 10+ crashes I've had in the past week.

 

OS- Windows 10 x64 OEM Version

Age of system - about 5-6 years old

Re-installed OS about 3 days ago

CPU - Intel i7-6700k

GPU - GTX 1080

Motherboard - Gigabyte GA-Z170-HD3P

Power Supply - Corsair 650W

System Manufacturer - Cyperpower PC (yes yes pre-built ew)

Model Number - 00326-01855-01991-AAOEM (not sure if this is right)

Desktop

BIOS - fully up to date

Ok so, what's happening?

For about the past 1-2 weeks my computer has been experiencing completely random BSOD.  The BSOD seems very random, sometimes it will crash as I log into windows, other times 1-2 hours after I've been playing VR games.  Every time the blue screen flashes very quickly then the computer immediately restarts, so to figure out what went wrong I looked up in event viewer the crash report and this is what I've got: 

Spoiler

Kernel-Power 41

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

  <Level>1</Level>

  <Task>63</Task>

  <Opcode>0</Opcode>

  <Keywords>0x8000400000000002</Keywords>

  <TimeCreated SystemTime="2021-05-11T01:46:17.4273277Z" />

  <EventRecordID>2128</EventRecordID>

  <Correlation />

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

  <Channel>System</Channel>

  <Computer>-------</Computer>

  <Security UserID="-------" />

  </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">3</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>

So what have I tried already:

• First off I tried to update windows, to which I was getting an instillation error, so I decided to download the windows instillation media and perform an in place upgrade, that went fine and I was able to update windows successfully.
• I then decided to turn off windows fast boot (as suggested by an article) - which had no change to the random BSOD.
• Next I noticed I got a SMART drive error on my secondary hard drive, so out of curiosity I unplugged the drive from the computer with no change to the random BSOD.
• I also performed a Windows Memory Diagnostic with nothing being found
• I also noticed some weird issues with my video and did a full reinstall of my video card drivers
• I have also run OCCT stress tests on everything, with again no change to the random BSOD.
• The one thing that did seem to work was unplugging all my unnecessary USB devices; however, the random BSOD still occurred, just now the computer seems to have more time until another crash.

Any ideas on further tests and other fixes will be greatly appreciated!

Thanks,

- Portable High Ground

[Bombastinator]

1 hour ago, PortableHighGround said:

Hello and thanks for taking the time to help me out!

First the stuff outlined in the BSOD post requirements:

  Reveal hidden contents

No dump files have been created in the 10+ crashes I've had in the past week.

 

OS- Windows 10 x64 OEM Version

Age of system - about 5-6 years old

Re-installed OS about 3 days ago

CPU - Intel i7-6700k

GPU - GTX 1080

Motherboard - Gigabyte GA-Z170-HD3P

Power Supply - Corsair 650W

System Manufacturer - Cyperpower PC (yes yes pre-built ew)

Model Number - 00326-01855-01991-AAOEM (not sure if this is right)

Desktop

BIOS - fully up to date

Ok so, what's happening?

For about the past 1-2 weeks my computer has been experiencing completely random BSOD.  The BSOD seems very random, sometimes it will crash as I log into windows, other times 1-2 hours after I've been playing VR games.  Every time the blue screen flashes very quickly then the computer immediately restarts, so to figure out what went wrong I looked up in event viewer the crash report and this is what I've got: 

  Reveal hidden contents

Kernel-Power 41

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

  <Level>1</Level>

  <Task>63</Task>

  <Opcode>0</Opcode>

  <Keywords>0x8000400000000002</Keywords>

  <TimeCreated SystemTime="2021-05-11T01:46:17.4273277Z" />

  <EventRecordID>2128</EventRecordID>

  <Correlation />

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

  <Channel>System</Channel>

  <Computer>-------</Computer>

  <Security UserID="-------" />

  </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">3</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>

So what have I tried already:

• First off I tried to update windows, to which I was getting an instillation error, so I decided to download the windows instillation media and perform an in place upgrade, that went fine and I was able to update windows successfully.
• I then decided to turn off windows fast boot (as suggested by an article) - which had no change to the random BSOD.
• Next I noticed I got a SMART drive error on my secondary hard drive, so out of curiosity I unplugged the drive from the computer with no change to the random BSOD.
• I also performed a Windows Memory Diagnostic with nothing being found
• I also noticed some weird issues with my video and did a full reinstall of my video card drivers
• I have also run OCCT stress tests on everything, with again no change to the random BSOD.
• The one thing that did seem to work was unplugging all my unnecessary USB devices; however, the random BSOD still occurred, just now the computer seems to have more time until another crash.

Any ideas on further tests and other fixes will be greatly appreciated!

Thanks,

- Portable High Ground

This one becomes somewhat low probability if the memory passed standard tests, but it at least doesn’t cost anything if it does take a while.  You put a single stick of memory in slot one and see if the problem goes away if it does the other stick (or one of the other sticks of more than two) (or next)  is bad.  If it doesn’t you do it with the other stick and see if it goes away then.  If it does the first stick is bad.  If it happens both (or all 4 times) times it’s a different problem.  It detects smaller faults than the windows apps does. 
 

Another thought is the PSU.  Trying a new bigger one could solve the issue if the thing is drawing too much power if the cpu and gpu spike at the same time. Again, not super likely , but if we’re grasping at straws these two are floating there. 

Edited May 11, 2021 by Bombastinator

[PortableHighGround]

6 hours ago, Bombastinator said:

This one becomes somewhat low probability if the memory passed standard tests, but it at least doesn’t cost anything if it does take a while.  You put a single stick of memory in slot one and see if the problem goes away if it does the other stick (or one of the other sticks of more than two) (or next)  is bad.  If it doesn’t you do it with the other stick and see if it goes away then.  If it does the first stick is bad.  If it happens both (or all 4 times) times it’s a different problem.  It detects smaller faults than the windows apps does. 
 

Another thought is the PSU.  Trying a new bigger one could solve the issue if the thing is drawing too much power if the cpu and gpu spike at the same time. Again, not super likely , but if we’re grasping at straws these two are floating there. 

Hi thanks so much for the response my friend!

I’ll definitely give swapping out the RAM a try later today but I do have one question regarding it. When I do run with just one stick (I do have 4) should I be performing memory diagnostics or just waiting to see if another crash occurs?

 

If that doesn’t work, I’ll borrow an old but still functioning 850 W PSU from a friend and give that a try and let you know how it works.

Thanks again!

[Bombastinator]

2 hours ago, PortableHighGround said:

Hi thanks so much for the response my friend!

I’ll definitely give swapping out the RAM a try later today but I do have one question regarding it. When I do run with just one stick (I do have 4) should I be performing memory diagnostics or just waiting to see if another crash occurs?

 

If that doesn’t work, I’ll borrow an old but still functioning 850 W PSU from a friend and give that a try and let you know how it works.

Thanks again!

I assume you already did memory diagnostics.  If they’re 8g  sticks they will be half full just running the OS and functioning off the bat.  If the stick is bad a crash should happen when the bad bit is addressed.  Assuming that is what is causing the crashes. Might not be.  The test predates memory diagnostics.  It’s old school.  It s capable of finding very subtle problems a memory diagnostic might not.  It’s even slower  than  a memory diagnostic though. Especially if there are lots of sticks.  If it doesn’t work the first two tries though chances are it won’t. It relies on the concept that there are multiple sticks and more than one likely won’t go bad at once, which is a bit imperfect. 

Edited May 11, 2021 by Bombastinator

[PortableHighGround]

30 minutes ago, Bombastinator said:

I assume you already did memory diagnostics.  If they’re 8g  sticks they will be half full just running the OS and functioning off the bat.  If the stick is bad a crash should happen when the bad bit is addressed.  Assuming that is what is causing the crashes. Might not be.  The test predates memory diagnostics.  It’s old school.  It s capable of finding very subtle problems a memory diagnostics might not.  It’s even slower  than a memory diagnostics though. Especially if there are lots of sticks.  If it doesn’t work the first two tries though chances are it won’t. It relies on the concept that there are multiple sticks and more than one likely won’t go bad at once, which is a bit imperfect. 

Okay I think I’m following, just to make sure though: there’s not some sort of test to do with just one stick of ram on, and what I should try is to fill it up the memory with programs to see if it’ll crash when a bad bit gets addressed?

[Bombastinator]

6 hours ago, PortableHighGround said:

Okay I think I’m following, just to make sure though: there’s not some sort of test to do with just one stick of ram on, and what I should try is to fill it up the memory with programs to see if it’ll crash when a bad bit gets addressed?

Yeah.  It’s not so much “a test” as testing.  A plug it in see if it works approach.  A memory diagnostic app will get 90+% of stuff and is much faster, so it’s a low probability thing saved for “it behaves like a possible memory problem but memory diagnostics come up clean” and other stuff has already been tried.  A filling in the corners move. Putting in just one stick isolates the tested part and makes it easier to address all the memory because there’s so much less of it.  It may very well be a situation where it still crashes with not only the first stick but the second as well, in which case dram likely isn’t the problem. Could still be a motherboard issue with a memory controller or a dram slot that is horked, but it’s not the dram itself.

Edited May 11, 2021 by Bombastinator

[PortableHighGround]

On 5/11/2021 at 3:46 PM, Bombastinator said:

Yeah.  It’s not so much “a test” as testing.  A plug it in see if it works approach.  A memory diagnostic app will get 90+% of stuff and is much faster, so it’s a low probability thing saved for “it behaves like a possible memory problem but memory diagnostics come up clean” and other stuff has already been tried.  A filling in the corners move. Putting in just one stick isolates the tested part and makes it easier to address all the memory because there’s so much less of it.  It may very well be a situation where it still crashes with not only the first stick but the second as well, in which case dram likely isn’t the problem. Could still be a motherboard issue with a memory controller or a dram slot that is horked, but it’s not the dram itself.

Hey just wanna update real quick, so when I removed all the ram sticks and tested one at a time, it didn't crash for any of the sticks.  So then I decided to put all 4 back in and it hasn't crashed in the few days I've been using it since!  I bet that it was a faulty connection or something related to that.  Thanks for your help Bombastinator!

[PortableHighGround]

Hate to say it but it literally just crashed again after a lot longer of uptime than before.  I'll attempt swapping the power supply next, as I'm pretty sure it isn't the ram that is causing the problem, (I made sure to fill up the ram sticks to as full as I could with youtube tabs).  I'll update again after that.

[PortableHighGround]

Hooked up friends PSU, system has been running for about 24 hours with no crash.  I ordered a new 850 W PSU (its not necessary but I'm hoping to upgrade soon and the extra wattage will be one less thing to worry about).  Seems like the old one was shorting or something like that.