чё мне деалать ? как исправить ???
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini042610-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
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Apr 26 21:11:21.203 2010 (GMT+3)
System Uptime: 0 days 8:14:47.931
*********************************************************************
* 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 aswMon2.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {b0, 2, 0, 804ef13c}
Примечание:
***** 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 : aswMon2.SYS ( aswMon2+20d4 )
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: 000000b0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 804ef13c, address which referenced memory
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+ *
*********************************************************************
MODULE_NAME: aswMon2
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4aaf72cc
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
000000b0
CURRENT_IRQL: 2
FAULTING_IP:
nt+1813c
804ef13c 8b80b0000000 mov eax,dword ptr [eax+0B0h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from a6d630d4 to 804ef13c
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b5c68994 a6d630d4 8a25b5a8 8936db48 8a5b3030 nt+0x1813c
b5c689b0 804eeeb1 89a2c020 89108c08 89a2c020 aswMon2+0x20d4
b5c689ec 805809cf 8936db48 00000000 8a5c88c0 nt+0x17eb1
b5c68a40 804f5106 c000019c b5c68b00 00000000 nt+0xa99cf
b5c68a70 80581830 8a5c7150 8a5c88c0 b5c68ba4 nt+0x1e106
b5c68b60 805bdd10 8a5c88c0 00000000 8a64ed28 nt+0xaa830
b5c68bd8 805ba398 00000000 b5c68c18 00000040 nt+0xe6d10
b5c68c2c 80574e4d 00000000 00000000 a8fd3401 nt+0xe3398
b5c68ca8 805757c4 00a8fdb0 00100001 00a8fd60 nt+0x9de4d
b5c68d04 80578f83 00a8fdb0 00100001 00a8fd60 nt+0x9e7c4
b5c68d44 8054060c 00a8fdb0 00100001 00a8fd60 nt+0xa1f83
b5c68d64 7c90eb94 badb0d00 00a8fd3c 0f0c0f8d nt+0x6960c
b5c68d68 badb0d00 00a8fd3c 0f0c0f8d b0f2b2f0 0x7c90eb94
b5c68d6c 00a8fd3c 0f0c0f8d b0f2b2f0 00000000 0xbadb0d00
b5c68d70 0f0c0f8d b0f2b2f0 00000000 00000000 0xa8fd3c
b5c68d74 b0f2b2f0 00000000 00000000 00000000 0xf0c0f8d
b5c68d78 00000000 00000000 00000000 00000000 0xb0f2b2f0
STACK_COMMAND: kb
FOLLOWUP_IP:
aswMon2+20d4
a6d630d4 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: aswMon2+20d4
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: aswMon2.SYS
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Примечание:
эээ как бы написано синий экран смерти !!!
а эт наверно ошибка которую он выдал !!!!
Примечание:
Кто нибуть поможет ????