aehd.sys - BSOD - DRIVER_VERIFIER_DETECTED_VIOLATION (c4) - WIndows 11 (intel)

[crutch12]

Problem

Since 2024-09-19 (when I've installed Android Emulator), I have been catching BSOD with UNEXPECTED_STORE_EXCEPTION error.

After some research (with WinDbg and .dmp file), I've investigated that aehd.sys throws this error.

I don't launch Android studio / Android emulator at all, but I always have Hyper-V turned on (because I run Docker in WSL). So I think it's Hyper-V who throws error.

System

• Windows 11 Pro (22631.4317)
• 11th Gen Intel(R) Core(TM) i7-11370H
• Android Studio (Build #AI-241.18034.62.2412.12266719, built on August 23, 2024)
• Android Emulator (35.2.10)
• Android Emulator Hypervisor Driver (installer) (2.2.0)

Error info

From dump file

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: ffffd28e508f87c8, name of the driver having the issue.
Arg3: ffffd28e55ef42e0, verifier internal structure with driver information.
Arg4: 0000000000000002, total # of (paged+nonpaged) allocations that weren't freed.
	Type !verifier 3 drivername.sys for info on the allocations
	that were leaked that caused the bugcheck.

// ...

IMAGE_NAME:  aehd.sys

Dump file

Here is the dump file:
111124-5421-01.dmp.txt

Caution

Rename file after download: 111124-5421-01.dmp.txt -> 111124-5421-01.dmp

[Glinte]

I have hit the same pattern.

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: ffff89897ccf43c0, name of the driver having the issue.
Arg3: ffff8989871031e0, verifier internal structure with driver information.
Arg4: 0000000000000002, total # of (paged+nonpaged) allocations that weren't freed.

I'm not sure if sharing memory dumps publicly is safe, so if anyone is trying to debug this please give me a way to privately share the dump file. For my own future reference the dump is in C:\Windows\Minidump\031925-15171-01.dmp

[f0xlife]

The same issue here. I launch Android Studio time to time for tests some apks. I use WSL as well.

Today I have BSOD Faulty Hardware Corrupted Page so I checked my RAM with Windows Diagnostic Memory and I did not find any issues. Then I turn on the Driver Verifier to detect what driver can cause it, so I restart my PC and then stuck on loading screen with BSOD DRIVER_VERIFIER_DETECTED_VIOLATION. The dump shows the aehd.sys as source of that error.

• CPU: AMD Ryzen 5 5500
• Windows: 10 (19045.3930)
• Android Studio: 2023.1.1 Patch 1 (Build #AI-231.9392.1.2311.11255304, built on December 27, 2023)
• Android Emulator: 35.2.10
• Android Emulator Hypervisor Driver: 2.2.0
• Hyper-V: disabled

041825-4828-01.dmp	18.04.25 13:34:00	DRIVER_VERIFIER_DETECTED_VIOLATION	0x000000c4	00000000`00000062	ffffe687`ac2ded20	ffffe687`b4fc4590	00000000`00000002	aehd.sys	aehd.sys+0	Android Emulator hypervisor driver	Android Emulator hypervisor driver	Google LLC	2.2	x64	ntoskrnl.exe+3fd6f0					C:\Windows\Minidump\041825-4828-01.dmp	12	15	19041	967,324	18.04.25 13:40:06	

[Shelluzo]

I have same problem when running on Windows 11 24H2. After I start android emulator version 36.1.9 it takes a minute or two then Windows 11 crashes hard saying that aehd.sys caused it. It doesn't matter if I start the emulator from command line or from Android Studio with software acceleration selected, it still crashes the computer. After uninstalling Android Emulator hypervisor I cannot run the android emulator but Windows 11 does not crash anymore.

So, for now I need to use HAXM 7.6.5 (and not 7.8.0) to run android emulator 36.1.9 or older. Note that my computer cpu and video hardware is a bit old.