Problem across multiple AMD drivers

clapo448 · Thursday at 7:19 AM

Heya all,

I've had some pretty intense issues lately; almost daily crashes usually pointing to the GPU.

Just to list a few of the issues experienced:

Crash to desktop
Crash into reboot
1. After rebooting, the drivers are kinda... missing? GPU-Z can't detect basically anything about the GPU except the model, dxdiag also doesn't know anything about the device
2. Resolution is capped at 1024x768
3. Proceed with DDU and fresh install, tried latest drivers and 24.5.1
Gray screen into reboot
Upon installation in 2.3), once screen went completely black and fans spun at 100%
A few weeks ago, another issue was that the PC wouldn't boot properly - I had to either try to boot it a few times and switch the PSU off if it failed, or weirdly, tilt the PC to the side and it'd usually work
1. I checked capacitors on the motherboard, none are problematic
2. Issue hasn't appeared lately, last time a few days before I updated the BIOS to the latest version
Even more weirdly, time-wise relating to 5), my headset (Audeze Maxwell) used to randomly connect and disconnect.

Now, for the things I've done so far:

Memtest86, twice, 4 passes, no errors. Sticks were run together, if you think I should do them individually I can.
GPU RMA'd both in the local store and the supplier, no issues found with the same games
Power stress test via both OCCT alone and OCCT+furmark+CPU-Z for GPU, VRAM and CPU.
This issue appeared on Windows 10, I installed fresh 11, basically the same issues, slightly different behavior due to some registry changes I did in 10 (tdr etc)
Rechecked cables; no daisy chaining

What makes this even more weird is... the PC worked with a spare RX 6800. But the 7900 XTX had no issues at RMA.

I'm also unable to install any chipset updates; the AMD chipset software installer stalls on the checking. Doesn't crash, just sits there forever; even after a few hours.

Running log collector and analyzing it with WinDbg shows the following, picked from the (what seems like) more relevant data:

If necessary I can upload the whole logcollector zip.

Code:

CRITICAL_STRUCTURE_CORRUPTION (109)

*** WARNING: Check Image - Checksum mismatch - Dump: 0xc2ed94, File: 0xc31fe0 - C:\ProgramData\Dbg\sym\ntkrnlmp.exe\783A7A83144f000\ntkrnlmp.exe

BUGCHECK_CODE:  109

BUGCHECK_P1: a39fe4e441d2b80f

BUGCHECK_P2: b3b6f16a9457b409

BUGCHECK_P3: ffffa58bb00a2ba6

BUGCHECK_P4: 27

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffa58c177a42c0

MEMORY_CORRUPTOR:  ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)

STACK_TEXT: 
ffffd88f`22e1efc8 00000000`00000000     : 00000000`00000109 a39fe4e4`41d2b80f b3b6f16a`9457b409 ffffa58b`b00a2ba6 : nt!KeBugCheckEx

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

Digging a bit deeper via !blackboxpnp, it lists a device ID of USB\VID_0582&PID_01D8\6&3365fbaf&0&8 which is a Roland device; some googling refers to Katana which is likely my Boss Katana Mk2 guitar amp; however that device has been unplugged for at least a few weeks, and is usually turned off.

I've uninstalled it for now; we'll see if that changes anything.

However, if it doesn't work, any tips?

spapakons · Thursday at 8:18 AM

Maybe you have to install the AMD chipset drivers, restart so Windows can detect basic system devices, then install the graphics drivers. Don't rely on Windows Update, download the AMD B550 chipset driver directly from AMD:

https://www.amd.com/en/support/downloads/drivers.html/chipsets/am4/b550.html

clapo448 · Thursday at 8:31 AM

spapakons said:
Maybe you have to install the AMD chipset drivers, restart so Windows can detect basic system devices, then install the graphics drivers. Don't rely on Windows Update, download the AMD B550 chipset driver directly from AMD:

https://www.amd.com/en/support/downloads/drivers.html/chipsets/am4/b550.html

I've downloaded them from the ASUS website for the motherboard, but I've looked into it and it seems that it's a fairly common issue. I'll try uninstalling and installing the one provided by AMD; realistically, ASUS just has it's own bloat on the installation anyways.

