BSOD 1000007e athrx.sys driver


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

    BSOD 1000007e athrx.sys driver


    I keep getting a BSOD with my athrx.sys driver being listed on the BSOD screen.

    I've uninstalled/reinstalled the driver, but still having the BSOD.

    Every time it crashes, I am doing nothing intense at all. Typically just reading an article or watching a YouTube Video. It has even crashed once while I was gone and all that was running was uTorrent.

    Other:
    --Nothing detected after running MalwareBytes
    --Nothing detected after running Avast! Antivirus
    --100% pass after running MemTest86
    --Ran ChkDsk with no problems
    --Ran SFC with no issues
    --Used system restore to two weeks ago when there were no problems, although nothing new was installed since then. Still BSOD-ed after that
    --Ran Startup repair using my Windows 7 installation disk

    Any help would be appreciated!
      My Computer


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

    Welcome to the forum.

    Do you receive BSOD's in safe mode too?: Start your computer in safe mode - Microsoft Windows Help

    Reduce items at start-up: Startup Programs - Change

    Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

    Avast seems to be contributing to your BSOD's. Please remove it for testing purpose. Use Microsoft Security Essentials.

    Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

    Microsoft Security Essentials - Free Antivirus for Windows

    Malwarebytes - Free

    Good and Free system security combination.

    Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

    ESET online scanner: Free Online Virus Scanner | ESET

    Please remove the software below for the time being:

    mcdbus.sys Tue Feb 24 16:34:07 2009 (49A3CD1F)
    MagicISO SCSI Host Controller driver
    Driver Reference Table - mcdbus.sys

    NTIOLib_X64.sys Tue Nov 20 14:14:23 2012 (50AB3BDF)
    MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5
    Driver Reference Table - NTIOLib_X64.sys

    pbfilter.sys Tue Nov 19 11:56:06 2013 (528AFD76)
    Peerblock
    Driver Reference Table - pbfilter.sys

    Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

    Code:
    athrx.sys Wed Feb 23 02:17:31 2011 (4D6419DB) 
    Atheros network adapter driver
    Driver Reference Table - athrx.sys

    Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

    Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

    Run Disk Check on your Hard Drive(s): Disk Check

    Let us know the results.

    BSOD BUGCHECK SUMMARY
    Code:
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sat Jan 18 23:13:29.161 2014 (UTC + 6:00)
    System Uptime: 0 days 2:20:34.957
    BugCheck 1000007E, {ffffffffc0000005, fffff88004c90b7e, fffff8800397a578, fffff88003979dd0}
    *** WARNING: Unable to verify timestamp for athrx.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrx.sys
    Probably caused by : athrx.sys ( athrx+59b7e )
    BUGCHECK_STR:  0x7E
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Thu Jan 16 06:14:55.178 2014 (UTC + 6:00)
    System Uptime: 0 days 0:01:17.959
    BugCheck C4, {f6, 118, fffffa8009f13620, fffff88004465058}
    *** WARNING: Unable to verify timestamp for mcdbus.sys
    *** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
    Probably caused by : mcdbus.sys ( mcdbus+22058 )
    BUGCHECK_STR:  0xc4_f6
    PROCESS_NAME:  MagicDisc.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Thu Jan 16 06:13:07.324 2014 (UTC + 6:00)
    System Uptime: 0 days 0:01:40.104
    BugCheck C4, {f6, 118, fffffa80099b1b30, fffff88004465058}
    *** WARNING: Unable to verify timestamp for mcdbus.sys
    *** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
    Probably caused by : mcdbus.sys ( mcdbus+22058 )
    BUGCHECK_STR:  0xc4_f6
    PROCESS_NAME:  MagicDisc.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Thu Jan 16 06:10:40.430 2014 (UTC + 6:00)
    System Uptime: 0 days 2:02:51.211
    BugCheck C4, {f6, 118, fffffa800775c720, fffff880045b9058}
    *** WARNING: Unable to verify timestamp for mcdbus.sys
    *** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
    Probably caused by : mcdbus.sys ( mcdbus+22058 )
    BUGCHECK_STR:  0xc4_f6
    PROCESS_NAME:  MagicDisc.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Wed Jan 15 10:20:42.440 2014 (UTC + 6:00)
    System Uptime: 0 days 0:01:36.221
    BugCheck C4, {f6, 1bc, fffffa8009b627a0, fffff8800f09ea6d}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+9aa6d )
    BUGCHECK_STR:  0xc4_f6
    PROCESS_NAME:  nvspcaps64.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Wed Jan 15 10:18:25.320 2014 (UTC + 6:00)
    System Uptime: 0 days 0:02:20.100
    BugCheck C4, {f6, 1bc, fffffa80077d6560, fffff8800f126a6d}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+9aa6d )
    BUGCHECK_STR:  0xc4_f6
    PROCESS_NAME:  nvspcaps64.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Wed Jan 15 09:36:28.442 2014 (UTC + 6:00)
    System Uptime: 0 days 4:30:22.223
    BugCheck 1000007E, {ffffffffc0000005, fffff88004c7cb7e, fffff8800a586578, fffff8800a585dd0}
    *** WARNING: Unable to verify timestamp for athrx.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrx.sys
    Probably caused by : athrx.sys ( athrx+59b7e )
    BUGCHECK_STR:  0x7E
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Wed Jan 15 04:24:52.261 2014 (UTC + 6:00)
    System Uptime: 0 days 0:00:33.042
    BugCheck C4, {f6, ac, fffffa8008406b30, fffff8800f0be0a1}
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+9b0a1 )
    BUGCHECK_STR:  0xc4_f6
    PROCESS_NAME:  rundll32.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Tue Jan 14 06:01:11.956 2014 (UTC + 6:00)
    System Uptime: 0 days 3:03:47.642
    BugCheck 1000007E, {ffffffffc0000005, fffff88004ad3b7e, fffff8800ad0c578, fffff8800ad0bdd0}
    *** WARNING: Unable to verify timestamp for athrx.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrx.sys
    Probably caused by : athrx.sys ( athrx+59b7e )
    BUGCHECK_STR:  0x7E
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      My Computer


  3. Posts : 3
    Windows 7 64-bit
    Thread Starter
       #3

    Thanks a lot for the reply, I greatly appreciate it! I'll complete the steps you mentioned and get back to you with results.

    You mentioned to update an old driver, athrx.sys. That's my network driver for my TP-LINK card, TL-WDN4800. I went to their website and downloaded the latest driver (TL-WDN4800 - Welcome to TP-LINK).

    I can't find a newer one than that, what flags it for you as being an outdated driver?

    Thanks so much!
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    what flags it for you as being an outdated driver?
    Code:
    *** WARNING: Unable to verify timestamp for athrx.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrx.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff88004c90b7e, fffff8800397a578, fffff88003979dd0}
    
    Probably caused by : athrx.sys ( athrx+59b7e )
    
    Followup: MachineOwner
    ---------
    Code:
    fffff880`04c37000 fffff880`04ed9000   athrx    T (no symbols)           
        Loaded symbol image file: athrx.sys
        Image path: \SystemRoot\system32\DRIVERS\athrx.sys
        Image name: athrx.sys
        Timestamp:        Wed Feb 23 01:47:31 2011 (4D6419DB)
        CheckSum:         0029D477
        ImageSize:        002A2000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    I can't find a newer one than that,
    TL-WDN4800 - Welcome to TP-LINK

    Attachment 302267
      My Computer


  5. Posts : 3
    Windows 7 64-bit
    Thread Starter
       #5

    @Arc

    That's actually the same website as in my link; although it appears to be a newer driver, I think it's just the bundle that was updated to include the Windows 8 driver. I downloaded that same file and it's still a Windows 7 driver from 2011 according to the date in device manager.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    For other people, it updates the driver.
      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 13:39.
Find Us