Reoccurring BSOD


  1. Posts : 5
    Windows 7
       #1

    Reoccurring BSOD


    Reoccurring BSOD.

    It started on the 13th of february, on that date i installed MagicISO, Pro Evo 2010, an Xbox Controller and a 'USB input device' (could be my external harddrive). Now i get BSOD whenever i leave my computer unmanned for any period of time, recently it's been happening everytime i try to leave my computer on over night downloading, i wake up in the morning and the progress is minimal, suggesting it happens early on into the night. I also suspect utorrent 2.0 for that reason.

    I may try to leave my computer on over night without utorrent to see, but that'll be my last resort.

    Attachment 57341

    Here is all the dump files in RAR.

    Any help would be very much appreciated. Cheers.
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    14 memory dumps - 5 STOP 0x1E and 9 STOP 0xD1
    All seem to blame athrxu6.sys - a component of your Atheros Extensible Wireless LAN device driver

    The problem will most likely be with the driver, but there are many other things that could cause this:
    - hardware failure of the networking card
    - security software malfunction
    - other hardware failure

    To start, please visit the support website of the manufacturer of your wireless device and download the latest Win7 driver (the Atheros site does not server drivers for this device, so you'll have to get it from either the manufacturer of the wireless device or the website of the PC manufacturer)
    - Then uninstall the current driver using Control Panel...Programs...Uninstall a program
    - Then install the freshly downloaded driver and monitor for further BSOD's.

    Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
    Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:
    How To Find Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - - The most common drivers are listed on this page: Driver Reference
    - - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

    Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:
    Code:
    athrxu6.sys  Wed Jul 04 22:58:34 2007 - Atheros Extensible Wireless LAN device driver - http://www.carrona.org/dvrref.html#a
    nvm62x64.sys Fri Oct 17 17:01:06 2008-    nVidia Etherenet Networking Driver (nForce chipset driver) - http://www.carrona.org/dvrref.html#n
    If this doesn't fix the problem, please post back and we'll try more diagnostic tests/fixes.

    Here's a summary of the BSOD's:
    Code:
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Thu Feb 11 23:26:26.765 2010 (GMT-5)
    System Uptime: 0 days 11:08:08.685
    BugCheck D1, {444f08f, 2, 0, fffff880020e0841}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Feb 13 06:22:45.578 2010 (GMT-5)
    System Uptime: 0 days 1:16:36.498
    BugCheck D1, {7139, 2, 0, fffff88002091841}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Feb 13 08:36:04.931 2010 (GMT-5)
    System Uptime: 0 days 2:12:13.726
    BugCheck D1, {1309, 2, 0, fffff8800210c841}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Feb 13 18:14:23.495 2010 (GMT-5)
    System Uptime: 0 days 9:36:51.415
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Feb 16 16:32:11.997 2010 (GMT-5)
    System Uptime: 0 days 11:21:02.885
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Feb 16 18:51:00.806 2010 (GMT-5)
    System Uptime: 0 days 2:17:18.694
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Feb 23 09:16:12.630 2010 (GMT-5)
    System Uptime: 0 days 2:43:53.519
    BugCheck D1, {2951, 2, 0, fffff880020e0841}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Wed Feb 24 11:31:24.854 2010 (GMT-5)
    System Uptime: 0 days 4:30:07.743
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Wed Feb 24 12:18:03.404 2010 (GMT-5)
    System Uptime: 0 days 0:45:34.308
    BugCheck D1, {52, 2, 0, fffff8800211f841}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Wed Feb 24 21:21:59.220 2010 (GMT-5)
    System Uptime: 0 days 1:17:33.124
    BugCheck D1, {322f, 2, 0, fffff8800209c841}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Fri Feb 26 21:46:45.942 2010 (GMT-5)
    System Uptime: 0 days 1:09:23.846
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Feb 27 02:26:02.224 2010 (GMT-5)
    System Uptime: 0 days 4:37:48.128
    BugCheck D1, {465f83a, 2, 0, fffff880022bd841}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Feb 27 17:19:29.440 2010 (GMT-5)
    System Uptime: 0 days 3:35:52.344
    BugCheck D1, {461d537, 2, 0, fffff880020c7841}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Sat Feb 27 21:34:57.209 2010 (GMT-5)
    System Uptime: 0 days 1:42:22.988
    BugCheck D1, {e271, 2, 0, fffff88002367841}
    *** WARNING: Unable to verify timestamp for athrxu6.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxu6.sys
    Probably caused by : athrxu6.sys ( athrxu6+76841 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
      My Computer


  3. Posts : 5
    Windows 7
    Thread Starter
       #3

    Well my computer was originally vista then i upgraded to windows 7. My internet access is done by a USB WLAN stick made by Buffalo - Air Station Wireless G WLI U2 KG54L. As far as i'm aware my computer should have no affiliation with Atheros nor nVidia since not even my graphics card is nVidia. When i installed windows 7 i intended to wipe my computer to get a clean install, since all the error logs you have posted say 'VISTA DRIVER FAULT' could i assume that the install wasn't as clean as i intended? I'm a bit of newbie when it comes to this sorta stuff.

    I'll try finding a windows 7 update for my Buffalo WLAN USB device, in the mean while, is it possible to find those two outdated drivers (athrxu6.sys and nvm62x64.sys) and uninstall them. If they are causing the problem then surely I can just do that and reinstall new versions if needed?

    Thanks for your time.
      My Computer


  4. Posts : 5
    Windows 7
    Thread Starter
       #4

    UPDATE

    I've worked out that the problematic athrxu6.sys file is in fact the driver for my Buffalo - Air Station Wireless G WLI U2 KG54L. Unfortunately these are notoriously hard to get windows 7 drivers for. I will however let you know in the next hour or so how my search goes.

    Secondly, there was two versions of the driver installed (where i had removed the stick then replaced it in the wrong USB slot) and i always remember how one used to give me trouble, so i moved the WLAN stick to the original USB slot and deleted the duplicate driver, that might help.
      My Computer


  5. Posts : 5
    Windows 7
    Thread Starter
       #5

    UPDATE #2

    I couldn't locate an up to date driver for the LAN stick, the buffalo website is shocking and nothing else suggested on the web seemed to work. I'm going to see if my re-jigging has had any effect, with another downloading session tonight.

    If not then i'll simply buy an ethernet to ethernet cable tonight.

    I'll let you know of my results tomorrow!
      My Computer


  6. Posts : 5
    Windows 7
    Thread Starter
       #6

    Had two BSODs since my last post:

    Attachment 57635

    Could someone please tell me whether it is the same problematic driver?

    Since it is becoming such a problem I am looking into getting a long ethernet cable/new wireless USB adapter...

    Any suggestions?
      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 04:20.
Find Us