Question Computer shuts down while gaming - but only in certain games.

[kerbies]

Recently my computer has been shutting itself off, but only during certain games. Not during particularly stressful games or in times of stress either. I can run other much more demanding games for hours with no problem, but for some other games, it can shut off within minutes. Any ideas on how to troubleshoot this? Drivers are updated.

6900 XT
EVGA GQ 1000W 80+G SM ATX PSU - New, bought 5 months ago
i5-12600k
PRO Z690-A DDR4
Windows 11
2x Crucial P5 500GB one with 70 gb free, other with 250gb.

Games causing shutdown: Total War: Warhammer III (Frequent)
Dark and Darker (Infrequent)

Games so far not causing shutdown: Escape from tarkov
Hogwarts Legacy

 

[Ralston18]

Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drives: make, model, capacity, how full?

What specific games cause shutdowns? What games do not cause shutdowns?

To troubleshoot, look in Reliability History and Event Viewer for error codes, warnings, and even informational events that were captured just before or at the time of the shutdowns.

Start with Reliability History. Much more user friendly and the timeline format may reveal patterns.

Event Viewer requires more time and effort.

FYI:

http://www.tomshardware.com/faq/id-3128616/windows-event-viewer.html

Both tools can provide detailed information via a click on any given entry. The details may or may not be helpful.

 

[kerbies]

Updated post with details

-Windows Reliability history displays Windows was not properly shut down for each crash. Don't see any patterns
Not seeing anything in event viewer that exclusively happen during the shutdowns, but Error: 0xC0000001 seems to happen alot during crashes, however that just seems to be a boot error - not relevant?

 

[johnbl]

0: kd> !error 0xC0000001
Error code: (NTSTATUS) 0xc0000001 (3221225473) - {Operation Failed} The requested operation was unsuccessful.


not too useful unless you know what was running.

check your c:\windows\minidump directory for any minidumps being created.

 

[kerbies]

0: kd> !error 0xC0000001
Error code: (NTSTATUS) 0xc0000001 (3221225473) - {Operation Failed} The requested operation was unsuccessful.


not too useful unless you know what was running.

check your c:\windows\minidump directory for any minidumps being created.

I don't see any minidump folder there

 

[johnbl]

I don't see any minidump folder there

c:\windows\minidump is the default location for these files. The default can be changed by the user. The owner of the directory should be "system" rather than the username.
the folder might be just empty but it should be on your machine unless the location was changed. (maybe some oem versions of windows change the location)

you could also start cmd.exe as an admin
then run:
cd c:\
dir /s *.dmp

and this will search your drive for *.dmp files
it would find any dumps that are being sent to microsoft and locate live dump and most likely dumps that are stored in non default directories.

 

[kerbies]

c:\windows\minidump is the default location for these files. The default can be changed by the user. The owner of the directory should be "system" rather than the username.
the folder might be just empty but it should be on your machine unless the location was changed. (maybe some oem versions of windows change the location)

you could also start cmd.exe as an admin
then run:
cd c:\
dir /s *.dmp

and this will search your drive for *.dmp files
it would find any dumps that are being sent to microsoft and locate live dump and most likely dumps that are stored in non default directories.

Alright I found it, and ran with windbg, but im out of my depth here on what to do/interpret it. Copy pasting some stuff, not sure if helpful:


0:006> !analyze -v
***

• *
• Exception Analysis *
• *

***


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 186

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 16785

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

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

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

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

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

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

Key : FailFast.Name
Value: FATAL_APP_EXIT

Key : FailFast.Type
Value: 7

Key : Timeline.OS.Boot.DeltaSec
Value: 134

Key : Timeline.Process.Start.DeltaSec
Value: 4

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Timestamp
Value: 2022-05-06T12:50:00Z

Key : WER.OS.Version
Value: 10.0.22621.1

Key : WER.Process.Version
Value: 2220.29.10.1130


