is ne PCI Express 521 mb (Radeon X700SE)
hab inzwischen den Windows debugger runtergeladen und die minidump ausgelesen...
da sagt er denn folgendes...
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini041508-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 0n2
*** 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 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Apr 15 15:49:20.468 2008 (GMT+2)
System Uptime: 0 days 1:32:37.060
*********************************************************************
* 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 0n2
*** 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 User Symbols
Loading unloaded module list
....................
Unable to load image KMWDFilter.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for KMWDFilter.SYS
*** ERROR: Module load completed but symbols could not be loaded for KMWDFilter.SYS
ERROR: FindPlugIns 8007007b
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, f6c3a3dc, ab477bc0, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** 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!_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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : KMWDFilter.SYS ( KMWDFilter+13dc )
Followup: MachineOwner
---------
1: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f6c3a3dc, The address that the exception occurred at
Arg3: ab477bc0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
***** 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!_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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 45d0fb59
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in "0x%08lx" verweist auf Speicher in "0x%08lx". Der Vorgang "%s" konnte nicht auf dem Speicher durchgef hrt werden.
FAULTING_IP:
KMWDFilter+13dc
f6c3a3dc 804e0301 or byte ptr [esi+3],1
TRAP_FRAME: ab477bc0 -- (.trap 0xffffffffab477bc0)
ErrCode = 00000002
eax=00000103 ebx=00000000 ecx=00000000 edx=85d38f00 esi=00000000 edi=86b54690
eip=f6c3a3dc esp=ab477c34 ebp=ab477c40 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
KMWDFilter+0x13dc:
f6c3a3dc 804e0301 or byte ptr [esi+3],1 ds:0023:00000003=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from 804ef095 to f6c3a3dc
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ab477c40 804ef095 86b545c0 85d38f68 806e5410 KMWDFilter+0x13dc
ab477c64 8057f56d 86b545c0 85d38f68 85c80270 nt+0x18095
ab477d00 805780c2 000000c4 000000c0 00000000 nt+0xa856d
ab477d34 8054086c 000000c4 000000c0 00000000 nt+0xa10c2
ab477d64 7c91eb94 badb0d00 009bf9ac 00000362 nt+0x6986c
ab477d68 badb0d00 009bf9ac 00000362 00000272 0x7c91eb94
ab477d6c 009bf9ac 00000362 00000272 00000000 0xbadb0d00
ab477d70 00000000 00000272 00000000 00000000 0x9bf9ac
STACK_COMMAND: kb
FOLLOWUP_IP:
KMWDFilter+13dc
f6c3a3dc 804e0301 or byte ptr [esi+3],1
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: KMWDFilter+13dc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: KMWDFilter
IMAGE_NAME: KMWDFilter.SYS
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
habe vorher schon die ganzenWin Systems runtergeladen und raufgekloppt ....und da hab ich erstmal gemerkt das ich unter win gar keinen Systems Ordner hatte...(jetzt ja
).....
so wie ich den Debuggerbericht deute hing es mit diesem .... wohl vorher nicht vorhandenen Ordner zusammen ... mal sehen obs wieder kommt das Problem ... (ich glaub ja
)
danke für deine Aufmerksamkeit... ist noch kein spammen : )
ach ja die neuesten Treiber hab ich mir für meine Grafikkarte neulich bei ATI runtergeladen ....vor ca 2 Wochen
und nach den Temperaturen hab ich auch mal gelinst und da sieht allet normal aus ...( ca 40 und 41 °C)
) möglichst vermeiden.
Re: Absturzproblem
