# Blue screen caused by digiclsb.sys

**URL:** <https://forums.digi.com/t/blue-screen-caused-by-digiclsb-sys/8007>\
**Category:** USB Devices\
**Created:** [March 7, 2011, 10:13am UTC](https://forums.digi.com/t/blue-screen-caused-by-digiclsb-sys/8007 "2011-03-07T10:13:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![flknap](https://avatars.discourse-cdn.com/v4/letter/f/e480ec/32.png) [@flknap](https://forums.digi.com/u/flknap)\
**Post date:** [March 7, 2011, 10:13am UTC](https://forums.digi.com/t/blue-screen-caused-by-digiclsb-sys/8007/1 "2011-03-07T10:13:13Z")

</div>

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:  
fffff880`009b0728 fffff800`02c94be9 : 00000000`0000000a fffff800`030936c0 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx  
fffff880`009b0730 fffff800`02c93860 : 00000001`885a0be3 fffffa80`07c2b308 00000000`00000002 fffffa80`0a29b510 : nt!KiBugCheckDispatch+0x69  
fffff880`009b0870 fffff800`030936c0 : fffff880`047edd22 00000000`00000000 fffffa80`00000003 fffff880`009b0a80 : nt!KiPageFault+0x260  
fffff880`009b0a08 fffff880`047edd22 : 00000000`00000000 fffffa80`00000003 fffff880`009b0a80 fffff800`0311da82 : nt!IoConnectInterrupt  
fffff880`009b0a10 00000000`00000000 : fffffa80`00000003 fffff880`009b0a80 fffff800`0311da82 fffffa80`000000a2 : 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

## Followup: MachineOwner

---

<div class="post-metadata">

**Author:** ![Admin1](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Admin1](https://forums.digi.com/u/Admin1)\
**Post date:** [March 7, 2011, 6:48pm UTC](https://forums.digi.com/t/blue-screen-caused-by-digiclsb-sys/8007/2 "2011-03-07T18:48:04Z")

</div>

Hi,  
You should probably open an online support request. With any blue screen issue, it is important to get a kernel memory dump so our engineers can analyze it.  
[http://www.digi.com/support/eservice/login.jsp?p=true](http://www.digi.com/support/eservice/login.jsp?p=true)