New
#30
Yeah, that looks good. I think he thought you were having symbol errors instead of the zip file problem.
His suggestion to open various dumps was to get the symbol server building a cache, so that's a good thing anyway.
Yeah, that looks good. I think he thought you were having symbol errors instead of the zip file problem.
His suggestion to open various dumps was to get the symbol server building a cache, so that's a good thing anyway.
I know it is a lot, that's just because it gets complex, but if you just focus on the basics I pointed out you'll at least have a good idea of what may be causing them.
Recently, when opening a dump. it hangs for a long time, like several minutes (3 to 5) here:
After that is shows: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
and sites there for another few then I finally get: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}
Over all take 5 to 10 minutes before I can start looking at a dump.Code:Probably caused by : netr28ux.sys ( netr28ux+1d8d1f ) Followup: MachineOwner
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?
Last edited by Ztruker; 03 Sep 2016 at 12:32.
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.
So what's "Normal" for the time to open the test dmp file. I get as far as the BugCheck 24 line and then it's just been sitting there for quite a while.
Anyone want to analyze a file for me while I wait? :)
092616-30609-01.zip