It's start 2 days ago i happen to see IRQL not less or equal , bugged usb device , system service excesstion , bad pool (bad pool some thing i dont sure) , APC index dismatch
and after i reinstall my window i see IRQL again... so i cam looking for help.
it show up when i playing my game for some time
i did play rise of nations i get the problem in 10 minute
when i play some thing like call of duty it happen to crash after a few then 30 sec some time just crash after i'm open the game
I am afraid that one DMP is very incomplete. Unfortunately nothing
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Upload all the new ones you have.
A couple of things you can do
Run a memory test
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.
Run a system file check
SFC /SCANNOW Command - System File Checker
Let us know if you need additional help
Ken
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\111110-17175-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image Unknown_Module_00000000`00000002, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000002
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000002
Debugger can not determine kernel base address
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a4e000 PsLoadedModuleList = 0xfffff800`02c8be50
Debug session time: Wed Nov 10 20:01:42.102 2010 (GMT-5)
System Uptime: 0 days 0:17:45.475
Unable to load image Unknown_Module_00000000`00000002, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000002
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000002
Debugger can not determine kernel base address
Loading Kernel Symbols
.
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa7f01a14360, 2, 1, fffff80002ac3fb4}
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000002
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000002
Unknown module 'Unknown_Module_00000000_00000002' found on stack, using vad to reload module.
!vad_reload -1 0x2
Failed to get new vadroot
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
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: fffffa7f01a14360, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002ac3fb4, address which referenced memory
Debugging Details:
------------------
Unknown module 'Unknown_Module_00000000_00000002' found on stack, using vad to reload module.
!vad_reload -1 0x2
Failed to get new vadroot
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffffa7f01a14360
CURRENT_IRQL: 0
FAULTING_IP:
+5a08952f01a0dc24
fffff800`02ac3fb4 48894108 mov qword ptr [rcx+8],rax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from fffff80002acda3a to fffff88003da67f2
STACK_TEXT:
fffff800`00b9cc98 fffff800`02acda3a : 00000000`002cdabc fffffa80`02c8a9d8 fffff800`02c46c40 00000000`00000001 : 0xfffff880`03da67f2
fffff800`00b9cca0 00000000`002cdabc : fffffa80`02c8a9d8 fffff800`02c46c40 00000000`00000001 fffff800`02c38e80 : 0xfffff800`02acda3a
fffff800`00b9cca8 fffffa80`02c8a9d8 : fffff800`02c46c40 00000000`00000001 fffff800`02c38e80 fffff800`02acb697 : 0x2cdabc
fffff800`00b9ccb0 fffff800`02c46c40 : 00000000`00000001 fffff800`02c38e80 fffff800`02acb697 00000000`bac460e2 : 0xfffffa80`02c8a9d8
fffff800`00b9ccb8 00000000`00000001 : fffff800`02c38e80 fffff800`02acb697 00000000`bac460e2 00000000`bac460e0 : 0xfffff800`02c46c40
fffff800`00b9ccc0 fffff800`02c38e80 : fffff800`02acb697 00000000`bac460e2 00000000`bac460e0 00000000`bac460e2 : 0x1
fffff800`00b9ccc8 fffff800`02acb697 : 00000000`bac460e2 00000000`bac460e0 00000000`bac460e2 00000000`000000cb : 0xfffff800`02c38e80
fffff800`00b9ccd0 00000000`bac460e2 : 00000000`bac460e0 00000000`bac460e2 00000000`000000cb fffffa80`02c8a940 : 0xfffff800`02acb697
fffff800`00b9ccd8 00000000`bac460e0 : 00000000`bac460e2 00000000`000000cb fffffa80`02c8a940 400000c2`400000c1 : 0xbac460e2
fffff800`00b9cce0 00000000`bac460e2 : 00000000`000000cb fffffa80`02c8a940 400000c2`400000c1 fffffa80`400000c3 : 0xbac460e0
fffff800`00b9cce8 00000000`000000cb : fffffa80`02c8a940 400000c2`400000c1 fffffa80`400000c3 00000000`6b066076 : 0xbac460e2
fffff800`00b9ccf0 fffffa80`02c8a940 : 400000c2`400000c1 fffffa80`400000c3 00000000`6b066076 00000000`00000000 : Unknown_Module_00000000_00000002+0xc9
fffff800`00b9ccf8 400000c2`400000c1 : fffffa80`400000c3 00000000`6b066076 00000000`00000000 fffff800`02ac60f4 : 0xfffffa80`02c8a940
fffff800`00b9cd00 fffffa80`400000c3 : 00000000`6b066076 00000000`00000000 fffff800`02ac60f4 00000000`00000010 : 0x400000c2`400000c1
fffff800`00b9cd08 00000000`6b066076 : 00000000`00000000 fffff800`02ac60f4 00000000`00000010 00000000`00000212 : 0xfffffa80`400000c3
fffff800`00b9cd10 00000000`00000000 : fffff800`02ac60f4 00000000`00000010 00000000`00000212 fffff800`00b9cd40 : 0x6b066076
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: CORRUPT_MODULELIST
Followup: MachineOwner
---------
Quote