Question about "Beta Drivers"

Discussion in 'Videocards - AMD Radeon Drivers Section' started by NeuroFunkeR, Jun 14, 2012.

  1. NeuroFunkeR

    NeuroFunkeR Member Guru

    Messages:
    125
    Likes Received:
    0
    GPU:
    Gigabyte NV WF3 670GTX
    Hello guys, i was just wondering, whats the point in beta drivers, and why everyone is so excited about them? Usually i see no changelog at all, only a screenshot of new driver version. So whats the point in installing them?
    I have no issues with WHQL drivers, and even if i had some, how can i know what have been changed in beta?
     
  2. bighead147

    bighead147 Active Member

    Messages:
    60
    Likes Received:
    0
    GPU:
    Ati 5650m 1GB
    Maybe better optimalization for games or other appliactions? New functions? And you dont need to wait for WHQL certificate so they are newer then official :) But they can have some problems like flickering or anything else.
     
  3. NeuroFunkeR

    NeuroFunkeR Member Guru

    Messages:
    125
    Likes Received:
    0
    GPU:
    Gigabyte NV WF3 670GTX
    you see? Maybe:) But why there is no changelog to see, what have been optimized, fixed, added etc?:nerd:
     
  4. Raiga

    Raiga Maha Guru

    Messages:
    1,099
    Likes Received:
    0
    GPU:
    GPU
    Beta drivers are mainly utilized to check up current ongoing implementation of either
    1. Fixes
    2. Performance bumps
    3. New Features

    All of the above, before finalizing what will be removed or added to the official drivers release.

    So there might be features or something which will not be available in the WHQL drivers immediately(or mostly never), so its the something to look out for every time these drivers are released. (edit: Leaked)

    Also each version of Beta will have different sets of unique elements in them. Changelogs mostly won't be available most of the time too.

    They also come with bugs, which the the company doesn't bother much..as its just a internal Beta (test ground drivers) they work(play) with. The installers might be broken sometimes, same with the uninstallers too (where it won't completely properly uninstall beta drivers).
     
    Last edited: Jun 14, 2012

  5. NeuroFunkeR

    NeuroFunkeR Member Guru

    Messages:
    125
    Likes Received:
    0
    GPU:
    Gigabyte NV WF3 670GTX
    ok, ty for quick replies guys, i think i've got it. I better keep my hands off betas and stick with WHQL drivers. :)
     
  6. perosmct

    perosmct Banned

    Messages:
    1,072
    Likes Received:
    0
    GPU:
    unknown
    you fail man, whqls have much more bugs than betas.....guaranteed opinion...:)
     
  7. Pilgrim1942

    Pilgrim1942 Master Guru

    Messages:
    200
    Likes Received:
    0
    GPU:
    GTX 470
    Couldn't agree more, perosmct. :)
     
  8. Raiga

    Raiga Maha Guru

    Messages:
    1,099
    Likes Received:
    0
    GPU:
    GPU
    Well 12.4 is still working good, ain't it?..for Single Card users :) like myself
     
  9. ipredator

    ipredator Master Guru

    Messages:
    542
    Likes Received:
    0
    GPU:
    Quadro K5000M
    Impressive, I'd have never thought we share the same opinion about something. :banana:
     
  10. The Goose

    The Goose Ancient Guru

    Messages:
    3,029
    Likes Received:
    354
    GPU:
    MSI Rtx3080 SuprimX
    what do you expect after microsoft have got involved
     

  11. The Goose

    The Goose Ancient Guru

    Messages:
    3,029
    Likes Received:
    354
    GPU:
    MSI Rtx3080 SuprimX
    i had to go back to the 12.4`s just so i could install 12.6beta over the top and get ccc working in the latest beta`s,all 12.6 have failed to install ccc for me but performance is good this way and tdu2 fps issues i had are gone,but in my opinion they should just release cap files instead....after all caps are just updates/fixes and thats what they`re trying to do with the betas
     
  12. NeuroFunkeR

    NeuroFunkeR Member Guru

    Messages:
    125
    Likes Received:
    0
    GPU:
    Gigabyte NV WF3 670GTX
    [​IMG]
     
  13. ipredator

    ipredator Master Guru

    Messages:
    542
    Likes Received:
    0
    GPU:
    Quadro K5000M
    Neuro he's dead serious.
    The last few WHQLs all had clock speed bugs, idle clock failures, came without the dll you need in SysWOW64 for overclocking cards, did not write its versioning info in the registry (12.4) and even broke CF for games like Bad Company 2.
     
  14. NeuroFunkeR

    NeuroFunkeR Member Guru

    Messages:
    125
    Likes Received:
    0
    GPU:
    Gigabyte NV WF3 670GTX
    ipredator ok, we assume ima gona believe him, and install that "beta driver", what if it's gona damage my card or causes system failure, who will guarantee me, i'm going to receive an replacement card from shop? AS far i know, if this will happen with an WHQL driver, at least there is a chance to become an replacement, but with beta, theres no guarantee for this.
     
  15. ipredator

    ipredator Master Guru

    Messages:
    542
    Likes Received:
    0
    GPU:
    Quadro K5000M
    Installing a video cards driver will NEVER cause system failure. At worst, you'll get a blue screen when you try to start windows. And this is easily fixed by booting into Safe Mode (no video drivers are loaded there, aka it is untouched by the bad driver install), and de-installing the video card('s) in the Device Manager. After another reboot the bluescreen is gone and you can install a working driver again.

    If it's gonna damage your card, you overclocked it too much and it's your fault, but that can happen with WHQL's too, and in neither cases you get a replacement. The beta drivers posted here are not so faulty as they would apply dangerous incorrect clocks to your card, at worst they mess the 2d and 3d clocks up, meaning you have 2d clocks in an 3d application or 3d clocks at idle. This won't burn your card instantly, it just means your card runs at 100% load for a couple of minutes. It's easily fixed by opening gpu-z and closing it again, or if this doesn't work simply install another driver.

    And by installing I hope you use a tool to delete old driver's registry entries and don't simply install the new driver over the old one, or rely on the AMD uninstaller app. It only deletes the files, not the reg entries, so there are leftovers. If the new driver does not overwrite them perfectly you're gonna have weird issues. Thats why tools like Driver Sweeper or ATIman uninstaller are mandatory imo.
     
    Last edited: Jun 14, 2012

  16. NeuroFunkeR

    NeuroFunkeR Member Guru

    Messages:
    125
    Likes Received:
    0
    GPU:
    Gigabyte NV WF3 670GTX
    ipredator yep, i know that with ATIman (heard about it not long ago) and driver sweeper, good old friend of every's man.
     

Share This Page