mini-dumps

Follow up to this issue, I downloaded and installed a debugger and fed my
mini-dump into it.

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

Loading Dump File [C:\WINDOWS\Minidump\Mini112003-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Thu Nov 20 21:58:43 2003
System Uptime: 0 days 3:15:28.220
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Loading Kernel Symbols
.................................................. ...........................
.................................................. ..............
Loading unloaded module list
..................
Loading User Symbols
************************************************** **************************
***
* *
* Bugcheck Analysis *
* *
************************************************** **************************
***
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, cd4, 2070001, 817ef2e8}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
************************************************** ***********************
*** ***
*** ***
*** 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. ***
*** ***
*** ***
************************************************** ***********************
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
************************************************** ***********************
*** ***
*** ***
*** 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. ***
*** ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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. ***
*** ***
*** ***
************************************************** ***********************
Cannot get _POOL_TRACKER_BIG_PAGES type size
Unable to load image css-dvp.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for css-dvp.sys
*** ERROR: Module load completed but symbols could not be loaded for
css-dvp.sys
Probably caused by : css-dvp.sys ( css_dvp+b7ba )
Followup: MachineOwner
---------

I have no idea what css-dvp.sys is except that it's on my PC in
C:\windows.... the question is, what application is it associated with?
I did a google search and the results from that did not reveal anything that
I have on my machine.



"Joshua Sparks" <nacs@nb.sympatico.ca> wrote in message
news:KGevb.32976$R13.973485@ursa-nb00s0.nbnet.nb.ca...

> I had a crash (stop error 0x000000c2). I have a mini-dump but I don't

know

> how to read it. Can anyone tell me what to do with it? When my machine
> crashed, I got a blue screen but no drivers were indicated as being the
> culprits. Just the BAD_POOL_CALLER, the stop code and an address line
> (0x0000007,0x00000cd4,0x02070001.0x817EF2E8)
>
>