I'll be testing all of this further after work.

KevTech · Thursday at 8:51 AM

Sometimes Asus has newer drivers that what is on the AMD site.

clapo448 · Thursday at 11:51 AM

Got home a bit ago, started up a game that didn't crash before, crashed after 10 minutes. Had to delete AMD folder in /Program Files x86 dir for the installation to work.

Right now playing the same game that crashed that usually doesn't, if that crashes we'll see what happens.

Error listed was LiveKernelEvent 141.

Gas · Thursday at 12:31 PM

clapo448 said:
Got home a bit ago, started up a game that didn't crash before, crashed after 10 minutes. Had to delete AMD folder in /Program Files x86 dir for the installation to work.

Right now playing the same game that crashed that usually doesn't, if that crashes we'll see what happens.

Error listed was LiveKernelEvent 141.

Hi clapo448,I know that what I'm saying doesn't help at all but I have to say that if I would have all the problems you are having I just couldn't use an unreliable system like seems to be yours, I just would make a fresh installation letting windows and the Asus utility downloading and install all the required drivers and firmwares and chipset updates and see if all works, so you can exclude any hardware problem. If the system works with no problems I'd make a system image backup and start installing what ever you need and see if and when the computer starts being unstable.

spapakons · Thursday at 1:22 PM

KevTech said:
Sometimes Asus has newer drivers that what is on the AMD site.

It sounds weird. Probably AMD has to release a new driver first before any manufacturer provides it on their support site. Unless the manufacturer provides bug-fixing ot customized versions of an existing driver. That makes sense.

werty · Thursday at 2:00 PM

spapakons said:
It sounds weird. Probably AMD has to release a new driver first before any manufacturer provides it on their support site. Unless the manufacturer provides bug-fixing ot customized versions of an existing driver. That makes sense.

AMD gives the OEMs the driver to test it and they usually release it even before AMD.

clapo448 · Friday at 5:17 PM

Okay, so - it crashed again after being quiet yesterday. Fresh drivers, no more wonky amp drivers... nada.

Event viewer reported ~30 events in the same second or so; LiveKernelEvents 141, 117, 113, 124, a1000005, 139 (which was weirdly listed as eventname: bluescreen even tho it was just a driver timeout), 109 (same as 139 regarding bluescreen) and AppHangB1 which is a bit more nondescript.

In the windir/LiveKernelEvents watchdog dump files, the following is listed
Time - 22:31

Code:

VIDEO_TDR_TIMEOUT_DETECTED (117)

BUGCHECK_CODE:  117

BUGCHECK_P1: ffffe60147a60010

BUGCHECK_P2: fffff80421c7fa20

BUGCHECK_P3: 0

BUGCHECK_P4: 0

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe60147a60010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

SYMBOL_NAME:  amdkmdag+ffa20

MODULE_NAME: amdkmdag

IMAGE_NAME:  amdkmdag.sys

STACK_COMMAND: .process /r /p 0xffffe6012d6b7040; .thread 0xffffe6013a2883c0 ; kb

Time - 22:30

Code:

VIDEO_ENGINE_TIMEOUT_DETECTED (141)

BUGCHECK_CODE:  141

BUGCHECK_P1: ffffe60148893010

BUGCHECK_P2: fffff80421c7fa20

BUGCHECK_P3: 0

BUGCHECK_P4: ffffe60143dfc080

FAULTING_THREAD:  ffffe6013a2883c0

YMBOL_NAME:  amdkmdag+ffa20

MODULE_NAME: amdkmdag

IMAGE_NAME:  amdkmdag.sys

STACK_COMMAND: .process /r /p 0xffffe6012d6b7040; .thread 0xffffe6013a2883c0 ; kb

FAILURE_BUCKET_ID:  LKD_0x141_IMAGE_amdkmdag.sys

Fresh drivers don't change anything; happens with 24.5.1 and 25.5.1.

Let me know if I can help myself by providing files or something.

KevTech · Friday at 6:37 PM

