• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Memory Error got me puzzled.

T

Tordek

[H]ard|Gawd
Joined
Dec 9, 2003
Messages
1,765
I keep getting this error in windows xp about this memory that could not be "read". The sector of the memory is represented in a hex number. I wonder what could it be.

At first i though it was my ram. But memtest ran perfectly for a complete day.
Then I thought it could be my hard drive, so I completely format it and started from scratch.
Then I thought it could be my MBR (master boot record), so I fix it with the windows recovery tool.
Then I thought it could be a faulty ram slot. So I moved the ram around. Now it seemed that all my problems went away....

BUT

I was playing call of duty for a while just now, and guess what. The thing crashed and the same "the instruction at hex_num could not be "read""... What the hell is going on here?

Anyone experienced anything like this. Is it my harddrive. Im posting this on the disk storage systems and memory forums....
 
That error is the result of a bad pointer, the address could well be odd or out of range. Usually it has nothing to do with hardware.
 
Snugglebear said:
That error is the result of a bad pointer, the address could well be odd or out of range. Usually it has nothing to do with hardware.
Click to expand...
I was thinking that. I took a C++ class a few months ago and whenever i fucked up the pointers, the same error showed up. What im wondering is what is causing it on my system?
 
what kind of nic do you have? is it a linksys? because mine would crash my system...often...with that error unti li swapped it out.
 
If memory serves me right, Windows isn't going to BSOD unless the offending program is running in kernel mode. That means either windows itself or a driver is at fault.
 
defakto said:
what kind of nic do you have? is it a linksys? because mine would crash my system...often...with that error unti li swapped it out.
Click to expand...
I dont have cable :(

Maybe my modem is to blame. I bought a cheap one on newegg a while ago and it turned out to have an intel chip. I heard that running an intel modem with my computer (in the sig) would cause errors. Could this be it?
 
We had a virus here that would set that off.

See if you have the processes running:

internit.exe
svxhost.exe
msnmsngr32.exe
netsvr.exe
bling.exe

and I think thats it..
 
primea said:
how are your temps?
Click to expand...
Before the problem used to pop up out of nowhere while doing lite multi tasking (office, firefox and leechget...) Once i changed the memory from the slot i think was to blame for the past errors, the only time ive had that error was while playing two straight hours of call of duty. But i hadnt oced anything and my temps are at mids thirties pretty much all the time. I had the AC on too.
 
You must log in or register to reply here.
Back
Top