Overclock.net banner
1 - 20 of 28 Posts

Premium Member
7,127 Posts
Discussion Starter · #1 ·
If you know other fixes please post and share your experince to help other users (no rant).


  • Perform clean install.
  • Fix missing files.
  • To manually copy and paste the missing files.
  • Fix Official Catalyst 12.2 AODdriver4.01 error.
  • Eyefinity Screen Tearing.
  • Screen Tearing/Flickering 120Hz Monitor.
  • Eyefinity Questions.
  • Misc.
  • AMD CrossFireX Mode for 3D Applications.
  • AMD Catalyst Release Notes
  • Crossfire Compatibility Chart.
  • How to force DVI and HDMI Res and Refresh Rate - Win 7
  • AMD ZeroCore Power State. Here post #22
  • How To Center the Taskbar Icons in Win 7 post #23

To perform clean install, do it in this order (single card user skip #6):

  1. Uninstall Afterburner/Trixx/Asus Tweak and Catalyst through Catalyst Manager.
  2. Clean it with Atiman Uninstaller v.6.3.1 (turn off UAC to install this).
  3. Install Official Catalyst RC11 - 7900 users. For 6000 users - Catalyst prior to official 12.2. http://support.amd.com/us/kbarticles/Pages/RC11Driver.aspx or http://sites.amd.com/us/game/downloads/Pages/radeon_win7-64.aspx
  4. Install CAP1 12.2 http://sites.amd.com/us/game/downloads/Pages/radeon_win7-64.aspx
  5. Install Afterburner 2.2.0

  6. To turn off ULPS;

    1. Go to regedit (start > search programs and files > "regedit").
    2. In drop down menu: find file > type "enableulps".
    3. For ALL instances (keep pressing F3) change the "1" value to a "0".
    4. Reboot PC
  7. Enable "unoffcial overclocking" HOW TO: Enable UNOFFICIAL overclocking mode in MSI AfterBurner
  8. Afterburner settings > enable all voltage controls.
  9. Delete these folders after step #1 above is optional.
    • C:\user\Program files\ ATI & AMD.
    • C:\user\Program files (x86)\ ATI & AMD.
    • C:\ProgramData\ATI & AMD (need to show hidden files).

Fix missing files - Overclocking with Afterburner & Trixx after Catalyst RC11 (7900) and Official 12.1:

  1. Uninstall the driver through catalyst manager.
  2. Clean it with Atiman Uninstaller v.6.3.1
  3. Install RC11 http://support.amd.com/us/kbarticles/Pages/RC11Driver.aspx Or Official 12.1 or 11.x or whatever version that works for 6000 users.
  4. Upgrade (overwite RC11-7900 users) with 12.2/12.3 Pre-Cert. Do not perform clean install because we need the missing files from RC11 or Official 12.1 (6000 users).
  5. For Crossfire user; Catalyst 12.2 CAP1 http://sites.amd.com/us/game/downloads/Pages/crossfirex-app-profiles.aspx
  6. Reinstall Afterburner, disable ULPS (Crossfire user only) and enable unoffcial overclocking.
  7. Delete these folders after step #1 above is optional.
    • C:\user\Program files\ ATI & AMD.
    • C:\user\Program files (x86)\ ATI & AMD.
    • C:\ProgramData\ATI & AMD (need to show hidden files).

AMD_Catalyst_MSIAB_patch.zip 535k .zip file

To manually copy and paste the missing files (too lazy to write my own, but this is good):

[GUIDE] Fixing video playback & overclocking problems. - Guru3D ... (k1net1cs)


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 .dll files on driver sets after 12.1 WHQL.

And the video problems I meant are :

  • My OS is Windows 7 Home Premium 64-bit, and I use Mobility drivers (except with non-WHQL drivers).
  • Black/blank screen on any video; DXVA or not.

Another note is that this guide is intending to help you create a more 'integrated' solution so that you can fix things before driver installation.
In other words, a do-it-yourself guide to create a slightly customized driver set in order to fix said problems.

With that covered, now let's begin 'hacking' the driver set.

Before we start

First, you need to know which previous driver set was working fine on video playback.
On my laptop, it was 11.12 WHQL, so that's what I'm going to use as an example.

Then download the driver sets that you'll need.
In my case, I downloaded 11.12 WHQL to fix video playback, 12.1 WHQL to fix overclocking problem, and 12.2 Pre-certified as the driver set to be fixed.
The driver set you want to fix could be anything, even the unofficial 8.960 set.

Next is to run the installer for each driver set, but click Cancel after it's done extracting the installation files.
As for unofficial driver sets, you can just extract it to any directory.

Fixing video problems

Locate these 8 files :

Green/static with mostly green on Flash videos.








In my case (Mobility 11.12 WHQL, Win7 64-bit), they're in :
C:\ATI\Support\11-12_mobility_vista_win7_64_dd_ccc_ocl\Packages\Driv ers\Display\W76A_INF\B128376

Copy them over to the installation directory of the driver set you want to fix.
Since I'm using 12.2 Pre-certified, I copied mine to :
C:\AMD\12-2_pre-certified_vista_win7_64_dd_ccc\Packages\Drivers\Di splay\W76A_INF\B133359

And yes, you obviously have to overwrite (replace) the files.

Fixing overclocking problem

This one requires copying two files and a little editing of an .inf file.

First, locate these 2 files :

  • atiumd64.dl_
  • atipdl64.dl_

You can use the files from 11.12 WHQL or 12.1 WHQL.
It doesn't really matter as long as it's 12.1 WHQL or older.
If you're using the ones form 11.12 WHQL, it's inside the same directory as the 8 files listed above.

If you're using 12.1 WHQL, by default it's in :
C:\AMD\Support\12-1_mobility_vista_win7_64_dd_ccc\Packages\Drivers\D isplay\W76A_INF\B129753

Now copy those two files also to C:\AMD\12-2_pre-certified_vista_win7_64_dd_ccc\Packages\Drivers\Di splay\W76A_INF\B133359 directory.

Next is editing the .inf file.
Depending on your OS, the .inf file might be different.
But in general, Win7's .inf is C7******.inf, and Vista is CH******.inf.

Since I intend on fixing 12.2 Pre-certified, I'm editing the C7133662.inf file.

Now open up your preferred text editor, and find [r300.Display].
Put a new line under it, and type : atipdl64.dll,,,0x00004000

Next, find [r300.DispWow].
Put a new line under it, and type : atipdlxx.dll,,,0x00004000

Lastly, find [SourceDisksFiles].
Put a new line under it, and type : atipdl64.dll=1
Put another new line, and type : atipdlxx.dll=1

In case you're wondering, yes, you can just copy & paste the colored text. =b
And, of course, save the changes you've made.

And then...

...that's it.
Just run the Setup.exe and see whether it blows your system up or not. =b

Since you replaced some files, I'm pretty sure you'd be warned by Windows about installing unsigned driver files.
This is fine, since the warning pops out just because Windows fails to verify the copied-over files against the security catalog for the driver set you're fixing.

If you have problems upon restart, though, just disable driver signature enforcement (Edit - Ken: Turn Off UAC).

Fix Official Catalyst 12.2 AODdriver4.01 error:

  1. Device manager > show hidden > uninstall AODdriver4.01, do not restart PC.
  2. Type "regedit" in search button > select regedit.exe
  3. Regedit > HKEY LOCAL MACHINE/SYSTEM/Controlset001/services > delete the AODdriver4.01 folder entry.
  4. Regedit > HKEY LOCAL MACHINE/SYSTEM/Controlset002/services > delete the AODdriver4.01 folder entry.
  5. Reboot PC then go back to #3 and #4 above to make sure all the AODdriver4.01 folder entry was gone. If not, delete it.

Eyefinity Screen Tearing: post #21

Screen Tearing/Flickering 120Hz Monitor:

Raise the 2D memory clocks

[Updated]AMD/ATi 2D Clock Guide - techPowerUp! Forums (erocker)

5770 tearing when adding second monitor

7970 Screentearing?

Serious screen tearing(?) issue

Premium Member
7,127 Posts
Discussion Starter · #2 ·
Eyefinity Questions:

I can't get my second monitor higher than 640x480 resolution

DisplayPort flicker on monitors

Stupid Eyefinity question from a noob

BenQ XL2410T Eyefinity with 6970

7970 EyeFinity?

Is there such thing as "stable" eyefinity experience?! Please let me know!

single or crossfire card recommendation - 3 different size displays with no screen sharing

Help! Eyefinity on one 7970! (BIG IMAGES BECAUSE I'M LAZY)

Eyefinity Question

Eyefinity Disconnecting

Problems with 4th monitor on 7970?

Eye-Finity Questions/Concerns

Eyefinity issues?

Eyefinity Trouble...Need Some Help

Triple Monitor Eyefinity Guidance Needed

ATI Radeon HD 5870 Eyefinity 6 Edition

going for eyefinity. what else do I need?

Weird Eyefinity stuttering issues. Please help!

Some questions concerning Eyefinity with 5850 Crossfire

Need Help With Eyefinity +1 Setup?

HD 6900 Series 2x DVI 1x HDMI

Help--I broke my Eyefinity

Dual monitors.. I don't want to extend..

Running a single 7970 3d over HDMI!

Want to see if this will work crossfire and eyefinity...

Eyefinity Dongle

4 monitors..help?

Help with Eyefinity/Adapters.

Need second opinions on DVI-HDMI cable for eyefinity

quadfire 6970

Thinking of going Eyefinity...

Screen Tearing on Desktop??

5870...how to connect two monitors?

Maximum monitor count per card?

Double Checking -- Triple Monitor with 5770


CCC Profiles/Presets

Crossfiring between different card of the same series

Crossfire of different VRAM

Crossfiring on PCI-E (x16, x4)

X16, x4 vs. x16, x16

Sapphire HD6970 overclocking - need help

How To: Run PhysX in Windows 7 with ATi Cards

Physx card with 6950 unlocked and ocd

Dedicated 9800gtx+ physx card showing 0% Gpu usage??

Hybrid Physx Not Enabled

Please help - Blue Screens :( remove ghost device)

Driver Installer Keeps crashing

<Solved>Unlocked Overclocking in MSI Afterburner not working on xfx 7970

How to overclock ScanFX HD 6990 and XFX HD 6970 in trifire?

CCC telling me I have an "XGP Module"???

How To: Unbrick Your Bricked Graphics Card/Fix a Failed BIOS Flash

Need Original BIOS - ASUS EAH6950 DCII/2DI4S/2GD5 & ASUS EAH6970 DCII/2DI4S/2GD5

Using RBE to flash card question

AMD Radeon 6990 Club

Crossfire 6950 - 2nd card not detected after BSOD/reboot

[CF]HD 6950 2GB weird freezes while gaming

[Solved] MSI afterburner crashes

BSOD in repeat cycles (all help welcome!)

Flashing a 7950 to 7970 without shader gain?

MSI R7770 Adding voltage in AfterBurner

My 7970 overclock keeps jumping back to stock! Help :(

MSI R5850 Twin Frozr II Problem

AMD 5870, won't work with any drivers installed (works only in VGA mode)

120hz not working on benq xl2420t at 1080p?

AMD vision center giving me no GPU options

Crossfire Issues

Voltage change not applying?

AMD 6990m crossfire

Help! Driver issues.

Issues with crossfire 5770's Drivers or Hardware to blame?

Windows 7 Icon flicker / refresh on log on

Crossfire 6870s memory underclocking

will quad channel memory work on x58? and triple channel work on x79?

Crossfire/driver issues with my 7970s

Is it possible to fold with my 275 while using a 6950 as my main GPU?

Afterburner not applying voltages

HD6990 Overclocking.

CAP profiles not showing

6870 - Simultaneous HDMI and DVI Not Working

need trouble shooting help with running 2 monitors

MSI AB precautions when changing gpu driver?

Did I do something incorrectly?

Sapphire 5870 Green pixel issue - flash BIOS? [FIXED]

[Solved] Accelero TWIN TURBO II & 6970

[SOLVED] Bootable USB for Flashing

[Solved] 7970 CF Blank screen???

Best way to install new drivers?

6870 Crossfire?

CFX trouble, out of ideas ... can someone help please!!

Question regarding Overscan

Problems started after watercooling!

*OFFICIAL* AMD Radeon HD 7950/7970 Owners Club

Flickering at desktop with Tri-Fire 7970 setup

Have I ruined my 6950? Pics inside! SOLVED

Unlock and OC that 6950 TF3/ Twin Frozr III- the definitive guide!

Dying PSU or something else?

Is it possible to specify "GPU affinity?"

another of the same MSI Afterburner questions

6750M overclocking in dual graphics configuration

Trust Furmark temps or GPUz temps more....

5870 crossfire question

Faulty 5870? Crashing for certain Valve/Steam games only.

How to distribute load on Enermax Maxrevo 1500w?

Sapphire 6950 2GB /w unlocked Shaders, keeps resetting overclock while idling?

Overclokcing HD 6990 under Water

OC tips on Watercooled 6990

Which 6950 can be flashed to 6970?

Sapphire 6950 2GB /w unlocked Shaders, keeps resetting overclock while idling?

6950 Video Driver stops responding and has recovered. Help please

AMD Radeon 6990 Club

6970 Lightning Immediate Crash under OC ~ Furmark

[SOLVED] 570 GTX SLI will not start

Windows Media Player 12 library problem

S.L..O...W PCIE bus with single GPU, 6970/7970 in any slot, why??

7970 cf witcher 2 ubersampling problem

CCC doesn't start, can't enable crossfire. None of the ususal fixes work.

Help! Unlock Afterburner ... already tried ini file and MSIAfterburner.exe /xcl

CCC Profiles/Presets

AMD CrossFireX Mode for 3D Applications.

Starting Catalyst 12.1, AMD incorporated user settings similar to RadeonPro. It's self-explanatory.

Under the drop down list:

  1. Disabled. This option turns off CrossFireX multi-GPU acceleration.
  2. Default uses whatever the global system default option is, or whatever AMD has configured, if the game already has a profile in the CAP package.
  3. AFR Friendly, which is for games which generally work well with Alternate Frame Rendering (AFR).
  4. Optimize 1x1. This is another AFR option, but with optimizations for 1x1 surfaces. The idea is, if AFR Friendly has problems, Optimize 1x1 is another option to try.
  5. Use AMD Pre-Defined Profile allows us to select the CrossFireX configuration of another game and apply it to the one for which we are making a profile.

(For more details and example: HARDOCP - Introduction - AMD Catalyst 12.1 Preview Profiles and ... )

AMD Catalyst Release Notes

The AMD Catalyst Control Center / AMD Vision Engine Control Center requires that the Microsoft .NET Framework SP1 be installed for Windows XP and Windows Vista. Without .NET SP1 installed, the AMD Catalyst Control Center / AMD Vision Engine Control Center will not launch properly and the user will see an error message.


  • When installing the AMD Catalyst driver for Windows operating system, the user must be logged on as Administrator or have Administrator rights to complete the installation of the AMD Catalyst driver.

  • The Catalyst driver requires Windows 7 Service Pack 1 to be installed.

Crossfire Compatibility Chart


How to force DVI and HDMI Res and Refresh Rate - Win 7

All you need to know is in the zip file below. I have tested and it worked. Do at your own risk - read thoroughly before damaging your monitor.

How to update EDID using INF.zip 1,109k .zip file

How to Use an INF to Override the Monitor EDID

November 5, 2008


All display devices (monitors, projectors, and televisions), analog or digital, must supply Extended Display Identification Data (EDID), which is stored in the monitor's EEPROM. Sometimes during manufacturing, incorrect or incomplete EDID might be flashed on the EEPROM. Such EDIDs can lead to problems such as setting incorrect display modes. This white paper describes how monitor manufacturers can avoid reflashing the monitor's EEPROM by implementing a monitor INF that overrides part of, or the entire, EDID information in software. This paper describes how to implement such an INF.

This information applies for the following operating systems:
Windows® 7
Windows Server® 2008
Windows Vista®

References and resources discussed here are listed at the end of this paper.

For the latest information, see:

Disclaimer: This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein.

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.


Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.

© 2008 Microsoft Corporation. All rights reserved.

Microsoft, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Document History



November 5, 2008

First publication


Introduction. 3

How to Update an EDID by Using an INF. 3

EDID Format 4

How to Override EDID Information in an INF. 4

Implementation Requirements and Guidelines. 5

Windows Logo Program EDID Requirements. 7

Call to Action. 8

Resources. 8


All monitors, analog or digital, must support Extended Display Identification Data (EDID), which contains information such as the monitor identifier, manufacturer data, hardware identifier, timing information, and so on. This data is stored in the monitor's EEPROM in a format that is specified by the Video Electronics Standards Association (VESA).

Monitors provide the EDID to Windows® components, display drivers, and some user-mode applications. For example, during initialization the monitor driver queries the WDDM driver for brightness query interface and device driver interface (DDI) support, which is in the EDID. Incorrect or invalid EDID information on the monitor's EEPROM can therefore lead to problems such as setting incorrect display modes.

There are two approaches to correcting EDIDs:

· The standard solution is to have the customer send the monitor back to the manufacturer, who reflashes the EEPROM with the correct EDID and returns the monitor to the customer.

· A better solution is for the manufacturer to implement an INF file that contains the correct EDID information and download it to the customer's computer. Windows extracts the updated EDID information from the INF and provides it to components instead of the information from the EEPROM EDID, effectively overriding the EEPROM EDID.

This paper describes how to implement an INF to override a monitor's EDID and briefly discusses the related Windows logo requirements.

In addition to replacing the EDID information as described in this white paper, a vendor can provide an override for the monitor name and the preferred display resolution. Such an override is frequently made available to end users through Windows Update or digital media in the shipped box. Such an override receives higher precedence than the EDID override mentioned in this paper. Guidelines for achieving this can be found in "Monitor INF File Sections" in the Windows Driver Kit (WDK).

How to Update an EDID by Using an INF

To update an EDID by using an INF:

1. The monitor manufacturer implements an INF that contains the updated EDID information and downloads the file to the user's computer. This can be done through Windows Update or by shipping a CD with the monitor.

2. The monitor class installer extracts the updated EDID information from the INF and stores the information as values under the following registry key:


Each EDID override is stored under a separate key, for example:

\Device Parameters\EDID_Override

3. The monitor driver checks the registry during initialization and uses any EDID information that is stored there instead of the corresponding information on EEPROM.

EDID information that has been added to the registry always takes precedence over EEPROM EDID.

4. Windows components and user-mode applications use the updated EDID information.

EDID Format

EDID data is formatted as one or more 128-byte blocks:

· EDID version 1.0 through 1.2 consists of a single block of data, per the VESA specification.

· With EDID version 1.3 or enhanced EDID (E-EDID), manufacturers can specify one or more extension blocks in addition to the primary block.

Each block is numbered, starting with 0 for the initial block. To update EDID information, the manufacturer's INF specifies the number of the block to be updated and provides 128 bytes of EDID data to replace the original block. The monitor driver obtains the updated data for the corrected blocks from the registry and uses the EEPROM data for the remaining blocks.

How to Override EDID Information in an INF

To override an EDID, include an AddReg directive in the INF for each block that you want to override, in the following format:

HKR, EDID_OVERRIDE, BlockNumber, Byte 1, Byte 2, Byte 3, Byte 4,...

The block number is followed by 128 hexadecimal integers that contain the binary EDID data.

Manufacturers must update only those EDID blocks that are incorrect. The system obtains the remaining blocks from EEPROM. The following example shows the relevant sections of an INF that updates EDID blocks 0, 4, and 5. The monitor driver obtains blocks 1 - 3 and any extension blocks that follow block 5 from EEPROM:





HKR, EDID_OVERRIDE, 0, 1, 00, FF, ..., 3B

HKR, EDID_OVERRIDE, 4, 1, 1F, 3E, ..., 4E

HKR, EDID_OVERRIDE, 5, 1, 24, 5C, ..., 2D


For more information on INFs in general and AddReg and DDInstall in particular, see "Creating an INF File" in the WDK.

Implementation Requirements and Guidelines

The following example shows a complete generic INF file for overriding monitor EDID information for Windows Vista® and later versions. The example is an edited version of a WDK sample-monsamp.inf-which is located at WinDDK\BuildNumber\src\video\monitors\inf\monsamp.inf. For an explanation of the numbered comments, see the notes after the following example:


signature="$WINDOWS NT$"























AddReg=MS_EDID_OVERRIDE-1.AddReg, 1024, 1280, DPMS




AddReg=MS_EDID_OVERRIDE-1.AddReg, 1024, 1280, DPMS





























SourceDisksNames="MS_EDID_OVERRIDE Monitor EDID Override Installation Disk"




1. Released versions of this INF should be accompanied by a signed catalog (.cat) file. To do this, remove the comment character from the following directive and change Sample.cat to the name of your signed catalog file.

2. To copy a monitor profile, remove the comment from the following directive. You must also add a corresponding CopyFiles section, as discussed in note 6.

3. Change the hardware ID from MON1234 to that of the monitor that is associated with this INF.

4. Replace the following example EDID directive with one or more EDID directives that contain the corrected information for each block that you want to override.

5. Use the following AddReg directives to define default settings for standard resolutions.

6. To copy a monitor profile, remove the comment character from the following directive.

Windows Logo Program EDID Requirements

The Windows Logo Program requires display devices to provide a well-formed EDID. The specific requirement is Display-0065. The following list summarizes the requirements at the time this paper was published. You should check the latest version of the Windows logo specification for the current requirements.

Display - 0065: Display device implements the EDID data structure

Effective Date: 01-Jun-2006
Expiration Date: None
Status: Approved
Required for:
Basic: Yes
Premium: Yes

The monitor must transmit an EDID that contains:

· A unique manufacturer ID.

· A unique manufacturer name.

· A unique product code ID.

· All the required fields as defined by the VESA Enhanced Extended Display Identification Data Standard specification, Release A, Section 3.

· For analog CRTs, the EDID must indicate at least one VESA mode at 75 Hz or higher for each supported resolution.

All monitors must support E-EDID by implementing an EDID 1.3 or later data structure that sets the preferred -mode bit for all monitor types. The EDID must:

· Include timing data for the preferred display mode in Timing #1:

· For an LCD or other fixed-format display, the preferred display mode is the panel's native mode.

· For other display types, the preferred display mode is the optimal display mode. It must be based on the size and capabilities of the device and meet the requirements for refresh rates that were defined earlier in this paper.

· Implement monitor descriptors.

The descriptors must include the monitor name and-for continuous frequency monitors-the monitor range limits. If the monitor does not support continuous frequencies, monitor range limits should not be exposed.

All-in-one systems-including mobile systems-must provide an EDID in one of the following ways:

· The LCD panel provides the EDID, much like an externally attached monitor.

· If the LCD panel does not provide an EDID, the WDDM miniport driver provides the EDID by using one of the following approaches:

· The WDDM miniport driver defines the EDID itself.

· The WDDM miniport driver retrieves the EDID from the system BIOS by executing the ACPI _DDC method on the child device that is associated with the internal panel.

Design and Implementation Note: The ACPI specification defines the method that is used to obtain the EDID from the BIOS so that it has functionality the same as that specified in ACPI 2.0b, Appendix B, or later.

No hardware requirements specifically are related to overriding EEPROM EDIDs, so supplying an EDID override in the monitor INF is completely optional. In particular, including EDID information in the monitor INF is not necessary if the monitor's EEPROM provides the correct information.

Call to Action

Monitor manufacturers:

If your display devices contain incorrect EDID data in the EEPROM, supply the correct information in your monitor INF. This approach significantly reduces support costs compared to shipping display devices back to the factory to reflash the EEPROM.

Note: Monitor manufacturers must update the monitor INFs through Windows Update.

Graphics hardware vendors:

Design your Windows Display Driver Model (WDDM) drivers to take advantage of EDID overrides.

System builders:

Build systems that work with many different display devices and switchboxes.


If you have additional questions that are not addressed by this document, send e‑mail to [email protected]. The following links provide further information on EDIDs and related topics.

Windows Driver Kit

Monitor INF File Sections


Creating an INF File


WHDC Web site

Display and Graphics - Architecture and Driver Support Resources


Windows Logo Program Requirements Suite, Version 3.0


Video Electronics Standards Association (VESA)


VESA Standards Summaries


There are too many threads that I have come across with fixes to list them all (more than 1,000 threads). If you can't find the answer, post it here.

Premium Member
7,127 Posts
Discussion Starter · #9 ·
Originally Posted by nugget toes View Post

this deserves a +rep

I'll have to try it later tonight, hopefully remedies my twin frozr 7950 because it has been awfully buggy.
Did you fix it?


Originally Posted by Griffin View Post

This thread is a great idea
Yeah, 90% of the threads with issues got it fixed with clean drivers install. Over 6,000 of my posts in graphics section are related to drivers to realize I keep repeating myself with the same solution over and over again.

So decided to put it here in one thread.

729 Posts
Amazing amount of effort gone into this Ken, thank you.

1 Posts
just created an account here to thank you for the Vaio VPCEA(390X for me) mobility 5650 fix.

Catalyst 12.2 (official) seems to bring slightly better performance in BF3 for me (compared to 11.12 and 12.1) and I'm happy I can use it now without breaking video playback.

Seriously, thanks,
- Tyler

Premium Member
7,127 Posts
Discussion Starter · #14 ·
Originally Posted by Tiezep View Post

just created an account here to thank you for the Vaio VPCEA(390X for me) mobility 5650 fix.

Catalyst 12.2 (official) seems to bring slightly better performance in BF3 for me (compared to 11.12 and 12.1) and I'm happy I can use it now without breaking video playback.

Seriously, thanks,
- Tyler
Welcome to OCN.

Glad it fixed for you, the credit should go to k1net1cs for taking the time to write that part in details

Premium Member
7,127 Posts
Discussion Starter · #15 ·
Found this (malware?) here. If anyone can confirm it is malware, will update it in OP.

12.3 ccc.exe not starting up on windows startup and crashing having to restart or huge delay for ccc.exe

Originally Posted by Avian View Post

I tried this and it worked for me:

"I recently removed the Vista Recovery Center malware from another one of our company laptops. It has ATI graphics installed. This malware hides most of the files on the PC in an attempt to fool you into thinking that your PC is really damaged like it is reporting.

Removing the malware does not undo the hidden aspects. In Vista, the c:\Users\"your profile name (usually Owner)" folder contains the AppData subdirectory that the Catalyst Control Center needs to access in order to function. When this directory is hidden, then CCC cannot locate the necessary files to launch.

To fix this issue, I use the following steps.
Navigate to c:\ and right click on Users. Select properties. Under the General tab, look at the bottom for the Hidden selection. If there is not a check mark in the box, place a check mark there. Hit apply, select yes to apply to all subdirectories.

If you clicked ok, you may notice that it disappeared from the right pane once it finishes. It should still be listed under the tree on the left.

Right click on it again. This time remove the check mark and apply to all subdirectories. Once it has finished, your files in the Users directory should reappear and Catalyst Control Center should function normally again. This has worked in all cases that I have encounterd so far. Hopefully this works for you as well.."

85 Posts
I got weird problem with the 12.2 catalyst uninstall, everytime in the middle of the uninstall the colors go weird, like 1bit or something, really frustrating as you cannot see any buttons or text on the desktop, only blurr. After the uninstall it throws something about a file, dunno what the window really says, but defo a problem with a file. Well, just smashed enter and finally when all the windows went away I reboot to Safe Mode and clean all the leftovers, go back to normal mode and install drivers. But they dont seem to work correctly, I get some weird anomalies in games and winamp visualization doesnt even work, only black screen there. Something isnt right.. Any suggestions? This problem first started with 12.1 drivers and I have tried to uninstall them like 10 times now, everytime this happens.

Premium Member
7,127 Posts
Discussion Starter · #17 ·
1. Restore all the adjustment in Windows Display to Windows default.


2. If you have used Driver Sweeper to delete traces of AMD drivers, try to repair Windows then update the motherboard and chipset drivers. Run Windows Update and install ALL excepts AMD graphics drivers. Avoid Driver Sweeper especially you are on AMD platform (CPU). It might have deleted other than the graphics related drivers.

3. Your problem started with 12.1. Only 12.2 has some video playback compatibility and 2 files not included as in previous version. So the issue is not related to Catalyst.

4. If you have done #1 and #2 above, perform clean install or use the overwrite or manual copy missing files if you wish to install 12.2. Details in post #1.

5. If all the above didn't fix it, re-format and fresh OS reinstall. Update as necessary don't take any shortcut and last install Catalyst. If still has issue, check the crossfire setup (motherboard slot, the cards, bridge and PSU).

Premium Member
7,127 Posts
Discussion Starter · #19 ·
I don't know if this is related to your issue or not but I can re-produce the crash by the followings;

1. Windows Screen Resolution > Change refresh rate.

2. Overwite Catalyst Driver with latest 3/19/2012 http://support.amd.com/us/kbarticles/Pages/HD78007Support.aspx

3. Restart PC > open BF3 > instant crash.

4. Go back to Windows Screen Resolution > set the correct refresh rate > Restart PC > problem solved.

The only problem I could imagine why you crash with lastest Catalyst (#2 above) contains updated EDID for the monitors. You are on Eyefinity, might worth to look into the refresh rate for each monitors see if that will fix it.

Premium Member
3,865 Posts
Ok, they are all asus 24" 1080p 60hz. I'll look up the specs again.

EDIT: Ended up doing another fresh install of the new driver, setup eyefinity and this time the settings were a little different?? Launched BF3 and it's working. Going to test and see if the other games launch too.

Thanks man, not sure what was different this time, but it worked.
1 - 20 of 28 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.