Computer Type: Desktop

GPU: AMD Lucienne - Internal GPU

CPU: RYZEN 5500U 6 cores, 12 threads

Motherboard: AZW SER V1.0

BIOS Version: FP655U505

RAM: 16GB Micron DDR4-3200

PSU:

Case:

Operating System & Version: Microsoft Windows 11 Professional (x64) Build 22631.4391 (23H2) Version 2009

GPU Drivers: AMD Adrenalin 24.9.1

Chipset Drivers: AMD Chipset Software 6.10.17.152

Background Applications: Battle.net

Description of Original Problem: problems all started when i decided to look into a replacement for DriverEasy since it became p2p.. the first one I tried immediately caused me to have BSOD. especially trying to run Diablo 4. I then began to see various BSOD errors interspersed with Radeon - Bad Image errors. PC started running really slowly and getting hung up on routine tasks.

Troubleshooting: I've tried everything that I can think of to try! I've run every diagnostic and repair utility (sfc, chkdsk, memory diagnostic and startup repair) after initially restoring the pc thru Windows Update to no avail. I then bit the bullet and did a complete reset, with a new installation of Windows. I've used the AMD Driver Cleanup Utility, as well as the DDU to attempt to fix the issue while booted in safe mode. but no matter what I try, i can't get the pc to successfully run Diablo 4. It always gets hung up at the login screen before throwing an error and crashing. I used WhoCrashed to look at the crash dumps:

On Sun 11/10/2024 12:01:07 AM your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\111024-6593-01.dmp (Minidump)

Bugcheck code: 0x3B(0xC0000006, 0xFFFFF8013F097272, 0xFFFF8806F58E4390, 0x0)

Bugcheck name: SYSTEM_SERVICE_EXCEPTION

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.

On Sun 11/10/2024 12:01:07 AM your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\MEMORY.DMP (Kernel memory dump)

Bugcheck code: 0x3B(0xC0000006, 0xFFFFF8013F097272, 0xFFFF8806F58E4390, 0x0)

Bugcheck name: SYSTEM_SERVICE_EXCEPTION

Driver or module in which error occurred: ntkrnlmp.exe (nt)

This is the core Windows kernel module. No offending driver has been revealed.

Description: NT Kernel & System

Product: Microsoft® Windows® Operating System

Company: Microsoft Corporation

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver. The crash analysis did not reveal an offending driver. Possibly this problem was caused by a driver that cannot be identified at this time.

On Sat 11/9/2024 11:07:35 PM your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\110924-6968-02.dmp (Minidump)

Bugcheck code: 0x154(0xFFFF8006DDFB9000, 0xFFFFFD0A11C584E0, 0x2, 0x0)

Bugcheck name: UNEXPECTED_STORE_EXCEPTION

Bug check description: This indicates that the store component caught an unexpected exception.

Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.

On Sat 11/9/2024 10:02:44 PM your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\110924-6968-01.dmp (Minidump)

Bugcheck code: 0x3B(0xC0000006, 0xFFFFF80717497272, 0xFFFFB6059006EB40, 0x0)

Bugcheck name: SYSTEM_SERVICE_EXCEPTION

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.

On Sat 11/9/2024 9:51:42 PM your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\110924-7031-01.dmp (Minidump)

Bugcheck code: 0x3B(0xC0000006, 0xFFFFF80356697272, 0xFFFFB00AC5E83B70, 0x0)

Bugcheck name: SYSTEM_SERVICE_EXCEPTION

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.