[Cr1ms0n]

Installed the new NVidia 178.13 drivers today

After an initial increase in fps the game crashes after a few minutes of play. Thought this might be a one off but upon restart the same thing happened.

After user has logged in, about 5 minutes later BSOD will appear, something about a lockup on the secondary processor, saw one other guy had this issue over the on the US forums.

Anyone else having the same problem?

[stratoc]

i did, hadnt played for 2 months thought id try again and within 10 minutes a secondry clock didnt.... bsod. tbh i use a phenom and thought it was that, i do use those drivers though. in 12 months 2 bsod both while playing conan. i cancelled again im not paying for this.

[Cr1ms0n]

Originally Posted by stratoc i did, hadnt played for 2 months thought id try again and within 10 minutes a secondry clock didnt.... bsod. tbh i use a phenom and thought it was that, i do use those drivers though. in 12 months 2 bsod both while playing conan. i cancelled again im not paying for this.

Yea exact same bsod as me, I am also using a phenom. This is ridiculous.

NOTE TO FUNCOM:
Any Funcom guys reading this thread, you really need to keep up with the latest drivers Nvidia uses, every time they bring out a new driver, it manages to break your game.

[stratoc]

i automatically thought it was the phenom but now you mention it, i did 39 levels with no bsod before i updated drivers after update is was a matter of minutes before the crash.

[Cr1ms0n]

I had no troubles before i updated the drivers either, have rolled back to the 175.19 for now. Could of been all the PhysX support stuff in the new drivers that AOC didn't like, who knows.

[stratoc]

well i have tried to understand the 'secondry clock failed to respond within allocated time' bsod and always thought the secondry clock wasnt on the cpu at all, this goes to show it looks like a hipertransport problem and the secondry clock is either the gpu, northbridge or indeed physx.
so rolling back solved the problem for yourself.

[araponga]

if you installed the updated new drivers from nvidia i must advise you to put the old drivers back, there are known issues with that driver causing the very same problem with other games, like assassins creed and others.

from what i have read around other forums, seems that it was either nvidia that launched a buggy updated driver or as some have stated it was due to an update from microsoft that messed up the driver.

hey go figure neither will assume the fault :P

so again, put the old drivers back, and take a look at the nvidia official forums for updated news about this.

[stratoc]

thanks for the heads up

[griffz]

omagad , this driver is WHQL ...
Ugly NV :/

[Gandalf-Greyhelm]

Originally Posted by araponga if you installed the updated new drivers from nvidia i must advise you to put the old drivers back, there are known issues with that driver causing the very same problem with other games, like assassins creed and others. from what i have read around other forums, seems that it was either nvidia that launched a buggy updated driver or as some have stated it was due to an update from microsoft that messed up the driver. hey go figure neither will assume the fault :P so again, put the old drivers back, and take a look at the nvidia official forums for updated news about this.

Could you link to these sources? As a regular visitor to the nV forums I've seen nothing mentioned along these lines regarding the new drivers - as regards updates from MS - the other day I installed the new Dreamscene content pack 4 on one of my other computers (which uses an 8800GTX) and almost immediately I received a "nvlddmkm.sys" error - is that the update you're referring to? - if so, perhaps people could try disabling Aero before playing AoC - as that was (a while ago) a fix for 8 Series cards BSOD'ing or TDR'ing.

The only other thing I'd like to question is whether the guys experiencing these problems performed a full de-installation of their old drivers before updating - or whether they simply installed the new drivers on top of the old - possibly leading to conflicting driver versions - especially in Vista.

G.