BSOD Increasing in frequency, IRQ possible problem, can't restore


  1. Posts : 2
    Windows 7 Professional, 64 bit
       #1

    BSOD Increasing in frequency, IRQ possible problem, can't restore


    Hello,

    Thanks for any help.

    My computer is giving me a BSOD with greater frequency. It typically occurs when the computer has been sleeping and I begin to use it. Unfortunately, the BSOD screen doesn't stay up long and I haven't been able to grab the error code. One time I did see a note about "IRQ not equal or less" but I did not see that the last time.

    I have unsuccessfully tried to restore to different points while in safe and normal modes.

    Attached is the zip file that shows my logs.

    Again, thanks for any help.
      My Computer


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

    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\MAIN-Tue_05_19_2015_170326_03\051915-54615-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    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 (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18839.amd64fre.win7sp1_gdr.150427-0707
    Machine Name:
    Kernel base = 0xfffff800`03654000 PsLoadedModuleList = 0xfffff800`0389b730
    Debug session time: Tue May 19 17:40:56.593 2015 (UTC + 6:00)
    System Uptime: 3 days 19:52:56.651
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    .........................................
    Loading User Symbols
    Loading unloaded module list
    ................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 10D, {6, 3, 57ff398f528, fffffa80113fce40}
    
    *** WARNING: Unable to verify timestamp for ax88179_178a.sys
    *** ERROR: Module load completed but symbols could not be loaded for ax88179_178a.sys
    Probably caused by : ax88179_178a.sys ( ax88179_178a+65f7 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WDF_VIOLATION (10d)
    The Kernel-Mode Driver Framework was notified that Windows detected an error
    in a framework-based driver. In general, the dump file will yield additional
    information about the driver that caused this bug check.
    Arguments:
    Arg1: 0000000000000006, A fatal error was made in handling a WDF request. In this case,
        Parameter 2 further specifies the type of fatal error that has
        been made, as defined by the enumeration WDF_REQUEST_FATAL_ERROR.
    Arg2: 0000000000000003, The driver attempted to send a framework request that has
        already been sent to an I/O target.
    Arg3: 0000057ff398f528, The WDF request handle value.
    Arg4: fffffa80113fce40, Reserved.
    
    Debugging Details:
    ------------------
    
    
    OVERLAPPED_MODULE: Address regions for 'hiber_msahci' and 'hiber_pciide' overlap
    
    BUGCHECK_STR:  0x10D_6
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  HPLJUTSCH.exe
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    DPC_STACK_BASE:  FFFFF80000BA0FB0
    
    LAST_CONTROL_TRANSFER:  from fffff88000e733d3 to fffff800036c88c0
    
    STACK_TEXT:  
    fffff800`00ba0558 fffff880`00e733d3 : 00000000`0000010d 00000000`00000006 00000000`00000003 0000057f`f398f528 : nt!KeBugCheckEx
    fffff800`00ba0560 fffff880`00e71384 : 00000000`00000000 fffff800`00ba0681 00000000`00000000 fffffa80`119187c0 : Wdf01000!FxIoTarget::SubmitLocked+0xcb
    fffff800`00ba0610 fffff880`00e72082 : fffffa80`0f8fc570 fffffa80`0c670ad0 fffff800`00ba06a0 fffff800`00ba06e0 : Wdf01000!FxIoTarget::Submit+0x60
    fffff800`00ba0650 fffff880`0b3cb5f7 : fffffa80`113fcfc0 fffffa80`0c670ad0 fffffa80`119187c0 fffffa80`0a0174c0 : Wdf01000!imp_WdfRequestSend+0x48e
    fffff800`00ba06e0 fffffa80`113fcfc0 : fffffa80`0c670ad0 fffffa80`119187c0 fffffa80`0a0174c0 00000000`00000000 : ax88179_178a+0x65f7
    fffff800`00ba06e8 fffffa80`0c670ad0 : fffffa80`119187c0 fffffa80`0a0174c0 00000000`00000000 fffff880`02c7170a : 0xfffffa80`113fcfc0
    fffff800`00ba06f0 fffffa80`119187c0 : fffffa80`0a0174c0 00000000`00000000 fffff880`02c7170a 00000000`00000000 : 0xfffffa80`0c670ad0
    fffff800`00ba06f8 fffffa80`0a0174c0 : 00000000`00000000 fffff880`02c7170a 00000000`00000000 00000000`00000000 : 0xfffffa80`119187c0
    fffff800`00ba0700 00000000`00000000 : fffff880`02c7170a 00000000`00000000 00000000`00000000 fffff800`00ba0800 : 0xfffffa80`0a0174c0
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    ax88179_178a+65f7
    fffff880`0b3cb5f7 ??              ???
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  ax88179_178a+65f7
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ax88179_178a
    
    IMAGE_NAME:  ax88179_178a.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  529d9206
    
    FAILURE_BUCKET_ID:  X64_0x10D_6_ax88179_178a+65f7
    
    BUCKET_ID:  X64_0x10D_6_ax88179_178a+65f7
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x10d_6_ax88179_178a+65f7
    
    FAILURE_ID_HASH:  {252e286c-6da5-fc7a-4004-7de723701cbc}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm ax88179_178a
    start             end                 module name
    fffff880`0b3c5000 fffff880`0b3dc000   ax88179_178a T (no symbols)           
        Loaded symbol image file: ax88179_178a.sys
        Image path: \SystemRoot\system32\DRIVERS\ax88179_178a.sys
        Image name: ax88179_178a.sys
        Timestamp:        Tue Dec 03 14:10:46 2013 (529D9206)
        CheckSum:         0001B2A2
        ImageSize:        00017000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    
    Unloaded modules:
    fffff880`0b3c5000 fffff880`0b3dc000   ax88179_178a
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00017000
    fffff880`0b3d8000 fffff880`0b3ef000   ax88179_178a
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00017000
    fffff880`0b284000 fffff880`0b29b000   ax88179_178a
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00017000
    fffff880`05cf0000 fffff880`05d07000   ax88179_178a
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00017000
    Can't find what software this driver belongs to.

     Clean boot


    Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

    Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
    • Click on the
    • Type CMD on Search
    • Left click and Run as Administrator
    • Type SFC /scannow

    Full tutorial here:
      My Computer


  3. Posts : 2
    Windows 7 Professional, 64 bit
    Thread Starter
       #3

    Thanks for the help. Oddly, I'm not having the issue anymore.
      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 03:55.
Find Us