Why does my ASUS TUF gaming laptop keep crashing with a blue screen after a Windows update?

Windows feature updates (22H2, 23H2, 24H2) frequently push new GPU, chipset, and audio drivers that conflict with ASUS-specific kernel components like Armoury Crate's ACPI driver or the ATK hotkey service. The most reliable fix is to boot into Safe Mode, run DDU to cleanly remove the GPU driver, then install the latest driver manually from NVIDIA.com or AMD.com. Also run 'sfc /scannow' and check Device Manager for any yellow-flagged devices after the update.

What does DRIVER_VERIFIER_DMA_VIOLATION mean on an ASUS ROG Strix or TUF laptop?

Stop code 0x000000E6 (DRIVER_VERIFIER_DMA_VIOLATION) means a driver attempted a Direct Memory Access operation that violated memory isolation rules enforced by Windows' Driver Verifier or by the platform's IOMMU/VT-d settings. On ASUS gaming laptops, this is almost always the NVIDIA or AMD GPU driver, Realtek audio driver, or Intel/AMD chipset driver. Fix: run 'verifier /reset' in an elevated prompt to disable Driver Verifier, then cleanly reinstall the GPU driver using DDU in Safe Mode. Also update the BIOS, as ASUS has released firmware fixes for ACPI/DMA remapping bugs on several ROG and TUF models.

My ASUS VivoBook or ZenBook shows CRITICAL_PROCESS_DIED — is it hardware or software?

CRITICAL_PROCESS_DIED (0x000000EF) on a VivoBook or ZenBook is software-side about 70% of the time. Start with 'sfc /scannow' and DISM RestoreHealth. Then check for a corrupt Armoury Crate installation or a third-party antivirus that hooks kernel processes. If the BSOD survives a clean Windows reinstall, suspect the NVMe SSD — check SMART data with CrystalDiskInfo. Failing SSDs produce this exact stop code because Windows cannot read critical OS files fast enough. Reallocated sectors or uncorrectable sector counts above zero confirm hardware failure.

How do I fix an ASUS laptop that is stuck in a blue screen loop and cannot boot?

Force-shutdown (hold the power button) three consecutive times during the Windows loading screen. Windows will enter Automatic Repair / WinRE. From there: 1) Try Startup Repair first. 2) If that fails, go to Troubleshoot → Advanced Options → System Restore and pick a restore point before the BSODs started. 3) If no restore points exist, try Command Prompt from WinRE and run 'bootrec /fixmbr', 'bootrec /fixboot', and 'bootrec /rebuildbcd'. 4) As a last resort, choose Reset this PC → Keep my files, or boot from a Windows USB and perform a repair install.

Can overheating cause blue screens on ASUS TUF A15 or TUF F15 laptops?

Yes. The ASUS TUF A15 and F15 are known to run hot, and sustained CPU/GPU temperatures above 95°C can cause NVMe SSDs (which often lack heatsinks on these models) to reach thermal limits, triggering driver timeouts that produce BSODs. Monitor temperatures with HWiNFO64 during load. Fixes include: repasting the CPU/GPU with quality thermal compound (e.g., Thermal Grizzly Kryonaut), adding a small NVMe SSD thermal pad, enabling 'Whisper mode' in Armoury Crate, and ensuring the laptop's vents are not blocked. ASUS also released a fan curve BIOS update for several TUF models addressing this.

ASUS Laptop Blue Screen (BSOD) Fix: Critical Process Died, Driver Verifier DMA Violation & More

Fix ASUS laptop blue screen errors including Critical Process Died & Driver Verifier DMA Violation with step-by-step commands and driver rollback guides.

Last updated: March 1, 2026

Last verified: March 1, 2026

2,152 words

Key Takeaways

Most ASUS laptop BSODs are caused by outdated, corrupt, or incompatible drivers — especially GPU, chipset, and ASUS-specific ACPI/ATK drivers installed via MyASUS or Armoury Crate.
Hardware faults (failing RAM, overheating SSD, or a defective NVMe controller) account for a significant percentage of ASUS TUF, ROG Strix, VivoBook, and ZenBook blue-screen loops that survive a clean Windows reinstall.
The fastest first-pass fix is to run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' in an elevated command prompt, then roll back or cleanly reinstall the ASUS GPU and chipset drivers using DDU in Safe Mode.

