Question Reboot 1x daily "Critical; Kernel-Power; Event ID:41" (no dump file) ?

Toggle sidebar Toggle sidebar
A

angelgabbby

Distinguished
Aug 1, 2013
13
0
18,520
(NOTE: I wasnt sure if I should put this under "systems" or here, so I closed my eyes & picked, lol.)

Hi.
My pc randomly started restarting about once a day, since Oct 14th. I realized this due to it would be on the log in screen when I got up or got home. In the event log they all say the same thing:

Critical; Kernel-Power; Event ID:41; Task category (63); Keywords: (70368744177664)(2); The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Click to expand...

I looked in windows\minidump however there are only 4 listed, the most recent was from June! I thought that was weird, but idk.

The critical error shows about monthly, until around 10/14, when it started about daily. I did not install anything then (I double-checked).

There are some odd errors in the event log too, but I didn’t know if I could load the saved event info or the xml in my google drive, and or if it has any info that would put my pc at risk publicly sharing. If its safe to share publicly, I’ll upload it to my google drive & post the link, unless there is a better way?

I just reran a virus scan from another program, just to double check. I also did dism & SFC /scannow . No help.



This is probably not related, but on 10/20 (after this had started doing this for a week or so) we had to replace my power supply. What happened was my pc wouldn’t turn on. After checking a few things, we found out the power supply wasn’t working (volt meter didn’t get an active reading – yes, volt meter is in working order, lol) and replaced the power supply. Nothing has changed on my issue though.



Here is my system info. If I left stuff out, just let me know what I missed.

Thanks for the assistance.


Processor Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz 3.40 GHz
Installed RAM 8.00 GB
System type 64-bit operating system, x64-based processor
Edition Windows 10 Pro
Version 22H2
Installed on ‎5/‎15/‎2023
OS build 19045.3031
Experience Windows Feature Experience Pack 120.2212.3030.0


Item Value
OS Name Microsoft Windows 10 Pro
Version 10.0.19045 Build 19045
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer
System Model
System Type x64-based PC
System SKU
Processor Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, 3401 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Intel Corp. BAP6710H.86A.0055.2011.0215.1656, 2/15/2011
SMBIOS Version 2.6
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer Intel Corporation
BaseBoard Product DP67BA
BaseBoard Version AAG10219-300
Platform Role Workstation
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "10.0.19041.2728"
Time Zone Central Daylight Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.98 GB
Available Physical Memory 2.54 GB
Total Virtual Memory 16.0 GB
Available Virtual Memory 7.69 GB
Page File Space 8.00 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, Disabled by policy, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
 
Sort by date Sort by votes
There is nothing personal or personally identifying in the event logs, we share them all the time, and since you have no recent dumps they will be our main source of troubleshooting info. Export and upload your System and Application logs as follows...
  1. Enter the command eventvwr into the Run command box. The Event Viewer will open.
  2. Locate the Windows Logs folder in the left hand pane and expand it by clicking on the arrow (>) to the left of it.
  3. Right-click on the Application entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'Application' (an .evtx suffix will be added automatically).
  4. Right-click on the System entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'System' (an .evtx suffix will be added automatically).
  5. Upload the Application.evtx and System.evtx files to a cloud service with a link to them here (be sure to make them public).
 
Upvote 0 Downvote
angelgabbby said:
I looked in windows\minidump however there are only 4 listed, the most recent was from June! I thought that was weird, but idk.
Click to expand...
What model PSU are you using?
If there are no minidumps, then PSU would be prime suspect. Or problems with power in your house.
angelgabbby said:
This is probably not related, but on 10/20 (after this had started doing this for a week or so) we had to replace my power supply.
Click to expand...
This probably is very related.
 
Upvote 0 Downvote
ubuysa said:
There is nothing personal or personally identifying in the event logs, we share them all the time, and since you have no recent dumps they will be our main source of troubleshooting info. Export and upload your System and Application logs as follows...
  1. Enter the command eventvwr into the Run command box. The Event Viewer will open.
  2. Locate the Windows Logs folder in the left hand pane and expand it by clicking on the arrow (>) to the left of it.
  3. Right-click on the Application entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'Application' (an .evtx suffix will be added automatically).
  4. Right-click on the System entry and select 'Save all events as...'. Choose a folder anywhere that suits you and a filename of 'System' (an .evtx suffix will be added automatically).
  5. Upload the Application.evtx and System.evtx files to a cloud service with a link to them here (be sure to make them public).
Click to expand...


Done (Hopefully correct... Thank you for the easy to understand instructions)

system.evtx

drive.google.com drive.google.com

application.evtx

drive.google.com drive.google.com
 
