Recurring BSOD eventually leads to reactivation of OS

Page 1 of 4 123 ... LastLast

  1. Posts : 21
    Window 7 Pro 64 bit
       #1

    Recurring BSOD eventually leads to reactivation of OS


    Hi! I upgraded to 7 Pro 64 bit 2-3 months ago after installing more ram than XP would allow for. Shortly after I installed an evga geforce gtx 660 ti and my computer began crashing, especially while browsing the internet and/or watching videos online. I updated the drivers for my gfx card and my mobo and nothing helped.

    Eventually my desktop went black on reboot and I was notified in the bottom right corner that the version wasn't genuine. A simple call to windows got me activated again.

    I have now uninstalled the gtx 660i and replaced it with my old radeon x550, complete with legacy catalyst drivers, and I'm still crashing; especially while watching videos online.

    I hope that wasn't too much information.

    Thanks!
      My Computer


  2. Posts : 851
    Windows 8 Professional x64
       #2

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    *** WARNING: Unable to verify timestamp for athrxusb.sys
    *** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
    Code:
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    TAG_NOT_DEFINED_c000000f:  FFFFF80004664FB0
    
    EXCEPTION_RECORD:  fffff8000465e268 -- (.exr 0xfffff8000465e268)
    ExceptionAddress: fffff88001608767 (nwifi!Pt6RepackRecvNBL+0x0000000000000103)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    TRAP_FRAME:  fffff8000465e310 -- (.trap 0xfffff8000465e310)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8009fbe230 rbx=0000000000000000 rcx=fffff880016406e0
    rdx=fffffa8009feff40 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001608767 rsp=fffff8000465e4a0 rbp=0000000000000000
     r8=0000000000000000  r9=c7a4d2e668434650 r10=fffff8800163e110
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    nwifi!Pt6RepackRecvNBL+0x103:
    fffff880`01608767 450fb701        movzx   r8d,word ptr [r9] ds:c7a4d2e6`68434650=????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002e81ffe to fffff80002e8a610
    
    STACK_TEXT:  
    fffff800`0465d348 fffff800`02e81ffe : 00000000`00000003 00000000`00000001 fffff800`0465dac0 fffff800`02eb62a0 : nt!KeBugCheck
    fffff800`0465d350 fffff800`02eb5f6d : fffff800`03091a10 fffff800`02fcdc78 fffff800`02e0a000 fffff800`0465e268 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff800`0465d380 fffff800`02eb4d45 : fffff800`02fd10fc fffff800`0465d3f8 fffff800`0465e268 fffff800`02e0a000 : nt!RtlpExecuteHandlerForException+0xd
    fffff800`0465d3b0 fffff800`02ec5dc1 : fffff800`0465e268 fffff800`0465dac0 fffff800`00000000 fffffa80`09dbf850 : nt!RtlDispatchException+0x415
    fffff800`0465da90 fffff800`02e89cc2 : fffff800`0465e268 00000000`00000000 fffff800`0465e310 fffffa80`0a576010 : nt!KiDispatchException+0x135
    fffff800`0465e130 fffff800`02e885ca : fffffa80`09f8a048 fffffa80`00000001 fffff800`0465e3d8 fffffa80`07db26e0 : nt!KiExceptionDispatch+0xc2
    fffff800`0465e310 fffff880`01608767 : 00000000`00000000 00000000`00000000 fffffa80`0a576010 fffffa80`095a6668 : nt!KiGeneralProtectionFault+0x10a
    fffff800`0465e4a0 fffff880`016096c8 : fffffa80`09ff7030 fffffa80`09fb4834 fffffa80`00000834 fffffa80`0a576010 : nwifi!Pt6RepackRecvNBL+0x103
    fffff800`0465e5a0 fffff880`017034f7 : fffffa80`0841b1a0 fffffa80`09dbf850 00000000`00000001 fffffa80`09fb8558 : nwifi!Pt6Receive+0x170
    fffff800`0465e600 fffff880`08a63202 : 00000000`00000000 fffff880`00f98130 fffffa80`09daaf90 fffffa80`0841b000 : ndis! ?? ::FNODOBFM::`string'+0xcf1f
    fffff800`0465e650 00000000`00000000 : fffff880`00f98130 fffffa80`09daaf90 fffffa80`0841b000 fffffa80`00000001 : athrxusb+0x11202
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nwifi!Pt6RepackRecvNBL+103
    fffff880`01608767 450fb701        movzx   r8d,word ptr [r9]
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  nwifi!Pt6RepackRecvNBL+103
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nwifi
    
    IMAGE_NAME:  nwifi.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc3b
    
    FAILURE_BUCKET_ID:  X64_0x1E_nwifi!Pt6RepackRecvNBL+103
    
    BUCKET_ID:  X64_0x1E_nwifi!Pt6RepackRecvNBL+103
    
    Followup: MachineOwner
    ---------
    Please update your Atheros Extensible Wireless LAN device driver

    The latest crashes blame wireless device. So updating the driver to the latest version should most likely solve your issue. If you get more BSOD post the dumps.
      My Computer


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

    Here are the links:
    If its wireless, match your device from here:

    If its not a wireless, match your device from here:
      My Computer


  4. Posts : 21
    Window 7 Pro 64 bit
    Thread Starter
       #4

    thanks for the speedy responses! I'll let you know how it turns out.
      My Computer


  5. Posts : 21
    Window 7 Pro 64 bit
    Thread Starter
       #5

    How do I know which update to download?
      My Computer


  6. Posts : 851
    Windows 8 Professional x64
       #6

    Check for the model number in the device manager or under user manual.

    Check for driver of that model and update it.
      My Computer


  7. Posts : 21
    Window 7 Pro 64 bit
    Thread Starter
       #7

    Thanks again! However, no model number is provided in either the device manager properties for my network adapter or in SIW.
      My Computer


  8. Posts : 851
    Windows 8 Professional x64
       #8

    bucklew1 said:
    Thanks again! However, no model number is provided in either the device manager properties for my network adapter or in SIW.

    Open device manager.
    Click network adapters.
    Right click the concerned adapter and check the model number under properties

    OR

    Speccy - Download
      My Computer


  9. Posts : 21
    Window 7 Pro 64 bit
    Thread Starter
       #9

    Thanks for Speccy! I did your first step exactly. And I located it within Speccy. All i get is this:
    Belkin Wireless G USB Network Adapter #5. It said #7 before.
      My Computer


  10. Posts : 851
    Windows 8 Professional x64
       #10

    See this

    Belkin
      My Computer


 
Page 1 of 4 123 ... LastLast

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