TDR is a timeout detection and recovery error related to the video card.
amdkmdag.sys is the video card driver.
Did you run the AMD cleanup before installing the drivers for the video card?

https://www.amd.com/en/resources/support-articles/faqs/GPU-601.html

clapo448 · Saturday at 3:00 AM

KevTech said:
TDR is a timeout detection and recovery error related to the video card.
amdkmdag.sys is the video card driver.
Did you run the AMD cleanup before installing the drivers for the video card?

https://www.amd.com/en/resources/support-articles/faqs/GPU-601.html

I usually use DDU, but I can try with that if it makes a difference.

Also, for what it's worth, after using ACU, my PC booted into this weird, black bars on top and bottom resolution and nothing was readable. Changing to 1024x768 fixed it kinda.

clapo448 · Saturday at 4:02 AM

Update; can't edit previous comment again; game crashed again. I'll check details after I finish the round. That's with 25.6.1

EDIT:

It's 141 again.

Here's the full !analyze -v

Code:

VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the display engines failed to respond in timely fashion.
(This code can never be used for a real BugCheck; it is used to identify live dumps.)
Arguments:
Arg1: ffff940c2dbef460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8001c527740, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: ffff940c21bcf0c0, Optional internal context dependent data.

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

Mini Kernel Dump does not contain unloaded driver list
Mini Kernel Dump does not contain unloaded driver list
Unable to load image amdkmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdkmdag.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1515

    Key  : Analysis.Elapsed.mSec
    Value: 2386

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x141

    Key  : Bugcheck.Code.TargetModel
    Value: 0x141

    Key  : Dump.Attributes.AsUlong
    Value: 0x18

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: LKD_0x141_IMAGE_amdkmdag.sys

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8001c527740

    Key  : Failure.Exception.IP.Module
    Value: amdkmdag

    Key  : Failure.Exception.IP.Offset
    Value: 0x1e7740

    Key  : Failure.Hash
    Value: {48b738dd-5a92-7ff8-63d0-f075fc680fe0}


BUGCHECK_CODE:  141

BUGCHECK_P1: ffff940c2dbef460

BUGCHECK_P2: fffff8001c527740

BUGCHECK_P3: 0

BUGCHECK_P4: ffff940c21bcf0c0

FILE_IN_CAB:  WATCHDOG-20250607-1000.dmp

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

FAULTING_THREAD:  ffff940c113e8180

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff940c2dbef460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: ffff940c21bcf0c0

PROCESS_NAME:  System

