• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Half Life 2: Ultimate Stability Test? Or just too sensitive

C

canadianpsycho

Diamond Member
Well,

I've had so many issues with my stock PC running CS:Source (finally checked the vcore - must have had a brain fart, don't know why I didn't check it earlier, I was convinced it was my GPU OC for the longest time) that I'm beginning to think its even more sensitive then P95 and other OC tools. And its more fun!

Seems like a lot of PCs that are "stable" seem to crash/lockup on HL2 and CS:S with the infamous "memory could not be read" error and the like. My previous P4 system would run CS:S all day long no issues, but the minute my new FX-53 and Neo2 Plat didn't have enough juice, the game would just throw a fit and refuse to be stable...

Is Source just too finicky? Or is that even possible to have a "finicky" game? Should we crown Source based games as the new "true" sign of PC stability? I must admit, its more fun "playing" my stress tests then waiting for them to finish 😉
 
Yeah, what the heck is that "memory could not be read" error anyways? I have gotten that message once while playing. Seemed to be random. I used to get that error at work on my old P266 gateway machine with NT4 when trying to edit pictures for use in presentations...
 
I had it crash on me once too. I have been running F@H for 2 days straight with no crashes and all my games run fine and then this game crashes. Wierd isn't it .
 
I've actually ran into this problem in a few different apps. Sometimes reinstalling the particular app helps. And make sure to run defrag. Probably won't help much, but it can't hurt to try. I actually only started getting that about the time SP1 came out for XP, though oddly enough it's been happening on this 2000 machine every so often as well. I blame MS.
 
all my memory could not be read probs stopped once I upgraded to 1 GB ram. depends on your quality settings too. are they sucking up too much ram? but my opinion is that the game is not a reliable stability tester. I just think it does a poor job of governing ram usage. if you don't have any to spare, you're going to crash. could also have to do with ram utilization by a specific chipset. even 1 gb for some configs may not be a good enough fix.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top