COH Log in Help?!?!

xoxo
Py

hmm are you sure you updated all your drivers? That seems like an open GL problem which i believe is associated with your video drivers.


Try making sure you have the latest directX too.

My experience with this kind of thing is limited so i could be wrong. I just know that i recently updated my drivers and missed one driver that i needed, after a couple of hours fooling around with it, i found out what i missed, downloaded that and all was good. Also i updated my directx to the latest version though i don't know if that had an impact on my driver issue from earlier.

After the patch, I couldn't log in.
I verified files, I still could not log in.
I shutdown completely (powerdown). Then restarted my system and I was able to get into the City the first try.

I'm assuming that you restarted your computer after you updated the video drivers. You usually have to do that.
If you haven't restarted your computer, I would do that. Let it get completely up.
Then shut it down completely (powerdown), give it a minute or two and then power it back up.
Then try to get into the City again.

It's an ATI card driver issue - but it may be a compatability thing with the game's last update, causing a problem and not the driver itself. I've seen this before, I generally wait for them to patch it. As long as you inform support, they know it's a problem.

This issue probably occurred because you patched your vid drivers, BUT you didn't completely restart the system after.

DLL files are Dynamic Link Libraries, batches of code that programs can call on when they're needed. However, they're not truly dynamic, in that when a device driver is loaded, it loads the DLL's that it uses.

Now, say you run a patch, which updates the DLL code on the disk, giving your vid card driver some new capabilities. However, the code that's currently being used by the computer isn't patched, cos it's being used, and it's bad form to update memory directly - tends to make things blow up in spectacular fashion.

So, you've a brand new video driver, but you're not using anything other than standard Windows calls, which probably haven't changed. Then you run your game... and it tries to call some code that HAS been changed... and the old copy of the DLL, still in memory, doesn't include the new functions, or references different memory addresses. It promptly crashes, and takes the driver with it... and the program that was using the driver.

That's when you see the dialogs above.

Now, if you'd restarted... you'd have loaded fresh shiny new stuff across the board.... theoretically. See... sometimes those driver install programs don't install a needed file if a copy already exists... an OLD copy. So if you've restarted and you still see this? UNINSTALL the driver, use Driver Cleaner or some other program to get rid of the driver's DLL files on the drive, then reinstall so that everything is a fresh copy. Then restart.


We seem to be doing a lot of restarting, don't we? Well, that's Windows for you.