FILE_IN_CAB: AUEPDU.exe.18700.dmp

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: 000000156e3feff0 -- (.cxr 0x156e3feff0)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000016 rsi=0000000000000002 rdi=0000000000000000
rip=0000000000000000 rsp=0000000000000020 rbp=0000000000000000
r8=000000156e3ff159 r9=0000018582ac0000 r10=00007ffe9b4cce8a
r11=0000018582bc0000 r12=0000018500000000 r13=0000000000000016
r14=0000000000000000 r15=0000000000000007
iopl=0 nv up di pl nz na pe nc
cs=0018 ss=0000 ds=1800 es=0000 fs=0000 gs=0000 efl=00000000
0000000000000000 ?? ??? Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ffe98e0f61e (ucrtbase!abort+0x000000000000004e) ExceptionCode: c0000409 (Security check failure or stack buffer overrun) ExceptionFlags: 00000001 NumberParameters: 1 Parameter[0]: 0000000000000007 Subcode: 0x7 FAST_FAIL_FATAL_APP_EXIT PROCESS_NAME: AUEPDU.exe ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application. EXCEPTION_CODE_STR: c0000409 EXCEPTION_PARAMETER1: 0000000000000007 FAULTING_THREAD: 00004940 STACK_TEXT: 000000156e3fe130 00007ffe98e0ed39 : 0000001500000003 0000001500000003 000000156e3fe250 0000000000000000 : ucrtbase!abort+0x4e 000000156e3fe160 00007ffe98dd80da : 000000156e3ff140 000000156e3fe750 000000156e3ff140 00007ffe98e92000 : ucrtbase!terminate+0x29 000000156e3fe190 00007ffe9b533eaf : 0000000000000000 00007ffe98d90000 0000000000000081 000000156e3ff140 : ucrtbase!_C_specific_handler_noexcept+0x4a 000000156e3fe1c0 00007ffe9b4aeae6 : 000000156e3ff140 00007ffe98d90000 00007ffe98db9363 00007ffe98e94880 : ntdll!RtlpExecuteHandlerForException+0xf 000000156e3fe1f0 00007ffe9b4e4b35 : 0000000000000000 000000156e3feff0 0000000000000000 00007ffe9b4e4a95 : ntdll!RtlDispatchException+0x286 000000156e3fe940 00007ffe98a8051c : 0000000000000007 00007ffe70c445d8 000000156e3ff280 00007ffe9b4cb1e1 : ntdll!RtlRaiseException+0x195 000000156e3ff120 00007ffe70bc66c0 : 0000000000000007 0000000000000000 0000000000000000 00007ffe70c1b174 : KERNELBASE!RaiseException+0x6c 000000156e3ff200 00007ffe70c1b582 : 0000000000000000 00007ffe20e3b742 00007ff628d21120 0000000000000000 : VCRUNTIME140!_CxxThrowException+0x90 000000156e3ff260 00007ff628cc787d : 00007ff628d21120 0000000000000000 0000000000000000 0000000000000000 : msvcp140!std::_Xinvalid_argument+0x22 000000156e3ff2b0 00007ff628cd10b6 : 0000000000000000 0000000000000000 0000000000000000 0000000000000024 : AUEPDU+0x787d 000000156e3ff2f0 00007ff628cd1a75 : 0000018582ac0000 00007ff628d20e40 000000156e3ff4a0 0000000000000000 : AUEPDU+0x110b6 000000156e3ff3a0 00007ff628cd2925 : 0000000000000000 0000000000000000 0000000000000000 00007ff628d211b0 : AUEPDU+0x11a75 000000156e3ff500 00007ff628cd2e2b : 0000000000000000 0000000000000000 0000018582ad9bf0 0000000000000000 : AUEPDU+0x12925 000000156e3ff610 00007ff628cc55fe : 000000156e1ffa58 00007ffe98a73a65 000000156e1ffa58 0000000000000000 : AUEPDU+0x12e2b 000000156e3ff730 00007ff628cc3b29 : 0000000000080001 0000018582ae7740 000000156e3ff7d0 ffffffffffffffff : AUEPDU+0x55fe 000000156e3ff770 00007ffe98db9363 : 0000018582ae7740 0000000000000000 0000000000000000 0000000000000000 : AUEPDU+0x3b29 000000156e3ff7a0 00007ffe99d726bd : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ucrtbase!thread_start<unsigned int (__cdecl*)(void *),1>+0x93 000000156e3ff7d0 00007ffe9b4edfb8 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x1d 000000156e3ff800 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28


STACK_COMMAND: ~6s ; .cxr ; kb

SYMBOL_NAME: ucrtbase!abort+4e

MODULE_NAME: ucrtbase

IMAGE_NAME: ucrtbase.dll

FAILURE_BUCKET_ID: FAIL_FAST_FATAL_APP_EXIT_c0000409_ucrtbase.dll!abort

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.22621.608

FAILURE_ID_HASH: {e31753ac-c98a-8055-3663-47e707543d20}

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

 

[johnbl]

this is just a simple program crash rather than a windows crash.
the program was
auepdu.exe and most likely was AMD User Experience Program Master
normally you would just uninstall it and reinstall the current version if you actually need it.
normally it would not cause a system crash unless it was calling in to a service that talked to a overclocking software. (maybe Performance Profile Client ???)

