Error Medic

ASUS Laptop Blue Screen (BSOD) Fix: Critical Process Died, DMA Violation & Crash Loops

Fix ASUS laptop blue screen errors including Critical Process Died, DMA Violation & boot loops. Step-by-step commands for VivoBook, ZenBook, TUF & ROG models.

Last updated:
Last verified:
2,460 words
Key Takeaways
  • Root cause 1: Outdated, corrupt, or incompatible drivers — especially ASUS-specific chipset, GPU, and MyASUS/ARMOURY CRATE software drivers — trigger BSODs like CRITICAL_PROCESS_DIED and DRIVER_VERIFIER_DMA_VIOLATION on TUF, VivoBook, ZenBook, and ROG Strix models.
  • Root cause 2: Faulty or incompatible RAM, corrupted Windows system files, or aggressive BIOS/UEFI firmware settings (especially fast boot and XMP/DOCP memory overclocking profiles) cause persistent crash loops that survive normal reboots.
  • Root cause 3: Overheating due to clogged vents or degraded thermal paste causes thermal throttling followed by emergency shutdowns that manifest as blue screens, particularly under load on ASUS TUF A15, TUF F15, and TUF Gaming F15 models.
  • Quick fix summary: Boot into Safe Mode, uninstall ASUS bloatware drivers (ARMOURY CRATE, MyASUS), run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth', update or roll back GPU and chipset drivers via Device Manager, disable Fast Boot in BIOS, and test RAM with MemTest86 to isolate hardware faults.
ASUS Laptop BSOD Fix Approaches Compared
MethodWhen to UseEstimated TimeRisk Level
Update/Roll Back Drivers via Device ManagerBSOD after Windows Update or driver install; codes like 0x000000EF, 0x0000013315–30 minLow
SFC + DISM System File RepairBSOD with CRITICAL_PROCESS_DIED or SYSTEM_SERVICE_EXCEPTION; corrupt OS files suspected20–45 minLow
Uninstall ARMOURY CRATE / MyASUS DriversBSOD immediately after ASUS software install; DRIVER_VERIFIER_DMA_VIOLATION10–20 minLow
BIOS Reset to Defaults / Disable Fast BootBSOD loop on boot; system fails to POST consistently; XMP/DOCP instability5–10 minLow-Medium
RAM Test with MemTest86Random BSODs with MEMORY_MANAGEMENT or PAGE_FAULT_IN_NONPAGED_AREA codes2–8 hoursNone
Windows Startup Repair / ResetUnbootable system; BSOD loop that bypasses Safe Mode30–90 minMedium (data risk if Reset)
Thermal Repasting + Vent CleaningBSODs under load (gaming/rendering); high CPU/GPU temps reported before crash1–2 hoursMedium (voids warranty if done incorrectly)
Clean Windows ReinstallAll other methods failed; severe file system corruption2–4 hoursHigh (data loss without backup)

Understanding ASUS Laptop Blue Screen Errors

A Blue Screen of Death (BSOD) on an ASUS laptop is Windows halting execution to prevent data corruption or hardware damage. Each BSOD displays a stop code that is your primary diagnostic clue. On ASUS laptops — including the VivoBook, ZenBook, TUF A15, TUF F15, TUF Gaming F15, and ROG Strix lines — certain stop codes appear far more frequently due to ASUS-specific software and hardware quirks.

Common stop codes on ASUS laptops:

  • CRITICAL_PROCESS_DIED (0x000000EF) — A critical Windows process terminated unexpectedly. Often triggered by corrupt system files or aggressive antivirus interaction.
  • DRIVER_VERIFIER_DMA_VIOLATION (0x000000E6) — A driver attempted an illegal Direct Memory Access operation. Frequently caused by ASUS ARMOURY CRATE, MyASUS service drivers, or ASUS System Control Interface.
  • SYSTEM_SERVICE_EXCEPTION (0x0000003B) — A kernel-mode service threw an unhandled exception. GPU driver conflicts are a primary cause.
  • MEMORY_MANAGEMENT (0x0000001A) — Points to RAM hardware failure or corrupt memory-mapped drivers.
  • WHEA_UNCORRECTABLE_ERROR (0x00000124) — Hardware-level error, often CPU or RAM instability; seen on TUF models with XMP profiles enabled.
  • CLOCK_WATCHDOG_TIMEOUT (0x00000101) — CPU core not responding; thermal throttling or overclocking issue.

Step 1: Capture the Stop Code and Minidump

