PCTech Forums

Hi, I'm struggling with an extremely confusing problem, and I saw in a recent post someone was able to cure their problem.. but we weren't supposed to use their solution for our own problem.

So anyway, I play the game Counter Strike Source Half Life 2.. etc, any Steam powered games relating, and I receive a "0x########" etc.. "Memory Could not be "read" error before i join a game or right before it enters into the video stress test.

I feel like I've tried every solution known to man and I could really use some help here.

Some Specs: (everything is up to date)
Windows XP Home: SP2
AMD Sempron 3000+ Processor [1.81ghz]
Nvidia Geforce4 MX 4000 graphics
960 MB ram (2, 512MB ram chips DDR memory)

Anything else you'd need to know I can give the info on.
I am open to any help anyone can give me.

Thanks in Advance. This is my last attempt at this

Go0se,

That generic error you listed most often mean that one of your rams sticks is causing the error but it could also be a driver problem or conflict.

I will need the exact error that you receive in order to help you resolve this problem.
Go to Start > Control panel > Administrative tools > Event viewer > look in the system section to find this error. Click inside the 'Description' section then highlight the text and copy and paste it into notepad.
At the bottom of the event window check 'words' and then copy and paste that text also
Then past it all into your reply to this thread.

Gecko,

Thanks for the reply first off.

Secondly I searched all of the errors in my event viewer, (red x's and yellow hazards), and couldnt find anything with my error code in it.

The exact code I'm recieving is as follows:

The instruction at "0x1264d254" refrenced at "0x0e458998". The memory could not be read.

If there's anything else i can check or anything i need to do, please.

Thanks.

For testing purposes, i would pull one of the sticks of ram and try to load the game then the other. If you get the same error with a certain stick then the solution is a little more obvious. Knowing it wont load as fast or run as smooth, were just looking to generate the same error.