Fix Approaches Compared
Method	When to Use	Time	Risk
SFC + DISM scan	First-pass fix for any BSOD; corrupted system files	10–20 min	Low
Driver rollback via Device Manager	BSOD started after a Windows Update or driver update	5–10 min	Low
DDU clean driver reinstall (Safe Mode)	GPU/chipset driver corruption; DRIVER_VERIFIER_DMA_VIOLATION	20–40 min	Low-Medium
Windows Memory Diagnostic / MemTest86	Random BSODs with no consistent stop code; WHEA_UNCORRECTABLE_ERROR	1–8 hrs	None
Check & replace NVMe SSD	CRITICAL_PROCESS_DIED or INACCESSIBLE_BOOT_DEVICE persists after reinstall	30–60 min	Medium
BIOS/UEFI update	DRIVER_VERIFIER_DMA_VIOLATION on new AMD/Intel platform; persistent loop	15–30 min	Medium
Windows Startup Repair / Reset	Blue screen loop prevents login; no hardware fault found	30–90 min	Medium
Clean Windows reinstall	All software fixes exhausted; OS-level corruption	1–3 hrs	High (data loss)

Understanding ASUS Laptop Blue Screen Errors

A Blue Screen of Death (BSOD) on an ASUS laptop — whether it's a TUF A15, TUF F15, ROG Strix, VivoBook, or ZenBook — is Windows telling you that a fatal kernel-level error occurred and the system cannot safely continue. Each BSOD carries a stop code (e.g., CRITICAL_PROCESS_DIED, DRIVER_VERIFIER_DMA_VIOLATION, SYSTEM_SERVICE_EXCEPTION) and often a responsible module filename (e.g., nvlddmkm.sys, atikmdag.sys, ntoskrnl.exe).

ASUS-specific factors that make BSODs more common include:

Armoury Crate / MyASUS kernel drivers that conflict with Windows updates.
AMD or NVIDIA dual-GPU switching (MUX switch) causing DMA violations.
Aggressive power management in TUF/ROG models that destabilizes NVMe controllers.
ACPI firmware bugs fixed only by BIOS updates.

Step 1: Read the Stop Code

When the blue screen appears, note the stop code at the bottom. If the machine reboots too fast:

Go to Settings → System → About → Advanced system settings.
Under Startup and Recovery, uncheck Automatically restart.
The stop code will now stay visible.

Alternatively, open Event Viewer (eventvwr.msc) → Windows Logs → System and filter for Critical events around the crash timestamp.

Use WinDbg or the free WhoCrashed tool to parse the minidump at C:\Windows\Minidump\*.dmp for the exact faulting module.

Step 2: Run SFC and DISM (Always Do This First)

Open an elevated Command Prompt or PowerShell and run:

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

Restart after both complete. This fixes corrupted Windows system files that are a frequent silent cause of CRITICAL_PROCESS_DIED.

Step 3: Identify and Fix the Faulting Driver

3a. Check recently updated drivers

In PowerShell run:

Get-WinEvent -LogName System | Where-Object {$_.Id -eq 7034 -or $_.Id -eq 7031} | Select-Object TimeCreated, Message | Format-List

Also check:

driverquery /v /fo csv > C:\drivers.csv

3b. For DRIVER_VERIFIER_DMA_VIOLATION (stop code 0x000000E6)

This is extremely common on ASUS ROG Strix and TUF gaming laptops after Windows 11 22H2+ updates. It is almost always caused by the NVIDIA or AMD GPU driver, the Intel/AMD chipset driver, or Realtek audio drivers.

Fix procedure:

