WDF_VIOLATION
Code: 0x10d (269)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x010d (269)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x010d (269)
Parameters
| Parameter | Description |
|---|---|
| 0x1 | Pointer to a WDF_POWER_ROUTINE_TIMED_OUT_DATA structure |
| 0x2 | Reserved |
| 0x3 | WDFREQUEST handle |
| 0x4 | Reserved |
| 0x5 | The handle value passed in |
| 0x6 | |
| 0x7 | The handle of the framework object |
| 0x8 | The handle of the DMA transaction object |
| 0x9 | |
| 0xA | A pointer to a WDF_QUEUE_FATAL_ERROR_DATA structure |
| 0xB | |
| 0xC | WDFDEVICE handle |
| 0xD | WDFDEVICE handle |
| 0xE | IRQL at which the event callback function was called. |
| 0xF | Address of an event callback function. |
Description
The WDF_VIOLATION bug check has a value of 0x0000010D. This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
Important
This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
Cause
See the description of each code in the Parameters section for an explanation of the cause.
Resolution
The !analyze debug extension displays information about the bug check and can be helpful in gathering information, such as the faulting code module.
Typically, the WDF dump file will yield further information on the driver that caused this bug check. Use this command to look at the log file.
kd> !wdfkd.wdflogdump <WDF_Driver_Name>
If Parameter 1 is equal to 0x2, examine the caller's stack to determine the lock in question.
If Parameter 1 is equal to 0x3, the driver's Kernel-Mode Driver Framework error log will include details about the outstanding references.
If Parameter 1 is equal to 0x4, use the ln debugger command with the value of Parameter 3 as its argument to determine which function requires a non-NULL parameter.
If Parameter 1 is equal to 0x7, use the !wdfkd.wdfhandleParameter 2 extension command to determine the handle type.
If Parameter 1 is equal to 0xA, then the WDF_QUEUE_FATAL_ERROR_DATA structure will indicate either the problematic request or the queue handle. It will also indicate the NTSTATUS, if not STATUS_SUCCESS, when available.
Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.
Associated Modules
| Module | Code | Found in | Description |
|---|---|---|---|
| EventCreate.exe | 0x10d | 78.11011 | %1 |
| mispace.dll | 0x10d | 1011 | The volume label is not valid. |
| ntdll.dll | 0x10d | 78.11011 | {No Quotas} No system quota limits are specifically set for this account. |
| storagewmi.dll | 0x10d | 8.11011 | The volume label is not valid. |
| webservices.dll | 0x10d | 78.11011 | An I/O packet could not be created. |
| 5 entries | |||