- Software and digital services
- Operating system
WDF_VIOLATION
Windows WDF_VIOLATION on PC: framework-based driver error
Risk level
Medium
Proceed carefully and stop if the check is unclear.
Urgency
High
Quick answer
Stop code 0x0000010D means Kernel-Mode Driver Framework (KMDF) detected an error in a framework-based driver. Start by unplugging recently added hardware, checking Device Manager for flagged devices, and installing updated drivers.
Safety first
Stop and check this first
- Before using Windows recovery options or updating BIOS, back up your personal files and confirm you have your 48-digit BitLocker recovery key; resetting the device removes all of your files.
Safe checks you can perform
- Remove any newly added hardware and restart
- Check Device Manager for exclamation points and update drivers
- Install latest Windows updates and keep BIOS/firmware current
- Restore from a system restore point or capture MEMORY.DMP
Leave these tasks to a qualified professional
- Do not attempt this professional task: WDF log inspection with !wdfkd.wdflogdump in WinDbg
- Do not attempt this professional task: Vendor driver update or disabling the kernel-mode filter/service
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
WDF log inspection with !wdfkd.wdflogdump in WinDbg
What they doA technician opens the crash dump in WinDbg, runs !analyze to find the faulting code module, and runs !wdfkd.wdflogdump <WDF_Driver_Name> (plus ln for Parameter 1 = 0x4 or !wdfkd.wdfhandle for 0x7) to inspect the Kernel-Mode Driver Framework error log.
They must show youthe !analyze output and the !wdfkd.wdflogdump log naming the faulting WDF driver.
In writingthe KMDF driver module name, Parameter 1 value (0x1 through 0xF), and the specific framework violation logged.
Vendor driver update or disabling the kernel-mode filter/service
What they doWith the offending KMDF driver identified, the specialist contacts the hardware or software vendor for an updated driver, rolls back the driver to a previous working version, or temporarily disables the related service or kernel-mode filter driver.
They must show youthe replacement driver version or the service/filter driver that was deactivated.
In writingwhich driver was updated, rolled back, or disabled and any vendor support case reference.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Remove any newly added hardware and restart
- Who:
- you, shutting down the PC before unplugging anything.
- How:
- if you added a USB peripheral, dock, or other hardware to your PC before WDF_VIOLATION appeared, shut down the PC, remove the hardware, and try restarting.
- Result that matters:
- checking whether the framework-based driver for that external device is causing the crash.
- If the blue screens stop after removing the hardware, check the vendor's website for an updated driver before reconnecting it.
- If the error continues with the hardware removed, inspect Device Manager next.
- Evidence to keep:
- name of the hardware removed and whether 0x0000010D returned.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors
Check Device Manager for exclamation points and update drivers
- Who:
- you, signed in with administrator rights.
- How:
- right-click the Start button, select Device Manager, and check whether any devices are marked with an exclamation point (!); right-click the device and select Update driver, or try disabling or uninstalling the device if updating does not help.
- Result that matters:
- updating or isolating a malfunctioning KMDF driver.
- If updating or disabling the flagged device stops the restarts, note the device and driver version.
- If no device is flagged or the crash persists, install the latest Windows and manufacturer updates.
- Evidence to keep:
- screenshot of Device Manager and the driver version updated or disabled.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Install latest Windows updates and keep BIOS/firmware current
- Who:
- you, with internet access and mains power.
- How:
- select Start, Settings, Windows Update, then select Check for updates to install the latest cumulative and rollup updates; also check with your PC manufacturer that BIOS and firmware are up to date.
- Result that matters:
- applying OS framework fixes and power management updates.
- If the stop error does not return after updating Windows and firmware, no further action is needed.
- If crashes continue, try rolling back a recently changed driver or using a system restore point.
- Evidence to keep:
- update history list and the installed BIOS/firmware version.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Restore from a system restore point or capture MEMORY.DMP
- Who:
- you, after backing up your personal files.
- How:
- if basic steps do not help, try restoring Windows using a system restore point from Recovery options, or enable Automatic memory dump under Advanced system settings, Startup and Recovery so %SystemRoot%\MEMORY.DMP is saved.
- Result that matters:
- reverting to a known working state or capturing the WDF log for debugger analysis.
- If restoring to an earlier point stops 0x10D, reintroduce any recent drivers one at a time.
- If the crash recurs, provide the MEMORY.DMP file to a technician for WDF log inspection.
- Evidence to keep:
- system restore point date or the saved MEMORY.DMP file timestamp.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x0000010D
- 0x10D
- bug check 0x10D
- STOP 0x0000010D
- stop code WDF_VIOLATION
- WDF VIOLATION
What it means
Microsoft assigns value 0x0000010D to WDF_VIOLATION when Kernel-Mode Driver Framework (KMDF) detects an error in a framework-based driver. Parameter 1 specifies the error code (Parameter 4 is reserved): 0x1 means a driver timed out during a power operation, 0x2 is acquiring a lock already held, 0x3 indicates lingering buffer references on a completed I/O request, 0x4 is a NULL parameter where non-NULL is required, 0x6 is a fatal WDF request handling error, 0x7 is calling WdfObjectDereference instead of WdfObjectDelete, 0x8 is a DMA transaction in the wrong state, and 0xE is a callback returning at the wrong IRQL. By itself, this code never proves hardware is faulty.
Warnings and stop conditions
- Mediumsource verified
Before using Windows recovery options or updating BIOS, back up your personal files and confirm you have your 48-digit BitLocker recovery key; resetting the device removes all of your files.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Find your BitLocker recovery key
Symptoms and causes
Probable causes · in order
- KMDF driver fault in power, locking, I/O buffer, or IRQL handlingCommon
Microsoft's 0x10D reference details driver coding errors such as power operation timeouts without DO_POWER_PAGABLE (0x1), lingering buffer references (0x3), malformed WDF requests (0x6), or unfreed spinlocks leaving IRQL at DISPATCH_LEVEL (0xE).
Evidence: Bug Check 0x10D WDF_VIOLATION
- Newly connected peripheral or recent driver/software changeCommon
Microsoft Support and Learn guides advise removing any new hardware added before the stop error and contacting the vendor to update or roll back drivers after software or hardware changes.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
- PnP state collision or unexpected power IRP in the device stackPossible
Parameter 1 values 0xC and 0xD occur when a new state-changing PnP IRP arrives while another is still being processed, or when a power policy owner receives a power IRP it did not request.
Evidence: Bug Check 0x10D WDF_VIOLATION
Virtual technician
Does WDF_VIOLATION still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Stop code error or bug check troubleshooting (IT professionals)
Microsoft · 2026 · official_doc
- 2
Troubleshooting Windows unexpected restarts and stop code errors
Microsoft · 2026 · official_doc
- 3
Solución de problemas de reinicios inesperados y errores de código de detención de Windows
Microsoft · 2026 · official_doc
- 4
Find your BitLocker recovery key
Microsoft · 2026 · official_doc
- 5
Buscar la clave de recuperación de BitLocker
Microsoft · 2026 · official_doc
- 6
Resolución avanzada de problemas para errores de código de parada
Microsoft · 2026 · official_doc
- 7
Microsoft · 2026 · official_doc
- 8
Comprobación de errores 0x10D WDF_VIOLATION
Microsoft · 2026 · official_doc
Was this entry useful?