I am trying to open a crash dump with WinDbg. I had it running previously, but now it doesn't want to work. I followed the steps here (http://www.iexbeta.com/board/lofiversion/index.php/t48617.html) posted by Kal-El but it doesn't want to work still. My symbol path looks like this: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols Here is the output I get: Microsoft (R) Windows Debugger Version 6.9.0003.113 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini101708-04.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: C:\windows\system32 *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp_sp2_rtm.040803-2158 Kernel base = 0x804de000 PsLoadedModuleList = 0x8056b4a0 Debug session time: Fri Oct 17 06:13:57.156 2008 (GMT-5) System Uptime: 0 days 0:04:32.777 *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Loading Kernel Symbols ................................................................................................................................. Loading User Symbols Loading unloaded module list ....................... *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1902fe, b42053d8, b42050d4, baf1a6de} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** ERROR: Symbol file could not be found. Defaulted to export symbols for fltMgr.sys - *** ERROR: Module load completed but symbols could not be loaded for klif.sys ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* Probably caused by : Ntfs.sys ( Ntfs+26de ) Followup: MachineOwner --------- crappy OEM comptuers...

There is a Microsoft page with help on reading minidumps: http://support.microsoft.com/kb/315263

I know how to google. I need to know how to get this working. crappy OEM comptuers...

If you 'really' know how to Google, I am sure there is an answer to your question somewhere out there on the web. I kinda doubt that anyone here has the answer. :-) Minidumps are normally used by the people at Microsoft who have the source code and all the reference manuals.

I am one of the "anyone here" that do not have the answer but if you were following what Kal-El posted in this 4-year old thread, you need to ask Kal-El (wherever he/she may be). i_Xp/VistaUser

I guess I forgot to mention that I did read the manual as well. I am going to try a reinstallation of WindDbg. The three R's of windows... crappy OEM comptuers...