[SOLVED] PC Power Cycling Randomly

[Ethan_E]

Lately I've noticed that my PC tends to power cycle specifically when I leave it idle. I've never witnessed it turn off in front of me, but often when I leave the room for a few minutes and come back it has restarted. Looking at Event Viewer always show the same thing first an error with the event ID 6008 telling me that the shutdown was unexpected, after that there is a critical error event ID 41 that says the system rebooted without cleanly shutting down, it says the source is Kernel-Power.

My current system specs are:
- CPU: Ryzen 3800X
- MoBo: MSI X570 GAMING PLUS BIOS A.M0
- RAM: G.SKILL TridentZ 32GB running at 3600mHz with XMP
- GPU: RTX 3070 (LHR)
- WD Black SN750 NVMe SSD
- Corsair 240mm AIO (Not sure of the model)
- PSU: Seasonic 750W 80+ Gold rated unit (again not sure of the exact model but I got it last year)

This problem has persisted throughout multiple different hardware configurations and Windows installations. There hasn't been any specific circumstances that cause this, but I'm starting to suspect either a CPU or motherboard issue since they're the longest standing components in the system. Any insight on this would be greatly appreciated, I'll be happy to provide any further information needed.

 

[helper800]

Do you have any sleep settings enabled? What is the BIOS version is your motherboard on?

 

[Lutfij]

https://forums.tomshardware.com/threads/pc-randomly-power-cycles.3730142/post-22505140
Did you retry performing a DDU but remove all drivers(Intel, AMD and Nvidia), manually reinstall the latest drivers sourced from Nvidia's support site in an elevated command, i.e, Right click installer>Run as Administrator?

PSU: Seasonic 750W 80+ Gold rated unit (again not sure of the exact model but I got it last year)
Take the side panels off your case and then see what the stickered info on the PSU is.

 

[Ethan_E]

Do you have any sleep settings enabled? What is the BIOS version is your motherboard on?

One thing I have noticed is that sleep is very inconsistent, sometimes my monitors will stay on for hours if I leave and never go to sleep it sometimes it goes into sleep exactly how it should. My BIOS revision is E7C37AMS.AM0.

 

[Ethan_E]

https://forums.tomshardware.com/threads/pc-randomly-power-cycles.3730142/post-22505140
Did you retry performing a DDU but remove all drivers(Intel, AMD and Nvidia), manually reinstall the latest drivers sourced from Nvidia's support site in an elevated command, i.e, Right click installer>Run as Administrator?

PSU: Seasonic 750W 80+ Gold rated unit (again not sure of the exact model but I got it last year)
Take the side panels off your case and then see what the stickered info on the PSU is.

That actually didn't fix it at all last time I was just lucky to not have it happen for a few weeks. I can see that the PSU is part of their Focus line but everything else is covered by the PSU shroud and since I'm at school I don't have the tools the disassemble anything right now. All drivers were manually installed a couple of weeks ago when I formatted my SSD and reinstalled Windows

 

[helper800]

My BIOS revision is E7C37AMS.AM0.

Do you mean 7C37vAM?

 

[Ethan_E]

Do you mean 7C37vAM?

Yep, that's the one.

 

[helper800]

Yep, that's the one.

Did you flash to that update recently? If so you may need to reset CMOS. If you do not know how to do that please reply to this message.

 

[Ethan_E]

Did you flash to that update recently? If so you may need to reset CMOS. If you do not know how to do that please reply to this message.

Just reset the CMOS. The default settings in the BIOS always sets the core voltage to 1.4v which I've read is too high so I manually undervolt it to 1.35v. Do you think this could cause it?

 

[Ethan_E]

PSU: Seasonic 750W 80+ Gold rated unit (again not sure of the exact model but I got it last year)
Take the side panels off your case and then see what the stickered info on the PSU is.

The exact model is Seasonic Focus GX-850 SSR-850FX. This is the third power supply I've had in this machine and the problem has persisted so I doubt it's PSU related.

 

[NedSmelly]

A bad stick of RAM is a possibility - it’s worth giving memtest86 a run.

 

[Ethan_E]

A bad stick of RAM is a possibility - it’s worth giving memtest86 a run.

I've ran memtest86 a couple of times and it comes back fine. I also swapped the sticks around to see if that had any effect but it didn't.

 

[helper800]

Just reset the CMOS. The default settings in the BIOS always sets the core voltage to 1.4v which I've read is too high so I manually undervolt it to 1.35v. Do you think this could cause it?

Don't touch the BIOS settings for voltage. Leave the voltage setting on auto. The CPU will only ask for such high voltages when it is idle or near idle to provide the highest single threaded performance. Change the settings to default and then go in and set XMP/DOCP setting back on for the RAM, then save and quit. Test to see if this issues happens again.

 

