A function which requires persistent thread is called within the callback |
Application Verifier break message
A function which requires persistent thread is called within the callback.
Probable cause
Some Microsoft Windows APIs need to be called inside a dedicated or persistent thread. In the threadpool you should generally avoid using thread local storage and queuing asynchronous calls that require a persistent thread, such as the RegNotifyChangeKeyValue function. However, such functions can be queued to a persistent worker thread using QueueUserWorkItem with the WT_EXECUTEINPERSISTENTTHREAD option. A kb in debugger will reveal the caller.
Information displayed by Application Verifier
Parameter1 - Callback function
Parameter2 - Context
Parameter3 - Threadpool Object allocation stack trace, use dds to dump it.
Parameter4 - Not used
Description - Some Microsoft Windows APIs need to be called inside a dedicated or persistent thread. In the threadpool you should generally avoid using thread local storage and queuing asynchronous calls that require a persistent thread, such as the RegNotifyChangeKeyValue function. However, such functions can be queued to a persistent worker thread using QueueUserWorkItem with the WT_EXECUTEINPERSISTENTTHREAD option. A kb in debugger will reveal the caller.
Additional information
Verifier stop code 706.