BSOD random, driver IRQ L not less than or =


  1. Posts : 3
    Windows 7 64bit Professional
       #1

    BSOD random, driver IRQ L not less than or =


    BSOD, seems to be random. Not really stressing the computer. I did throw some hard drives back in but I am not sure if that is related.

    Thanks,

    Patrick
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    BSOD seems to be caused by Marvell 91xx SATA Controller Driver. Update or remove it and see if BSOD persists.

    Driver Reference Table

    Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-



    Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program: How to Clean Left Over Driver Files with Driver Sweeper
    Code:
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Downloads\SF_ApexMotorsports\SF_20-10-2014\102014-36722-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`0305f000 PsLoadedModuleList = 0xfffff800`032a2890
    Debug session time: Tue Oct 21 03:03:54.199 2014 (UTC + 6:00)
    System Uptime: 0 days 2:27:12.120
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff8801239a3be, 2, 0, fffff8800113c26d}
    
    *** WARNING: Unable to verify timestamp for mvs91xx.sys
    *** ERROR: Module load completed but symbols could not be loaded for mvs91xx.sys
    Probably caused by : mvs91xx.sys ( mvs91xx+2826d )
    
    Followup: MachineOwner
    ---------
    
    11: 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: fffff8801239a3be, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800113c26d, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330c100
    GetUlongFromAddress: unable to read from fffff8000330c1c0
     fffff8801239a3be Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    mvs91xx+2826d
    fffff880`0113c26d 664439632e      cmp     word ptr [rbx+2Eh],r12w
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  firefox.exe
    
    TAG_NOT_DEFINED_c000000f:  FFFFF88003767FB0
    
    TRAP_FRAME:  fffff88003767ce0 -- (.trap 0xfffff88003767ce0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000002
    rdx=0000000000000022 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800113c26d rsp=fffff88003767e70 rbp=fffffa800dc9b008
     r8=0000000000000029  r9=0000000000000000 r10=fffffa800d64b6e0
    r11=fffff8801239a030 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    mvs91xx+0x2826d:
    fffff880`0113c26d 664439632e      cmp     word ptr [rbx+2Eh],r12w ds:00000000`0000002e=????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800030d4169 to fffff800030d4bc0
    
    STACK_TEXT:  
    fffff880`03767b98 fffff800`030d4169 : 00000000`0000000a fffff880`1239a3be 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`03767ba0 fffff800`030d2de0 : c0bd9400`00000000 00000000`00000000 00000000`0000001b fffff880`1239a390 : nt!KiBugCheckDispatch+0x69
    fffff880`03767ce0 fffff880`0113c26d : fffff880`1239a390 fffffa80`0dc9b008 fffffa80`1337a6e0 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`03767e70 fffff880`1239a390 : fffffa80`0dc9b008 fffffa80`1337a6e0 00000000`00000000 00000000`00000000 : mvs91xx+0x2826d
    fffff880`03767e78 fffffa80`0dc9b008 : fffffa80`1337a6e0 00000000`00000000 00000000`00000000 fffff880`01115f3b : 0xfffff880`1239a390
    fffff880`03767e80 fffffa80`1337a6e0 : 00000000`00000000 00000000`00000000 fffff880`01115f3b fffffa80`0dc9b008 : 0xfffffa80`0dc9b008
    fffff880`03767e88 00000000`00000000 : 00000000`00000000 fffff880`01115f3b fffffa80`0dc9b008 fffffa80`0dc9b030 : 0xfffffa80`1337a6e0
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    mvs91xx+2826d
    fffff880`0113c26d 664439632e      cmp     word ptr [rbx+2Eh],r12w
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  mvs91xx+2826d
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: mvs91xx
    
    IMAGE_NAME:  mvs91xx.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4eb79dc9
    
    FAILURE_BUCKET_ID:  X64_0xD1_mvs91xx+2826d
    
    BUCKET_ID:  X64_0xD1_mvs91xx+2826d
    
    Followup: MachineOwner
    ---------
    
    11: kd> lmvm mvs91xx
    start             end                 module name
    fffff880`01114000 fffff880`011a4000   mvs91xx  T (no symbols)           
        Loaded symbol image file: mvs91xx.sys
        Image path: \SystemRoot\system32\DRIVERS\mvs91xx.sys
        Image name: mvs91xx.sys
        Timestamp:        Mon Nov 07 14:58:49 2011 (4EB79DC9)
        CheckSum:         0005CADA
        ImageSize:        00090000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      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:39.
Find Us