Boot into Safe Mode (hold Shift while clicking Restart → Troubleshoot → Advanced Options → Startup Settings → F4).
Download Display Driver Uninstaller (DDU) from guru3d.com.
Run DDU in Safe Mode, select your GPU vendor, and choose Clean and restart.
Download the latest stable driver directly from NVIDIA.com or AMD.com — not from MyASUS or Windows Update.
Install and restart normally.

If the BSOD recurs, disable Driver Verifier:

verifier /reset

Then reboot.

3c. For CRITICAL_PROCESS_DIED (stop code 0x000000EF)

This usually means ntoskrnl.exe, lsass.exe, csrss.exe, or a critical boot driver has crashed. Common culprits on ASUS laptops:

Armoury Crate service or its ACPI driver (AsusFanControlService, AsusCertService).
Corrupted NVMe driver after a firmware update.
Antivirus kernel filter (especially third-party AV after a Windows feature update).

Fix:

Uninstall Armoury Crate completely using the official ASUS Armoury Crate Uninstall Tool from the ASUS support site.
In Safe Mode, disable startup items: msconfig → Services → Hide Microsoft services → Disable all → OK.
Roll back the NVMe driver in Device Manager → Disk drives → [Your NVMe] → Properties → Driver → Roll Back Driver.

Step 4: Check RAM

Random BSODs with varying stop codes almost always indicate failing RAM.

Run the built-in test:

mdsched.exe

Choose Restart now and check for problems. Results appear in Event Viewer → Windows Logs → System after restart (search for MemoryDiagnostics-Results).

For a more thorough test, boot MemTest86 from a USB drive and run at least 2 full passes. On ASUS TUF A15/F15 models with dual-channel RAM slots, test each stick individually.

Step 5: Check NVMe SSD Health

ASUS laptops, especially the TUF and VivoBook lines, have experienced NVMe controller issues. Check drive health:

Get-PhysicalDisk | Select-Object FriendlyName, OperationalStatus, HealthStatus, Size

Install CrystalDiskInfo (free) to read SMART data. Look for:

Reallocated Sectors Count > 0
Uncorrectable Sector Count > 0
NVM Subsystem Reset Count > 0

If values are elevated, the SSD is failing and needs replacement.

Step 6: Update the BIOS/UEFI

ASUS releases BIOS updates that fix ACPI bugs and DMA remapping issues causing BSODs. Do NOT skip this step for ROG Strix or TUF gaming laptops.

Go to asus.com/support and search your exact model number (found on the sticker on the bottom of the laptop).
Download the latest BIOS .zip file.
Extract and copy the .cap or .bin file to a FAT32-formatted USB drive.
Restart and enter BIOS (press F2 or Del during POST).
Use EZ Flash utility (usually under Advanced or Tool menu) to flash the BIOS.

Warning: Do not power off during a BIOS flash. Plug in the AC adapter before starting.

Step 7: Perform a Windows Startup Repair or Reset

If the laptop is stuck in a blue screen loop and cannot boot to desktop:

Force-shutdown 3 times during the Windows logo to trigger Automatic Repair mode.
Go to Troubleshoot → Advanced Options → Startup Repair.
If that fails, try System Restore to a point before the BSODs started.
Last resort: Reset this PC → Remove everything (ensure backups first).

ASUS Monitor Blue Screen Note

If you see a blue tint or blue screen on an ASUS monitor (not a Windows BSOD), this is a display/cable issue — check the DisplayPort/HDMI cable, try a different input source, and update the GPU driver. This is distinct from a Windows stop-code BSOD.

Preventing Future BSODs

Keep Armoury Crate and MyASUS updated — or uninstall them if stability is preferred over features.
Use Windows Update but defer optional driver updates via Settings → Advanced Windows Update options.
Enable automatic minidump creation: System Properties → Advanced → Startup and Recovery → Write debugging information → Small memory dump (256 KB).
Monitor temperatures with HWiNFO64; thermal throttling can trigger NVMe and GPU driver crashes on TUF and ROG laptops with inadequate cooling paste (especially units over 2 years old).

Frequently Asked Questions

powershell

