none
Blue Screen - IRQL NOT EQUAL OR LESS

    Question

  • Hey 

     I have a system with following config.

    RAM 6 GB 

    Nvidia 525M with intel i7 2670 

    OS win 7 Home Premium 64 bit OS 

     

    now as soon as i insert my USB stick for net surfing the blue screen appears and the error is shown as IRQL not equal or less .. 

    Technical Error Code 0X0000000A .....

    How can upload the dump file ? 

    and all the drivers are updated !!!

    i just bought the pc 3 days back and the stick was working fine till today .

    Pls help im freaking out !! 


    • Edited by kingkev1 Saturday, September 24, 2011 7:13 PM
    Saturday, September 24, 2011 6:59 PM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        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: 00000000000003f8, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, 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: fffff80002e94900, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030cd100
     00000000000003f8

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!memcpy+250
    fffff800`02e94900 488b440af8      mov     rax,qword ptr [rdx+rcx-8]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  svchost.exe

    TRAP_FRAME:  fffff8800ef9bf70 -- (.trap 0xfffff8800ef9bf70)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa800d09dbd0 rbx=0000000000000000 rcx=fffffa800d09dff8
    rdx=0000057ff2f62408 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002e94900 rsp=fffff8800ef9c108 rbp=fffffa80055931a0
     r8=0000000000000400  r9=0000000000000020 r10=fffff80003025348
    r11=fffffa800d09dbf8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe cy
    nt!memcpy+0x250:
    fffff800`02e94900 488b440af8      mov     rax,qword ptr [rdx+rcx-8] ds:0006:00000000`000003f8=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80002e9d2a9 to fffff80002e9dd00

    STACK_TEXT: 
    fffff880`0ef9be28 fffff800`02e9d2a9 : 00000000`0000000a 00000000`000003f8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0ef9be30 fffff800`02e9bf20 : fffffa80`08d9a1a0 fffffa80`08d9a1a0 fffffa80`08d9a1a0 fffff880`0ef9c608 : nt!KiBugCheckDispatch+0x69
    fffff880`0ef9bf70 fffff800`02e94900 : fffff880`0906f9bc ffff0000`0f9e113d fffff800`02ed280a fffffa80`00000028 : nt!KiPageFault+0x260
    fffff880`0ef9c108 fffff880`0906f9bc : ffff0000`0f9e113d fffff800`02ed280a fffffa80`00000028 00000000`00000028 : nt!memcpy+0x250
    fffff880`0ef9c110 ffff0000`0f9e113d : fffff800`02ed280a fffffa80`00000028 00000000`00000028 fffffa80`0d09dbd0 : connctfy+0x39bc
    fffff880`0ef9c118 fffff800`02ed280a : fffffa80`00000028 00000000`00000028 fffffa80`0d09dbd0 ffffffff`ffffffff : 0xffff0000`0f9e113d
    fffff880`0ef9c120 fffffa80`08d9af68 : fffffa80`08d9a1a0 fffff880`016a110c 00000000`00000000 00000000`00000000 : nt!MiSwapWslEntries+0x10a
    fffff880`0ef9c180 fffffa80`08d9a1a0 : fffff880`016a110c 00000000`00000000 00000000`00000000 fffff880`0ef9c500 : 0xfffffa80`08d9af68
    fffff880`0ef9c188 fffff880`016a110c : 00000000`00000000 00000000`00000000 fffff880`0ef9c500 00000000`00000000 : 0xfffffa80`08d9a1a0
    fffff880`0ef9c190 fffff880`016a3460 : fffffa80`0cb2d010 00000000`40010008 00000000`40010008 00000000`40010008 : ndis!ndisDereferenceMiniport+0x3c
    fffff880`0ef9c1d0 fffff880`016a3b72 : fffff880`0ef9c608 00000000`40010008 00000000`40010000 fffffa80`055931a0 : ndis!ndisIndicateStatusInternal+0x790
    fffff880`0ef9c3f0 fffff880`016a3d15 : fffff880`0ef9c601 00000000`00000000 00000000`40010000 fffffa80`055931a0 : ndis!NdisMIndicateStatusEx+0x432
    fffff880`0ef9c4a0 fffff880`2147e527 : fffffa80`0c909390 00000000`00120000 00000000`00000001 fffffa80`0cc57060 : ndis!NdisMIndicateStatus+0x165
    fffff880`0ef9c5c0 fffff880`2147d57f : fffffa80`0d5b9290 fffff6fc`4000b5c0 fffff6fc`4000b6b8 fffffa80`059923c0 : asyncmac!AsyncIOCtlRequest+0x8f3
    fffff880`0ef9c670 fffff880`016b8547 : fffffa80`0d5b9300 fffffa80`0558ecb0 00000000`00000000 ffffe0fb`e4d873dc : asyncmac!AsyncDriverDispatch+0x4f
    fffff880`0ef9c6a0 fffff880`016b83dc : fffffa80`0d5b9300 00000000`00000000 fffffa80`0d5b9290 00000000`00000000 : ndis!ndisDummyIrpHandler+0xb7
    fffff880`0ef9c6e0 fffff800`031b8127 : fffffa80`059246a0 fffff880`0ef9cb60 fffffa80`059246a0 fffffa80`0d5b9290 : ndis!ndisDeviceControlIrpHandler+0x3bc
    fffff880`0ef9c8d0 fffff800`031b8986 : fffffa80`0c11b060 00000000`00000000 00000000`00000000 00000000`0540ebc0 : nt!IopXxxControlFile+0x607
    fffff880`0ef9ca00 fffff800`02e9cf93 : fffffa80`0c11b060 00000000`00000001 fffffa80`0ccb0b60 fffff800`03194bc4 : nt!NtDeviceIoControlFile+0x56
    fffff880`0ef9ca70 00000000`7794138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0540ea78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7794138a


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    connctfy+39bc
    fffff880`0906f9bc ??              ???

    SYMBOL_STACK_INDEX:  4

    SYMBOL_NAME:  connctfy+39bc

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: connctfy

    IMAGE_NAME:  connctfy.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4bfe3927

    FAILURE_BUCKET_ID:  X64_0xA_connctfy+39bc

    BUCKET_ID:  X64_0xA_connctfy+39bc

    Followup: MachineOwner
    ---------

    0: kd> lmvm connctfy
    start             end                 module name
    fffff880`0906c000 fffff880`09077000   connctfy T (no symbols)          
        Loaded symbol image file: connctfy.sys
        Image path: \SystemRoot\system32\DRIVERS\connctfy.sys
        Image name: connctfy.sys
        Timestamp:        Thu May 27 11:19:35 2010 (4BFE3927)
        CheckSum:         0000EAEA
        ImageSize:        0000B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

     

    --------------------------------------------

    Your BSOD was caused by connctfy.sys driver. The connctfy.sys is a Connectify driver.

    Uninstalling it should solve your problem.

    See that: http://www.sevenforums.com/crashes-debugging/154096-sad-bsod-when-plugging-usb-cdma-modem.html


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator

    Monday, September 26, 2011 8:38 AM