[Ethan_E]

Don't touch the BIOS settings for voltage. Leave the voltage setting on auto. The CPU will only ask for such high voltages when it is idle or near idle to provide the highest single threaded performance. Change the settings to default and then go in and set XMP/DOCP setting back on for the RAM, then save and quit. Test to see if this issues happens again.

I reenabled XMP after resetting the CMOS. Setting the core voltage back to auto, I'll update with what happens.

 

[Ethan_E]

Ok so about 24 hours later and I was trying to fix an issue with refresh rate and my computer blue screened. Event viewer showed the same events as before but with the added error coming from BugCheck event ID 1001. It says "The computer has rebooted from a bugcheck. The bugcheck was: 0x000000be (0xffff94fadd811009, 0x8a00000000200121, 0xfffff985f40f4180, 0x000000000000000b). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: c53e2063-e149-470b-9c0a-030f0194e45e." I think I'm going to try DDU again but once again any further advice would be appreciated.

 

[Ethan_E]

Analyzing in WinDbg gives me the following:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the BugCheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffff94fadd811009, Virtual address for the attempted write.
Arg2: 8a00000000200121, PTE contents.
Arg3: fffff985f40f4180, (reserved)
Arg4: 000000000000000b, (reserved)

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2749

Key : Analysis.Elapsed.mSec
Value: 4869

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0xbe

Key : Failure.Bucket
Value: AV_nt!MiSystemFault

Key : Failure.Hash
Value: {d80c40a2-5000-439f-696b-1bd8abb14be3}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: be

BUGCHECK_P1: ffff94fadd811009

BUGCHECK_P2: 8a00000000200121

BUGCHECK_P3: fffff985f40f4180

BUGCHECK_P4: b

FILE_IN_CAB: 021824-6578-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: services.exe

TRAP_FRAME: fffff985f40f4180 -- (.trap 0xfffff985f40f4180)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff94fadd810ff1 rbx=0000000000000000 rcx=ffff94fadd811011
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80423e12fb0 rsp=fffff985f40f4318 rbp=fffff985f40f44b0
r8=0000000000000021 r9=0000000000000020 r10=ffff94fadd811010
r11=0000000078088090 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!memset+0x30:
fffff804`23e12fb0 4a895408f8 mov qword ptr [rax+r9-8],rdx ds:ffff94fa`dd811009=????????????????
Resetting default scope

