The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Which GPU driver are you using for the G73JH?

    Discussion in 'ASUS Gaming Notebook Forum' started by Crogge, Apr 8, 2012.

  1. Crogge

    Crogge Notebook Consultant

    Reputations:
    3
    Messages:
    166
    Likes Received:
    3
    Trophy Points:
    31
    I use personally always the newest driver but I don't like the last version, every 3-4 days I get at least 1 bluescreen since I installed it. I only installed the latest version of flash in the meanwhile.

    Which AMD drivers are you using and what is in your pov the best / most stable version?
     
  2. Heihachi88

    Heihachi88 Notebook Deity

    Reputations:
    124
    Messages:
    1,148
    Likes Received:
    15
    Trophy Points:
    56
    12.2 WHQL is awesome.
     
  3. Crogge

    Crogge Notebook Consultant

    Reputations:
    3
    Messages:
    166
    Likes Received:
    3
    Trophy Points:
    31
    Well I use the default 12.3 driver currently and got for example today again a BS. Guess I will give 12.2 a try, thanks :)
     
  4. Heihachi88

    Heihachi88 Notebook Deity

    Reputations:
    124
    Messages:
    1,148
    Likes Received:
    15
    Trophy Points:
    56
    Have you used modded vBios for ur 5870? (Chastity has it)
     
  5. HavokD

    HavokD Notebook Guru

    Reputations:
    13
    Messages:
    54
    Likes Received:
    0
    Trophy Points:
    15
    What kind of BSOD do you get? Check the event in event viewer.

    Is it anything related to the "driver has stopped and recovered"? Event 41 if I recall correctly....
     
  6. Crogge

    Crogge Notebook Consultant

    Reputations:
    3
    Messages:
    166
    Likes Received:
    3
    Trophy Points:
    31
    I use the custom vBIOS but had never any issues with it, as I said the new issues appear with the latest driver installation.

    Yes it seems to be related with the "Attempt to reset the display driver and recover from timeout failed." issue, here the crash dump:
    Code:
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800923f4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004f1a9e0, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000d, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    atikmpag+79e0
    fffff880`04f1a9e0 4883ec28        sub     rsp,28h
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`02de49c8 fffff880`0674e000 : 00000000`00000116 fffffa80`0923f4e0 fffff880`04f1a9e0 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02de49d0 fffff880`0674dd87 : fffff880`04f1a9e0 fffffa80`0923f4e0 fffffa80`085aad50 fffffa80`090f8010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`02de4a10 fffff880`04f77f07 : fffffa80`0923f4e0 00000000`00000000 fffffa80`085aad50 fffffa80`090f8010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
    fffff880`02de4a40 fffff880`04fa1b75 : 00000000`ffffffff 00000000`0027d464 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`02de4b20 fffff880`04fa02bb : 00000000`00000102 00000000`00000001 00000000`0027d464 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`02de4b50 fffff880`04f732c6 : ffffffff`ff676980 fffffa80`090f8010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`02de4bf0 fffff880`04f9fe7a : 00000000`00000000 fffffa80`0addb290 00000000`00000080 fffffa80`090f8010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`02de4d00 fffff800`0332bf7a : 00000000`fffffc32 fffffa80`085a6b60 fffffa80`054ee740 fffffa80`085a6b60 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`02de4d40 fffff800`030829c6 : fffff800`03206e80 fffffa80`085a6b60 fffff800`03214cc0 fffff880`01623a20 : nt!PspSystemThreadStartup+0x5a
    fffff880`02de4d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+79e0
    fffff880`04f1a9e0 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  atikmpag+79e0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f3b14b8
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    Followup: MachineOwner
    

    Another crashlog:

    Code:
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800ae74390, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004f1a9e0, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000d, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    atikmpag+79e0
    fffff880`04f1a9e0 4883ec28        sub     rsp,28h
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`02de79c8 fffff880`06757000 : 00000000`00000116 fffffa80`0ae74390 fffff880`04f1a9e0 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02de79d0 fffff880`06756d87 : fffff880`04f1a9e0 fffffa80`0ae74390 fffffa80`09056d50 fffffa80`09028010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`02de7a10 fffff880`04f77f07 : fffffa80`0ae74390 00000000`00000000 fffffa80`09056d50 fffffa80`09028010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
    fffff880`02de7a40 fffff880`04fa1b75 : 00000000`ffffffff 00000000`00313b28 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`02de7b20 fffff880`04fa02bb : 00000000`00000102 00000000`00000001 00000000`00313b28 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`02de7b50 fffff880`04f732c6 : ffffffff`ff676980 fffffa80`09028010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`02de7bf0 fffff880`04f9fe7a : 00000000`00000000 fffffa80`09c87d50 00000000`00000080 fffffa80`09028010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`02de7d00 fffff800`0337cf7a : 00000000`fffffc32 fffffa80`08caeb60 fffffa80`054ee740 fffffa80`08caeb60 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`02de7d40 fffff800`030d39c6 : fffff880`03688180 fffffa80`08caeb60 fffff880`036930c0 fffff880`0161da20 : nt!PspSystemThreadStartup+0x5a
    fffff880`02de7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+79e0
    fffff880`04f1a9e0 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  atikmpag+79e0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f3b14b8
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    Followup: MachineOwner
    ---------
    
     
  7. Crogge

    Crogge Notebook Consultant

    Reputations:
    3
    Messages:
    166
    Likes Received:
    3
    Trophy Points:
    31
    I had again two bluescreens and changed 3 days ago the driver back to version 11.10 which I used for months. So far not a single bluescreen or any other issues, it seems to be seriously a AMD driver issue related with the 5870 mobility.
     
  8. mite_jan

    mite_jan Notebook Deity

    Reputations:
    147
    Messages:
    1,105
    Likes Received:
    4
    Trophy Points:
    56
    which driver doesn't have stutter on Lord of the rings war in the north
    god damnit i am waiting a patch or driver update half a year for this ...
     
  9. KuroLionheart

    KuroLionheart Notebook Deity

    Reputations:
    147
    Messages:
    727
    Likes Received:
    2
    Trophy Points:
    31
    I've been on 11.8 for ages. Haven't yet felt a need to upgrade.
     
  10. apachehavok

    apachehavok Notebook Evangelist

    Reputations:
    22
    Messages:
    419
    Likes Received:
    3
    Trophy Points:
    31
    12.3 here. Working for a week now. Just played bf3 and l4d last night for 4 hours with zero issues.
     
  11. JehutyZeroshift

    JehutyZeroshift Notebook Evangelist

    Reputations:
    51
    Messages:
    393
    Likes Received:
    1
    Trophy Points:
    31
    12.3 on me too and got no problems either while playing Starcraft 2, Diablo 3 Beta and CoD:MW3. Maybe reinstalling the hard way (w/ Driver Sweeper and CCleaner) before restart and then on safemode might fix your issue.
     
  12. megaX05

    megaX05 Notebook Consultant

    Reputations:
    41
    Messages:
    205
    Likes Received:
    0
    Trophy Points:
    30
    11.8 works like charm for me.
     
  13. Crogge

    Crogge Notebook Consultant

    Reputations:
    3
    Messages:
    166
    Likes Received:
    3
    Trophy Points:
    31
    I cleaned of course everything before I used 12.3 but I had no chance to use it, all the time bluescreens. 2 weeks have passed since I use 11.10 again and I didn't had a single bluescreen or anything else even if the NB is 24/7 running!