AMD ALL OVER SYSTEM HORRIBLE EXPERIENCE WITH APEX
Technical Bug Report: Persistent LiveKernelEvent 1b8, BSOD 0x1A, Forced Shutdowns (Event 6008), and Network Service Failures on Alienware m17 R5 (AMD Advantage) Only in Apex Legends
System Specifications:
- Computer Name: Rick-Alienware
- Laptop Model: Alienware m17 R5 AMD Advantage Edition
- Processor: AMD Ryzen 7 6000 Series
- Graphics Card (dGPU): AMD Radeon RX 6700M / 6700M XT
- Memory (RAM): 64 GB
- Operating System: Windows 11 Home/Pro (Standard public release, Build 10.0.26200.2.0.0.256.48)
- Game Platform: Steam
Symptoms & Recurring Crash Logs:
The game crashes frequently and inconsistently. Sometimes it freezes or drops to a black screen instantly upon launching; other times it causes a hard lockup, forcing a full system crash, dirty power shutdown, or Blue Screen of Death (BSOD) mid-match. This behavior ONLY occurs while playing Apex Legends on Steam. All other resource-heavy games and hardware stress tests run flawlessly on this laptop.
Log 1: Hardware Subsystem Timeout (Most Frequent & Persistent)
Description: A problem with your hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name: LiveKernelEvent
Code: 1b8
Parameter 1: a
Parameter 2: 0
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_26200
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.26200.2.0.0.256.48
Locale ID: 1033
Files that help describe the problem: WATCHDOG4401-20260525-1045.dmp, sysdata.xml, WERInternalMetadata.xml, memory.csv, sysinfo.txt, WERInternalRequest.xml
Log 2: Memory Management Blue Screen (Escalated Pipeline Failure)
Problem signature
Problem Event Name: BlueScreen
Code: 1a
Parameter 1: 61941
Parameter 2: ffff80c060301f80
Parameter 3: 9
Parameter 4: ffffc201d09dbd20
OS Version: 10.0.26200.2.0.0.256.48
Locale ID: 1033
Files that help describe the problem: 052526-19187-01.dmp, sysdata.xml, WERInternalMetadata.xml, memory.csv, sysinfo.txt, WERInternalRequest.xml
Note: Parameter 61941 points directly to PAGE_TABLE_RESERVED_BITS_SET, indicating critical corruption in the memory page tables handled by the display driver connection when processing game rendering instructions.
Log 3: Kernel Security / EventTracing Failure
System - Provider: Microsoft-Windows-Kernel-EventTracing {b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}
EventID: 28
Level: 2 (Error)
Task: 3
Opcode: 25
ProcessID: 4
ThreadID: 404
Channel: Microsoft-Windows-Kernel-EventTracing/Admin
EventData:
ProviderGuid: {8444a4fb-d8d3-4f38-84f8-89960a1ef12f}
ErrorCode: 3221225473
Note: Error Code 3221225473 (0xC0000001 / STATUS_UNSUCCESSFUL) indicates a severe driver interface block where a kernel-level tracing operation failed to execute, matching the time of the driver freeze.
Log 4: Unanticipated System Shutdown (Critical Event Viewer Entry)
System - Provider: EventLog
EventID: 6008
Qualifiers: 32768
Level: 2 (Error)
TimeCreated [SystemTime]: 2026-05-26T05:48:49.0947067Z
Execution [ProcessID]: 4120 [ThreadID]: 4228
Channel: System
EventData: 12:24:40 AM | 5/26/2026
Binary Data (In Words):
0000: 000507EA 001A0002 00180000 01100028
0010: 000507EA 001A0002 00180005 01100028
Note: Event 6008 confirms that the Apex Legends crash completely bypassed operating system safety controls, forcing an unhandled system power cut or hard restart directly associated with the LiveKernelEvent 1b8 display timeout.
Log 5: Host-Network-Service Critical Disconnect
System - Provider: Microsoft-Windows-Host-Network-Service {0c885e0d-6eb6-476c-a048-2457eed3a5c1}
EventID: 1030
Level: 2 (Error)
ProcessID: 4076 | ThreadID: 4992
Channel: Microsoft-Windows-Host-Network-Service-Admin
EventData:
HResult: 0x80070032
API: 1
Note: HResult 0x80070032 translates directly to ERROR_NOT_SUPPORTED. This shows the network adapter pipeline completely collapsed or was violently requested to perform an invalid operational state during the game engine/anti-cheat lockup.
Everything Attempted So Far (None of This Worked):
We have tried separating, configuring, and modifying every software and hardware layer possible. Absolutely none of these steps stopped the crashes:
1. Driver Reinstalls: Completed a full, clean wipe using Display Driver Uninstaller (DDU) in Safe Mode, followed by a fresh installation of the latest stable AMD Adrenalin drivers.
2. Display Mode Switching (MUX/SAG): Tested both available modes in the Alienware system configuration. Switched between Hybrid Graphics and AMD SmartAccess Graphics. Even when locked into SmartAccess Graphics to bypass the integrated GPU pipeline, the game crashes instantly upon startup or throws errors.
3. GPU Power & Clock Adjustments: Used AMD Adrenalin software to set a manual tuning profile. Downclocked the Maximum GPU Frequency by -100 MHz and -150 MHz to prevent aggressive RDNA2 transient voltage spikes. Disabled Radeon Anti-Lag and Radeon Boost.
4. Disabled Driver Upscaling: Completely turned off Radeon Super Resolution (RSR) in the driver backend to prevent resolution-switching conflicts with the anti-cheat software.
5. Virtual Memory Adjustments: Modified Windows Paging File sizes manually to match the 64GB RAM pool. Set both Initial and Maximum Virtual Memory sizes to exactly 65536 MB to prevent page table exhaustion.
6. Hardware Overclocking & ECO Settings: Turned off all factory overclocks, disabled XMP/EXPO memory profiles in the BIOS, and forced Alienware Command Center (AWCC) into Full Speed thermal profiles to eliminate power throttling.
7. Windows File Integrity Updates: Ran sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth via Admin Command Prompt. System files are verified healthy.
8. Steam & Game Settings Adjustments: Wiped and verified the integrity of game files on Steam. Completely deleted and clean-reinstalled the EasyAntiCheat folder service as Administrator. Turned off the Steam Overlay. Lowered Texture Streaming Budgets and Spot Shadow details in-game.
9. Launch Option Tests: Tried running the engine with frame caps (+fps_max 144). Attempted forcing different DirectX pipelines (-dx11 and the revised -anticheat_settings=Settings.json). Invalid or obsolete beta commands like SettingsDX12.json were entirely cleared out.
Conclusion for Developers:
There is a fundamental compatibility conflict between the Apex Legends engine/Easy Anti-Cheat layer and the AMD Advantage mobile platform architecture (SmartShift / RDNA2) under modern Windows 11 updates. The system hardware passes every memory diagnostic test flawlessly and runs all other software perfectly. The game is structurally broken for this specific hardware stack, and user-end tweaking cannot fix it.