STACK_TEXT: 
fffff586`7b6def30 fffff800`760de159     : ffff940c`2dbef460 00000000`00000000 00000000`00000000 00000000`00000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e
fffff586`7b6df460 fffff800`7648224a     : 00000000`00000000 00000000`00000000 fffff800`764a6c70 00000000`c0000099 : nt!DbgkpWerProcessPolicyResult+0x21
fffff586`7b6df490 fffff800`76482049     : 00000000`00000003 fffff586`7b6df670 ffff940c`2dbef460 ffff940c`1c84cf10 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea
fffff586`7b6df4f0 fffff800`07c9c7f9     : ffff808d`f6a0c200 ffff808d`f6a0c200 ffff808e`4703c8e3 ffff940c`2dbef460 : nt!DbgkWerCaptureLiveKernelDump+0x69
fffff586`7b6df570 fffff800`1c118182     : 00000000`00000006 00000000`00000006 ffff940c`113e3000 ffff940c`1135c000 : dxgkrnl!TdrCollectDbgInfoStage1+0xd69
fffff586`7b6df730 fffff800`1c177186     : ffff940c`113e3000 ffff940c`113e3000 ffff940c`1135c000 00000000`00000000 : dxgmms2!VidSchiResetEngine+0x37a
fffff586`7b6df920 fffff800`1c1a37d6     : fffff780`00000000 ffff940c`1135c000 fffff586`7b6dfab9 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xea
fffff586`7b6df970 fffff800`1c0f9a74     : ffff940c`1135c000 00000000`00000000 fffff586`7b6dfab9 00000000`00031f4a : dxgmms2!VidSchiCheckHwProgress+0x316
fffff586`7b6dfa00 fffff800`1c1a4192     : ffff940c`1135c000 fffff586`7b6dfb70 ffff940c`2e7d7600 ffff940c`1135c000 : dxgmms2!VidSchiScheduleCommandToRun+0x64
fffff586`7b6dfb20 fffff800`1c17731c     : ffff940c`1135c500 ffff940c`1135c000 fffff800`1c177240 ffff940c`1135c000 : dxgmms2!VidSchiRun_PriorityTable+0x42
fffff586`7b6dfb70 fffff800`75e4d1fa     : ffff940c`113e8180 fffff800`00000001 ffffb281`a85db180 024fe07f`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xdc
fffff586`7b6dfbb0 fffff800`7607ca94     : ffffb281`a85db180 ffff940c`113e8180 fffff800`75e4d1a0 00000001`00000004 : nt!PspSystemThreadStartup+0x5a
fffff586`7b6dfc00 00000000`00000000     : fffff586`7b6e0000 fffff586`7b6d9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  amdkmdag+1e7740

MODULE_NAME: amdkmdag

IMAGE_NAME:  amdkmdag.sys

STACK_COMMAND: .process /r /p 0xffff940c016bc040; .thread 0xffff940c113e8180 ; kb

FAILURE_BUCKET_ID:  LKD_0x141_IMAGE_amdkmdag.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {48b738dd-5a92-7ff8-63d0-f075fc680fe0}

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

I've run log-collector but I can't notice anything; let me know if I should send the files. I'm tired of crashing quite literally every day.

spapakons · Saturday at 4:19 AM

Probably it's not the graphics drivers. It's something that tries to use accelerated graphics and crashes. See at the BSOD section how to generate and post the relevant logs. @zbook will examine the logs and diagnose.

clapo448 · Saturday at 4:42 AM

spapakons said:
Probably it's not the graphics drivers. It's something that tries to use accelerated graphics and crashes. See at the BSOD section how to generate and post the relevant logs. @zbook will examine the logs and diagnose.

Dropbox

www.dropbox.com

Should be accessible. In any case, I'm out of ideas.

KevTech · Saturday at 8:56 AM

If this only happens playing a game I would look at possible heat issue.

Maybe the GPU Hot Spot temperature or ram temps but look at all max temps.

Download HWiNFO portable then let it run while playing a game then see what your max temps are.

Also check the voltages in HWiNFO particularly the min voltages for board and GPU.

clapo448 · Saturday at 9:16 AM

KevTech said:
If this only happens playing a game I would look at possible heat issue.

Maybe the GPU Hot Spot temperature or ram temps but look at all max temps.

Download HWiNFO portable then let it run while playing a game then see what your max temps are.

Also check the voltages in HWiNFO particularly the min voltages for board and GPU.

Everything except hotspot is under 85°C, hotspot reaches 92 tops usually but I'll test it anyways.

edit: crashed again not even 5 mins into the game.

update hwinfo:

hottest ccd 88.5°C but average 73°C.

GPU junction 88°C, hotspot 93°C, GPU max 75°C.

GPU voltages:
Min core vddcr_gfx 0.065V, max 1.140V, average 0.915V (current min 1.612, max 210.557)
Memory vddio: min 1.331, max 1.335, avg: 1.351 (current min 13.323, max 28.92)
SOC vddcr_soc 0.982 min, 1.061 max, 1.025 avg (current min 13.41 max 55.025)
memory vddci_mem min 0.774 max 0.805 avg 0.803 (current min: 13.324, max 18.9)

Motherboard is within normal ranges, up to 84 for the cpu package. Nothing else stands out.

clapo448 · Saturday at 10:18 AM

ALSO: I noticed that when the games crash, Event viewer lists attached files in %windir%/Minidump, but those files are never there. Ditto for /LiveKerneEvents/WHEA stuff which either aren't there or point towards old dump files.

WHEA files list the following:

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe50523c6d020, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000bea00000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000001000108, Low order 32-bits of the MCi_STATUS value.

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

Mini Kernel Dump does not contain unloaded driver list
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
Mini Kernel Dump does not contain unloaded driver list

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1671

    Key  : Analysis.Elapsed.mSec
    Value: 1767

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x124

    Key  : Bugcheck.Code.TargetModel
    Value: 0x124

    Key  : Dump.Attributes.AsUlong
    Value: 0x18

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: LKD_0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

    Key  : Failure.Hash
    Value: {f59f17e7-f24e-04f5-3f16-e9425b2acba5}


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe50523c6d020

BUGCHECK_P3: bea00000

BUGCHECK_P4: 1000108

FILE_IN_CAB:  WHEA-20250530-1550.dmp

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

FAULTING_THREAD:  ffffe50523259080

PROCESS_NAME:  smss.exe

STACK_TEXT: 
ffffdf8a`bc77efc0 fffff800`c67aa85e     : ffffe505`23c6d000 00000000`00000000 ffffe505`23c6d020 000000a2`71a7f6e8 : nt!LkmdTelCreateReport+0x1c8
ffffdf8a`bc77f500 fffff800`c67aa75a     : ffffe505`23c6d000 00000000`00000001 ffffe505`23c6d000 00000000`00000000 : nt!WheapReportLiveDump+0x76
ffffdf8a`bc77f540 fffff800`c67aa6c7     : 00000000`00000001 ffffdf8a`bc77fb20 00000000`00000000 000000a2`71a7f6e8 : nt!WheapReportDeferredLiveDumps+0x7a
ffffdf8a`bc77f570 fffff800`c6aa0163     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!WheaCrashDumpInitializationComplete+0x4b
ffffdf8a`bc77f5a0 fffff800`c668ef58     : ffffe505`23259000 00000000`00000000 ffffe505`23259080 00000000`00000000 : nt!NtSetSystemInformation+0x5f3
ffffdf8a`bc77faa0 00007ffd`e001f734     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000a2`71a7f688 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`e001f734


MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND: .process /r /p 0xffffe50523862040; .thread 0xffffe50523259080 ; kb

FAILURE_BUCKET_ID:  LKD_0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f59f17e7-f24e-04f5-3f16-e9425b2acba5}

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

Furthermore, running error records for ffffe50523c6d020, I get this, among many complaints about symbols:

Code:

-------------------------------------------------------------------------------
Descriptor    @ ffffe50523c6d130
Section       @ ffffe50523c6d510
Offset        : 1264
Length        : 1192
Flags         : 0x00000000
Severity      : Fatal

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: hal!_WHEA_XPF_MCA_SECTION                     ***
***                                                                   ***
*************************************************************************

Error         : Unknown (Proc 0 Bank 0)
  Status      : 0x0000000000000000

===============================================================================

clapo448 · Saturday at 11:23 AM

Some more info - went into safemode to try verifier but that yielded no results cause I'm incompetent, I went to restart and I BSODed twice. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

It generated a minidump file, and it's pointing towards FaceIt anti cheat. The issue is, it could be a part of the problem but this crashing happened long before I had faceit installed.

That's being removed. As for the crashes in other games... no idea.

KevTech · Saturday at 11:57 AM

Try these setting in adrenalin software and test gaming.

Voltage mV: 1120

VRAM: 2650 MHz

Power Limit: 15%

Clock freq: 2300 MHz and 2400 MHz

If it works you can adjust from there.

clapo448 · Saturday at 12:09 PM

KevTech said:
Try these setting in adrenalin software and test gaming.

Voltage mV: 1120

VRAM: 2650 MHz

Power Limit: 15%

Clock freq: 2300 MHz and 2400 MHz

If it works you can adjust from there.

Not sure if it's gonna make a difference; the GPU went to RMA and no issues were found. I'll try it anyways, it doesn't cost me anything to do so.

It's likely CPU, mobo or RAM, or any combination of the 3.

Problem across multiple AMD drivers

Member

My Computer

Well-known member

My Computers

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Member

My Computer

Well-known member

My Computers

Member

My Computer

Well-known member

My Computer

Member

My Computer

Member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Similar threads