Random BSOD while playing games

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by MrApproved, Dec 8, 2011.

  1. MrApproved

    MrApproved New Member

    Joined:
    Dec 8, 2011
    Messages:
    8
    Likes Received:
    0
    Hey guys im having a spot of bother, recently ive been having the BSOD about 3/4 times a day, sometimes instantly when i open a game (Terraria/WoW/BFBC3/Minecraft etc) or it can take up to hours or whenever, the time is always different.
    I did try to install Fedora 16 VIA usb pen about a month ago, but it did do it before but not as much, anyways here is the zip file with all the minidumbs and i hope it helps :) also i have just updated my graphics card drivers but nothing else, if anyone has a good program that detects if there is a newer driver, it would be awesome :),

    View attachment MiniDump.rar

    MrApproved

    Cheers for the help.
     
  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Most of your recent dump files 12 of the last 13) identify a problem with
    athr.sys 9/26/2010 Atheros Extensible Wireless LAN device driver
    This could be an actual Atheros card or one of many top tier vendor cards using an atheros chipset.
    If you can identify exactly what network adapter you are using you may be able to update the driver from here ATHEROS drivers for Microsoft Windows (Atheros?????)
    Otherwise post the Hardware Ids and we'll help find you the proper driver.
    As an additional priority you need to update this driver
    ASACPI.sys 8/12/2004 from here ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
    Near the middle of the page under utilities ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit should get you to the 5/13/2009 version
    The only other driver I see an issue with is
    nvm62x32.sys 10/17/2008 NVIDIA MCP Networking Function Driver you may need to check with Nvidia or more likely the motherboard vendor for your specific motherboard for an updated version of that driver.
    DUMP FILE:
    Code:
    ................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck D1, {c, 2, 1, 9249f159}
    Unable to load image \SystemRoot\system32\DRIVERS\[COLOR=#ff0000][U][B]athr.sys[/B][/U][/COLOR], Win32 error 0n2
    *** WARNING: Unable to verify timestamp for [B][U][COLOR=#ff0000]athr.sys[/COLOR][/U][/B]
    *** ERROR: Module load completed but symbols could not be loaded for[U][B][COLOR=#ff0000] athr.sys[/COLOR][/B][/U]
    [U][B][COLOR=#ff0000]Probably caused by : athr.sys ( athr+13159 )[/COLOR][/B][/U]
    Followup: MachineOwner
    ---------
    1: 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: 0000000c, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 9249f159, address which referenced memory
    Debugging Details:
    ------------------
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82f6d718
    Unable to read MiSystemVaType memory at 82f4d180
     0000000c 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    athr+13159
    9249f159 c7400c00000000  mov     dword ptr [eax+0Ch],0
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    TRAP_FRAME:  9e02fb5c -- (.trap 0xffffffff9e02fb5c)
    ErrCode = 00000002
    eax=00000000 ebx=866e2008 ecx=863d6c90 edx=00000000 esi=863380e0 edi=00000002
    eip=9249f159 esp=9e02fbd0 ebp=9e02fbdc iopl=0         nv up ei ng nz ac pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010296
    athr+0x13159:
    9249f159 c7400c00000000  mov     dword ptr [eax+0Ch],0 ds:0023:0000000c=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from 9249f159 to 82e4b7cb
    STACK_TEXT:  
    9e02fb5c 9249f159 badb0d00 00000000 00000020 nt!KiTrap0E+0x2cf
    WARNING: Stack unwind information not available. Following frames may be wrong.
    9e02fbdc 924a1349 863d9020 863d6d38 00000001 [U][B][COLOR=#ff0000]athr[/COLOR][/B][/U]+0x13159
    9e02fc14 924a06ca 863d9020 00000001 00000002 [U][B][COLOR=#ff0000]athr[/COLOR][/B][/U]+0x15349
    9e02fc30 92508164 863d9020 9e02fc58 9250d3ce [U][COLOR=#ff0000]athr[/COLOR][/U]+0x146ca
    9e02fc3c 9250d3ce 863df020 866e2d30 00000ec9 [U][B][COLOR=#ff0000]athr[/COLOR][/B][/U]+0x7c164
    9e02fc58 924aa4fd 863df020 9e02fc74 9248d791 [B][U][COLOR=#ff0000]athr[/COLOR][/U][/B]+0x813ce
    9e02fc64 9248d791 85bb6020 863d9020 9e02fcb0 [U][B][COLOR=#ff0000]athr[/COLOR][/B][/U]+0x1e4fd
    9e02fc74 88eec309 863d9020 00000000 9e02fca0 [B][U][COLOR=#ff0000]athr[/COLOR][/U][/B]+0x1791
    9e02fcb0 88ecd6b2 866e201c 006e2008 00000000 ndis!ndisMiniportDpc+0xe2
    9e02fd10 88eb4976 866e2108 00000000 851782a0 ndis!ndisQueuedMiniportDpcWorkItem+0xd0
    9e02fd50 83013a55 00000001 ba597127 00000000 ndis!ndisReceiveWorkerThread+0xeb
    9e02fd90 82ec5239 88eb488b 00000001 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    [U][B][COLOR=#ff0000]athr[/COLOR][/B][/U]+13159
    9249f159 c7400c00000000  mov     dword ptr [eax+0Ch],0
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  [B][U][COLOR=#ff0000]athr[/COLOR][/U][/B]+13159
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: [B][U][COLOR=#ff0000]athr[/COLOR][/U][/B]
    IMAGE_NAME:  [B][U][COLOR=#ff0000]athr.sys[/COLOR][/U][/B]
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c9fdc60
    FAILURE_BUCKET_ID:  0xD1_[B][U][COLOR=#ff0000]athr[/COLOR][/U][/B]+13159
    BUCKET_ID:  0xD1_[B][U][COLOR=#ff0000]athr[/COLOR][/U][/B]+13159
    Followup: MachineOwner
     
  3. MrApproved

    MrApproved New Member

    Joined:
    Dec 8, 2011
    Messages:
    8
    Likes Received:
    0
    Awesome, k first off i downloaded the
    ATK0110
    driver and i have updated that, the wireless network card i am using is
    TL-WN851ND
    made by TP-LINK
    also the Nvidia driver? any chance i could get a link for a driver or? do you want me to get you the hardware ID

    Cheers

    Also i just downloaded drivers for my network card here http://www.tp-link.com/en/support/download/?model=TL-WN851ND+
    are these up to date?
     
    #3 MrApproved, Dec 8, 2011
    Last edited: Dec 8, 2011
  4. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
  5. MrApproved

    MrApproved New Member

    Joined:
    Dec 8, 2011
    Messages:
    8
    Likes Received:
    0
  6. MrApproved

    MrApproved New Member

    Joined:
    Dec 8, 2011
    Messages:
    8
    Likes Received:
    0
  7. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Yes, I would have recommended the chipset update from there and if Blue Screens persist you may want to consider a BIOS update from there as well (if applicable).
     

Share This Page

Loading...