Question PC randomly restarts with no bsod

[Tezeract]

This problem has been annoying me for several days now. I'm running win 10 22h2 and the pc randomly restarts with no bsod or error code. it happens at random times, not related to any particular app, wether if it's just sitting idle or playing games or browsing something.

Things I've already tried
- reinstalled graphic card drivers using ddu
- ran memtest 86 with no errors
- ran malware bytes scan, came up clean
- changed powers settings
- disabled automatic restart
- increased the hibernation file size to 100%
- ran sfc scannow, it said it repaired some corrupted files but the issue came back again after some time

issue has really stumped me. pls help
this is what the dump file showed a few days ago. now when it restarts, there is no dump file being created at all



Loading Dump File [C:\Windows\Minidump\041524-46140-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have process information
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff806`47600000 PsLoadedModuleList = 0xfffff806`4822a770
Debug session time: Mon Apr 15 21:25:02.772 2024 (UTC + 5:30)
System Uptime: 0 days 1:53:40.420
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......
Loading User Symbols
Unable to get PEB pointer
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`479fd5b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffbe8a`2e86eea0=00000000000000a0
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 000000000000000b, The hibernation file is too small.
Arg2: 00000000cbc31000, Size of the hibernation file.
Arg3: 0000000000000005, HIBERFILE_PROGRESS_TABLE_PAGES
Arg4: 000000006595b000

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3218

Key : Analysis.Elapsed.mSec
Value: 13369

Key : Analysis.IO.Other.Mb
Value: 5

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 25

Key : Analysis.Init.CPU.mSec
Value: 749

Key : Analysis.Init.Elapsed.mSec
Value: 50266

Key : Analysis.Memory.CommitPeak.Mb
Value: 93

Key : Bugcheck.Code.LegacyAPI
Value: 0xa0

Key : Bugcheck.Code.TargetModel
Value: 0xa0

Key : Dump.Attributes.AsUlong
Value: 9

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: 0xa0_b_HIBERFILE_TOO_SMALL_nt!PopRequestWrite

Key : Failure.Hash
Value: {30230df0-b231-2774-9072-86767a01757a}


BUGCHECK_CODE: a0

BUGCHECK_P1: b

BUGCHECK_P2: cbc31000

BUGCHECK_P3: 5

BUGCHECK_P4: 6595b000

FILE_IN_CAB: 041524-46140-01.dmp

DUMP_FILE_ATTRIBUTES: 0x9
Hiber Crash Dump
Kernel Generated Triage Dump

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffbe8a`2e86ee98 fffff806`47fa6d57 : 00000000`000000a0 00000000`0000000b 00000000`cbc31000 00000000`00000005 : nt!KeBugCheckEx
ffffbe8a`2e86eea0 fffff806`47f96da6 : ffffc28e`bd4714f0 ffff808e`10958e20 ffffbe8a`2e86f010 00000000`00006000 : nt!PopRequestWrite+0xffa3
ffffbe8a`2e86ef40 fffff806`47988c44 : 00000000`00000010 00000000`00000000 80000000`00000000 8a000001`cee8a863 : nt!PopCompressCallback+0x16
ffffbe8a`2e86ef70 fffff806`47b9179c : ffffd680`2e467000 00000000`02008014 00000003`00000000 00000000`00000014 : nt!RtlpMakeXpressCallback+0x24
ffffbe8a`2e86efa0 fffff806`47a97a91 : ffffd680`2e466a03 ffffc28e`cd185000 ffffc28e`cd185000 00000000`00000003 : nt!RtlCompressBufferXpressHuffMax+0x1f8
ffffbe8a`2e86f070 fffff806`47f974a5 : 00001052`f73df548 00000000`00000003 00000000`00000001 00000000`0001a000 : nt!RtlCompressBufferProgress+0x114681
ffffbe8a`2e86f0d0 fffff806`47f96d4d : ffffc28e`bd4714f0 ffffbe8a`00000000 ffffc28e`cbe00000 00000000`00000010 : nt!PopAddPagesToCompressedPageSet+0xb1
ffffbe8a`2e86f150 fffff806`47fa6986 : ffffc28e`bd4714f0 00000000`002370a4 00000000`00150000 ffff808e`10958e20 : nt!PopWriteHiberImage+0xd9
ffffbe8a`2e86f310 fffff806`47a06bc5 : 00000000`00000000 00000000`00000004 00000000`00000000 00000000`00000037 : nt!PopSaveHiberContext+0x101e6
ffffbe8a`2e86f5f0 fffff806`479857aa : fffff78e`00008000 fffff806`47a70000 fffff806`46881180 fffff806`47a06b90 : nt!PopSaveHiberContextWrapper+0x35
ffffbe8a`2e86f620 fffff806`47f962cc : ffffbe8a`2e86f800 ffffbe8a`2e86f840 fffff806`46881180 00000000`00000004 : nt!HaliAcpiSleep+0x20a
ffffbe8a`2e86f6b0 fffff806`47f96026 : fffff806`48250560 ffffbe8a`2e86f830 fffff806`48250560 00000000`00000001 : nt!PopHandleNextState+0x1fc
ffffbe8a`2e86f700 fffff806`47f95d21 : 00000000`00000100 fffff806`48250560 00000000`00000000 00000000`00000001 : nt!PopIssueNextState+0x1a
ffffbe8a`2e86f730 fffff806`47f99439 : ffffbe8a`2e86fa20 00000000`00000000 00000000`00000000 fffff806`47f991bf : nt!PopInvokeSystemStateHandler+0x2b9
ffffbe8a`2e86f930 fffff806`47f98dda : ffffffff`00000000 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : nt!PopEndMirroring+0x1e9
ffffbe8a`2e86f9f0 fffff806`47f98ac5 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!MmDuplicateMemory+0x2be
ffffbe8a`2e86fa80 fffff806`479078e5 : ffffc28e`c44d1000 ffffc28e`c44d1040 fffff806`47f98990 00000000`00000000 : nt!PopTransitionToSleep+0x135
ffffbe8a`2e86fb10 fffff806`47a06378 : fffff806`46881180 ffffc28e`c44d1040 fffff806`47907890 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffbe8a`2e86fb60 00000000`00000000 : ffffbe8a`2e870000 ffffbe8a`2e869000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nt!PopRequestWrite+ffa3

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.4046

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: ffa3

FAILURE_BUCKET_ID: 0xa0_b_HIBERFILE_TOO_SMALL_nt!PopRequestWrite

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {30230df0-b231-2774-9072-86767a01757a}

PROCESS_NAME: Unknown

Followup: MachineOwner

 

[Aeacus]

Full system specs, including PSU make and model (or part number) is? Also, how old the PSU is, and was the PSU bought new or used/refurbished?

 

[Tezeract]

Full system specs, including PSU make and model (or part number) is? Also, how old the PSU is, and was the PSU bought new or used/refurbished?

I5 7400, 8gb ram, rx 580 graphics card. The psu is Cooler Master MWE 550watt. It's around three years old

 

[Aeacus]

The psu is Cooler Master MWE 550watt.

What i like to know is the part number of the PSU, since there are several iterations of MWE series, from mediocre quality all the way to the crap quality.

So, it would be nice if you'd take a pic of PSU's label, upload the pic to net (e.g www.imgur.com) and share the pic here.

In the mean time; when you boot into Safe Mode, does the reboots/BSoD still happen?

 

[Tezeract]

What i like to know is the part number of the PSU, since there are several iterations of MWE series, from mediocre quality all the way to the crap quality.

So, it would be nice if you'd take a pic of PSU's label, upload the pic to net (e.g www.imgur.com) and share the pic here.

In the mean time; when you boot into Safe Mode, does the reboots/BSoD still happen?

MPE - 5501 - ACABW is the part number looks like. It's the 80plus bronze 230V one.

Haven't booted into safe mode much tbh. But it wasn't happening when I did boot for an hour or so. It's really random, happens after hours or days.

 

[Aeacus]

MPE - 5501 - ACABW is the part number looks like. It's the 80plus bronze 230V one.

That's a low quality PSU and i'd replace it ASAP.

For 2nd opinion about your PSU build quality, look it up from PSU Tier list,
link: https://forums.tomshardware.com/thr...er-list-rev-14-8-final-update-jul-21.3624094/

You'll find it under Tier C, low-priority unit: Cooler Master MWE V2 Bronze [MPE] 230V.

For new PSU, look towards Seasonic Focus/Vertex/PRIME or Corsair RMx/RMi/HXi/AXi or Super Flower Leadex Gold/Platinum/Titanium, in 650W range. - All these PSUs are Tier A.
Now, if you plan to upgrade your GPU to RTX 4070 Ti, then 750W unit. If RTX 4080 then 1000W PSU and RTX 4090 does fine with 1600W unit. 650W unit is good for your current GPU and up to RTX 4070.

I'm quite sure that once you get yourself a good/great quality PSU, your random restarts go away.

 

[Tezeract]

That's a low quality PSU and i'd replace it ASAP.

For 2nd opinion about your PSU build quality, look it up from PSU Tier list,
link: https://forums.tomshardware.com/thr...er-list-rev-14-8-final-update-jul-21.3624094/

You'll find it under Tier C, low-priority unit: Cooler Master MWE V2 Bronze [MPE] 230V.

For new PSU, look towards Seasonic Focus/Vertex/PRIME or Corsair RMx/RMi/HXi/AXi or Super Flower Leadex Gold/Platinum/Titanium, in 650W range. - All these PSUs are Tier A.
Now, if you plan to upgrade your GPU to RTX 4070 Ti, then 750W unit. If RTX 4080 then 1000W PSU and RTX 4090 does fine with 1600W unit. 650W unit is good for your current GPU and up to RTX 4070.

I'm quite sure that once you get yourself a good/great quality PSU, your random restarts go away.

so you're 100% sure it's a psu problem then? cause it only started a few weeks ago, and the problem happens even when not intensive tasks like gaming

could it be a driver issue?

 

[Aeacus]

Hardware wise, the poorest one is the PSU, that you cheaped out on. And since PSU is the one that powers everything and has to keep the PC running, random restarts are often PSU issue which can't keep the PC running. Either that, or random restarts are caused by overheating CPU/GPU, which i don't think is the issue, because you have restarts even when system is idle.

Now, if you think it is software issue, then there is easy and cost free fix:
* format your C:\ drive
* make a clean Win installation

This will get rid of all software issues.

Still, there is lingering danger that your low quality PSU can go "boom", release magic smoke and for good measure, fry everything it is connected to.
So, your call, if you want to risk it and buy completely new PC after that happens. Or buy good/great quality PSU now and be safe that PSU won't kill your hardware.

Different persons have different standards (some have higher standards while others have lower standards) and it's up to every person to decide how good of a build quality components are safe to use in their PC. But keep in mind that PSU is the most important component inside the PC since it powers everything.

Since i care a lot about all my PCs, i won't put a mediocre quality unit into my PC that fails to meet ATX PSU standards set in place for all OEMs to follow, so that the PSUs are safe to use and doesn't damage other components. In fact, i've gone above and beyond regarding PSUs in my PCs;
Some may call me nuts that i payed €206.80 for a PSU that sits in my Skylake build (Seasonic PRIME 650 80+ Titanium [SSR-650TD]) and my latest PSU purchase for Haswell build costed €205.50 (Seasonic PRIME Ultra 650 80+ Titanium [SSR-650TR]), while i would've been safe with a PSU that costs €80.50 (Seasonic Focus GX-550). While that can be true and i could've saved a lot of money, i feel safe and comfortable that my two main PCs are powered by the best offered by Seasonic. Only for my 3rd PC, old AMD build, i slightly reduced my PSU quality standard and bought a PSU that costed €101.50 (Seasonic Focus+ 550 80+ Platinum [SSR-550PX]). Still, all 3 of my PSUs are Tier A quality.
On top of that, my Focus PSU has 10 years of warranty while my two PRIME PSUs have 12 years of warranty. 12 years warranty is the most you'll ever get with PSUs. That speaks volumes regarding PSU reliability. For comparison, your CM MWE Bronze PSU has 5 years of warranty, half of what my "lowest spec" PSU has it.

I won't suggest expensive PSUs in builds when the budget is way restricted. But i still suggest getting a PSU that at least meets all the ATX PSU standards (like Seasonic Focus-GM-650 or Focus-GX-650 or Focus-GX-750 ATX 3.0). These three Seasonic Focus PSUs cost ~€100.

 

[LinuxDevice]

This is sort of overly general, but you will tend to find that switching mode power supplies need a certain load to be stable, and so they shut down if output is not what it considers stable. The power supply is highly suspect.

The CPU itself has something called a triple exception possible. CPUs are designed to try to avoid corrupting or destroying components, including data (not just hardware). Various methods exist for handling errors ("exceptional conditions"). When the things get to a certain failure point the CPU will intentionally shut down to avoid corruption. It is possible that something in hardware or software was so corrupt that the CPU just shut down. If that is the case, then you'd need to know why.

One possibility is that a particular software is a cause, but this is very unlikely. A bad driver or other issue usually gets handled and you might see some sort of debug dump. To reach a triple exception it is more likely that the RAM itself is corrupt, and having this occur under so many different conditions of what software is running says it likely isn't RAM, but you could run memtest86 overnight to test.

A very common reason for RAM to corrupt, if it is otherwise functional, is that the power must be cleanly delivered. Power supplies, when going bad, quite often show up first as corrupt RAM even though the RAM is not at fault. Something like memtest86 might show the RAM is 100% functional, and yet still fail under load...because power delivery under load is more difficult to regulate.

Test with memtest86. If it passes, likely it is your power supply. If memtest86 fails after running all night, then the question is whether it fails at the same address each time, or if it is random. If it is random, then the power supply is possibly the issue (or power components on the motherboard, but the PSU is more likely); if the address of failure is the same place each time, then the RAM itself might be the reason for a triple exception causing instant shutdown.

 

[Tezeract]

This is sort of overly general, but you will tend to find that switching mode power supplies need a certain load to be stable, and so they shut down if output is not what it considers stable. The power supply is highly suspect.

The CPU itself has something called a triple exception possible. CPUs are designed to try to avoid corrupting or destroying components, including data (not just hardware). Various methods exist for handling errors ("exceptional conditions"). When the things get to a certain failure point the CPU will intentionally shut down to avoid corruption. It is possible that something in hardware or software was so corrupt that the CPU just shut down. If that is the case, then you'd need to know why.

One possibility is that a particular software is a cause, but this is very unlikely. A bad driver or other issue usually gets handled and you might see some sort of debug dump. To reach a triple exception it is more likely that the RAM itself is corrupt, and having this occur under so many different conditions of what software is running says it likely isn't RAM, but you could run memtest86 overnight to test.

A very common reason for RAM to corrupt, if it is otherwise functional, is that the power must be cleanly delivered. Power supplies, when going bad, quite often show up first as corrupt RAM even though the RAM is not at fault. Something like memtest86 might show the RAM is 100% functional, and yet still fail under load...because power delivery under load is more difficult to regulate.

Test with memtest86. If it passes, likely it is your power supply. If memtest86 fails after running all night, then the question is whether it fails at the same address each time, or if it is random. If it is random, then the power supply is possibly the issue (or power components on the motherboard, but the PSU is more likely); if the address of failure is the same place each time, then the RAM itself might be the reason for a triple exception causing instant shutdown.

This is what the event viewer shows after the reboot. What does it mean
https://ibb.co/VQ1yKzH

 

[LinuxDevice]

This is what the event viewer shows after the reboot. What does it mean
https://ibb.co/VQ1yKzH

This is a message I have no knowledge of. You'd probably need to Google that. It does sound like there is some sort of corruption being avoided, but Windows tends to hide issues in its messages and require looking them up.

 

[Aeacus]

This is what the event viewer shows after the reboot. What does it mean
https://ibb.co/VQ1yKzH

I don't do well with software issues. I'm specialized on hardware issues. But found these from Google if you want to know what ID 16384 is,
link 1: https://community.spiceworks.com/t/system-reboot-with-event-id-16384/788559
link 2: https://www.reddit.com/r/techsupport/comments/wuz9l5/securityspp_event_16384_repeating_every_minute/

Software wise, things to try:
1. Open Start.
2. Search for Command Prompt (or cmd.exe), right-click the top result, and select the Run as administrator option.
3. Type the following command to perform system repair and press Enter:
SFC /scannow
4. If the scan found corrupt files and repaired them, run the same command again, just in case:
(if no errors were found, skip to step #5)
SFC /scannow
5. Once no errors are found with SFC /scannow, type the following command to perform a quick check and press Enter:
DISM /Online /Cleanup-Image /CheckHealth
6. Once this is done and when corruption is detected, type in another command for in-depth scan and press Enter:
DISM /Online /Cleanup-Image /ScanHealth
7. Once this is done and there are issues with system image, type in another command for fixing it and press Enter:
DISM /Online /Cleanup-Image /RestoreHealth
8. Once the system image repair is complete, type in another command and press Enter:
SFC /scannow
9. After last once completes, final command with Enter press would be:
Exit
This closes the terminal window.

Note: SFC /scannow, DISM /ScanHealth and DISM /RestoreHealth may take a long time to complete. Do not close the terminal window or do not reboot the system, when each of theses scans/fixes are taking place, even when they seemingly get stuck.