Before fixing anything, record the exact stop code. If the machine reboots too fast:

  1. Go to Settings → System → About → Advanced system settings → Startup and Recovery.
  2. Under "System failure", uncheck Automatically restart and set small memory dump (256 KB).
  3. After the next BSOD, minidumps are saved to C:\Windows\Minidump\.
  4. Use WhoCrashed (free) or WinDbg to analyze the dump file and identify the faulting driver module.

In WinDbg, load the dump and run: !analyze -v — this outputs the faulting module name (e.g., AsusSystemAnalysis.sys, HpqKbFiltr.sys misidentified as ASUS component, or nvlddmkm.sys for NVIDIA GPU driver crashes).


Step 2: Boot Into Safe Mode

If the system is in a BSOD loop:

  1. Force-power off the laptop three times during boot. Windows will enter Automatic Repair mode.
  2. Navigate to Troubleshoot → Advanced options → Startup Settings → Restart.
  3. Press 4 or F4 for Safe Mode, or 5 / F5 for Safe Mode with Networking.

In Safe Mode, most third-party drivers — including ASUS proprietary software — do not load, which often stops the crash loop immediately and confirms a driver-level cause.


Step 3: Uninstall ASUS Bloatware Drivers (Critical Step)

ASUS-specific software is the most common BSOD trigger on new laptops or after Windows reinstalls. In Safe Mode or a stable environment:

  1. Open Control Panel → Programs and Features (or Settings → Apps).
  2. Uninstall in this order:
    • ARMOURY CRATE and ARMOURY CRATE Service
    • MyASUS (if present and recently updated)
    • ASUS System Control Interface v2/v3
    • ASUS Framework Service
    • Aura Sync / Aura Creator
  3. Open Device Manager, click View → Show hidden devices.
  4. Expand System devices and uninstall any ASUS System Control Interface driver entries.
  5. Reboot and test stability before reinstalling these applications from the official ASUS support page for your specific model.

Why this works: ARMOURY CRATE installs low-level kernel drivers (AsIO3.sys, AsIO2.sys) that communicate directly with hardware. Corrupt or version-mismatched installs of these drivers trigger DRIVER_VERIFIER_DMA_VIOLATION and SYSTEM_SERVICE_EXCEPTION BSODs.


Step 4: Update or Roll Back GPU and Chipset Drivers

For ASUS ROG Strix, TUF Gaming, and VivoBook models with NVIDIA or AMD discrete GPUs:

NVIDIA GPU (e.g., RTX 3060 on TUF A15/F15):

  1. Download DDU (Display Driver Uninstaller) and boot into Safe Mode.
  2. Run DDU to completely purge the GPU driver.
  3. Reboot into normal mode and install the latest WHQL-certified driver from nvidia.com — avoid beta drivers.

AMD GPU (e.g., RX 6600M on TUF A15):

  1. Use AMD's Clean Uninstall Utility or DDU in Safe Mode.
  2. Install the latest Adrenalin driver from amd.com.

Intel/AMD Chipset Drivers:

  • Download from intel.com (for Intel HM570/H570 platform) or amd.com (for AMD 500/600 series chipsets).
  • Install via the setup executable — do not use Windows Update versions as they are often outdated.

Step 5: Repair Windows System Files

Corrupt system files cause CRITICAL_PROCESS_DIED BSODs that persist regardless of driver fixes. Run these commands in an elevated Command Prompt:

sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, re-run sfc /scannow to verify all protected files were repaired. If SFC reports it cannot repair files, you may need to mount a Windows ISO and point DISM to it as the repair source:

DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess

Step 6: BIOS/UEFI Configuration Fixes

ASUS BIOS settings are a frequent BSOD source, especially on TUF gaming models where users enable XMP/DOCP RAM overclocking profiles:

  1. Restart and press F2 (or DEL on some models) during POST to enter BIOS.
  2. Press F9 to load Optimized Defaults.
  3. Disable Fast Boot (causes driver initialization issues on some ASUS models).
  4. If you have XMP/DOCP enabled, disable it and test at stock RAM speeds. If BSODs stop, try a lower XMP profile or manually tune RAM timings.
  5. Enable CSM (Compatibility Support Module) if you recently switched from Legacy to UEFI boot mode.
  6. Save and exit with F10.

Step 7: Thermal and Hardware Checks

ASUS TUF laptops (A15, F15, Gaming F15) are known for thermal throttling under sustained gaming loads. Use HWiNFO64 to monitor temps during stress testing:

  • CPU temps above 95°C and GPU above 90°C suggest cooling issues.
  • Use MSI Afterburner to set a custom GPU fan curve.
  • In ASUS' MyASUS or ARMOURY CRATE (if stable), switch to Performance or Turbo fan mode.
  • Physically clean dust from vents with compressed air.
  • If the laptop is over 2 years old, consider professional thermal repaste with quality compound (Thermal Grizzly Kryonaut).

