BSOD IRQL Not Less or Equal, KMode Exception Not Handled, Service Exce


  1. Posts : 2
    windows 7 professional 64bit
       #1

    BSOD IRQL Not Less or Equal, KMode Exception Not Handled, Service Exce


    Hey,
    I keep getting BSOD every few hours randomly. I've tried updating drivers, removing AVG, Registry cleaners, MemTest64, and Seagate drive test. Here are my dump files. Attachment 240526 I'm just stuck and need some help. Any ideas will be much appreciated.

    Thanks,
    Mugsy420
      My Computer


  2. Posts : 51,384
    Windows 11 Workstation x64
       #2

    The dumps are blaming sptd.sys so if you have Daemon tools please uninstall it and see how you go.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {200, 2, 1, fffff80002ad6065}
    
    *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for sptd.sys
    Probably caused by : sptd.sys ( sptd+45c7e )
    
    Followup: MachineOwner
    ---------
    
    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: 0000000000000200, 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: fffff80002ad6065, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfc100
    GetUlongFromAddress: unable to read from fffff80002cfc1c0
     0000000000000200 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KeAcquireSpinLockRaiseToDpc+55
    fffff800`02ad6065 f0480fba2900    lock bts qword ptr [rcx],0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff880031fb8a0 -- (.trap 0xfffff880031fb8a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000200
    rdx=fffffa80038691a0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002ad6065 rsp=fffff880031fba30 rbp=0000000000000200
     r8=0000000000000000  r9=0000000000000000 r10=000000000000001c
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nt!KeAcquireSpinLockRaiseToDpc+0x55:
    fffff800`02ad6065 f0480fba2900    lock bts qword ptr [rcx],0 ds:00000000`00000200=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002acc569 to fffff80002accfc0
    
    STACK_TEXT:  
    fffff880`031fb758 fffff800`02acc569 : 00000000`0000000a 00000000`00000200 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`031fb760 fffff800`02acb1e0 : fffffa80`05a36010 fffff880`00000103 fffff880`07963398 00000000`00000002 : nt!KiBugCheckDispatch+0x69
    fffff880`031fb8a0 fffff800`02ad6065 : fffffa80`05be1d90 fffffa80`05d5edf0 fffffa80`05d5eec8 fffffa80`06d27230 : nt!KiPageFault+0x260
    fffff880`031fba30 fffff880`0618efed : fffffa80`038691a0 fffff880`0619055c 00000000`00000000 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x55
    fffff880`031fba80 fffff880`0618c657 : 00000000`00000002 fffffa80`038691a0 fffffa80`05420050 00000000`00000000 : USBPORT!USBPORT_Core_DecIoRequestCount+0x31
    fffff880`031fbac0 fffff880`0618cb0f : fffffa80`03825002 fffffa80`05a36010 00000000`ffffffff fffffa80`05420eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa3b
    fffff880`031fbba0 fffff880`0618a66f : fffffa80`05420eb0 fffffa80`054201a0 fffffa80`05421050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
    fffff880`031fbc00 fffff880`0617bf89 : fffffa80`05420050 00000000`00000000 fffffa80`05420e02 fffffa80`05420eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
    fffff880`031fbc40 fffff880`00ec2c7e : fffffa80`0534b000 fffffa80`05420ec8 fffffa80`05420e00 fffff880`031fbcc8 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
    fffff880`031fbc70 fffffa80`0534b000 : fffffa80`05420ec8 fffffa80`05420e00 fffff880`031fbcc8 00000000`00000000 : sptd+0x45c7e
    fffff880`031fbc78 fffffa80`05420ec8 : fffffa80`05420e00 fffff880`031fbcc8 00000000`00000000 fffffa80`0534c1dd : 0xfffffa80`0534b000
    fffff880`031fbc80 fffffa80`05420e00 : fffff880`031fbcc8 00000000`00000000 fffffa80`0534c1dd fffff880`031d3180 : 0xfffffa80`05420ec8
    fffff880`031fbc88 fffff880`031fbcc8 : 00000000`00000000 fffffa80`0534c1dd fffff880`031d3180 fffffa80`05420eb0 : 0xfffffa80`05420e00
    fffff880`031fbc90 00000000`00000000 : fffffa80`0534c1dd fffff880`031d3180 fffffa80`05420eb0 fffffa80`05420ec8 : 0xfffff880`031fbcc8
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    sptd+45c7e
    fffff880`00ec2c7e ??              ???
    
    SYMBOL_STACK_INDEX:  9
    
    SYMBOL_NAME:  sptd+45c7e
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: sptd
    
    IMAGE_NAME:  sptd.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bbd315c
    
    FAILURE_BUCKET_ID:  X64_0xA_sptd+45c7e
    
    BUCKET_ID:  X64_0xA_sptd+45c7e
    
    Followup: MachineOwner
      My Computers


  3. Posts : 2
    windows 7 professional 64bit
    Thread Starter
       #3

    update


    pc finally bricked. pretty sure motherboard is fried. eventually quit getting errors and am stuck with amber flashing power button. have reset cmos, replaced psu, and tried many other things. mobo beeps with no memory and light is green but with memory it will not beep (post).
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:27.
Find Us