none
bsod/freezing while gaming

    Question

  • Built a new machine.
    ASRock N7AD-SLI
    e7400
    powercooler 4770 video care
    4g super talent ram
    1 tb WD green
    dvd burner

    This was a brand new build with win7 build 7100  installed from the beginning. Win7 runs perfectly except from time to time while playing atlantica online (a mmorpg that shouldnt be too intensive, i used to play on 80% settings on my old amd 3000/9800 pro)
    Sometimes it will play for 2 hours without an issue, sometime 15 mins. in 1 of 2 things will happen. It will either freeze the video, still have music and will only respond to reset button or it will bsod.

    here is the recovery message after a restart

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7100.2.0.0.256.1
      Locale ID:    1033

    Additional information about the problem:
      BCCode:    116
      BCP1:    FFFFFA8006A5F010
      BCP2:    FFFFF88004833AC8
      BCP3:    0000000000000000
      BCP4:    0000000000000002
      OS Version:    6_1_7100
      Service Pack:    0_0
      Product:    256_1

    Files that help describe the problem:
      C:\Windows\Minidump\060209-20139-01.dmp
      C:\Users\Richards\AppData\Local\Temp\WER-31340-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt


    i have several .dmp files also but sorry not sure how to attach them.

    any ideas would be greatly appreciated
    Mike
    Thursday, June 04, 2009 2:12 AM

Answers

