On Tue, 17 Aug 2004 12:31:43 +0200, "Leo Havmøller"
>
>Download og installér debug tools:
>
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
>Derefter "open crash dump" i file menuen.
>Så burde du får noget mere information om hvad der gik galt.
Okay tak.
Følgende giver dog ikke så meget mening for mig...
--
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini081704-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 UP Free x86 compatible
Product: WinNt
Kernel base = 0x804d0000 PsLoadedModuleList = 0x8053e0a8
Debug session time: Tue Aug 17 12:04:00 2004
System Uptime: 0 days 1:11:33.461
*********************************************************************
* 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 44, {816e0a88, d60, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
***
***
***
***
*** 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!_IRP
***
***
***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+1f4c9 )
Followup: MachineOwner
---------
--
ja det var en lang smøre, men har du en idé om hvad fejlen skyldes?
Tak
MVH Sune