#M audio fast track driver blue screen driver
#M audio fast track driver blue screen code

#M audio fast track driver blue screen driver

A driver has mismanaged an internal LIST_ENTRY-style linked list.Sometimes, Driver Verifier with special pool can help track down the culprit (if the corrupted KTIMER is in a pool block that has already been freed). The timer being manipulated may be the corrupted one, but it might be necessary to inspect the timer table with !timer (or manually walking the timer list links) to identify which timer has been corrupted.

#M audio fast track driver blue screen code

This type of bug check typically occurs in nt!Ke* or nt!Ki* code and involves signaling a timer, or inserting or removing a timer from a timer table.

A driver has corrupted a periodic KTIMER.

Sometimes, Driver Verifier with special pool can help track down the culprit (if the corrupted synchronization object is in a pool block that has already been freed). Usually, the synchronization object being signaled is the one that has been corrupted. It can happen when a thread finishes waiting on a synchronization object or when code attempts to put a synchronization object in the signaled state. This type of bug check typically occurs in nt!Ke* or nt!Ki* code.

A driver has corrupted a kernel synchronization object, such as a KEVENT (for example double initializing a KEVENT while a thread was still waiting on that same KEVENT, or allowing a stack-based KEVENT to go out of scope while another thread was using that KEVENT).

Unfortunately, the inconsistency is not necessarily detected at the time when the corruption occurred, so some detective work may be necessary to identify the root cause.Д¬ommon causes of list entry corruption include: LIST_ENTRY corruption can be difficult to track down and this bug check, indicates that an inconsistency has been introduced into a doubly-linked list (detected when an individual list entry element is added to or removed from the list). Using the parameter 1 table, and a dump file, it is possible to narrow down the cause for many bug checks of this type. The reference count for an object is invalid.ДЄn attempt was made to switch to an invalid jmp_buf context.ДЄn unsafe modification was made to read-only data.ДЄn invalid call was made from within DllMain.ДЄn invalid image base address was detected.ДЄn unrecoverable failure was encountered while protecting a delay load import.ДЄn out of bounds buffer access was detected.ДЄn RTL_BALANCED_NODE RBTree entry has been corrupted.ДЄn out of range switch jumptable entry was invoked.ДЄ longjmp was attempted to an invalid target.ДЄn export suppressed call target couldn't be made a valid call target. Write guard check detected invalid memory write.ДЄn attempt was made to switch to an invalid fiber context.ДЄn attempt was made to assign an invalid register context. Indirect call guard check detected invalid control transfer. To avoid this problem, you must build the driver to run on an earlier version of Windows.ДЄ array bounds check inserted by the compiler detected an illegal array indexing operation.ДЄ call to RtlQueryRegistryValues was made specifying RTL_QUERY_REGISTRY_DIRECT without RTL_QUERY_REGISTRY_TYPECHECK, and the target value was not in a trusted system hive. This may be caused by building a driver to run only on WindowsВ 8 and attempting to load the driver image on an earlier version of Windows. The stack cookie security cookie was not properly initialized by the loader. For more information, see the following Cause section.ДЄn invalid parameter was passed to a function that considers invalid parameters fatal. Stack cookie instrumentation code detected a stack-based buffer overrun (/GS violation).ДЄ LIST_ENTRY was corrupted (for example, a double remove). Typically, a C++ object was corrupted, and then a virtual method call was attempted using the corrupted object's this pointer. VTGuard instrumentation code detected an attempt to use an illegal virtual function table.

Parameter 1ДЄ stack-based buffer has been overrun (legacy /GS violation). The following table describes possible values for Parameter 1.

For more information, see the following table.ДЄddress of the trap frame for the exception that caused the bug checkДЄddress of the exception record for the exception that caused the bug check

Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE Parameters Parameter If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.