Issue with New Catalyst drivers? LoadLibrary failed with error126. Solution is here.
By
5th_Player,
Posted on: 2010-06-16 20:52 in ALL ACCESS Gameplay Technical Issues Bugs
Have you tried installing Driver Sweeper (a free program) then uninstalling the CCC and driver files, rebooting into Safe Mode and running Driver Sweeper to get rid of the residual files?
If the game spit out 20 dollar bills people would complain that they weren't sequentially numbered. If they were sequentially numbered people would complain that they weren't random enough.
Black Pebble is my new hero.
From a careful read, it looks to me like this isn't a problem solved by Driver Sweeper as it is mentioned there towards the end.
It is known that there are an infinite number of worlds, simply because there is an infinite amount of space for them to be in. However, not every one of them is inhabited. Therefore, there must be a finite number of inhabited worlds. Any finite number divided by infinity is as near to nothing as makes no odds, so the average population of all the planets in the Universe can be said to be zero. From this it follows that the population of the whole Universe is also zero, and that any people you may meet from time to time are merely the products of a deranged imagination.
I've seen people not use the recommended steps for running Driver Sweeper and there isn't enough information in the post to make it clear when or how the OP ran Driver Sweeper.
Also, I've not had this issue pop up going from 10.2 down to 10.1 for Issue 17 testing then to 10.4 and now to 10.5 so I'm curious what drivers the OP was using before upgrading, what OS they are using (including Service Packs if applicable), and video card.
There just isn't enough concrete information there to tell much of anything.
EDIT: If it were simply an issue with the 10.5 drivers we'd have had many more reports about it. I know that je_saist is likely running the 10.5 drivers, or at least did until the 10.6 drivers were available for testing and I know several other posts I've seen with CoH Helper reports have shown the 10.5 drivers in use. And this is the first post I've seen about this problem. It seems rather isolated but there really isn't enough concrete information there to go on.
If the game spit out 20 dollar bills people would complain that they weren't sequentially numbered. If they were sequentially numbered people would complain that they weren't random enough.
Black Pebble is my new hero.
In truth, I'd have to agree with you. The info isn't as solid as it could be. OTOH, even if done prefectly, the issue seems odd and perhaps rare enough that Driver Sweeper might not be capable of fixing it even under ideal conditions.
For myself, I run the 10.5s and have done since they got released and I expect I will move to 10.6 before long. And I use Driver Sweeper between evey upgrade. So far, I haven't seen this issue myself. But I suppose it is good there at least is a solution of some sort for those rare folk who do get hit with it.
But yes, more info and details would be useful.
It is known that there are an infinite number of worlds, simply because there is an infinite amount of space for them to be in. However, not every one of them is inhabited. Therefore, there must be a finite number of inhabited worlds. Any finite number divided by infinity is as near to nothing as makes no odds, so the average population of all the planets in the Universe can be said to be zero. From this it follows that the population of the whole Universe is also zero, and that any people you may meet from time to time are merely the products of a deranged imagination.
Quote:
Actually I'm running 10.1, 10.4, 10.5, and now 10.6 against CoH Ultra Mode. (and no, you don't want to know how long it takes me to go through the entire set)|
Originally Posted by Texas Justice
I've seen people not use the recommended steps for running Driver Sweeper and there isn't enough information in the post to make it clear when or how the OP ran Driver Sweeper.
Also, I've not had this issue pop up going from 10.2 down to 10.1 for Issue 17 testing then to 10.4 and now to 10.5 so I'm curious what drivers the OP was using before upgrading, what OS they are using (including Service Packs if applicable), and video card. There just isn't enough concrete information there to tell much of anything. EDIT: If it were simply an issue with the 10.5 drivers we'd have had many more reports about it. I know that je_saist is likely running the 10.5 drivers, or at least did until the 10.6 drivers were available for testing and I know several other posts I've seen with CoH Helper reports have shown the 10.5 drivers in use. And this is the first post I've seen about this problem. It seems rather isolated but there really isn't enough concrete information there to go on. |
I have not been able to duplicate this error on Live or Test with WinNT6 or WinNT5 against my own RadeonHD cards.
Quote:
That was sort of what I expected to hear. Had there been any problems with those drivers I was certain you'd have let us know either here on on the Test server forums if it was discovered on Test.
|
Originally Posted by je_saist
Actually I'm running 10.1, 10.4, 10.5, and now 10.6 against CoH Ultra Mode. (and no, you don't want to know how long it takes me to go through the entire set)
I have not been able to duplicate this error on Live or Test with WinNT6 or WinNT5 against my own RadeonHD cards. |
If the game spit out 20 dollar bills people would complain that they weren't sequentially numbered. If they were sequentially numbered people would complain that they weren't random enough.
Black Pebble is my new hero.
I'm running Vista 32-bit with latest service pack.
I'm using the 5850 Sapphire Overclocked.
I was using the Vista 32-bit 10.4 drivers before upgrading.
I was having errors in an outdated version of DirectX but tried the video card drivers first, since the 10.3 drivers were having problems stalling.
Since I've had the problem, sweeping and reinstalling ANY OTHER 10.xx doesn't fix the problem.
The only reports I've seen are issues on Vista 32-bit, so it may not be directly related to the drivers, all I know is what appears to FIX the problem, not what the problem is actually. The XP drivers do not have this problem, and I haven't seen any complaints from Windows 7 users.
This didn't occur until I installed 10.5. Apparently it has something to do with a messup with the OGL portion of the drivers. Since the OGL portion is updated less often by the drivers, it may not be included in the uninstall process or easy to find with driver sweeper.
This is why once it happens, I can't seem to get rid of it.
Now, it appears the issue is very rare, which is obvious by the lack of complaints on the net.
However, everyone who has the issue has taken all the steps I described and haven't been able the fix the drivers either.
.dlls are very unpredictable things. Who knows what's actually attempting to load the file ".dll", but as far as I can tell it isn't removed by any process I've been suggested so far.
The issue may not even be within the driver set for all I can tell. I just know it occurs WHEN I installed 10.5
Most of the people who've had this issue had it occur to them on the 10.2 install, which obviously didn't happen to me.
There may be several reasons for the rareness.
1. Not a lot of people play CoH. Then you have to count how many use NVid instead of ATI.
2. A lot of people are having issues with OGL no longer working when installing Catalyst 10.xx drivers. The complaints even extend into 9.xx. However, not many have recognized that this is the problem. There have been several hotfixes in 9.xx drivers to correct this issue, but not as many people have had the problem in the 10.5 drivers.
3. A lot of people that have problems don't realize it's a problem with a driver. A lot of the complaints I've found is reported in game forums and not driver forums.
5th, I'm going to level with you. I haven't heard of anybody else having this problem, and I don't see anything popping on the ATi bug-tracking system's in response to this issue. Given that nobody else seems to have run into this problem, it just sounds like it this was a driver-corruption issue limited to your machine's configuration.
Why? Couldn't tell you that. Driver corruption issues tend to cause some of the more annoying headaches for tech support, hence the importance of being able to duplicate / replicate the problem.
Now, if you honestly KNOW people who are able to replicate this error, or if you are able to replicate it yourself, you need to go get some bug reports listed:
http://www.amd.com/us/CatalystCrewSurvey
http://ati.cchtml.com/
Quote:
Wait. What?|
Originally Posted by 5th_Player
I'm running Vista 32-bit with latest service pack.
I'm using the 5850 Sapphire Overclocked. I was using the Vista 32-bit 10.4 drivers before upgrading. I was having errors in an outdated version of DirectX but tried the video card drivers first, since the 10.3 drivers were having problems stalling. |
How did you have an outdated version of DirectX if you are running Vista with SP2? Vista shipped with DirectX 10. Vista SP1 included DirectX 10.1 and since SP2 is an incremental update it would have installed 10.1 if you skipped SP1.
What version of DirectX do you have that can be outdated and how did you get it on your computer?
If the game spit out 20 dollar bills people would complain that they weren't sequentially numbered. If they were sequentially numbered people would complain that they weren't random enough.
Black Pebble is my new hero.
Quote:
This is NOT non-issue.|
Originally Posted by Texas Justice
Wait. What?
How did you have an outdated version of DirectX if you are running Vista with SP2? Vista shipped with DirectX 10. Vista SP1 included DirectX 10.1 and since SP2 is an incremental update it would have installed 10.1 if you skipped SP1. What version of DirectX do you have that can be outdated and how did you get it on your computer? |
Apparently my outdated DirectX 9, was the issue.
The tech email I have from CoH says I need to keep DX9 updated even though I have DX10.
This (so far) solved my complaint of CoH crashing 10 seconds into the game. My post is on this forum as well. The crashing was random, so I'm giving it some time to tell for sure.
Quote:
|
Thank you for the Game Advisor results. The game client requires the latest DirectX 9 components; this is true even if you have DirectX 10 or higher already installed. Please follow these instructions to install the newest DirectX 9 update: http://www.microsoft.com/downloads/d...1-50ceb6d8fa8d Once the DirectX 9 version is updated, if the issue is still persistent, then please re-run the Game Advisor tests, update your incident at the provided link, and attach the report. |
Hold on, I'll find the links of others having this problem.
1. http://futuremark.yougamers.com/foru....php?p=1399938
2. http://www.quakelive.com/forum/showthread.php?p=374224
3. http://forums.amd.com/game/messagevi...VIEWTMP=Branch
4. http://www.quakelive.com/forum/showthread.php?p=374530
ATI is recommending to replace the OGL dlls from 10.5 / .6 with 10.4's version. Apparently this also fixes the problem.
However, you lose OGL 4.0 and are left with OGL 3.3
My fix allows to use OGL 4.0
http://forum.notebookreview.com/alie...ml#post6369776
Quote:
| If you are using OpenGL applications or games, you may want to use Catalyst 10.4 or earlier anyway (or at least the atioglxx.dll from drivers earlier than 10.5), as 10.5 and 10.6 have a buggy atioglxx.dll that breaks some OpenGL applications as well as OpenGL games with Quake III engine and the likes. |
Quote:
Would you care to point out to me where exactly I said that I disbelieve you? |
Originally Posted by 5th_Player
...
Apparently my outdated DirectX 9, was the issue. The tech email I have from CoH says I need to keep DX9 updated even though I have DX10. This (so far) solved my complaint of CoH crashing 10 seconds into the game. My post is on this forum as well. The crashing was random, so I'm giving it some time to tell for sure. I can copy that email if it would satisfy your need to disbelieve me. Hold on, I'll find the links of others having this problem. |
That was never said or implied in any of my posts here. I simply asked how you had an outdated version of DirectX installed and how it got on your computer. I also stated which versions of DirectX came with Vista and the various Service Packs.
Not a bit of that is saying that I disbelieve you. Asking questions to clarify something you said isn't saying I disbelieve you, it is merely seeking clarification and information.
Perhaps you need to stop reading things into posts that aren't there.
Now, in your post you say you have DirectX 9 on your computer and that CoH Tech support says you need to keep DirectX 9 updated. Ok. That answered the two questions I asked plus gave some additional information.
It raises more questions in my mind, but I'll just leave them there since asking them may cause you to accuse me of other things that I didn't say.
If the game spit out 20 dollar bills people would complain that they weren't sequentially numbered. If they were sequentially numbered people would complain that they weren't random enough.
Black Pebble is my new hero.
Quote:
Ok, I'm sorry. I did read a little too much into your post.|
Originally Posted by Texas Justice
Would you care to point out to me where exactly I said that I disbelieve you?
That was never said or implied in any of my posts here. I simply asked how you had an outdated version of DirectX installed and how it got on your computer. I also stated which versions of DirectX came with Vista and the various Service Packs. Not a bit of that is saying that I disbelieve you. Asking questions to clarify something you said isn't saying I disbelieve you, it is merely seeking clarification and information. Perhaps you need to stop reading things into posts that aren't there. Now, in your post you say you have DirectX 9 on your computer and that CoH Tech support says you need to keep DirectX 9 updated. Ok. That answered the two questions I asked plus gave some additional information. It raises more questions in my mind, but I'll just leave them there since asking them may cause you to accuse me of other things that I didn't say. |
To me, the posts you and Je-Saist are making sound accusatory, like:
It's my machine that's messed up and no one else is having this problem.
I messed up the driver sweeper.
etc.
Sometimes I read too much emotion into posts, so if I misread you, I'm sorry. However, I can tell you, that it felt that way. So at least you can understand why I'm a little defensive.
Anyway, I've posted my evidence that this is a rare but not isolated problem.
I'm having this issue, but the command prompt isn't doing it for me...
I just updated the drivers for my card, too.
Help!
EDIT: The command prompt isn allowing the file to be copied even after I takeown.
This thread is several months old, so I have closed it. If anyone is still have this issue, or a similar issue, please create a new thread for it. Thanks.
I updated to catalyst 10.5 and started having an error pop up every time I loaded the game.
LoadLibrary failed with error126: The specified module could not be found.
***FIND*** [Start] -> Programs -> Accessories -> Command Prompt
1. Right click that and select Run as Administrator.
2. If don't see C:/Windows/System32 on the screen next to your cursor, type the command: cd /d C:/Windows/System32
(If windows isn't on C:, replace C: with the drive windows is installed on)
3. Type the command: COPY atioglxx.dll .dll
And that should do it.
You'll have to do this EVERY TIME YOU UPDATE THE DRIVER until the issue is fixed.
Now, IF THIS FAILS, you may need to take control of the Windows/System32 folder. That's a pretty crazy process, so I won't post that unless someone needs it. {meaning if you need to know how, ask}
Now for the story:
After digging around in what the process was loading, I confirmed it was the same rare error people are having with other OGL games using Catalyst 10.xx
Apparently some dll out there is trying to load ".dll" instead of "atioglxx.dll". You'll see this if you run some form of a process analyzer and look at the dlls COH is loading up. You'll see it fails at finding ".dll"
I tried backing up to 10.4 and still had the same problem. Apparently, once you get it, even using driver sweeper refuses to remove the problem. It's probably some DLL is not being updated by the driver updates (if it exists already) and doesn't get noticed by driver sweeper. So until I can narrow down what file is being corrupted, we're stuck with the following solution.
This isn't my solution, but it's well hidden on the net so I figure I would post it here.
From the looks of it, it has to do with the ATI support for OGL 4.0. I'm guessing those files don't get updated or removed by uninstalling Catalyst, and I can't find the full extent of those files.
However, this solution does allow you to use 10.6 if you were having this error, and it does run hella smooth compared to 10.4