| 0x00002710 | A driver package which uses user-mode driver framework version %2 is being installed on device %1. |
A driver package which uses user-mode driver framework version %2 is being installed on device %1. |
| 0x00002711 | The UMDF service %1 (CLSID %2) was installed. It requires framework version %3 or higher. |
The UMDF service %1 (CLSID %2) was installed. It requires framework version %3 or higher. |
| 0x00002712 | The UMDF service %1 (CLSID %2) was upgraded. It requires framework version %3 or higher. |
The UMDF service %1 (CLSID %2) was upgraded. It requires framework version %3 or higher. |
| 0x00002774 | The driver package installation has succeeded. |
The driver package installation has succeeded. |
| 0x00002775 | The driver package installation has failed. The final status was %1. |
The driver package installation has failed. The final status was %1. |
| 0x0000277E | A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. |
A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. |
| 0x0000277F | The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device %5 more times. Please contact the device manufacturer for more information about this problem. |
The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device %5 more times. Please contact the device manufacturer for more information about this problem. |
| 0x00002780 | The device %2 (location %3) is offline due to a user-mode device crash. Windows will no longer attempt to restart this device because the maximum restart limit has been reached. Disconnecting the device and reconnecting it, or disabling it and re-enabling it from the device manager, will reset this limit and allow the device to be accessed again. Please contact the device manufacturer for more information about this problem. |
The device %2 (location %3) is offline due to a user-mode device crash. Windows will no longer attempt to restart this device because the maximum restart limit has been reached. Disconnecting the device and reconnecting it, or disabling it and re-enabling it from the device manager, will reset this limit and allow the device to be accessed again. Please contact the device manufacturer for more information about this problem. |
| 0x00002781 | The device %2 was unable to start due to conflict between the settings for driver %5 (%3 - %4) and the other drivers. Windows will not be able to start this device. Please contact the device manufacturer for assistance. |
The device %2 was unable to start due to conflict between the settings for driver %5 (%3 - %4) and the other drivers. Windows will not be able to start this device. Please contact the device manufacturer for assistance. |
| 0x00002782 | %2 (part of UMDF) did not load yet. After it does, Windows will start the device again. |
%2 (part of UMDF) did not load yet. After it does, Windows will start the device again. |
| 0x00002783 | The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device %5 more times in its own process. Please contact the device manufacturer for more information about this problem. |
The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device %5 more times in its own process. Please contact the device manufacturer for more information about this problem. |
| 0x00002784 | The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process %5 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. |
The device %2 (location %3) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process %5 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. |
| 0x00002785 | UMDF driver service %1 failed to load because it was compiled using a pre-release version of the Windows Driver Kit(WDK). The driver should be recompiled using a release version of the WDK. Driver's function table count is %2 and the expected count is %3. |
UMDF driver service %1 failed to load because it was compiled using a pre-release version of the Windows Driver Kit(WDK). The driver should be recompiled using a release version of the WDK. Driver's function table count is %2 and the expected count is %3. |
| 0x00004E1F | UMDF Test Event (%1) |
UMDF Test Event (%1) |
| 0x30000000 | Info |
Info |
| 0x30000001 | Start |
Start |
| 0x30000002 | Stop |
Stop |
| 0x50000001 | Critical |
Critical |
| 0x50000002 | Error |
Error |
| 0x50000004 | Information |
Information |
| 0x50000005 | Verbose |
Verbose |
| 0x70000010 | Startup of the driver manager service. |
Startup of the driver manager service. |
| 0x70000011 | Creation of a new driver host process. |
Creation of a new driver host process. |
| 0x70000012 | Shutdown of a driver host process. |
Shutdown of a driver host process. |
| 0x70000020 | Startup of a new driver host process. |
Startup of a new driver host process. |
| 0x70000021 | Loading drivers to control a newly discovered device. |
Loading drivers to control a newly discovered device. |
| 0x70000025 | Pnp or Power Management operation to a particular device. |
Pnp or Power Management operation to a particular device. |
| 0x70000030 | Installation or update of device drivers. |
Installation or update of device drivers. |
| 0x70000040 | User-mode Driver problems. |
User-mode Driver problems. |
| 0x70000050 | Pnp or Power Management operation to a particular driver in a device stack. |
Pnp or Power Management operation to a particular driver in a device stack. |
| 0x70000065 | Startup of the UMDF reflector |
Startup of the UMDF reflector |
| 0x70000074 | Testing UMDF |
Testing UMDF |
| 0x70000075 | DDI call to read from Hardware. |
DDI call to read from Hardware. |
| 0x70000076 | Read from Hardware. |
Read from Hardware. |
| 0x70000077 | DDI call to Write to hardware. |
DDI call to Write to hardware. |
| 0x70000078 | Write to hardware. |
Write to hardware. |
| 0x70000079 | UMDF hardware interrupt notification. |
UMDF hardware interrupt notification. |
| 0x90000001 | Microsoft-Windows-DriverFrameworks-UserMode |
Microsoft-Windows-DriverFrameworks-UserMode |
| 0x90000002 | Operational |
Operational |
| 0x90000003 | System |
System |
| 0xB00103E8 | The Driver Manager service started successfully |
The Driver Manager service started successfully |
| 0xB00103E9 | The Driver Manager service failed to start. The error reported was %2. |
The Driver Manager service failed to start. The error reported was %2. |
| 0xB00103EA | The Driver Manager service was stopped |
The Driver Manager service was stopped |
| 0xB00103EB | The Driver Manager service is starting a host process for device %3. |
The Driver Manager service is starting a host process for device %3. |
| 0xB00103EC | The host process (%1) started successfully. |
The host process (%1) started successfully. |
| 0xB00103ED | The host process (%1) failed to start successfully. The error reported was %2. |
The host process (%1) failed to start successfully. The error reported was %2. |
| 0xB00103EE | The host process (%1) is being asked to shutdown. |
The host process (%1) is being asked to shutdown. |
| 0xB00103EF | The host process (%1) has a problem (%2) and is being terminated. |
The host process (%1) has a problem (%2) and is being terminated. |
| 0xB00103F0 | The host process (%1) has been shutdown. |
The host process (%1) has been shutdown. |
| 0xB00107D0 | The UMDF Host Process (%1) is starting up. |
The UMDF Host Process (%1) is starting up. |
| 0xB00107D1 | The UMDF Host Process (%1) started successfully. |
The UMDF Host Process (%1) started successfully. |
| 0xB00107D2 | The UMDF Host Process (%1) failed to start successfully. The error reported was %2. |
The UMDF Host Process (%1) failed to start successfully. The error reported was %2. |
| 0xB00107D3 | The UMDF Host Process (%1) has been asked to load drivers for device %2. |
The UMDF Host Process (%1) has been asked to load drivers for device %2. |
| 0xB00107D4 | The UMDF Host is loading driver %4 at level %3 for device %2. |
The UMDF Host is loading driver %4 at level %3 for device %2. |
| 0xB00107D5 | The UMDF Host Process (%1) has loaded module %3 while loading drivers for device %2. |
The UMDF Host Process (%1) has loaded module %3 while loading drivers for device %2. |
| 0xB00107D6 | The UMDF Host successfully loaded the driver at level %3. |
The UMDF Host successfully loaded the driver at level %3. |
| 0xB00107D7 | The UMDF Host failed to load the driver at level %3. The error reported was %4. |
The UMDF Host failed to load the driver at level %3. The error reported was %4. |
| 0xB00107DA | The UMDF Host Process (%1) has successfully loaded drivers for device %2. |
The UMDF Host Process (%1) has successfully loaded drivers for device %2. |
| 0xB00107DB | The UMDF Host Process (%1) has failed to load drivers for device %2. The error reported was %3 |
The UMDF Host Process (%1) has failed to load drivers for device %2. The error reported was %3 |
| 0xB0010834 | Received a Pnp or Power operation (%3, %4) for device %2. |
Received a Pnp or Power operation (%3, %4) for device %2. |
| 0xB0010835 | Completed a Pnp or Power operation (%3, %4) for device %2 with status %9. |
Completed a Pnp or Power operation (%3, %4) for device %2 with status %9. |
| 0xB0010836 | Forwarded a finished Pnp or Power operation (%3, %4) to the lower driver for device %2 with status %9. |
Forwarded a finished Pnp or Power operation (%3, %4) to the lower driver for device %2 with status %9. |
| 0xB0010839 | Forwarded a Pnp or Power operation (%3, %4) for device %2 to the lower driver with status %9 |
Forwarded a Pnp or Power operation (%3, %4) for device %2 to the lower driver with status %9 |
| 0xB001083A | Received a Pnp or Power operation (%3, %4) for device %2 which was completed by the lower drivers with status %9 |
Received a Pnp or Power operation (%3, %4) for device %2 which was completed by the lower drivers with status %9 |
| 0xB0010B54 | The UMDF Host (%1) has been asked to shutdown. |
The UMDF Host (%1) has been asked to shutdown. |
| 0xB0010B55 | The UMDF Host (%1) has shutdown. |
The UMDF Host (%1) has shutdown. |
| 0xB0010BB8 | UMDF State Machine %4 start processing event %5 (Queueing %6) |
UMDF State Machine %4 start processing event %5 (Queueing %6) |
| 0xB0010BB9 | UMDF State Machine %4 dropped event %5 |
UMDF State Machine %4 dropped event %5 |
| 0xB0010BC2 | UMDF State Machine %4 state change from %5 to %7 on event %6 |
UMDF State Machine %4 state change from %5 to %7 on event %6 |
| 0xB0010BC3 | UMDF State Machine %4 event processing finished in state %5 |
UMDF State Machine %4 event processing finished in state %5 |
| 0xB0010BCC | UMDF State Machine %4 event processing stopped in state %5 |
UMDF State Machine %4 event processing stopped in state %5 |
| 0xB0014E3E | Power IRP related event in the User-mode Driver Frameworks Host Process |
Power IRP related event in the User-mode Driver Frameworks Host Process |
| 0xB0017538 | DDI to read from hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). |
DDI to read from hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). |
| 0xB0017539 | DDI to read from hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). |
DDI to read from hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). |
| 0xB001753A | Read from hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). |
Read from hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). |
| 0xB001753B | Read from hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). |
Read from hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). |
| 0xB001753C | DDI to write to hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). |
DDI to write to hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). |
| 0xB001753D | DDI to write to hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). |
DDI to write to hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). |
| 0xB001753E | Write to hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). |
Write to hardware begins (TargetType: %1, TargetSize: %2, BufferCount: %3). |
| 0xB001753F | Write to hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). |
Write to hardware ends (TargetType: %1, TargetSize: %2, BufferCount: %3). |
| 0xB0017544 | UMDF Reflector sent notification for hardware interrupt (Message ID %1). |
UMDF Reflector sent notification for hardware interrupt (Message ID %1). |
| 0xB0017545 | UMDF framework received notification for hardware interrupt (Message ID %1). |
UMDF framework received notification for hardware interrupt (Message ID %1). |
| 0xB00203E9 | The Driver Manager service failed to start. The error reported was %1. |
The Driver Manager service failed to start. The error reported was %1. |
| 0xD0000001 | QueueToTail |
QueueToTail |
| 0xD0000002 | QueueToFront |
QueueToFront |
| 0xD0000003 | QueueFull |
QueueFull |