Hi also ich hatte gestern irgendwann in der Nacht nen Bluescreen habe mir also heute en Programm runter geladen um den Bericht auszulesen.
Nur Verstehen tue ich da nicht allzuviel vl könnt ihr mir ja helfen!?
Erstmal zum Pc:
Windows XP Service Pack 1
P4 3 Ghz
1024 MB Ram
Asus P4P800 SE
Seagate Barracuda 120 Gb
DSL 1Mbit Netcologne
wenn ihr sonst was wissen wollt?
Nun zum Fehlerbericht!?
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini092304-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) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054a230
Debug session time: Thu Sep 23 08:04:02 2004
System Uptime: 2 days 16:11:13.025
*********************************************************************
* 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 A, {14, 2, 1, 8052fa60}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
Probably caused by : ntoskrnl.exe ( nt+5ba60 )
Followup: MachineOwner
---------
0: kd> !analyze –v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {14, 2, 1, 8052fa60}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : ntoskrnl.exe ( nt+5ba60 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000014, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8052fa60, address which referenced memory
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
WRITE_ADDRESS: unable to get nt!MmPoolCodeEnd
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSpecialPoolStart
unable to get nt!MmPagedPoolStart
unable to get nt!MiSessionPoolStart
unable to get nt!MiSessionPoolEnd
unable to get nt!MmNonPagedPoolExpansionStart
unable to get nt!MmPoolCodeStart
00000014
CURRENT_IRQL: 2
FAULTING_IP:
nt+5ba60
8052fa60 f00fba2900 lock bts dword ptr [ecx],0x0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from 805334b1 to 804f5471
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b2c50c5c 805334b1 0000000a 00000014 00000002 nt+0x21471
b2c50c78 ffffffff 00000202 80534787 b2c50cac nt+0x5f4b1
805348b3 00000000 00000000 00000000 00000000 0xffffffff
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nt+5ba60
8052fa60 f00fba2900 lock bts dword ptr [ecx],0x0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt+5ba60
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 3ea80977
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
windbg> .hh nt!MmPoolCodeEnd
0: kd> !thread
GetPointerFromAddress: unable to read from 8054abd4
*************************************************************************
*** ***
*** ***
*** 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!_ETHREAD ***
*** ***
*************************************************************************
860d9da8: Unable to get thread contents
0: kd> nt!_ETHREAD
^ Syntax error in 'nt!_ETHREAD'
Wer jetzt nicht so 8O guckt weiß vl. was damit anzufangen ![]()
Noch was zum Pc also es kam keine Neue Hardware rein.Hab das letzte mal vor ein paar Monaten Format gemacht und jetzt das erste mal seitdem so einen Vorfall!