Remember Windows 10 memory compression module crash analysis
Remember Windows 10 memory compression module crash analysis one: background 1. Storytelling While analyzing various faults of .NET programs for free for friends, we often also receive various other types of dumps, such as: Windows crashes, C++ crashes, Mono crashes, really everything, because of the basics Due to the relative lack of knowledge, the analysis is not so smooth. Today I will talk about a Windows crash kernel dump. This dump was given to me by a friend a few days ago and asked me to help take a look. , use windbg to analyze after having the dump. Two: WinDbg analysis 1. Where to start As long as there is a crash on the Windows platform, the operating system will maintain an EXCEPTION_POINTERS structure. The interpretation of this structure is very important for analyzing the problem. Use !analyze -v The brief output of the command is as follows: 2: kd> !analyze -v *************************************************** ******************************* * * *Bugcheck Analysis* * * *************************************************** ******************************* UNEXPECTED_STORE_EXCEPTION (154) The store component caught an unexpected exception. Arguments: Arg1: ffffb402b9851000, Pointer to the store context or data manager Arg2: ffffe607bc53df30, Exception information Arg3: 0000000000000002, Reserved Arg4: 0000000000000000, Reserved … EXCEPTION_RECORD: ffffe607bc53eeb8 — (.exr 0xffffe607bc53eeb8) ExceptionAddress:…
Remember Windows 10 memory compression module crash analysis
Remember Windows 10 memory compression module crash analysis one: background 1. Storytelling While analyzing various faults of .NET programs for free for friends, we often also receive various other types of dumps, such as: Windows crashes, C++ crashes, Mono crashes, really everything, because of the basics Due to the relative lack of knowledge, the analysis is not so smooth. Today I will talk about a Windows crash kernel dump. This dump was given to me by a friend a few days ago and asked me to help take a look. , use windbg to analyze after having the dump. Two: WinDbg analysis 1. Where to start As long as there is a crash on the Windows platform, the operating system will maintain an EXCEPTION_POINTERS structure. The interpretation of this structure is very important for analyzing the problem. Use !analyze -v The brief output of the command is as follows: 2: kd> !analyze -v *************************************************** ***************************** * * *Bugcheck Analysis* * * *************************************************** ***************************** UNEXPECTED_STORE_EXCEPTION (154) The store component caught an unexpected exception. Arguments: Arg1: ffffb402b9851000, Pointer to the store context or data manager Arg2: ffffe607bc53df30, Exception information Arg3: 0000000000000002, Reserved Arg4: 0000000000000000, Reserved … EXCEPTION_RECORD: ffffe607bc53eeb8 — (.exr 0xffffe607bc53eeb8) ExceptionAddress:…