All replies

  • Hi Mike,

    Can you ZIP C:\Windows\Minidump\060209-20139-01.dmp, password-protect the ZIP file, upload the ZIP file somewhere, and then privately or publicly share the location of the ZIP file, and privately share the password with those you would have inspect the .dmp file?
    Thursday, June 04, 2009 1:27 PM
  • ok i found the debugger program and was able to open them. while i understand very little of it, it seems to be a video card driver issue. I may have to live with it for awhile, as i am using a 4770 which is brand new on the market and not alot of driver options yet. i am using the most current driver that was listed on the ati site for win7.
    i have several lof these minidumps, if i see something that looks way different than this one i will post it as well

    Thanks
    Mike


    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\060209-20139-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 7100 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
    Machine Name:
    Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02e3be90
    Debug session time: Tue Jun  2 20:31:24.272 2009 (GMT-5)
    System Uptime: 0 days 0:01:03.207
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 116, {fffffa8006a5f010, fffff88004833ac8, 0, 2}

    Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : atikmdag.sys ( atikmdag+12ac8 )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8006a5f010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004833ac8, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, Optional internal context dependent data.

    Debugging Details:
    ------------------


    FAULTING_IP:
    atikmdag+12ac8
    fffff880`04833ac8 48895c2408      mov     qword ptr [rsp+8],rbx

    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

    CUSTOMER_CRASH_COUNT:  1

    BUGCHECK_STR:  0x116

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    STACK_TEXT: 
    fffff880`033c3988 fffff880`042d1cbc : 00000000`00000116 fffffa80`06a5f010 fffff880`04833ac8 00000000`00000000 : nt!KeBugCheckEx
    fffff880`033c3990 fffff880`042d19c6 : fffff880`04833ac8 fffffa80`06a5f010 fffffa80`05466710 fffffa80`05468010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`033c39d0 fffff880`04378f07 : fffffa80`06a5f010 00000000`00000000 fffffa80`05466710 fffffa80`05468010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`033c3a00 fffff880`043a2b75 : 00000000`ffffffff 00000000`00000f41 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`033c3ae0 fffff880`043a12bb : 00000000`00000102 00000000`00000000 00000000`00000f41 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`033c3b10 fffff880`043742c6 : ffffffff`ff676980 fffffa80`05468010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`033c3bb0 fffff880`043a0e7a : 00000000`00000000 fffffa80`054ecab0 00000000`00000080 fffffa80`05468010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`033c3cc0 fffff800`02f06e66 : 00000000`fffffc32 fffffa80`0548ca10 fffffa80`0366b890 fffffa80`0548ca10 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`033c3d00 fffff800`02c33a86 : fffff800`02de8e80 fffffa80`0548ca10 fffff800`02df6c40 fffff880`012569a0 : nt!PspSystemThreadStartup+0x5a
    fffff880`033c3d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND:  .bugcheck ; kb

    FOLLOWUP_IP:
    atikmdag+12ac8
    fffff880`04833ac8 48895c2408      mov     qword ptr [rsp+8],rbx

    SYMBOL_NAME:  atikmdag+12ac8

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: atikmdag

    IMAGE_NAME:  atikmdag.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  49f7ba28

    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys

    BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys

    Followup: MachineOwner
    ---------

    Thursday, June 04, 2009 4:44 PM
  • hmm this one is different so ill add it as well. thanks again for any help.


    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\060109-18392-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Mini Kernel Dump does not have process information
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7100 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
    Machine Name:
    Kernel base = 0xfffff800`02c49000 PsLoadedModuleList = 0xfffff800`02e82e90
    Debug session time: Mon Jun  1 01:20:06.552 2009 (GMT-5)
    System Uptime: 0 days 3:11:07.487
    Loading Kernel Symbols
    .............................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
    Unable to add module at 00000000`00000000

    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7F, {8, 80050031, 406f8, fffff80002cc6069}

    Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000406f8
    Arg4: fffff80002cc6069

    Debugging Details:
    ------------------


    BUGCHECK_STR:  0x7f_8

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    CURRENT_IRQL:  2

    TRAP_FRAME:  fffff8800465b000 -- (.trap 0xfffff8800465b000)
    Unable to read trap frame at fffff880`0465b000

    LAST_CONTROL_TRANSFER:  from fffff80002cc74e9 to fffff80002cc7f80

    STACK_TEXT: 
    fffff800`00ba4d28 fffff800`02cc74e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
    fffff800`00ba4d30 fffff800`02cc59b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00ba4e70 fffff800`02cc6069 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`0465b000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x169


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!KiDoubleFaultAbort+b2
    fffff800`02cc59b2 90              nop

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  49ee9439

    FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

    BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

    Followup: MachineOwner
    ---------

    Thursday, June 04, 2009 4:48 PM
  • Yes, this appears to be related to the video driver, or perhaps the hardware.  Any video card firmware updates available?
    Thursday, June 04, 2009 5:00 PM
  • This is a double fault; one of the more common causes can be a hardware problem.  Another common cause is a kernel stack overflow.  What is the output of fltmc.exe, when run from an elevated CMD prompt?
    Thursday, June 04, 2009 5:03 PM
  • i actually just found there is one newer now on ati sites than the one i had. will try it and post back if i keep having issues.

    thank you
    Mike
    Thursday, June 04, 2009 5:03 PM
  • ok so here is the most common one i am getting (btw the new driver for my gpu seems to be working much better)

    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\061509-12604-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 7100 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
    Machine Name:
    Kernel base = 0xfffff800`02e15000 PsLoadedModuleList = 0xfffff800`0304ee90
    Debug session time: Mon Jun 15 09:47:29.415 2009 (GMT-5)
    System Uptime: 0 days 0:00:05.350
    Loading Kernel Symbols
    ................................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa8004429038, 0, 0}

    Probably caused by : hardware

    Followup: MachineOwner
    ---------

    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8004429038, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

    Debugging Details:
    ------------------


    BUGCHECK_STR:  0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    STACK_TEXT: 
    fffff880`02fe06b0 fffff800`030cba99 : fffffa80`04429010 fffffa80`036ed040 00000000`0000000c 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`02fe0bd0 fffff800`02facba7 : fffffa80`04429010 fffff800`03026638 fffffa80`036ed040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`02fe0c00 fffff800`02f16b85 : fffff800`030883a0 00000000`00000001 fffff880`0103d080 fffffa80`036ed040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`02fe0c40 fffff800`02e99744 : fffffa80`042fce00 fffff800`03088400 fffffa80`036ed000 fffff800`03019638 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`02fe0c70 fffff800`03119e66 : ec834857`41564155 00000000`00000001 fffffa80`036ed040 3c8b4865`c0220f44 : nt!ExpWorkerThread+0x11a
    fffff880`02fe0d00 fffff800`02e46a86 : fffff880`009e8180 fffffa80`036ed040 fffff880`009f2f40 009f01ed`32407824 : nt!PspSystemThreadStartup+0x5a
    fffff880`02fe0d40 00000000`00000000 : fffff880`02fe1000 fffff880`02fdb000 fffff880`02fe0060 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

    Followup: MachineOwner
    ---------

    Monday, June 15, 2009 2:54 PM
  • This is a double fault; one of the more common causes can be a hardware problem.  Another common cause is a kernel stack overflow.  What is the output of fltmc.exe, when run from an elevated CMD prompt?

    ok im kinda a novice so not sure if this is what you are looking for.. (i went to accessories, right click command prompt and run as admin.) typed in fltmc.exe and this is what i got:


    Filter name      Num Instances         Altitude     Frame

    KLIF                      4                      320400        0
    luafv                     1                       135000       0
    FileInfo                  4                       45000        0
    Monday, June 15, 2009 2:59 PM
  • Looks like the analysis is pointing the finger at faulty hardware (WHEA - Windows Hardware Error Architecture).  Wonder if executing dt -r nt!WHEA_ERROR_RECORD 0xfffffa8004429038 in the debugger may provide any further details?
    Monday, June 15, 2009 3:18 PM
  • Any chance you could try AV software other than Kaspersky, to see if things get any better?
    Monday, June 15, 2009 3:19 PM
  • Looks like the analysis is pointing the finger at faulty hardware (WHEA - Windows Hardware Error Architecture).  Wonder if executing dt -r nt!WHEA_ERROR_RECORD 0xfffffa8004429038 in the debugger may provide any further details?
    unless im doing something wrong, i just get this:

    1: kd> dt -r nt!WHEA_ERROR_RECORD 0xfffffa8004429038
    Symbol nt!WHEA_ERROR_RECORD not found.


    as far as AV, im open to anything, what is recommended?


    Thanks
    Mike
    Monday, June 15, 2009 3:32 PM
  • what is recommended?
    Unfortunately, I'm unable to offer any suggestions.
    Symbol nt!WHEA_ERROR_RECORD not found.
    Oh well - it was just a thought. 

    Is, or has the system ever been, overclocked?

    Are you able to run any diagnostic utilities (manufacturer diagnostics, etc.)?
    Monday, June 15, 2009 3:51 PM
  • never overclocked, bought all the components myself and assembled recently.

    This bsod hasn't been a huge issue, its very infrequent, but just thought if it was something easy to fix, id give it a shot.

    will report back if it starts happening frequently.


    Thanks
    Mike
    Monday, June 15, 2009 3:57 PM
  • The most recent analysis posted points to hardware failure.  Perhaps, recheck connections, etc. and ensure heat is not an issue for any components (adequate ventilation and cooling, etc.). Also, do consider running any diagnostics you can get your hands on, for the components in the system...
    Monday, June 15, 2009 4:19 PM
  • Ok over the last few days i have run everything i can think of, ran furmark for well over 1 hour, ran memtest, prime95 torture test for 1:20.  Everything passed fine. And i still get this intermittent freezeup. Its very random and sometimes will go days, sometimes when it happens it will happen again right away within 5 mins, sometimes not again for days. im kinda at a loss and thinking of putting vista on this computer (new build have only run win7) and see if still happens.

    Thanks
    Mike
    Thursday, June 18, 2009 3:46 PM
  • Do you have any other video hardware you can try? 
    Thursday, June 18, 2009 3:54 PM
  • Do you have any other video hardware you can try? 

    unfortunately i do not. old computer was agp, this one of course is pci-e and my board has no integrated video.
    Thursday, June 18, 2009 8:24 PM
  • Have you checked connections, blown dust out of the enclosure, and ensured excessive heat is not at work?
    Friday, June 19, 2009 1:57 AM