A fatal error has occured while updating your device software
Here is a debugging example: kb [Lists the stack trace.]Child EBP Ret Addr Args to Child8013ed5c 801263ba 00000000 00000000 e12ab000 NT!_Dbg Break Point8013eecc 801389ee 0000000a 00000000 0000001c NT!Contact the software manufacturers to obtain updates of these third-party tools.The MAXIMUM_WAIT_OBJECTS_EXCEEDED bug check has a value of 0x0000000C.It is better to use the Ke Stack Attach Process function.If the current thread was already attached to another process, the Ke Stack Attach Process function saves the current APC state before it attaches the current thread to the new process._Ki Trap0E 0x256 (FPO: [0,0] Trap Frame @ 8013eee8)8013ed5c 801263ba 00000000 00000000 e12ab0008013ef64 00000246 fe551aa1 ff690268 00000002 NT!
_Dbg Break Point (FPO: [0,0,0])8013eecc 801389ee 0000000a 00000000 0000001c NT!A positive value indicates that a driver has enabled special or normal APCs too many times. For example, each call to Ke Enter Critical Region must have a matching call to Ke Leave Critical Region.If you are developing a driver, you can use Static Driver Verifier, a static analysis tool available in the Windows Driver Kit, to detect problems in your code before you ship your driver.The Combined Apc Disable field consists of two separate 16-bit fields: Special Apc Disable and Kernel Apc Disable.A negative value of either field indicates that a driver has disabled special or normal APCs (respectively) without re-enabling them. A possible cause for this bug check is when a file system or driver has a mismatched sequence of system calls to enter or leave guarded or critical regions.