STACK_TEXT:
fffff985`f40f3ed8 fffff804`23e3bbb3 : 00000000`000000be ffff94fa`dd811009 8a000000`00200121 fffff985`f40f4180 : nt!KeBugCheckEx
fffff985`f40f3ee0 fffff804`23c24660 : ffff8501`2f8f4000 00000000`00000003 fffff985`f40f4200 00000000`00000000 : nt!MiSystemFault+0x1d8653
fffff985`f40f3fe0 fffff804`23e0d358 : ffffffff`ffffffff 00000000`00000001 ffff8501`2f8e6180 fffff804`23c8eff5 : nt!MmAccessFault+0x400
fffff985`f40f4180 fffff804`23e12fb0 : fffff804`23cebb08 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x358
fffff985`f40f4318 fffff804`23cebb08 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memset+0x30
fffff985`f40f4320 fffff804`242d3387 : 00000000`0000010e 00000000`78088091 00000000`78087f83 00000000`00000000 : nt!RtlClearBitsEx+0x98
fffff985`f40f4350 fffff804`242d330c : ffffd902`fecd9c20 00000000`00000001 00000000`00000000 00000000`000010d8 : nt!MiMarkRetpolineBits+0x63
fffff985`f40f4380 fffff804`24226b80 : ffffd902`fecd9c20 ffffd902`fecd9c20 fffff985`f40f44b0 00000000`00000001 : nt!MiMarkKernelImageRetpolineBits+0x34
fffff985`f40f43b0 fffff804`24171d71 : 00000000`00000000 fffff804`ffffffff ffffa482`00000001 ffffb608`186c8bc0 : nt!MiUnloadSystemImage+0x1309f8
fffff985`f40f4550 fffff804`24171c9e : ffffd902`f650d3e0 fffff985`f40f4880 00000000`00000000 fffff985`f40f49f0 : nt!MmUnloadSystemImage+0x41
fffff985`f40f4580 fffff804`24045880 : ffffd902`f650d3e0 fffff985`f40f4880 ffffd902`f650d3e0 fffff804`24074f9f : nt!IopDeleteDriver+0x4e
fffff985`f40f45d0 fffff804`23c45c07 : 00000000`00000000 00000000`00000000 fffff985`f40f4880 ffffd902`f650d410 : nt!ObpRemoveObjectRoutine+0x80
fffff985`f40f4630 fffff804`23c45b2e : ffffd902`f650d410 fffff985`f40f49f0 ffffd902`f650d3e0 00000000`00060001 : nt!ObfDereferenceObjectWithTag+0xc7
fffff985`f40f4670 fffff804`24169968 : ffffd902`f650d410 fffff985`f40f4880 fffff985`f40f49f0 00000000`c0000001 : nt!HalPutDmaAdapter+0xe
fffff985`f40f46a0 fffff804`2429d97b : ffffd902`fe6ea640 00000000`00000000 00000000`00000001 ffffd902`f650d410 : nt!IopUnloadDriver+0x250
fffff985`f40f47d0 fffff804`23e11138 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffb607`fc9c9060 : nt!NtUnloadDriver+0xb
fffff985`f40f4800 fffff804`23e02290 : fffff804`242471fc ffffd902`fe6ea640 fffff804`2402af0d 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
fffff985`f40f4998 fffff804`242471fc : ffffd902`fe6ea640 fffff804`2402af0d 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff985`f40f49a0 fffff804`2429d97b : ffffd902`fe6ea640 000000c0`3d8fea14 00000000`00000000 00000000`00000000 : nt!IopUnloadDriver+0xddae4
fffff985`f40f4ad0 fffff804`23e11138 : ffffd902`fe6ea600 00000284`73f08460 fffff985`f40f4b80 00000000`00000000 : nt!NtUnloadDriver+0xb
fffff985`f40f4b00 00007ffd`1cff08d4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000c0`3d8fe9c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`1cff08d4


SYMBOL_NAME: nt!MiSystemFault+1d8653

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.4046

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 1d8653

FAILURE_BUCKET_ID: AV_nt!MiSystemFault

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d80c40a2-5000-439f-696b-1bd8abb14be3}

Followup: MachineOwner
---------

 

[Ethan_E]

Update: After reinstalling drivers I’m now not able to keep Windows from crashing. I’m now getting a variety of BSOD messages instead of just the one. Running chkdsk /f /r /x in recovery.

 

[helper800]

Update: After reinstalling drivers I’m now not able to keep Windows from crashing. I’m now getting a variety of BSOD messages instead of just the one. Running chkdsk /f /r /x in recovery.

Do you have another graphics card to test with? What are CPU and GPU temps like? Did you upgrade from a prior windows to the version you are on now? We know its not the PSU because of two things, if a PSU cuts power there is no BSOD message, just a blank screen, and you have tried multiple PSUs. Have you tried running the PC without the XMP/DOCP profile? Does the GPU work fine in another PC?

You may have to try reinstalling windows, or swapping out parts to see if the problems persist. A local PC parts shop would likely be able to help with the latter.

 

[Ethan_E]

Do you have another graphics card to test with? What are CPU and GPU temps like? Did you upgrade from a prior windows to the version you are on now? We know its not the PSU because of two things, if a PSU cuts power there is no BSOD message, just a blank screen, and you have tried multiple PSUs. Have you tried running the PC without the XMP/DOCP profile? Does the GPU work fine in another PC?

You may have to try reinstalling windows, or swapping out parts to see if the problems persist. A local PC parts shop would likely be able to help with the latter.

I've had a GTX 1070ti and the current RTX 3070 in it and the problem has persisted. It's always been a Windows 10 machine. I reinstalled the AMD chipset drivers earlier today and I noticed that my power plan now says "Ryzen Balanced" instead of just "Balanced" so I'm hoping that might have solved the issue since I haven't had instability since. I won't mark the thread as solved quite yet since sometimes there's a few days in between restarts.

 

[helper800]

I've had a GTX 1070ti and the current RTX 3070 in it and the problem has persisted. It's always been a Windows 10 machine. I reinstalled the AMD chipset drivers earlier today and I noticed that my power plan now says "Ryzen Balanced" instead of just "Balanced" so I'm hoping that might have solved the issue since I haven't had instability since. I won't mark the thread as solved quite yet since sometimes there's a few days in between restarts.

When you first built the PC did you install the chipset drivers? If you did, do you recall having any problems installing them? When was the last time you updated the chipset drivers?

 

[Ethan_E]

It's now been about over a week since I installed the chipset drivers and it seems like my system is running fine. Looking at event viewer I haven't had any further shutdowns so I think it's been resolved.

When you first built the PC did you install the chipset drivers? If you did, do you recall having any problems installing them? When was the last time you updated the chipset drivers?

I think I failed to reinstall them when I reinstalled Windows back in December, but even before that I had pesky Intel drivers that refused to uninstall themselves from my system even after I was running the R7. Looking back, this is probably what was causing instability on my prior Windows installation.