[GUIDE] Fixing video playback & overclocking problems.

Discussion in 'Videocards - AMD Radeon Catalyst Drivers Section' started by k1net1cs, Mar 7, 2012.

  1. k1net1cs

    k1net1cs Ancient Guru

    Messages:
    3,783
    Likes Received:
    0
    GPU:
    Radeon HD 5650m (550/800)
    [GUIDE] Fixing video playback & enabling unofficial OC. (5650m and possibly others)

    Now, before I start, here's what you should know first.
    • I based this guide on my laptop, a Sony VAIO VPCEA16FG, which has a Mobility Radeon HD 5650 clocked at 450/790.
    • Video playback problems may not appear on many other cards, even the same ones as mine but on a laptop from different manufacturer.
    • Overclocking problem is focused only on the inability to set clocks with Afterburner due to missing atipdlxx.dll file on driver sets after 12.1 WHQL.
    • The OS I'm using is Windows 7 Home Premium 64-bit, so while these steps might still be applicable on Vista or WinXP, it might not be for Windows 8; you're welcome to try, though.

    And the video problems I meant are :
    • Black/blank screen on any video; DXVA or not.
    • Green/static with mostly green on Flash videos.


    Fixing video problems

    First, download this.
    Use 7-Zip to extract it.
    (and yes, you can now throw that WinRAR trial/crack away since 7-Zip opens RAR files just fine)

    You should now have these 4 files:
    • atiumd6a.dll
    • atiumd6a.cap
    • atiumdva.dll
    • atiumdva.cap

    Now, you need to copy atiumd6a.dll and atiumd6a.cap to C:\Windows\System32\ directory.
    Next, copy atiumdva.dll and atiumdva.cap to C:\Windows\SysWOW64\ directory.

    If you are using 32-bit Windows 7, just copy over atiumdva.dll and atiumdva.cap to C:\Windows\System32\ directory.

    Why does it seem the file placement is inverted in 64-bit Windows 7, you ask?
    I don't know. =b
    And yes, you obviously have to overwrite (replace) the existing files.



    Enabling unofficial OC in Afterburner on 12.2/3 WHQL and newer

    First, you need to make sure Afterbuner isn't running.
    Close it, stop it, kill process it, whatever you need to do.
    Just don't uninstall it.

    Download this.
    Put it inside your Afterburner installation directory.
    e.g C:\Program Files (x86)\MSI Afterburner

    [alternative method]
    If you want to use an atipdlxx.dll file from a Catalyst set of your choosing, you can get the file from any version prior to 12.2/3 WHQL, like [THREAD=357787]12.2 Preview[/THREAD] and under.
    Just run the installer, let it extract the files, then cancel when the setup windows shows up.
    Navigate to the folder it extracted the files into, and copy the atipdlxx.dll to Afterburner's installation folder as indicated above.
    Now press Win+R to bring up the Run window, locate the MSIAfterburner.exe file, double-click it, but don't run it yet.
    Add "/XCL" after the double-quotes, separated with a space.

    So it'd be something like this:
    "C:\Program Files (x86)\MSI Afterburner\MSIAfterburner.exe" /XCL

    Now you can run it.
    If everything was done correctly, you should see a pop-up notification saying you have to restart your PC.
    After you've restarted your PC, you should be able to OC your GPU using Afterburner.

    I've tested this method on multiple Afterburner versions up to 2.3.1, which works fine, but I haven't tested 3.0.0 betas.
    If you can still enable unofficial OC in Afterburner on 12.2/3 WHQL and newer, chances are you have installed 2.2.3 and installed newer Afterburner versions without uninstalling the older version.
    Afterburner 2.2.3 had atipdlxx.dll included by default, but newer versions don't.

    The /XCL method also enables the 'Performance' tab on CCC, which is basically Overdrive.
    So, you can either set your OC with Afterbuner or via CCC.



    Closing notes

    If you have problems upon restart, disable driver signature enforcement by either pressing F8 on boot-up just like when you want to enter Safe Mode, or using ReadyDriverPlus for a more automated means.
    You can get RDP from here.
    This only applies to 64-bit Windows, since 32-bit Windows, IIRC, doesn't have such driver signature checks.
    RDP doesn't support Windows 8, so Windows 8 users have to do it manually.

    Adding from what xacid0 pointed out below, PowerPlay feature is most likely not going to work if you're using 8.960 unofficial sets from marthand.

    Thanks to leucos for rectifying which files are really needed for fixing video playback.
    And just in case it's needed for another bug hunting, I put the excluded files from the original file list here.

    • atiumd6v.dll
    • atiumdmv.dll
    • atiumdag.dll
    • atiumd64.dll

    As always, I'm open for correction.

    Well, HTH.
     
    Last edited: Feb 27, 2013
  2. xacid0

    xacid0 Master Guru

    Messages:
    438
    Likes Received:
    0
    GPU:
    Zotac GTX980Ti AMP! Omega
    Thanks for the guide, but my GPU lost PowerPlay function after i start overclock it. Anyway to get PowerPlay back? :(
     
  3. k1net1cs

    k1net1cs Ancient Guru

    Messages:
    3,783
    Likes Received:
    0
    GPU:
    Radeon HD 5650m (550/800)
    If you're using Afterburner, make sure that UnofficialOverclockingMode is set to 1, not 2.

    The driver set you're using as a base for customization may also be at fault.
    I found that marthand's 8.960 unofficial Beta didn't work well with PowerPlay, while with 12.2 Pre-certified (and probably the recent 12.2 WHQL too; I haven't tested it yet) it works just fine.
     
  4. xacid0

    xacid0 Master Guru

    Messages:
    438
    Likes Received:
    0
    GPU:
    Zotac GTX980Ti AMP! Omega
    I see, i'm using Leshcat's latest driver which is based on Marthand v8.960 Feb 28. Hopefully that is the problem.
     

  5. k1net1cs

    k1net1cs Ancient Guru

    Messages:
    3,783
    Likes Received:
    0
    GPU:
    Radeon HD 5650m (550/800)
    Might be the case, but try switching Enable low-level hardware access interface to kernel mode.
    If that doesn't work, try an older leshcat driver set then.
     
  6. xacid0

    xacid0 Master Guru

    Messages:
    438
    Likes Received:
    0
    GPU:
    Zotac GTX980Ti AMP! Omega
    I'd used that since day 1 :p and changing back to user-mode doesn't fix it.

    No biggie.. i'll just downclock the GPU when i'm not playing any game and wait for better driver. So far i'm satisfied with this driver performance. Thanks for the help. :)
     
  7. k1net1cs

    k1net1cs Ancient Guru

    Messages:
    3,783
    Likes Received:
    0
    GPU:
    Radeon HD 5650m (550/800)
    Well, tough luck. =b

    No probs. ;)
     
  8. PhazeDelta1

    PhazeDelta1 Moderator Staff Member

    Messages:
    15,614
    Likes Received:
    1
    GPU:
    EVGA 1080 FTW
    this thread deserves a bump. :thumbup:
     
  9. leucos

    leucos Member

    Messages:
    25
    Likes Received:
    0
    GPU:
    Radeon HD5650m 650/900
    Hello
    I have a Sony VAIO VPCEB3M1E (Core i3 370m and HD5650) and I've recently upgraded to Windows 8 Pro (upgrade with clean install).

    I also have the blackscreen video playback problem. After a bit of testing I've come to the conclusion that the driver fails to use EVR to render the video. EVR (enhanced video renderer) is used by WMP, WMC and Win8 Metro Apps. If I use MPC-HC with a different video renderer, like madVR or VMR9, the video plays even with DXVA enabled (specifically LAV Video Decoder set to use "DXVA native" as hardware decoder).

    I've followed your guide to "merge" Catalyst version 13.1 (9.012.0 WHQL) with version 11.12 (8.920 WHQL) and, after tests, found out that the files really required for the video playback are only four:

    • atiumd6a.ca_
    • atiumd6a.dl_
    • atiumdva.ca_
    • atiumdva.dl_
    This modification fixes playback in WMP, Flash and Win8 Metro Apss.


    Two more things I have to mention:

    • atiumd6v.dl_ and atiumdmv.dl_ are still a mystery.
    • I haven't tried any overclocking, but powerplay seems to work fine.
    That said, I'm still testing this modification and I'll post more if anything comes up (like a BSOD).
     
  10. k1net1cs

    k1net1cs Ancient Guru

    Messages:
    3,783
    Likes Received:
    0
    GPU:
    Radeon HD 5650m (550/800)
    Holy crap; I forgot I had made this guide. o_O


    Well, yes and no.

    Usually, EVR works fine if you disable MPC-HC's built-in DXVA decoder.
    Go to Options -> Internal Filters -> Transform Filters.
    Look for the ones with (DXVA), untick it, Apply.

    Then, I don't know since when but probably somewhere after 12.4 or 12.7, AMD managed to bork EVR, so even disabling MPC-HC's internal DXVA decoders didn't do jack sh!t because none of the decoded frames are being rendered.
    There were some sets that even managed to make WinSAT (the one that generate tests for your laptop's WEI score a.k.a. Windows Experience Index) crashed when it tried to run video decoding tests.

    For MPC-HC, better stick to at least LAV Filters & madVR, because madVR excels at scaling; high-res videos don't look jagged in smaller resolutions, and sharper.
    If you found some video files to be a bit stuttery (which usually is WMV9 materials), disable DXVA decoding in LAV decoder.
    Latest madVR has managed to fully utilize the GPU for its scaling processes, and for some reason LAV decoder is bottlenecked or unoptimized for decoding WMV9.


    Cool.
    Thanks for the feedback. :)
    I will amend the first post sometimes later; other people might have the same problem as yours.


    Please do, and thanks in advance.
     
    Last edited: Feb 13, 2013

  11. leucos

    leucos Member

    Messages:
    25
    Likes Received:
    0
    GPU:
    Radeon HD5650m 650/900
    After a week of testing the modified driver, I've got two bugchecks (BSOD) the first two days and then nothing more. The bugchecks are the same: 133 (0,281,280,0) DPC_WATCHDOG_VIOLATION, and means that something failed to activate/respond in the given time. After searching a bit I've found that it can be caused by two problems:

    • faulty RAM
    • bad or corrupted driver
    Now I haven't made any test like memtest or similar to test my RAM, but I haven't had any other possibly memory related problems (like corrupted files/download) before and when I was using Windows 7 I *never* got a BSOD, so I think it's safe to assume that it's the driver at fault.

    I humbly think it might be a Windows 8 problem, tough. 11.12 where a set of driver for Windows 7 only.

    Anyways here's the bugcheck analysis:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DPC_WATCHDOG_VIOLATION (133)
    The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
    or above.
    Arguments:
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    Page 10d3bb not present in the dump file. Type ".hh dbgerr004" for details
    
    DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x133
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  d
    
    TAG_NOT_DEFINED_c000000f:  FFFFF8032691EFB0
    
    LAST_CONTROL_TRANSFER:  from fffff80326bdc143 to fffff80326a83340
    
    STACK_TEXT:  
    fffff803`26918428 fffff803`26bdc143 : 00000000`00000133 00000000`00000000 00000000`00000281 00000000`00000280 : nt!KeBugCheckEx
    fffff803`26918430 fffff803`26aae011 : fffff880`02ecf180 fffff803`26cfe180 fffff803`269185e0 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13c4c
    fffff803`269184b0 fffff803`26aaee97 : ffffffff`ffd0dc08 fffff803`2719d502 fffff803`269185e0 fffff880`03c0e525 : nt!KeUpdateRunTime+0x51
    fffff803`269184e0 fffff803`27173eca : ffffffff`ffd0dc08 fffff803`2719d502 fffff803`269187b0 fffff803`26c8c000 : nt!KeUpdateTime+0x3f9
    fffff803`269186d0 fffff803`26a7c7ee : 00000049`265d1907 fffffa80`038f1b00 fffff803`2719d580 fffff803`26918880 : hal!HalpTimerClockInterrupt+0x86
    fffff803`26918700 fffff803`26aad542 : 00000015`00000050 fffff803`00000002 fffffa80`037d0090 fffffa80`096d8cd0 : nt!KiInterruptDispatchLBControl+0x1ce
    fffff803`26918890 fffff803`26aafa6b : fffff803`26cfe180 00000000`00000100 fffff803`26918c00 fffff880`009b0000 : nt!KiDeferredReadyThread+0xef2
    fffff803`269189a0 fffff803`26aaffd5 : fffffa80`08a991b0 00000000`0001ca1f 00000000`00140001 00000000`00000031 : nt!KiProcessExpiredTimerList+0x39b
    fffff803`26918ae0 fffff803`26aafe88 : fffff803`26cfe180 fffff803`26d00f80 00000000`00000005 00000000`00124819 : nt!KiExpireTimerTable+0xa9
    fffff803`26918b80 fffff803`26aaa2d6 : fffffa80`00000000 00001f80`00ff00ff 00000000`00000000 00000000`00000002 : nt!KiTimerExpiration+0xc8
    fffff803`26918c30 fffff803`26aae67a : fffff803`26cfe180 fffff803`26cfe180 00000000`00183de0 fffff803`26d58880 : nt!KiRetireDpcList+0x1f6
    fffff803`26918da0 00000000`00000000 : fffff803`26919000 fffff803`26913000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+13c4c
    fffff803`26bdc143 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+13c4c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50ab0e64
    
    BUCKET_ID_FUNC_OFFSET:  13c4c
    
    FAILURE_BUCKET_ID:  0x133_DPC_nt!_??_::FNODOBFM::_string_
    
    BUCKET_ID:  0x133_DPC_nt!_??_::FNODOBFM::_string_
    
    Followup: MachineOwner
    ---------
    
    What I was doing when the BSOD hit:

    1. I was playing freecell from Solitaire Collection Win8 App
    2. I right clicked a folder in file explorer
    After that the system froze for a second and then the BSOD appeared.
    One note both BSOD happened after the system has been shutdown once. Not sure if everyone knows that Windows 8 uses the "hybrid boot" which combines hibernation with logon/logoff (basically when you press shutdown, Windows logs you off and the hibernate; when the system restart Windows resumes from hibernation and let you logon).



    Unfortunately now I don't have the time to analyze deeply these crashes.

    I have to say that since these two first BSOD, I have never encountered other problems. I have played many videos with WMP and MPC (both using DXVA or not) without problems. Playback in Firefox+Flash is a bit jerky, but it has been always that way. I haven't played any intensive videogame, though.

    Sorry for the WOT.
     
  12. k1net1cs

    k1net1cs Ancient Guru

    Messages:
    3,783
    Likes Received:
    0
    GPU:
    Radeon HD 5650m (550/800)
    Most likely.

    Moreover, there were probably some function calls that were made to the "patched" .dll files and they didn't give back the proper values, or the functions simply doesn't exist in the old .dll files, thus making the binary that made the call waited for nothing.


    Yep.
    Though 'til this day I still can't figure out whether it's Firefox with its dodgy hardware acceleration on Gecko or the Flash plugin, or both.

    One thing I noticed from newer Flash plug-ins is that they no longer have its process encased in Firefox's plugin-container.exe process, but rather their own FlashPlayerPlugin_11_*_***_***.exe process.


    I also just tested replacing the files on the latest beta (13.2 Beta 6) and the previous ones.
    No BSOD nor crashes on games that I tested extensively (a.k.a. playing too much) like Hitman Absolution.
    Video playback works fine on any mode, except that in CCC the Quality options are limited to 'Enforce Smooth Video Playback' and 'Apply current video settings to Internet video'; Color options are normal.

    Also, it turns out that replacing atiumdag.dll and atiumd64.dll is a detriment in some cases.
    DXVA native mode with LAV video decoder will cause a kind of ghosting effect, something like a color layer of the video shifted quite a few pixels down.
    To 'fix' it you have to use copy-back mode, but that's rather making the point of using DXVA a bit moot, especially when madVR is also trying to make the most of it; better off not using DXVA at all and give all GPU resources to madVR.


    From the tests I've done, I've found one telltale sign to know whether the currently installed driver set will bork EVR or not without even playing a video file.
    If the picture of the girl with a bunch of flowers & fruits on Color settings in CCC won't show up, or just simply black, pretty much any video you're trying to play on WMP will be the same.


    Thanks for the follow-up!
     
    Last edited: Feb 20, 2013
  13. jaggu1989

    jaggu1989 Member

    Messages:
    33
    Likes Received:
    0
    GPU:
    AMD Radeon HD5650

    Hey Dude i have a request ......

    plz send me those 4 file from 11.12 whql driver ... my net is slow these days :( plz plz .. upload them to any media share site :) thanks in advance
     
  14. leucos

    leucos Member

    Messages:
    25
    Likes Received:
    0
    GPU:
    Radeon HD5650m 650/900
    IIRC the new process is tied to the sandbox system implemented some versions ago in Flash (that has also caused an infamous crash on exit problem that Mozilla fixed with ad-hoc update). Also I've read somewhere that Firefox uses an outdated type of plugin standard or something, that has several limitations and causes these stupid performance problems. Good thing that Flash will die and Firefox will get h264 acceleration (yes on desktop :)).
    This must be a problem with 13.2. In my CCC I have all the normal option (edge enhancement, denoise & co.). Probably AMD messed up with some registry keys, or with the CCC itself. A comparison of the *.inf files from version 13.1 and 13.2 should tell if there are any changes in the registry keys.
    According to this article on leshcat's site, both files are related to Direct3D DX09, so replacing them with older version will nullify all the d3d games related fixes and performance improvement.
    Curious, I've got the ghosting problem (which is, if I'm not mistaken a wrong chroma offset) when I was using a very old (a year ago) version of the LAV filter.
    Just to check, I use the latest version (9.7.5) of the K-lite codec pack, mega flavor which is highly configurable, if you know what to do. Among other this pack include:

    • a stripped down version of MPC-HC (without most of the internal filters) v1.6.6.6517,
    • LAV filters v0.55.2 & ffdshow (LAV preferred for videos and ffdshow preferred for audio),
    • madVR.
    Everything works fine when playing an MP4 file with LAV video decoder (tested DXVA copyback and native).
    The directshow graph is as follows: [Input file]>[LAV Splitter]>[LAV Video Decoder]>[madVR]
    The colorspace used is NV12.
    Small note: I always use DXVA copyback because I also need xy-vsfilter for styled subtitles.
    Yes, but I think It's faster to open up a video with WMP. The bulky CCC it's the first thing I disable after the reboot, I've even made a registry patch for that LOL. I like to keep my boot barebone.

    Whenever I find the time I'll surely test the 13.2 beta, hoping that AMD won't pull another stunt like the BSOD in the 12.11 beta IIRC. :)

    You will receive a PM shortly with the links. Just the time to upload them (at 30KB/s...).
     
    Last edited: Feb 20, 2013
  15. k1net1cs

    k1net1cs Ancient Guru

    Messages:
    3,783
    Likes Received:
    0
    GPU:
    Radeon HD 5650m (550/800)
    Some of the latest (Flash) 11.5 had it, but earlier revisions didn't.


    Well, YouTube already has WebM versions for all their h.264 encodes on YouTube's (still) experimental HTML5 version of the site, so it shouldn't matter much whether Firefox starts supporting h.264 or not.
    Other sites like Vimeo still uses Flash-based players too, so Flash'd still be needed regardless, at least for quite some time.

    But it's probably still going to the right direction with supporting h.264, regardless of how much Mozilla have to pay for licenses.


    I haven't actually tested 'patching' 13.1 WHQL files, so I wouldn't know.
    And I probably won't download it just to compare .inf files, but who knows. =b


    Well, the original list of files for replacement were simply based on their filenames; anything with 'atiumd' on it were included.
    I really had no prior knowledge of what each file does, only what I concluded from Windows' error reports on what made WinSAT crashed on media decoding tests; all of them had atiumdag.dll involved.


    I used 0.55.3.
    I always install & update each component individually.

    I basically use the same config for media playback: MPC-HC Lite, LAV Filters, madVR, and xy-VSFilter.
    I just don't use codec packs.


    Native can display styled (soft)subtitles just fine, at least on my setup.
    I always use it to play my anime fansubs and the subs are rendered perfectly fine with DXVA native.

    In MPC-HC, you just have to make sure 'Auto-load subtitles' is off on 'Playback' settings.
    In 'External Filters' I arranged them like this:
    • LAV Splitter
    • LAV Video Decoder
    • DirectVobSub (auto-loading version) <-- xy-VSFilter
    • LAV Audio Decoder
    I set all of their merits to 'Prefer', and that's it.


    I routinely open CCC for the first time after a reboot from a new driver installation, just to set (mainly disable) some things related to video quality.
    After that, I just use CCleaner to disable it on startup.
    I also disable the AMD External Events Utility service.


    As far as 5650m is concerned, I think it's doing fine with 13.2 betas.
    Seems like only newer cards are afflicted with crashes or BSODs, and even that seems rather sporadic from what I've read on AMD driver subforum.

    Unless it's Beta 5, that is.
    (which I, personally, didn't have a problem with)
     
    Last edited: Feb 21, 2013

  16. jaggu1989

    jaggu1989 Member

    Messages:
    33
    Likes Received:
    0
    GPU:
    AMD Radeon HD5650

    thanks dude :)
     
  17. Kyon

    Kyon New Member

    Messages:
    3
    Likes Received:
    0
    GPU:
    HD5470M 895/890Mhz
    Can you give me the links too?
     
  18. k1net1cs

    k1net1cs Ancient Guru

    Messages:
    3,783
    Likes Received:
    0
    GPU:
    Radeon HD 5650m (550/800)
    Last edited: Feb 22, 2013
  19. darxider

    darxider Member

    Messages:
    19
    Likes Received:
    0
    GPU:
    AMD Radeon HD 6630m
    k1net1cs, since you're here and answering questions: what Catalyst version are you using right now? have you modded it with your method? if so, are you able to overvolt your 5650m?
     
  20. k1net1cs

    k1net1cs Ancient Guru

    Messages:
    3,783
    Likes Received:
    0
    GPU:
    Radeon HD 5650m (550/800)
    Currently using 13.2 Beta 6, with the 4 files listed above being replaced with the ones from 11.11c.

    The OC fix above is not meant specifically to enable overvolt, but just to enable OC-ing with Afterburner.
    All sets after 12.1 does not include the atipdlxx.dll file that is required by Afterburner to enable unofficial overclocking (via running AB with the /XCL switch).

    I probably need to update the guide above since you don't really have to re-add the atipdlxx.dll file to the installation setup, but you can just put it on the folder where AB is installed.
    I also have stopped updating my AB so I've only used 2.2.3, which works just fine.
    Therefore, I can't guarantee whether putting atipdlxx.dll inside AB's folder would still enable unofficial OC with newer AB.

    Anyway, unless your laptop BIOS allows you to, overvolting on a laptop is next to impossible without flashing a custom BIOS.
    You also have to keep in mind that in most laptops CPU & GPU share the same heatsink.
    Even if you're able to overvolt your GPU, it'll most likely raise the CPU's temp indirectly and make your laptop throttling the CPU down, making the GPU OC rather moot.
    Some actually have more success in OC-ing the GPU by undervolting it.

    Oh, and no, I don't overvolt my GPU. =b
    I'm keeping it stock.
     

Share This Page