Windows BSOD - Revision history

91.1.234.41: typo

2025-03-07T12:01:23Z

typo

2025-03-07T12:00:40Z

e´howto enable memory.dmp

2023-10-15T02:50:38Z

‎Debug Print Buffer

2023-10-15T02:50:20Z

‎Debug Print Buffer

2023-10-13T12:30:11Z

Set symbol path using symfix/sympath

2023-10-13T12:26:54Z

easier way to write cbuf without having to copy and paste the address

2022-04-18T02:20:52Z

Update with example for OpenZFS

2019-11-28T06:55:17Z

Corrected path C:\Program Files\OpenZFS On Windows\symbols\

2019-06-06T03:21:47Z

‎WinDbg.exe in the GUI

2019-06-06T03:19:52Z

‎WinDbg.exe in the GUI

@@ Line 2: / Line 2: @@
 == Windows Crash Dumps ==
-Crashdumps can be enables in Settings > System > Info under "extended system settings"
+Crashdumps can be enabled in Settings > System > Info under "extended system settings"
 If you do managed to get a Blue Screen Of Death (BSOD), Windows should in theory write a crash dump file to:

← Older revision		Revision as of 12:00, 7 March 2025
Line 2:		Line 2:
	== Windows Crash Dumps ==		== Windows Crash Dumps ==

		+	Crashdumps can be enables in Settings > System > Info under "extended system settings"
	If you do managed to get a Blue Screen Of Death (BSOD), Windows should in theory write a crash dump file to:		If you do managed to get a Blue Screen Of Death (BSOD), Windows should in theory write a crash dump file to:

@@ Line 80: / Line 80: @@
 New
-  kd> .writemem C:\Users\<your Windows username>\Desktop\cbuf.txt poi(ZFSin!cbuf) L100000
+  kd> .writemem C:\Users\<your Windows username>\Desktop\cbuf.txt poi(OpenZFS!cbuf) L100000
 Do not worry if you get a message about short write, it just means you have not yet filled the buffer.

@@ Line 76: / Line 76: @@
 Old
- kd> r $t0 = poi(ZFSin!cbuf)
+  kd> .writemem C:\Users\<your Windows username>\Desktop\cbuf.txt poi(ZFSin!cbuf) L100000
-  kd> .writemem C:\Users\<your Windows username>\Desktop\cbuf.txt $t0 L100000
 New
- kd> r $t0 = poi(OpenZFS!cbuf)
+  kd> .writemem C:\Users\<your Windows username>\Desktop\cbuf.txt poi(ZFSin!cbuf) L100000
-  kd> .writemem C:\Users\<your Windows username>\Desktop\cbuf.txt $t0 L100000
 Do not worry if you get a message about short write, it just means you have not yet filled the buffer.

@@ Line 28: / Line 28: @@
 === WinDbg.exe in the GUI ===
-Launch WinDbg.exe and set the Symbol path in:
+Launch WinDbg.exe and set the symbol path:
- <nowiki>
-  File > Symbol File Path:
+  kd> .symfix c:\cache
- srv*c:\cache*https://msdl.microsoft.com/download/symbols;C:\Program Files\OpenZFS On Windows\symbols
+ kd> .sympath+ C:\Program Files\OpenZFS On Windows\symbols
-  </nowiki>
+  kd> .reload
 So that it can load both the symbols from Microsoft, and from the installed Open ZFS directory.

@@ Line 76: / Line 76: @@
 Old
-: kd> dt ZFSin!cbuf
+  kd> r $t0 = poi(ZFSin!cbuf)
-xffffe089`f0010000  "FFFFC1072DE87580: SPL: start.FFFFC1072DE87580: SPL: total ncpu 4
+  kd> .writemem C:\Users\<your Windows username>\Desktop\cbuf.txt $t0 L100000
-−
-Note the first string, i.e. "0xffffe089`f0010000". Write the buffer out with the following:
-−
-  kd> .writemem C:\Users\<your Windows username>\Desktop\cbuf.txt 0xffffe089`f0010000 L100000
 New
-: kd> dt OpenZFS!cbuf
+  kd> r $t0 = poi(OpenZFS!cbuf)
-xffffa781`39de0000  "FFFFA781802D5040:dprintf: dbuf.c:3137:dbuf_create(): ds=tank4 obj=261 lvl=0 blkid=324 db=FFFFA781427CFB60.FFFFA781802D5040:dprintf: dbuf.c:3137:dbuf_create():
+  kd> .writemem C:\Users\<your Windows username>\Desktop\cbuf.txt $t0 L100000
-−
-Note the first string, i.e. "0xffffa781`39de0000". Write the buffer out with the following:
-−
-  kd> .writemem C:\Users\<your Windows username>\Desktop\cbuf.txt 0xffffa781`39de0000 L100000
 Do not worry if you get a message about short write, it just means you have not yet filled the buffer.

@@ Line 10: / Line 10: @@
 Debug builds of ZFSin include debugging symbols to assist in dump analysis which are located at:
-  C:\Program Files (x86)\OpenZFS On Windows\symbols\
+  C:\Program Files\OpenZFS On Windows\symbols\
 === WinDbg.exe at the Command Line ===
@@ Line 16: / Line 16: @@
 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
+  WinDbgX.exe -y ‘C:\Program Files\OpenZFS On Windows\symbols\’ -z C:\Windows\MEMORY.DMP
 This will launch the application and you can perform dump analysis with:
@@ Line 24: / Line 24: @@
 To run the analysis in a single command:
-  WinDbgX.exe -y ‘C:\Program Files (x86)\OpenZFS On Windows\symbols\’ -z C:\Windows\MEMORY.DMP -c !analyze -v
+  WinDbgX.exe -y ‘C:\Program Files\OpenZFS On Windows\symbols\’ -z C:\Windows\MEMORY.DMP -c !analyze -v
 === WinDbg.exe in the GUI ===
@@ Line 31: / Line 31: @@
   <nowiki>
   File > Symbol File Path:
-  srv*c:\cache*https://msdl.microsoft.com/download/symbols;C:\Program Files (x86)\OpenZFS On Windows\symbols
+  srv*c:\cache*https://msdl.microsoft.com/download/symbols;C:\Program Files\OpenZFS On Windows\symbols
   </nowiki>

@@ Line 53: / Line 53: @@
 Image:minidump4.png|''Locate minidump''
 Image:minidump5.png|''minidump loading''
-Image:minidump5.png|''analyze with stack''
+Image:minidump6.png|''analyze with stack''
 </gallery>