Step 8: RAM Testing

For MEMORY_MANAGEMENT, PAGE_FAULT_IN_NONPAGED_AREA, or WHEA_UNCORRECTABLE_ERROR BSODs:

  1. Download MemTest86 from memtest86.com and boot from USB.
  2. Run at least 2 full passes (4+ passes recommended for thorough testing).
  3. Any errors = faulty RAM. Try removing one stick at a time to isolate the bad module.
  4. Also run Windows Memory Diagnostic: press Win+R, type mdsched.exe, and schedule a test on next reboot.

Frequently Asked Questions

bash
# ============================================================
# ASUS LAPTOP BSOD DIAGNOSTIC & REPAIR COMMANDS
# Run in elevated Command Prompt (Run as Administrator)
# ============================================================

# --- STEP 1: Disable automatic restart on BSOD to capture stop code ---
wmic recoveros set AutoReboot=False
# Set small memory dump for minidump analysis
wmic recoveros set DebugInfoType=3

# --- STEP 2: Check system file integrity ---
sfc /scannow

# --- STEP 3: DISM system image repair ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# If RestoreHealth fails, mount Windows ISO as D: and run:
# DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess

# --- STEP 4: Analyze minidump files (requires WinDbg) ---
# List available minidump files
dir C:\Windows\Minidump\ /od

# Open latest dump in WinDbg (change filename to match)
# In WinDbg console after loading dump:
# !analyze -v
# lmvm <faulting_module_name>

# --- STEP 5: Check ASUS driver services running ---
sc query AsIO3
sc query AsusFanControlService
sc query AsusROGLSLService
sc query ASUSSystemAnalysis
# Stop and disable identified ASUS services causing issues:
# sc stop AsIO3 && sc config AsIO3 start= disabled

# --- STEP 6: Uninstall ASUS kernel drivers via command line ---
# List all ASUS-related OEM drivers
pnputil /enum-drivers | findstr /i "asus"
# Remove a specific driver (replace oem15.inf with actual .inf from above output)
# pnputil /delete-driver oem15.inf /uninstall /force

# --- STEP 7: Check Windows Event Log for crash context ---
wevtutil qe System /q:"*[System[Level=1 or Level=2]]" /f:text /c:20
# Export critical errors from last 24 hours
wevtutil qe System /q:"*[System[(Level=1 or Level=2) and TimeCreated[timediff(@SystemTime) <= 86400000]]]" /f:text > %USERPROFILE%\Desktop\CriticalErrors.txt

# --- STEP 8: Check GPU driver version and status ---
wmic path win32_videocontroller get name,driverversion,status

# --- STEP 9: Check RAM for errors using Windows Memory Diagnostic ---
mdsched.exe
# (Schedules memory test on next reboot - choose restart now)

# --- STEP 10: Verify disk health ---
chkdsk C: /f /r /x
# (Will schedule check on next reboot if C: is system drive)

# --- STEP 11: Check CPU and motherboard temps (requires WMIC) ---
wmic /namespace:\\root\wmi PATH MSAcpi_ThermalZoneTemperature get CurrentTemperature
# Convert to Celsius: (CurrentTemperature - 2732) / 10

# --- STEP 12: Reset TCP/IP stack (in case of BSOD related to network drivers) ---
netsh int ip reset
netsh winsock reset

# --- STEP 13: Re-enable automatic restart after troubleshooting ---
wmic recoveros set AutoReboot=True

# ============================================================
# BONUS: PowerShell - Get last 10 BSODs from Event Log
# ============================================================
# Run in elevated PowerShell:
# Get-WinEvent -FilterHashtable @{LogName='System'; Id=41} | Select-Object -First 10 | Format-List TimeCreated, Message
# Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001} | Where-Object {$_.Message -like '*BlueScreen*'} | Select-Object -First 10 | Format-List TimeCreated, Message
E

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SREs, and Windows systems administrators with 10+ years of experience diagnosing hardware and software failures across enterprise and consumer environments. We specialize in translating cryptic error codes into actionable, step-by-step remediation guides for developers, IT professionals, and power users. Our BSOD and driver troubleshooting guides are based on real-world incident analysis, official Microsoft and hardware vendor documentation, and community-validated fixes.

Sources

Related Articles in Asus

Explore More windows Guides