After I upgraded to Windows 7 x64 edition I very often get blue screen caused by digiclsb.sys. I am used the latest verion (8.1.22.0 from 06-11-2007)
If I use windbg to analyse the minidump created by windows I get the following:
3: 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: fffff800030936c0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, 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: fffff800030936c0, address which referenced memory
Debugging Details:
READ_ADDRESS: fffff800030936c0
CURRENT_IRQL: 2
FAULTING_IP:
nt!IoConnectInterrupt+0
fffff800`030936c0 4881ec88000000 sub rsp,88h
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880009b0870 – (.trap 0xfffff880009b0870)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000a2 rbx=0000000000000000 rcx=fffffa80081565e8
rdx=fffff880047e5140 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030936c0 rsp=fffff880009b0a08 rbp=00000000c0000016
r8=fffffa8008156470 r9=0000000000000000 r10=fffff980193c4e10
r11=fffff80002c15000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!IoConnectInterrupt:
fffff800`030936c0 4881ec88000000 sub rsp,88h
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c94be9 to fffff80002c95640
FAILED_INSTRUCTION_ADDRESS:
nt!IoConnectInterrupt+0
fffff800`030936c0 4881ec88000000 sub rsp,88h
STACK_TEXT:
fffff880009b0728 fffff80002c94be9 : 000000000000000a fffff800030936c0 0000000000000002 0000000000000008 : nt!KeBugCheckEx
fffff880009b0730 fffff80002c93860 : 00000001885a0be3 fffffa8007c2b308 0000000000000002 fffffa800a29b510 : nt!KiBugCheckDispatch+0x69
fffff880009b0870 fffff800030936c0 : fffff880047edd22 0000000000000000 fffffa8000000003 fffff880009b0a80 : nt!KiPageFault+0x260
fffff880009b0a08 fffff880047edd22 : 0000000000000000 fffffa8000000003 fffff880009b0a80 fffff8000311da82 : nt!IoConnectInterrupt
fffff880009b0a10 0000000000000000 : fffffa8000000003 fffff880009b0a80 fffff8000311da82 fffffa80000000a2 : digiclsb+0xed22
STACK_COMMAND: kb
FOLLOWUP_IP:
digiclsb+ed22
fffff880`047edd22 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: digiclsb+ed22
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: digiclsb
IMAGE_NAME: digiclsb.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47322489
FAILURE_BUCKET_ID: X64_0xA_VRF_CODE_AV_BAD_IP_digiclsb+ed22
BUCKET_ID: X64_0xA_VRF_CODE_AV_BAD_IP_digiclsb+ed22