| Previous | Next |
| WIN32K_SECURITY_FAILURE | KERNEL_STORAGE_SLOT_IN_USE |
UFX_LIVEDUMP
The UFX_LIVEDUMP bug check has a value of 0x00000198. This indicates that a UFX live dump occurred.
Important
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
UFX_LIVEDUMP Parameters
| Parameter | Description |
|---|---|
| 1 | Failure type 0x1 : A class driver failed to activate the bus. 2 - Mask of enumerated child PDOs 3 - Mask of activated child PDOs 4 - Reserved |
| 2 | See parameter 1 |
| 3 | See parameter 1 |
| 4 | See parameter 1 |
Live dumps do not reset the OS, but allow for the capture of memory information for abnormal situations where the operating system can continue.
Kernel live dump compared to bug check
With a traditional bug check, the PC resets and the user's work is disrupted. The goal of kernel live dump is to gather data to trouble shoot an abnormal situation, but allow the OS to continue operation. This reduces downtime when compared to a bug check for “non-fatal” but high-impact failures and hangs. Kernel live dumps are used when it is possible to recover the OS to a known good state. For example a hardware reset of a subsystem, such as video/display, USB3 or Wi-Fi can allow those systems to return to a known good state, with minimal user impact.
A kernel live dump creates a consistent snapshot of kernel memory and saves it to a dump file for the future analysis. To minimize impact on the performance, memory copy techniques are used to create the dump file in a short period of time. In addition, the collection of live dumps is throttled, so that user impact is minimized.
A kernel live dump is effective for a category of problems where something is taking a long time, and yet nothing is technically failing. A watchdog timer can be initialized when an operation is started. If the watchdog expires before operation completes with in the expected time, a live dump of the system can be taken. Then the dump can be analyzed by traversing the call stack and related wait chain for that operation to investigate why it is not completing with the expected time frame.
System logs work well when something fails and the code owner has recorded the cause of the failure and can identify the cause. Live dumps that use watchdog timers attempt to catch failure paths that were not anticipated and logged. But as with every failure, the system logs may identify other issues that may provide clues to the specific root cause of the failure.