Upvote 0 Downvote
From your logs these were not BSODs (hence no dumps) they were uncontrolled crashes. That strongly suggests a hardware problem, the kernel catches most software problems and BSODs.

Can you export the msinfo32.exe output and upload it please? Just do a File > Save and upload the resulting .nfo file.
 
Upvote 0 Downvote
ubuysa said:
From your logs these were not BSODs (hence no dumps) they were uncontrolled crashes. That strongly suggests a hardware problem, the kernel catches most software problems and BSODs.

Can you export the msinfo32.exe output and upload it please? Just do a File > Save and upload the resulting .nfo file.
Click to expand...

Sure! {Links attached below}

I noticed that apparently it had been doing this about 4x a month, various dates, up until it started it regularly in mid October. I kinda found that odd. I mean, I knew several times I would get up or come home to find that it had restarted, but foolishly I just ignored it, ASSuming it mustve had a windows update restart. I dont find any pattern in the days of each month that it had the critical error. I also dont recall anything unusual on the days it first started doing it regularly.

Here is it as txt https://drive.google.com/file/d/1u5TX82AzgwtH1qMApVq8beeULCNd8xZO/view?usp=drive_link

And nfo

msinfo.nfo

drive.google.com drive.google.com
 
Upvote 0 Downvote
SkyNetRising said:
What graphics card are you using?

You downgraded from 600W to 400W PSU ?
I'd expect worn out DELL 400W PSU to be the old one and Thermaltake 600W - new one.
Click to expand...


Nvidia geforce gtx 1660 super

Nope, the thermaltake quit. The 400w is temporary until we can get a better one. We did confirm w/a pc parts store that it would work (granted, this guy THOUGHT he was an expert, but just I wouldnt take anything he says 'to the bank', lol). It started doing this regularly before the power supply switch though and nothing changed about this issue before vs after.
 
Upvote 0 Downvote
SkyNetRising said:
Minimum recommended PSU for GTX 1660 super is 450W.
Your Dell PSU has only 385W on 12V rail.

So ... your problems are most likely caused by PSU.
Click to expand...
But what about the fact it was doing the same thing before I replaced the other one? Just coincidence that the other one made it do the same thing when it was going out?


Also @ubuysa I dont know how important it is, but I also forgot to say that it hasnt ever shutdown/restarted while I have been using it. Its often at minimum an hour or more after I've last touched it.
 
Upvote 0 Downvote
I'm in full agreement with @SkyNetRising that the 400W PSU is wholly unsuitable, so I'm not keen on doing any further troubleshooting until we know you have a capable PSU - there's really no point. In addition, if your previous PSU was flaky and needed replacing that could have been the problem. Get a quality capable PSU and let us know if it crashes afterwards.

I didn't see anything that frightens me in your msinfo32 output, it all looks very normal there.
Are there any minidumps in the folder C:\Windows\Minidump? If so please upload them.
Are there any dumps in ANY sub-folder below the folder C:\Windows\LiveKernelReports? If so please upload them.

When you have a capable PSU, I think it will be worth stopping Windows from auto-restarting, at least then it will be sitting on whatever error screen caused the crash. In case you don't know how to do that, here's how...
  1. Enter the command sysdm.cpl in the RUN command box.
  2. Click the Advanced tab.
  3. Click the bottom Settings button (in Start-up & Recovery).
  4. Uncheck the 'Automatically restart' checkbox.
  5. Click OK and close the dialog.
 
Upvote 0 Downvote
ubuysa said:
I'm in full agreement with @SkyNetRising that the 400W PSU is wholly unsuitable, so I'm not keen on doing any further troubleshooting until we know you have a capable PSU - there's really no point. In addition, if your previous PSU was flaky and needed replacing that could have been the problem. Get a quality capable PSU and let us know if it crashes afterwards.

I didn't see anything that frightens me in your msinfo32 output, it all looks very normal there.
Are there any minidumps in the folder C:\Windows\Minidump? If so please upload them.
Are there any dumps in ANY sub-folder below the folder C:\Windows\LiveKernelReports? If so please upload them.

When you have a capable PSU, I think it will be worth stopping Windows from auto-restarting, at least then it will be sitting on whatever error screen caused the crash. In case you don't know how to do that, here's how...
  1. Enter the command sysdm.cpl in the RUN command box.
  2. Click the Advanced tab.
  3. Click the bottom Settings button (in Start-up & Recovery).
  4. Uncheck the 'Automatically restart' checkbox.
  5. Click OK and close the dialog.
Click to expand...
I am getting a 600 tomorrow, so I'll let you know if it fixes it.
Thanks alot!
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom