Difference between revisions of "Windows BSOD"
m |
(Expanded Windows Crash Dump text at the request of Lundman) |
||
| Line 1: | Line 1: | ||
| − | == Windows | + | == Windows Crash Dumps == |
| − | If you do managed to get a Blue Screen Of Death, Windows should in theory write a dump file: | + | If you do managed to get a Blue Screen Of Death (BSOD), Windows should in theory write a crash dump file to: |
C:\Windows\MEMORY.DMP | C:\Windows\MEMORY.DMP | ||
| − | + | The dump file can be analyzed with [http://windbg.org WinDbg.exe] | |
| − | + | Debug builds of ZFSin include debugging symbols to assist in dump analysis which are located at: | |
| + | |||
| + | C:\Program Files (x86)\OpenZFS On Windows\symbols\’ | ||
| + | |||
| + | Once installed, WinDbg.exe can be run from a CMD.com or PowerShell terminal with Administrative privileges: | ||
| + | |||
| + | WinDbgX.exe -y ‘C:\Program Files (x86)\OpenZFS On Windows\symbols\’ -z C:\Windows\MEMORY.DMP | ||
| + | |||
| + | This will launch the application and you can perform dump analysis with: | ||
| + | |||
| + | kd> !analyze -v | ||
| + | |||
| + | Windows features a circular debug print buffer which can also be written to disk: | ||
| + | |||
| + | 2: kd> dt ZFSin!cbuf | ||
| + | 0xffffe089`f0010000 "FFFFC1072DE87580: SPL: start.FFFFC1072DE87580: SPL: total ncpu 4 | ||
| + | |||
| + | Note the first string, i.e. "0xffffe089`f0010000". Enter write this out with the following: | ||
| + | |||
| + | kd> .writemem C:\Users\<your Windows username>\Desktop\cbuf.txt 0xffffe089`f0010000 L100000 | ||
| + | |||
| + | This will include -EB- at the end of the buffer, followed by "@" symbols until the buffer wraps around. | ||
| + | |||
| + | Please provide the contents of the dump analysis and cbuf.txt in you ZFSin in your crash-related tickets. | ||
Revision as of 04:26, 14 March 2019
Windows Crash Dumps
If you do managed to get a Blue Screen Of Death (BSOD), Windows should in theory write a crash dump file to:
C:\Windows\MEMORY.DMP
The dump file can be analyzed with WinDbg.exe
Debug builds of ZFSin include debugging symbols to assist in dump analysis which are located at:
C:\Program Files (x86)\OpenZFS On Windows\symbols\’
Once installed, WinDbg.exe can be run from a CMD.com or PowerShell terminal with Administrative privileges:
WinDbgX.exe -y ‘C:\Program Files (x86)\OpenZFS On Windows\symbols\’ -z C:\Windows\MEMORY.DMP
This will launch the application and you can perform dump analysis with:
kd> !analyze -v
Windows features a circular debug print buffer which can also be written to disk:
2: kd> dt ZFSin!cbuf 0xffffe089`f0010000 "FFFFC1072DE87580: SPL: start.FFFFC1072DE87580: SPL: total ncpu 4
Note the first string, i.e. "0xffffe089`f0010000". Enter write this out with the following:
kd> .writemem C:\Users\<your Windows username>\Desktop\cbuf.txt 0xffffe089`f0010000 L100000
This will include -EB- at the end of the buffer, followed by "@" symbols until the buffer wraps around.
Please provide the contents of the dump analysis and cbuf.txt in you ZFSin in your crash-related tickets.
