Install and Configure WinDBG for BSOD Analysis  

What I want to know is why the symbol file problem goes away when I view a dump from within a zip file. Has anyone else tried this?

I have Rich. I've done it both ways. Think I responded as such. I'm following everyone's advice for a solution.

I have always opened dumps in zip files directly, never extracted them before.

Caledon Ken said:

I have Rich. I've done it both ways. Think I responded as such. I'm following everyone's advice for a solution.

Different problem Ken, sorry. I was talking about the symbol files not being found. You now have the last part of the automatic debug missing.

Is it only that one dump or all dumps? Can you share the dump so we can try it?

axe0 said:

I have always opened dumps in zip files directly, never extracted them before.

That's funny as I have always unzipped first then worked from the unzipped files. A couple programs I run like your EventFilter and my own ScanNFO need some files extracted.

EventFilter doesn't need a zip file to be extracted as it can do that on its own.

Ztruker said:

Different problem Ken, sorry. I was talking about the symbol files not being found. You now have the last part of the automatic debug missing.

Is it only that one dump or all dumps? Can you share the dump so we can try it?

Thanks Rich. Sure. Recently posted

BSOD during games or internet browsing.

Here is output I get without automatic debug.

axe0 said:

EventFilter doesn't need a zip file to be extracted as it can do that on its own.

That is cool, did not know that, thanks.

Code:

Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\ztruk\AppData\Local\Temp\Temp1_DESKTOP-NLRQJ68-(2019-06-23_01-06-40).zip\Crash Dumps\062219-8250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*D:\Symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*D:\Symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.637.amd64fre.rs3_release_svc.180808-1748
Machine Name:
Kernel base = 0xfffff802`52e1c000 PsLoadedModuleList = 0xfffff802`53185110
Debug session time: Sat Jun 22 22:09:05.233 2019 (UTC - 4:00)
System Uptime: 2 days 16:29:10.767
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {6000, ffffcb8008961ac0, ffffffffc0000225, 0}

Probably caused by : memory_corruption ( nt!MiStoreFaultComplete+7d )

Followup:     MachineOwner
---------

Works okay for me with that dump. Only difference is I'm using an older windbg: Debugger Version 10.0.17763.132

I was using older version and thought I would uninstall and re-install new version as a possible fix. That obviously didn't work. Thanks for looking.