All replies

  • Hello,

    Bug Check Code 0xA: http://msdn.microsoft.com/en-us/library/ff560129(VS.85).aspx

    Please use Microsoft Skydrive to upload dump files (c:\windows\minidumps). Once done, post a link here.

    You can also contact Microsoft CSS.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator 

    Sunday, September 25, 2011 12:25 AM
  • Thanks for the reply .. 

    Now i must tell you that i installed a USB key board n mouse drivers yesterday and eversince the blue screen has been coming .

    The only strange thing is that when i plug the keyboard/mouse in BSOD doesn't come up .. It comes up when i plugin the Net Connecter USB ( whose drivers are already updated ) 

    May there be the case with USB keyboard / mouse drivers ?

    The dump files are in here 

    https://skydrive.live.com/#!/?cid=d53fcf2a08c730e6&sc=documents&uc=2&nl=1&id=D53FCF2A08C730E6%21118

    • Edited by kingkev1 Sunday, September 25, 2011 6:38 AM
    Sunday, September 25, 2011 6:29 AM
  • *******************************************************************************
    *                                                                             *
    *                        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: 00000000000003f8, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, 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: fffff80002e94900, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030cd100
     00000000000003f8

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!memcpy+250
    fffff800`02e94900 488b440af8      mov     rax,qword ptr [rdx+rcx-8]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xA

    PROCESS_NAME:  svchost.exe

    TRAP_FRAME:  fffff8800ef9bf70 -- (.trap 0xfffff8800ef9bf70)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa800d09dbd0 rbx=0000000000000000 rcx=fffffa800d09dff8
    rdx=0000057ff2f62408 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002e94900 rsp=fffff8800ef9c108 rbp=fffffa80055931a0
     r8=0000000000000400  r9=0000000000000020 r10=fffff80003025348
    r11=fffffa800d09dbf8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe cy
    nt!memcpy+0x250:
    fffff800`02e94900 488b440af8      mov     rax,qword ptr [rdx+rcx-8] ds:0006:00000000`000003f8=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80002e9d2a9 to fffff80002e9dd00

    STACK_TEXT: 
    fffff880`0ef9be28 fffff800`02e9d2a9 : 00000000`0000000a 00000000`000003f8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0ef9be30 fffff800`02e9bf20 : fffffa80`08d9a1a0 fffffa80`08d9a1a0 fffffa80`08d9a1a0 fffff880`0ef9c608 : nt!KiBugCheckDispatch+0x69
    fffff880`0ef9bf70 fffff800`02e94900 : fffff880`0906f9bc ffff0000`0f9e113d fffff800`02ed280a fffffa80`00000028 : nt!KiPageFault+0x260
    fffff880`0ef9c108 fffff880`0906f9bc : ffff0000`0f9e113d fffff800`02ed280a fffffa80`00000028 00000000`00000028 : nt!memcpy+0x250
    fffff880`0ef9c110 ffff0000`0f9e113d : fffff800`02ed280a fffffa80`00000028 00000000`00000028 fffffa80`0d09dbd0 : connctfy+0x39bc
    fffff880`0ef9c118 fffff800`02ed280a : fffffa80`00000028 00000000`00000028 fffffa80`0d09dbd0 ffffffff`ffffffff : 0xffff0000`0f9e113d
    fffff880`0ef9c120 fffffa80`08d9af68 : fffffa80`08d9a1a0 fffff880`016a110c 00000000`00000000 00000000`00000000 : nt!MiSwapWslEntries+0x10a
    fffff880`0ef9c180 fffffa80`08d9a1a0 : fffff880`016a110c 00000000`00000000 00000000`00000000 fffff880`0ef9c500 : 0xfffffa80`08d9af68
    fffff880`0ef9c188 fffff880`016a110c : 00000000`00000000 00000000`00000000 fffff880`0ef9c500 00000000`00000000 : 0xfffffa80`08d9a1a0
    fffff880`0ef9c190 fffff880`016a3460 : fffffa80`0cb2d010 00000000`40010008 00000000`40010008 00000000`40010008 : ndis!ndisDereferenceMiniport+0x3c
    fffff880`0ef9c1d0 fffff880`016a3b72 : fffff880`0ef9c608 00000000`40010008 00000000`40010000 fffffa80`055931a0 : ndis!ndisIndicateStatusInternal+0x790
    fffff880`0ef9c3f0 fffff880`016a3d15 : fffff880`0ef9c601 00000000`00000000 00000000`40010000 fffffa80`055931a0 : ndis!NdisMIndicateStatusEx+0x432
    fffff880`0ef9c4a0 fffff880`2147e527 : fffffa80`0c909390 00000000`00120000 00000000`00000001 fffffa80`0cc57060 : ndis!NdisMIndicateStatus+0x165
    fffff880`0ef9c5c0 fffff880`2147d57f : fffffa80`0d5b9290 fffff6fc`4000b5c0 fffff6fc`4000b6b8 fffffa80`059923c0 : asyncmac!AsyncIOCtlRequest+0x8f3
    fffff880`0ef9c670 fffff880`016b8547 : fffffa80`0d5b9300 fffffa80`0558ecb0 00000000`00000000 ffffe0fb`e4d873dc : asyncmac!AsyncDriverDispatch+0x4f
    fffff880`0ef9c6a0 fffff880`016b83dc : fffffa80`0d5b9300 00000000`00000000 fffffa80`0d5b9290 00000000`00000000 : ndis!ndisDummyIrpHandler+0xb7
    fffff880`0ef9c6e0 fffff800`031b8127 : fffffa80`059246a0 fffff880`0ef9cb60 fffffa80`059246a0 fffffa80`0d5b9290 : ndis!ndisDeviceControlIrpHandler+0x3bc
    fffff880`0ef9c8d0 fffff800`031b8986 : fffffa80`0c11b060 00000000`00000000 00000000`00000000 00000000`0540ebc0 : nt!IopXxxControlFile+0x607
    fffff880`0ef9ca00 fffff800`02e9cf93 : fffffa80`0c11b060 00000000`00000001 fffffa80`0ccb0b60 fffff800`03194bc4 : nt!NtDeviceIoControlFile+0x56
    fffff880`0ef9ca70 00000000`7794138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0540ea78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7794138a


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    connctfy+39bc
    fffff880`0906f9bc ??              ???

    SYMBOL_STACK_INDEX:  4

    SYMBOL_NAME:  connctfy+39bc

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: connctfy

    IMAGE_NAME:  connctfy.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4bfe3927

    FAILURE_BUCKET_ID:  X64_0xA_connctfy+39bc

    BUCKET_ID:  X64_0xA_connctfy+39bc

    Followup: MachineOwner
    ---------

    0: kd> lmvm connctfy
    start             end                 module name
    fffff880`0906c000 fffff880`09077000   connctfy T (no symbols)          
        Loaded symbol image file: connctfy.sys
        Image path: \SystemRoot\system32\DRIVERS\connctfy.sys
        Image name: connctfy.sys
        Timestamp:        Thu May 27 11:19:35 2010 (4BFE3927)
        CheckSum:         0000EAEA
        ImageSize:        0000B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

     

    --------------------------------------------

    Your BSOD was caused by connctfy.sys driver. The connctfy.sys is a Connectify driver.

    Uninstalling it should solve your problem.

    See that: http://www.sevenforums.com/crashes-debugging/154096-sad-bsod-when-plugging-usb-cdma-modem.html


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator

    Monday, September 26, 2011 8:38 AM