etd.sys blue screen (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)
etd.sys is commonly the ELAN touchpad/HID driver on laptops. When 0x7E names it, remove or replace that OEM driver — do not chase unrelated GPU guides.
etd.sys via minidump. Other modules → nvlddmkm / ntoskrnl.
Step 1 — Confirm etd.sys on the stop screen or dump
Forum and Microsoft Answers threads for “etd.sys blue screen” and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED consistently point at ELAN touchpad stacks after Windows or OEM driver updates.
Step 2 — Enter Safe Mode
Use an external USB mouse if the pad is required for navigation. Path: Safe Mode.
Step 3 — Remove or replace the ELAN driver
- Device Manager → Mice and other pointing devices (and HID) → ELAN / ETDevice entries → Uninstall device; check delete driver if shown.
- Alternatively Roll Back Driver if the failure began right after an update.
- Reboot. Windows may load a generic mouse driver — enough to browse.
- Install the touchpad package only from your laptop OEM support page for the exact model (or ELAN via OEM), not from a random driver pack.
Step 4 — Retest
Use the system with the external mouse first, then reconnect the pad after the OEM driver is installed. If 0x7E returns only when the ELAN device is enabled, stay on OEM support or leave the generic driver.
Branches
FAQ
What is etd.sys?
A kernel driver associated with ELAN touchpad solutions on many OEM laptops. Crashes naming it are driver/hardware-input stack issues.
Can I just delete etd.sys from System32?
No — remove it through Device Manager / OEM installer so Windows servicing stays consistent.
Official and primary sources
Symptom map
- SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (start here)
- Enter Safe Mode for this stop code
- Read the minidump / faulting module
- 0x7E parameters and exception codes
- After a Windows Update
- On startup / boot
- Boot loop / keeps restarting
- During Windows install
- Faulting module nvlddmkm.sys
- Faulting module ntoskrnl.exe
- Faulting module etd.sys
- SYSTEM_SERVICE_EXCEPTION (different stop code)