I would see if I could uninstall it. (you don't want overclocking running while you try to figure out system crashes)
you would have to check the file date to see if it happened before any system crash.
Apps like this must match the service and the driver and bios version or they can crash like this.
best bet is to remove them and reinstall a current version and hope the installer does the correct things.

Alright I found it, and ran with windbg, but im out of my depth here on what to do/interpret it. Copy pasting some stuff, not sure if helpful:


0:006> !analyze -v
***

• *
• Exception Analysis *
• *

***


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 186

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 16785

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

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

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

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

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

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

Key : FailFast.Name
Value: FATAL_APP_EXIT

Key : FailFast.Type
Value: 7

Key : Timeline.OS.Boot.DeltaSec
Value: 134

Key : Timeline.Process.Start.DeltaSec
Value: 4

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Timestamp
Value: 2022-05-06T12:50:00Z

Key : WER.OS.Version
Value: 10.0.22621.1

Key : WER.Process.Version
Value: 2220.29.10.1130


FILE_IN_CAB: AUEPDU.exe.18700.dmp

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: 000000156e3feff0 -- (.cxr 0x156e3feff0)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000016 rsi=0000000000000002 rdi=0000000000000000
rip=0000000000000000 rsp=0000000000000020 rbp=0000000000000000
r8=000000156e3ff159 r9=0000018582ac0000 r10=00007ffe9b4cce8a
r11=0000018582bc0000 r12=0000018500000000 r13=0000000000000016
r14=0000000000000000 r15=0000000000000007
iopl=0 nv up di pl nz na pe nc
cs=0018 ss=0000 ds=1800 es=0000 fs=0000 gs=0000 efl=00000000
0000000000000000 ?? ??? Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ffe98e0f61e (ucrtbase!abort+0x000000000000004e) ExceptionCode: c0000409 (Security check failure or stack buffer overrun) ExceptionFlags: 00000001 NumberParameters: 1 Parameter[0]: 0000000000000007 Subcode: 0x7 FAST_FAIL_FATAL_APP_EXIT PROCESS_NAME: AUEPDU.exe ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application. EXCEPTION_CODE_STR: c0000409 EXCEPTION_PARAMETER1: 0000000000000007 FAULTING_THREAD: 00004940 STACK_TEXT: 000000156e3fe130 00007ffe98e0ed39 : 0000001500000003 0000001500000003 000000156e3fe250 0000000000000000 : ucrtbase!abort+0x4e 000000156e3fe160 00007ffe98dd80da : 000000156e3ff140 000000156e3fe750 000000156e3ff140 00007ffe98e92000 : ucrtbase!terminate+0x29 000000156e3fe190 00007ffe9b533eaf : 0000000000000000 00007ffe98d90000 0000000000000081 000000156e3ff140 : ucrtbase!_C_specific_handler_noexcept+0x4a 000000156e3fe1c0 00007ffe9b4aeae6 : 000000156e3ff140 00007ffe98d90000 00007ffe98db9363 00007ffe98e94880 : ntdll!RtlpExecuteHandlerForException+0xf 000000156e3fe1f0 00007ffe9b4e4b35 : 0000000000000000 000000156e3feff0 0000000000000000 00007ffe9b4e4a95 : ntdll!RtlDispatchException+0x286 000000156e3fe940 00007ffe98a8051c : 0000000000000007 00007ffe70c445d8 000000156e3ff280 00007ffe9b4cb1e1 : ntdll!RtlRaiseException+0x195 000000156e3ff120 00007ffe70bc66c0 : 0000000000000007 0000000000000000 0000000000000000 00007ffe70c1b174 : KERNELBASE!RaiseException+0x6c 000000156e3ff200 00007ffe70c1b582 : 0000000000000000 00007ffe20e3b742 00007ff628d21120 0000000000000000 : VCRUNTIME140!_CxxThrowException+0x90 000000156e3ff260 00007ff628cc787d : 00007ff628d21120 0000000000000000 0000000000000000 0000000000000000 : msvcp140!std::_Xinvalid_argument+0x22 000000156e3ff2b0 00007ff628cd10b6 : 0000000000000000 0000000000000000 0000000000000000 0000000000000024 : AUEPDU+0x787d 000000156e3ff2f0 00007ff628cd1a75 : 0000018582ac0000 00007ff628d20e40 000000156e3ff4a0 0000000000000000 : AUEPDU+0x110b6 000000156e3ff3a0 00007ff628cd2925 : 0000000000000000 0000000000000000 0000000000000000 00007ff628d211b0 : AUEPDU+0x11a75 000000156e3ff500 00007ff628cd2e2b : 0000000000000000 0000000000000000 0000018582ad9bf0 0000000000000000 : AUEPDU+0x12925 000000156e3ff610 00007ff628cc55fe : 000000156e1ffa58 00007ffe98a73a65 000000156e1ffa58 0000000000000000 : AUEPDU+0x12e2b 000000156e3ff730 00007ff628cc3b29 : 0000000000080001 0000018582ae7740 000000156e3ff7d0 ffffffffffffffff : AUEPDU+0x55fe 000000156e3ff770 00007ffe98db9363 : 0000018582ae7740 0000000000000000 0000000000000000 0000000000000000 : AUEPDU+0x3b29 000000156e3ff7a0 00007ffe99d726bd : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ucrtbase!thread_start<unsigned int (__cdecl*)(void *),1>+0x93 000000156e3ff7d0 00007ffe9b4edfb8 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x1d 000000156e3ff800 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28


STACK_COMMAND: ~6s ; .cxr ; kb

SYMBOL_NAME: ucrtbase!abort+4e

MODULE_NAME: ucrtbase

IMAGE_NAME: ucrtbase.dll

FAILURE_BUCKET_ID: FAIL_FAST_FATAL_APP_EXIT_c0000409_ucrtbase.dll!abort

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.22621.608

FAILURE_ID_HASH: {e31753ac-c98a-8055-3663-47e707543d20}

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

 

[kerbies]

Disabling AMD User exp didnt work, however -

I switched out my GPU to a 1660 Super, and that fixed the problem. What could be causing the AMD GPU to cause shutdowns only for specific games? Very strange, all drivers are updated.