# ============================================================
# ASUS LAPTOP BSOD DIAGNOSTIC & FIX SCRIPT
# Run PowerShell as Administrator
# ============================================================

# 1. Scan and repair Windows system files
Write-Host "[1/7] Running SFC scan..." -ForegroundColor Cyan
sfc /scannow

# 2. DISM image repair
Write-Host "[2/7] Running DISM RestoreHealth..." -ForegroundColor Cyan
DISM /Online /Cleanup-Image /RestoreHealth

# 3. List recent critical system events (last 24 hrs)
Write-Host "[3/7] Fetching recent Critical events..." -ForegroundColor Cyan
$startTime = (Get-Date).AddHours(-24)
Get-WinEvent -LogName System -ErrorAction SilentlyContinue |
    Where-Object { $_.Level -eq 1 -and $_.TimeCreated -gt $startTime } |
    Select-Object TimeCreated, Id, Message |
    Format-List | Out-File "$env:USERPROFILE\Desktop\critical_events.txt"
Write-Host "Critical events saved to Desktop\critical_events.txt"

# 4. Export list of all installed drivers with dates
Write-Host "[4/7] Exporting driver list..." -ForegroundColor Cyan
driverquery /v /fo csv > "$env:USERPROFILE\Desktop\drivers.csv"
Write-Host "Driver list saved to Desktop\drivers.csv"

# 5. Check disk health via SMART (requires admin)
Write-Host "[5/7] Checking physical disk health..." -ForegroundColor Cyan
Get-PhysicalDisk | Select-Object FriendlyName, OperationalStatus, HealthStatus, `
    @{Name='Size(GB)';Expression={[math]::Round($_.Size/1GB,1)}} | Format-Table -AutoSize

# 6. Check memory for errors in Event Log
Write-Host "[6/7] Checking for Memory Diagnostic results..." -ForegroundColor Cyan
Get-WinEvent -LogName System -ErrorAction SilentlyContinue |
    Where-Object { $_.ProviderName -eq 'Microsoft-Windows-MemoryDiagnostics-Results' } |
    Select-Object TimeCreated, Message | Format-List

# 7. Reset Driver Verifier if it was enabled (may be causing BSOD loop)
Write-Host "[7/7] Resetting Driver Verifier settings..." -ForegroundColor Yellow
verifier /reset
Write-Host "Driver Verifier reset complete. Reboot required to take effect."

# ---- Optional: Launch Windows Memory Diagnostic ----
# Uncomment the line below to schedule a RAM test on next reboot:
# mdsched.exe

# ---- Optional: Open minidump folder for manual analysis ----
# explorer.exe C:\Windows\Minidump

Write-Host "
[DONE] Review the output above and the files saved to your Desktop.
Next steps:
  1. If SFC/DISM found errors, reboot and check if BSOD is resolved.
  2. If a driver is suspect, boot to Safe Mode and use DDU to remove it.
  3. If disk health shows warnings, back up data immediately.
  4. If no issues found, run MemTest86 from USB for RAM testing.
" -ForegroundColor Green

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows system administrators with a combined 40+ years of experience diagnosing kernel crashes, driver conflicts, and hardware failures across consumer and enterprise environments. We specialize in translating dense Windows internals and vendor-specific quirks into actionable, step-by-step troubleshooting guides.

Sources

Explore More windows Guides

Acer Aspire Blue Screen of Death Fix: How to Stop BSOD Crashes on Acer Laptops

Fix Acer Aspire Blue Screen of Death errors fast. Step-by-step guide covering driver updates, RAM checks, overheating, and Windows repair commands.

Acer Aspire Blue Screen of Death Fix: Step-by-Step Troubleshooting Guide (BSOD Errors Solved)

Fix Acer Aspire blue screen of death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK and more. Step-by-step commands included.

Acer Aspire Blue Screen of Death Fix: Stop Codes, Causes & Complete Solutions

Fix Acer Aspire Blue Screen of Death errors fast. Covers MEMORY_MANAGEMENT, DRIVER_IRQL, KERNEL_SECURITY_CHECK_FAILURE & more with exact commands.