Nov 26 2006, 02:50 PM
Can any1 please tell me what's the problem with this debug? :
Microsoft ® Windows Debugger Version 6.3.0017.0
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini112406-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Fri Nov 24 17:11:40 2006
System Uptime: 0 days 0:01:36.891
Loading Kernel Symbols
............................................................................................................................................
Loading unloaded module list
..........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {a6d60484, 2, 0, f78d0c8b}
Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmFlush+23 )
Followup: MachineOwner
---------
kd> .reload
Loading Kernel Symbols
............................................................................................................................................
Loading unloaded module list
..........
Loading User Symbols
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: a6d60484, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f78d0c8b, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: a6d60484
CURRENT_IRQL: 2
FAULTING_IP:
PCIIDEX!BmFlush+23
f78d0c8b ff37 push dword ptr [edi]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from f73aaa05 to f78d0c8b
STACK_TEXT:
80548dbc f73aaa05 86d603f0 80551b80 80551920 PCIIDEX!BmFlush+0x23
80548e2c 80540d5d 86d3c0a4 86d3c030 00000000 atapi!IdePortCompletionDpc+0x75
80548e40 80551920 ffdffc50 00000000 00000000 nt!KiRetireDpcList+0x46
80548e50 80540cd6 00000000 0000000e 00000000 nt!KiIdleThread0
FOLLOWUP_IP:
PCIIDEX!BmFlush+23
f78d0c8b ff37 push dword ptr [edi]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: PCIIDEX!BmFlush+23
MODULE_NAME: PCIIDEX
IMAGE_NAME: PCIIDEX.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 41107b4c
STACK_COMMAND: kb
BUCKET_ID: 0xD1_PCIIDEX!BmFlush+23
Followup: MachineOwner
---------
sometimes it will be DRIVER_IRQL_NOT_LESS_OR_EQUAL (a)
[FAQ] PC auto restart/Blue Screen (BSOD), All questions go here please.
Quote
0.0597sec
0.52
7 queries
GZIP Disabled