Вот что он мне показал командой !analyze -v
читать дальше »
FAULTING_IP:
ntdll+c6ab2
00000000`77bd6ab2 eb00 jmp ntdll+0xc6ab4 (00000000`77bd6ab4)
EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000077bd6ab2 (ntdll+0x00000000000c6ab2)
ExceptionCode: c0000374
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000077c4d430
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
PROCESS_NAME: spoolsv.exe
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: ntdll
FAULTING_MODULE: 0000000077b10000 ntdll
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc7b325
ERROR_CODE: (NTSTATUS) 0xc0000374 - <Unable to get error code text>
EXCEPTION_CODE: (NTSTATUS) 0xc0000374 - <Unable to get error code text>
EXCEPTION_PARAMETER1: 0000000077c4d430
FAULTING_THREAD: 0000000000000850
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS
IP_ON_HEAP: 00000000c0000374
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.
IP_IN_FREE_BLOCK: c0000374
FRAME_ONE_INVALID: 1
LAST_CONTROL_TRANSFER: from 00000000c0000374 to 0000000077bd6ab2
STACK_TEXT:
00000000`0594f280 00000000`c0000374 : 00000000`00000000 00000000`77c4d430 00000000`c0000374 00000001`c0000374 : ntdll+0xc6ab2
00000000`0594f288 00000000`00000000 : 00000000`77c4d430 00000000`c0000374 00000001`c0000374 00000000`00000000 : 0xc0000374
FOLLOWUP_IP:
ntdll+c6ab2
00000000`77bd6ab2 eb00 jmp ntdll+0xc6ab4 (00000000`77bd6ab4)
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: ntdll+c6ab2
FOLLOWUP_NAME: MachineOwner
