View Full Version : Could this be faulty RAM?
javierdl 06-17-2005, 09:40 PM While playing HL2 I get this error message while the game freezes:
"0x241c9c17" referenced memory at "0x00d50cc0". The memory could not be "read".
Getting new ram would fix this?
Thank guys,
DPC
|
|
Vertizor
06-17-2005, 09:44 PM
Try updating your video drivers first, since that's free. Sometimes buggy video drivers will cause apps to crash, or even complete system lock ups.
javierdl
06-18-2005, 05:40 AM
Vertizor, thanks for the tips :)
I did change the drivers after your advice, and although it did improve some things, it didn't keep those crashes from happening again, I am getting that exact message again.
I wish I had a friend with the same type of ram to try his and see if I still had those messages.
DPC
SirLuthor
06-18-2005, 03:02 PM
Uhh. That's not a RAM problem. That's a stray pointer somewhere in the program that's giving you grief, not your hardware. Try to reproduce the error, and note down what you do to get it, then send it in as a bug report.
javierdl
06-18-2005, 07:06 PM
Thanks SL :)
All I can say as for how it happens is that it happens while I'm playing, pretty much out of the blue, without any particular signs prior to the actual crash.
I ran AVG Antivirus, MS Antispyware, and SpySweeper, finding only cookies from some Ad tracker companies, I don't suppose cookies could be the culprit for this, would they?
DPC
javierdl
06-18-2005, 11:22 PM
You won't believe what fixed the problem!
Actually you will as you were right from the beggining in that it was software ;)
Switching to OpenGL from Direct3D did it.
I am so happy now :)
Thanks guys!
DPC
Vertizor
06-19-2005, 01:52 AM
You can do that in HL2? I thought the engine was D3D only?
I've played various games in the past that were not stable in D3D and switching to OpenGL fixed it. Would have suggested it sooner but like I said, I thought HL2 was D3D only. :shrug:
singularity2006
06-19-2005, 05:58 AM
I get those errors when I overclock my RAM and it happens with just about any program that taxes the system.
SirLuthor
06-19-2005, 02:05 PM
You won't believe what fixed the problem!
Actually you will as you were right from the beggining in that it was software ;)
Switching to OpenGL from Direct3D did it.
I am so happy now :)
Thanks guys!
DPC
I can't exactly say why that would have helped though.... :shrug: Considering that OpenGL and D3D are in essence simply abstraction layers over the hardware. Might be a problem with the Source engine's D3D module, but it sounds more like one of those nasty hiding bugs that only pops up in certain hardware and software configurations :eek:
Vertizor: AFAIK, you can use the OpenGL rendering, but it requires some messing around with the config to get it to work. Although I'm going of memory here, I've never actually had to do this my self.
CGTalk Moderation
06-19-2005, 02:05 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.
vBulletin v3.0.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.