Install and Configure WinDBG for BSOD Analysis  

Ok mate I usually look at dumps of various captures too. It is just such a lot to take in.

Recently, when opening a dump. it hangs for a long time, like several minutes (3 to 5) here:

Code:

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


Loading Dump File [F:\Temp\Dumps\AK4774\083116-25609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*G:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*G:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.82.amd64fre.rs1_release.160805-1735
Machine Name:
Kernel base = 0xfffff800`d3c03000 PsLoadedModuleList = 0xfffff800`d3f08060
Debug session time: Wed Aug 31 00:09:55.374 2016 (UTC - 4:00)
System Uptime: 0 days 15:22:08.115
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.................................................
Loading User Symbols

After that is shows:

Code:

Loading unloaded module list
..................................................
*** WARNING: Unable to verify timestamp for netr28ux.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28ux.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80626d88d1f, ffffc781fd5642e8, ffffc781fd563b10}

and sites there for another few then I finally get:

Code:

Probably caused by : netr28ux.sys ( netr28ux+1d8d1f )

Followup: MachineOwner

Over all take 5 to 10 minutes before I can start looking at a dump.

My Symbol folder, G:\Symbols is pretty well populated as it's 1.08GB in size and was setup initially on 3/231/2016.

Anyone have any ideas on how to fix this?

Edit: Just noticed it says Downloading symbols for [ntkrnlmp.pdb] at bottom left of windbg window and sits there for a long time. Is this a Windows Symbol Server problem?

Would downloading ad populating the folder with all Windows 10 symbols help this?

Hi Rich,

I have the same problem, but I can add that I may have some symbol corruption too because my symbol folder is more than 5GB where I lately frequently get the messages that certain Windows kernel files failed to load in the initialization part.

Why it takes this long could be because of new symbols that need to be downloaded with the 1607 version.

I downloaded all the Windows 10 symbols, 32 and 64 bit as .msi files and installed them.
Came out to 55.1GB on disk. Set that folder as the symbol file folder.
windbg still very, very slow.

My normal Symbol File Path is SRV*G:\Symbols*http://msdl.microsoft.com/download/symbols.
I changed it to SRV*G:\Symbols and windbg ran fast. Dump loaded and got to the

Followup: memory_corruption
---------

part in 3-5 seconds. Problem is definitely the Microsoft Symbol Server.

Also change the symbol path from htto:// to https://

Made a big difference for me.