Datacache.dll FOR THE LOSS

[Switchblade]

O M F@@KIN G!!!!!!!!!!!!!!!!!!!111oneone

It used to be that every other time I ran my computer I would get a random crash and I'd just restart and it would work. Now I can't play source at all. As soon as I load one map, Crash CRASH F@@KING CRASH! And not only that. After it crashes, my CPU goes to full load and everything starts getting extremely hot and I have to force a shutdown because every program ends up "Not responding" and it'll take 15 min to wait on that.

SO MANY people have this problem, the datacache.dll error...AND...Valve ACKNOWLEDGES that it's out there and says they're doing something...but it's been nearly a month since all these people have been getting errors. It's not even just Source. ANY game running on the HL2 engine will get this error, given you have something like a dual core processor or a 64 bit processor or a mix.

This just pisses me off to no end. Valve knows it, and they seem to be taking their time. They could put up an update about source, notifying people that they're working on it...BUT NOOO. People always ask if Valve cares....I'm pretty sure they don't give a F@@K until the money starts to drain to a trickle, and THEN they kick it up a notch.

There's no fix for it because it's faulty f@@King coding of the HL2 engine or teh F@@K ever it is.

I hate you Valve...

/end rant

Only about half of my insanely pissed rant there might be true, but I know for sure that very few people (I'd guess 2% or less) are permanently fixing the problem. It's a dual core/64 bit thing, and MANY people have this problem across several HL2 engine games. I've spent about 10 hours total looking for a fix for this, and all I see are people making guesses trying to help. "Update your video drivers", etc etc. Nothing works. I'm not the kind of person to sit around and wait weeks or months for some random guy in a chair to type 5 lines of code.

Hopefully they fix this damn problem and maybe they'll have less people hating them...

So yeah, if you have problem with a Steam game and you think buying new hardware will fix it...probably won't help. If you can play other games then things should be good, seeing how Source is screwing a lot of people over right now.

[Craig]

you and your fancy dual cores and your sixty four bits...peeshaw!

[capt-kevlar]

try running game on 1 core ive known this to help.

[Switchblade]

Quote:

Originally Posted by capt-kevlar

try running game on 1 core ive known this to help.

Tried affinity set to 1, set to 0, used setaffinity.exe to manage them and also did it manually. I've run the game with ATI shared memory on and off, didn't change anything...

Last time the game worked properly was in DirectX 8.0, before that I was running 7.0 and I got pissed at the lack of shadows, and attempted to bump it up to 8.0 and that was successful. After starting up the system again, I started Source on core 1...crash. Restart. Ran Source on core 1 again, and it loaded. I started my own server, and as the screen should pop up with the map loaded and ready to play, CTD and a nice error message. I can't remember what the message says, however when Source crashes with Xfire running, it will pick up the errors for me and give me a report. Datacache.dll is always the culprit in this, and Valve acknowledges this issue, however it's been out there for a long time. Sometimes Windows will pick up the error, and it will spit out it's jargon, as well as Datacache.dll being the culprit even with Xfire not running.

The worst part of all this is that after the game crashes, my system will act fine and then after a random amount of time the laptop fan kicks into high gear and my CPU usage is through the roof at like 50% or above, sometimes 100%. Very bad for a system to just be running heat like that...could be very damaging as well. That's one of the reasons I'm extremely irritated about this issue...also that every forum I went to, out of about 30-40 had no idea what was going on and had no solutions to offer, meaning lots of people are being left clueless like me, and the non-computer-savvy people are probably calling up tech support for a problem that not many people know how to fix.

Quote:

Originally Posted by Craig

you and your fancy dual cores and your sixty four bits...peeshaw!

I'm thinking about loading up Casey's config onto my old AMD Sempron 2800+ 1.61ghz single core for Source to help with the FPS (which are like 20-40 in 32 man Office). At least it's single core and if my laptop chooses to poop on itself, then I can fall back to this and get that little bit of building anger out and work on it later. As long as I can have my shadows on high and my sound on medium with reasonable FPS...then I'm happy.

At least this thing will get more use than a small-time server if I do that.

[Dukefrukem]

switch my source has been crashing lately too. it has some weird error afterwards too. next time it happens ill post a screenshot.

just weird how i've never had crashing problems with source then all of a sudden it crashes almost every time i play.

[Switchblade]

Yeah, same here, my laptop ran it like a beast, but now it's like it barely get the game started, leastways keep it running. Many people on the forums I've searched have been saying that it's a Source engine error in the code itself due to some patch they put out. Something a little before that Chat box patch. The error I get when it crashes from a map load is like "IDirect9Device:Present()" or something similar to that. It has "Present" at the end. (I know someone will probably make a gift joke about that...)

Also my game crashes when trying to change the game resolution, and I have to force it to load in the resolution that my screen is currently at, AND if I try to change certain video settings via ingame controls, it will crash. Changing texture, model detail, and mostly all of them will result in a CTD with no error message.

Oh, and just some extra info, this crash occurred with both Omega drivers and ATI drivers that came with the system.

Duke, I assume you have a multi-core processor or 64 bit processor as well, since you're having these crashes too.

[Deathscythe]

Quote:

Originally Posted by Switchblade

Only about half of my insanely pissed rant there might be true, but I know for sure that very few people (I'd guess 2% or less) are permanently fixing the problem. It's a dual core/64 bit thing, and MANY people have this problem across several HL2 engine games. I've spent about 10 hours total looking for a fix for this, and all I see are people making guesses trying to help. "Update your video drivers", etc etc. Nothing works. I'm not the kind of person to sit around and wait weeks or months for some random guy in a chair to type 5 lines of code.

i have had this problem once and i dont have 64 bit nor dual core
i fixed it by first doing search of my computer for the file to find where it is located then i go to that folder and look at the file version so i know exact version i need then i search google for filename.ext then go thru searching for the exact version and overwrite the old bad file and it works for all most all of the computer problems i have ever had even the blue screen of death messages

[Deathscythe]

Quote:

Originally Posted by Craig

you and your fancy dual cores and your sixty four bits...peeshaw!

i want 2 dual core cpu's dual gfx cards as well =( then i could run 2 or 3 games at once and still leave enough cpu for windows processes by having 1 core per game and having 1 core solely for windows processes making the computer run smoothly even with 3 games running after i got another 1.5 gigs of ram ot max out my ram with 4 sticks total sadly my 1 gig sticks dont work in all four slots correctly it runs as a 256 stick in 2 of the slots but in the other 2 it works as a 1 gig stick or it dont work i cant remember exactly but i have it working right now

[Switchblade]

Quote:

Originally Posted by Deathscythe

i have had this problem once and i dont have 64 bit nor dual core
i fixed it by first doing search of my computer for the file to find where it is located then i go to that folder and look at the file version so i know exact version i need then i search google for filename.ext then go thru searching for the exact version and overwrite the old bad file and it works for all most all of the computer problems i have ever had even the blue screen of death messages

So you downloaded a "good" copy of "datacache.dll" and replaced your old one? I was thinking about that, but what if it locks up my system and forces me to reinstall XP?

Well, hell, I have two hard drives on my desktop. Gigabit LAN Backup Time :o. I'll give it a try and see if it helps. Hopefully so, cuz I like playing CS, but it's just a pain to get it running.

[chode_messiah]

Yea I gave up on source when it became impossible to play and have fun.