BSOD twice a day, sometimes none at all.


  1. Posts : 15
    Windows 7 Ultimate x64
       #1

    BSOD twice a day, sometimes none at all.


    Is Windows 7 . . .
    - x86 (32-bit) or x64 ? x86
    - the original installed OS on the system? I don't think so.
    - an OEM or full retail version? Not sure; bought this from CL a while back.
    - OEM = came pre-installed on system Not sure.
    - Full Retail = you purchased it from retailer Came with Windows 7 on it.

    - What is the age of system (hardware)? 4 years old or so.
    - What is the age of OS installation (have you re-installed the OS?) Person on CL said the 7 install was clean
    and no more than a few days old.


    This is my sister's computer so I don't have access to it all of the time; she tells me now and then it will
    just randomly blue-screen on her. I followed the posting instructions.. and came here for assistance? Another problem that keeps happening is that she has to restart the PC twice per day or so because the USB Belkin wireless adapter stops working. Repairing and resetting the connection in the control panel does nothing. It just sits there. Reinserting the USB plug to it also doesn't help. It seems only a reboot fixes it.

    Also, keep in mind that last night I installed the latest Windows updates, particularly those that are critical and I ran sfc scannow and chkdsk.
      My Computer


  2. Posts : 17,796
    Windows 10, Home Clean Install
       #2

    Code:
     
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp2_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\101210-21169-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 7600 UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.x86fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0x8280e000 PsLoadedModuleList = 0x82956810
    Debug session time: Tue Oct 12 17:10:51.025 2010 (GMT-4)
    System Uptime: 0 days 0:03:36.131
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck D1, {5f2ae9ae, 2, 0, 909ba860}
    Unable to load image \SystemRoot\system32\DRIVERS\athrusb.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for athrusb.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrusb.sys
    Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for sptd.sys
    Probably caused by : nwifi.sys ( nwifi!Dot11GetSenderAddr+e )
    Followup: MachineOwner
    ---------
    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: 5f2ae9ae, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 909ba860, address which referenced memory
    Debugging Details:
    ------------------
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82976718
    Unable to read MiSystemVaType memory at 82956160
     5f2ae9ae 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    nwifi!Dot11GetSenderAddr+e
    909ba860 0fb710          movzx   edx,word ptr [eax]
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    TRAP_FRAME:  8293487c -- (.trap 0xffffffff8293487c)
    ErrCode = 00000000
    eax=5f2ae9ae ebx=856f3d58 ecx=85701528 edx=00000001 esi=85cb9008 edi=00000000
    eip=909ba860 esp=829348f0 ebp=829348f0 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    nwifi!Dot11GetSenderAddr+0xe:
    909ba860 0fb710          movzx   edx,word ptr [eax]       ds:0023:5f2ae9ae=????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from 909ba860 to 8285482b
    STACK_TEXT:  
    8293487c 909ba860 badb0d00 00000001 855f36a0 nt!KiTrap0E+0x2cf
    829348f0 909be02e 8586ffa0 00000000 85cb9008 nwifi!Dot11GetSenderAddr+0xe
    82934978 909be3ec 85cb9008 00000030 856f3d58 nwifi!Pt6RepackRecvNBL+0xb0
    829349a4 86f63a2e 85e0cc08 856f3d58 00000000 nwifi!Pt6Receive+0x128
    829349cc 86f0ec1e 855ab0e0 856f3d58 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x62
    829349f4 908350a4 855ab0e0 856f3d58 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x52
    WARNING: Stack unwind information not available. Following frames may be wrong.
    82934a30 90834be3 855f5300 00000000 00000002 athrusb+0xd0a4
    82934a44 9088007a 855f5300 856eda98 00000001 athrusb+0xcbe3
    82934a68 9087fdd0 85329500 00000002 82934a90 athrusb+0x5807a
    82934a78 90882a93 85329500 856d7048 00001006 athrusb+0x57dd0
    82934a90 86c4aea5 7aa0c958 7a928ff0 00001006 athrusb+0x5aa93
    82934abc 86c5f317 7a9129d0 7aa0c958 856ed57c Wdf01000!FxUsbPipeContinuousReader::_FxUsbPipeRequestComplete+0x3c
    82934ae8 86c43c36 8549c008 855f36a0 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0xf6
    82934b04 86c43cde 016ed628 853a5280 82934b3c Wdf01000!FxIoTarget::RequestCompletionRoutine+0x12d
    82934b14 828978b6 00000000 8549c008 856ed628 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
    82934b3c 82876b33 00000000 8549c008 853a5280 nt!IopUnloadSafeCompletion+0x45
    82934b84 8cc37868 8284e354 8449dcd8 00000000 nt!IopfCompleteRequest+0x128
    82934bb4 8cc38178 8557d8b0 8549c008 856ed5c4 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
    82934be0 8cc3b9af 85392028 853920f0 85392a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
    82934c08 8cc35d18 85392028 85392a98 85392002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
    82934c2c 86cca894 85392aa4 85392002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
    82934c78 828763b5 85392aa4 85392a98 00000000 sptd+0x11894
    82934cd4 82876218 82937d20 82941280 00000000 nt!KiExecuteAllDpcs+0xf9
    82934d20 82876038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
    82934d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
    
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nwifi!Dot11GetSenderAddr+e
    909ba860 0fb710          movzx   edx,word ptr [eax]
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nwifi!Dot11GetSenderAddr+e
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nwifi
    IMAGE_NAME:  nwifi.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc89f
    FAILURE_BUCKET_ID:  0xD1_nwifi!Dot11GetSenderAddr+e
    BUCKET_ID:  0xD1_nwifi!Dot11GetSenderAddr+e
    Followup: MachineOwner
    Update this driver
    Athrusb.sys file description
    Productname: Driver for Atheros Wireless USB Network Adapter
    Description: Atheros Extensible Wireless LAN device driver
    Company: Atheros Communications, Inc


    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done:
    http://www.duplexsecure.com/en/faq
      My Computer


  3. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #3

    Update your wireless driver Atheros Communications, Inc

    Atheros Communications

    This was likely caused by the following module: athrusb.sys
    Bugcheck code: 0xD1 (0x1680076, 0x2, 0x1, 0x884160B8)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
      My Computer


  4. Posts : 15
    Windows 7 Ultimate x64
    Thread Starter
       #4

    yowanvista said:
    Update your wireless driver Atheros Communications, Inc

    Atheros Communications

    This was likely caused by the following module: athrusb.sys
    Bugcheck code: 0xD1 (0x1680076, 0x2, 0x1, 0x884160B8)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    I'm already using the latest drivers for her wireless adapter. I tried looking for some generic chipset adapters but I couldn't get any of them to work.

    I did uninstall Daemon tools though. Hopefully this will yield some good results later today. I'll keep you guys posted on the conditions of the wireless and BSODs.
      My Computer


  5. Posts : 15
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Wireless died again. I'm never buying another Belkin product.

    Can anyone help me locate some different drivers for this device?
      My Computer


  6. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #6

    Pash00n said:
    Wireless died again. I'm never buying another Belkin product.

    Can anyone help me locate some different drivers for this device?
    You can try older drivers
      My Computer


  7. Posts : 15
    Windows 7 Ultimate x64
    Thread Starter
       #7

    yowanvista said:
    Pash00n said:
    Wireless died again. I'm never buying another Belkin product.

    Can anyone help me locate some different drivers for this device?
    You can try older drivers
    Tried 'em. My guess is that the adapter is just faulty at this point.

    The good news though is that the BSODs seemed to have taken a leave of absence. :)
      My Computer


 

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 09:32.
Find Us