IRQL_NOT_LESS_OR_EQUAL
STOP: 0X0000000A (0X006C280, 0X0000002, 0X00000000 , 0X80520689)
Below is details of memory dump
Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini052510-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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon May 24 21:57:24.109 2010 (UTC + 1:00)
System Uptime: 0 days 4:04:01.828
*********************************************************************
* 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
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {c006c280, 2, 0, 80520689}
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+49689 )
Followup: MachineOwner
---------
1: kd> .restart /f
Loading Dump File [C:\WINDOWS\Minidump\Mini052510-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: http://msdl.microsof...ownload/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.100216-1514
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon May 24 21:57:24.109 2010 (UTC + 1:00)
System Uptime: 0 days 4:04:01.828
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {c006c280, 2, 0, 80520689}
Probably caused by : Unknown_Image ( nt!KiTrap0E+d0 )
Followup: MachineOwner
---------
1: 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: c006c280, 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: 80520689, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: c006c280
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmAccessFault+cab
80520689 8b07 mov eax,dword ptr [edi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: QBMsgMgr.exe
TRAP_FRAME: b46f7b34 -- (.trap 0xffffffffb46f7b34)
ErrCode = 00000004
eax=00000000 ebx=00000000 ecx=5d090000 edx=7c90e514 esi=00000000 edi=00000000
eip=7c9102f6 esp=0012ecfc ebp=0012ed24 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
001b:7c9102f6 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from 805445b0 to 80520689
STACK_TEXT:
b46f7b1c 805445b0 00000000 5d090000 00000001 nt!MmAccessFault+0xcab
b46f7b1c 7c9102f6 00000000 5d090000 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012ed24 00000000 00000000 00000000 00000000 0x7c9102f6
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+d0
805445b0 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiTrap0E+d0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: RAISED_IRQL_USER_FAULT
MODULE_NAME: Unknown_Module
Followup: MachineOwner
---------
1: 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: c006c280, 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: 80520689, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: c006c280
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmAccessFault+cab
80520689 8b07 mov eax,dword ptr [edi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: QBMsgMgr.exe
TRAP_FRAME: b46f7b34 -- (.trap 0xffffffffb46f7b34)
ErrCode = 00000004
eax=00000000 ebx=00000000 ecx=5d090000 edx=7c90e514 esi=00000000 edi=00000000
eip=7c9102f6 esp=0012ecfc ebp=0012ed24 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
001b:7c9102f6 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from 805445b0 to 80520689
STACK_TEXT:
b46f7b1c 805445b0 00000000 5d090000 00000001 nt!MmAccessFault+0xcab
b46f7b1c 7c9102f6 00000000 5d090000 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012ed24 00000000 00000000 00000000 00000000 0x7c9102f6
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+d0
805445b0 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiTrap0E+d0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: RAISED_IRQL_USER_FAULT
MODULE_NAME: Unknown_Module
Followup: MachineOwner
---------
1: 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: c006c280, 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: 80520689, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: c006c280
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmAccessFault+cab
80520689 8b07 mov eax,dword ptr [edi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: QBMsgMgr.exe
TRAP_FRAME: b46f7b34 -- (.trap 0xffffffffb46f7b34)
ErrCode = 00000004
eax=00000000 ebx=00000000 ecx=5d090000 edx=7c90e514 esi=00000000 edi=00000000
eip=7c9102f6 esp=0012ecfc ebp=0012ed24 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
001b:7c9102f6 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from 805445b0 to 80520689
STACK_TEXT:
b46f7b1c 805445b0 00000000 5d090000 00000001 nt!MmAccessFault+0xcab
b46f7b1c 7c9102f6 00000000 5d090000 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012ed24 00000000 00000000 00000000 00000000 0x7c9102f6
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+d0
805445b0 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiTrap0E+d0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: RAISED_IRQL_USER_FAULT
MODULE_NAME: Unknown_Module
Followup: MachineOwner
---------
1: 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: c006c280, 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: 80520689, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: c006c280
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmAccessFault+cab
80520689 8b07 mov eax,dword ptr [edi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: QBMsgMgr.exe
TRAP_FRAME: b46f7b34 -- (.trap 0xffffffffb46f7b34)
ErrCode = 00000004
eax=00000000 ebx=00000000 ecx=5d090000 edx=7c90e514 esi=00000000 edi=00000000
eip=7c9102f6 esp=0012ecfc ebp=0012ed24 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
001b:7c9102f6 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from 805445b0 to 80520689
STACK_TEXT:
b46f7b1c 805445b0 00000000 5d090000 00000001 nt!MmAccessFault+0xcab
b46f7b1c 7c9102f6 00000000 5d090000 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012ed24 00000000 00000000 00000000 00000000 0x7c9102f6
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+d0
805445b0 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiTrap0E+d0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: RAISED_IRQL_USER_FAULT
MODULE_NAME: Unknown_Module
Followup: MachineOwner
---------