Thanks Ken. I'll try this out.
Art From: Ken Schaefer [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 7:01 PM To: NT System Admin Issues Subject: RE: Trying to debug a memory.dmp file Hi, You can do this in WinDBG Alternatively, if you want to point it to the symbols in your folder then do: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols That way, WinDBG will use local symbols (if they are correct for the actual files used in the dump file), or download the symbols from the MS public symbol server if not. Then do .symfix and .reload to reload the currently used symbols. Cheers Ken From: Art DeKneef [mailto:[EMAIL PROTECTED] Sent: Thursday, 13 March 2008 11:45 AM To: NT System Admin Issues Subject: RE: Trying to debug a memory.dmp file Yes it has very slow Internet access. Where do I do the commands. This is the first time doing this so I am somewhat confused trying to understand what the help file tells me. Thanks Art From: Ken Schaefer [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 5:31 PM To: NT System Admin Issues Subject: RE: Trying to debug a memory.dmp file Does the server have internet access? If so, just do .symfix and then .reload Cheers Ken From: Art DeKneef [mailto:[EMAIL PROTECTED] Sent: Thursday, 13 March 2008 11:03 AM To: NT System Admin Issues Subject: Trying to debug a memory.dmp file I've been trying to figure this out for the past couple of days with no luck. Customer has a server that reboots by itself. Sometimes it is several times a day and then it won't do it for a few days letting me think I have fixed the problem. Same error code 8E every time and almost the same hex values also. Server is 2003 Enterprise fully patched running as a Terminal Server. Server has been fine for several years. Nothing in the event logs other than the last reboot was unexpected. Events before the reboot show someone printed something but that entry is usually 5 minutes earlier. I have verified every driver is the latest for this Dell PE1600SC. Ran the Dell diagnostics with no faults found. Downloaded the latest debugging tools (ver. 6.8.0004.0) and the latest symbols from the Microsoft website. The SP2 symbols are installed to D:\Symbols, the 2003 CD files are installed to D:\2003CD. In windbg I tell it the symbols are in D:\Symbols, executable search path is D:\2003CD\I386. No matter what I try I get the same error message: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe. Then under Loading User Symbols it shows PEB is paged out. Under Bugcheck Analysis it tells me that the Kernel symbols are WRONG. Please fix symbols to do analysis. Then there are eight sections that tell me I am not using the correct symbols. In order for the command to work properly the symbol path must be pointing to the .pdb files that have full type information. Anyone have any ideas as to what I am doing wrong as my searching so far sucks as I haven't been able to figure this out. Thanks. Art ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
