📎 AI Summary:
The thread discusses a user experiencing a Windows 10 crash with an "INVALID_IO_BOOST_STATE" bug check. After the user initially shares a file, responders identify a potential cause related to driver or system issues and suggest checking recent changes or driver updates. The overall sentiment is helpful and ongoing troubleshooting, with an invitation to continue posting if problems persist.
The thread discusses a user experiencing a Windows 10 crash with an "INVALID_IO_BOOST_STATE" bug check. After the user initially shares a file, responders identify a potential cause related to driver or system issues and suggest checking recent changes or driver updates. The overall sentiment is helpful and ongoing troubleshooting, with an invitation to continue posting if problems persist.
Solution
kemical
Essential Member
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INVALID_IO_BOOST_STATE (13c)
A thread exited with an invalid I/O boost state. This should be zero when
a thread exits.
Arguments:
Arg1: ffffa98af3b65040, Pointer to the thread which had the invalid boost state.
Arg2: 00000000ffffffff, Current boost state.
Arg3: 0000000000000001
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 3
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-R3SQ3S0
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 3
Key : Analysis.Memory.CommitPeak.Mb
Value: 70
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 13c
BUGCHECK_P1: ffffa98af3b65040
BUGCHECK_P2: ffffffff
BUGCHECK_P3: 1
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff9209`6bb80a28 fffff806`4a631b3f : 00000000`0000013c ffffa98a`f3b65040 00000000`ffffffff 00000000`00000001 : nt!KeBugCheckEx
ffff9209`6bb80a30 fffff806`4a53dc60 : fffff806`49f11020 ffffa98a`f3b65010 fffff806`49fcdd80 ffffa98a`d4880cf0 : nt!PspThreadDelete+0x1a71ff
ffff9209`6bb80aa0 fffff806`49f5f629 : 00000000`00000000 00000000`00000000 fffff806`49fcdd80 ffffa98a`f3b65040 : nt!ObpRemoveObjectRoutine+0x80
ffff9209`6bb80b00 fffff806`49fcddf2 : ffffa98a`e7946c98 00000000`00000000 fffff806`4a2c9660 ffffa98a`f3b65658 : nt!ObfDereferenceObjectWithTag+0xc9
ffff9209`6bb80b40 fffff806`49fa71fa : ffffa98a`e9ba4040 fffff806`4a2c9660 ffffa98a`e18dde00 ffffa98a`00000000 : nt!PspReaper+0x72
ffff9209`6bb80b70 fffff806`49f149c5 : ffffa98a`e9ba4040 ffffa98a`d4868040 ffffa98a`e9ba4040 00000008`0000000a : nt!ExpWorkerThread+0x16a
ffff9209`6bb80c10 fffff806`4a079dfc : ffffe781`93600180 ffffa98a`e9ba4040 fffff806`49f14970 00000008`0000000a : nt!PspSystemThreadStartup+0x55
ffff9209`6bb80c60 00000000`00000000 : ffff9209`6bb81000 ffff9209`6bb7b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c
SYMBOL_NAME: nt!PspThreadDelete+1a71ff
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.17763.973
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1a71ff
FAILURE_BUCKET_ID: 0x13C_nt!PspThreadDelete
OS_VERSION: 10.0.17763.1
BUILDLAB_STR: rs5_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {6fe88179-1572-f8e2-aeff-cd9c600ecf3a}
Followup: MachineOwnera number of things can cause this bugcheck.
Have you made any changes recently?
Are your drivers up to date?
if you have any more dump files please post as the more we see the better really.
