- This topic has 11 replies, 6 voices, and was last updated 19 years, 5 months ago by
.
-
Posts
-
I can not play CSS currently, I keep getting this error: The Instruction at “0x0fc132e2c” referenced memory at “0x0d70a1a0”. The memory could not be “read”.
I have contacted steam about this error because I have done all their tech support BS.
The problem started yesterday May 22, 2007. I performed the Casey’s config to increase my fps earlier that day, but I had restarted my computer since then. I played the game, closed out of it, went back into, closed it out, and then when I tried to go back into it it gives me the error. I reinstalled steam and the game on a different drive, but I receive the same error. So if nobody can help me, I guess I won’t be playing CSS.
I used to get that error all the time when trying to play source engine games. It was a driver problem with Windows XP and it took a Windows Vista installation to fix it. If you’ve recently installed any new drivers, I would recommend rolling them back.
Well, I havent installed any drivers lately, the last drivers I installed were about 2-3 weeks ago when I reformatted my drives, and those were the drivers I had before i reformatted.
It will not let me on, and this issue only occurs when CS:S is fully updated. I can play all other source engine games I have, but I can not play CS:S. I have reformatted my computer just so I could make sure BIOS and everything has been loaded correctly, but still I get the exact same error.
So problem solved, what I had to do to fix it………I dont feel like taking that much time to post all of it….
basically though, you had to bend over backwards, and allow steam to pump you in teh butt for a few hours. we’ve all been there before.
No I had to bend over backwards while *edited* slapping steam, I had to configure so *edited* much, and about 1/4 of it dealt with steam and CS:S
I had a very similar error, My problem was with IE7, I had a brand new system brand new install and I was getting this error WTF!! Try uninstalling Internet Explorer 7 if you have it installed. Fixed my issue.
i had this error, i dont know if IE7 has anything to do with it, I actually got a new graphics card, also another gig of ram, it fixed it because support with source can suck sometimes, you also should try just Restoring to a past date when everything worked b4 spending buttloads(YES I SAID BUTTLOADS) of money, u can try uninstalling IE7 and just go wit Mozilla.
- The forum ‘Counter-Strike: Source Discussion’ is closed to new topics and replies.