Here is a DMP file analysis results to the server, because before played windbg, trouble great god help to see what is abnormal, thanks!
FAULTING_IP:
+ 97 c4e00
00000000 ` 00000000?? ?????
EXCEPTION_RECORD: FFFFFFFFFFFFFFFF -- (. Exr 0 XFFFFFFFFFFFFFFFF)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0
0000000000002 dd8 FAULTING_THREAD:
PROCESS_NAME: zidongpaichan. Exe
ERROR_CODE: (NTSTATUS) 0 x80000003 - {
EXCEPTION_CODE: (NTSTATUS) 0 x80000003 (2147483651) - {
MOD_LIST: & lt; ANALYSIS/& gt;
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
MANAGED_STACK:! Dumpstack - EE
No export dumpstack found
ADDITIONAL_DEBUG_TEXT: Followup set -based on the attribute [Is_ChosenCrashFollowupThread] from Frame: [0] on the thread: [PSEUDO_THREAD]
LAST_CONTROL_TRANSFER: f2738 from 00000000773 to 00000000773 f2772
BUGCHECK_STR: APPLICATION_FAULT_STACKIMMUNE_NOSOS
PRIMARY_PROBLEM_CLASS: STACKIMMUNE
DEFAULT_BUCKET_ID: STACKIMMUNE
STACK_TEXT:
00000000 00000000 00000000 00000000 zidongpaichan ` `. Exe + 0 x0
Exe SYMBOL_NAME: zidongpaichan.
FOLLOWUP_NAME: MachineOwner
There comes MODULE_NAME:
Exe IMAGE_NAME: zidongpaichan.
527 a18f5 DEBUG_FLR_IMAGE_TIMESTAMP:
STACK_COMMAND: dt NTDLL! LdrpLastDllInitializer BaseDllName; Dt NTDLL! LdrpFailureData; * * the Pseudo Context * *; KB
FAILURE_BUCKET_ID: STACKIMMUNE_80000003_________ exe! Unknown
Exe BUCKET_ID: X64_APPLICATION_FAULT_STACKIMMUNE_NOSOS_________.
FOLLOWUP_IP:
____ + 0
00000000 ` 00 e30000 4 d5a pop r10
Followup: MachineOwner
-- -- -- -- -- -- -- -- --
CodePudding user response:
To what windb, exe PDB file copy of the bug to DMP file directory, with 2010 directly open the DMP file, run, you can see the source location error,
CodePudding user response:
You put the corresponding PDB file windbg to import, then execute! Analysis - V analysis
CodePudding user response:
With the depends. Exe view zidongpaichan. Exe depend on which DLL
CodePudding user response:
