Problems with RAM

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am hoping someone here can help me with this issue, which has been going on
for a while now...

I have a Compaq Presario 5150 PC with the latest BIOS update running with a
AMD K6-2 processor at approx 500 MHz... Yeah, is an old clunker compared to
the newer systems out there, but, hey, takes me where I need to...

My system currently has a total of 512 MB of RAM, however, the systems
motherboard has three RAM slots, which means I could be using 768 MB of
RAM... My system will start up fine as long as I only use two 256 MB chips,
but each time I try adding that third RAM chip, Windows XP will start
rebooting while in start up...

ALL three chips are of the same brand, type and size, and I have used each
possible combination of the RAM chips I have (two out of the three), so I
know all three RAM chips are good... Also, when all three chips are
installed, the computer hardware starts up normally indicating the correct
amount of RAM... The problem usually starts when Windows XP is starting up...
Somewhere during startup it will force the computer to reboot! If I remove
the third 256 MB RAM chip, THEN, it starts up normally...

Can anyone here perhaps point me in the right direction as to wht should I
check into?

By the way, the Windows in question is Windows XP SP2 Home Edition...

If you need any more additional information, please let me know...

Beforehand, thanks for any help any of you can provide...

Eddie
 
Visit COMPAQ tech support

I'd start at www.crucial.com and use their tool to see what it says. In most
cases it's a lot faster than searching the manufacturer site. If you don't
trust them, then hike over to www.kingston.com and do the same dance. In my
experience both of them have good info.

-John O
 
A BIOS test is only a quick pass/fail and is not extensive.
Try running Memtest86+, this runs from a boot disk and should eliminate or
confirm if your ram is good or bad.
Let it run for as long as you can, 2,4,6,8 or more hours, if no errors by
then your ram is OK.
See: http://www.memtest.org/

JS
 
Truth be told, when I was at first shopping for the RAM, I visited both
sites... It was through the info I gleaned form these (and other sites) that
I finally purchased the RAM I currently have...
 
I think I need to clear something out here: I do not think the problem is
with the RAM chips... I should have probably been a bit more specific about
this, but I tested all three 256 MB chips, used ALL THREE of them in all
possible pair combinations, and none of them showed any problems when only
using TWO out of THREE in the system...

The problem occurs when I try to use ALL THREE of them together...

Thanks, though...
 
When first looking to update the BIOS and add RAM, Opened the computer to
find it has a GYGABYTE GA-5SMM Motherboard, and when checking the specs for
the motherboard it shows the following Memory specifications:

- 8MB to 768MB DRAM size
- 3 x 3.3V DIMM Socket
- Supports 8/16/32/64/128/256 MB EDO/SDRAM DIMM Module
- Supports ECC Type DIMM Module (72 bits)

This was the information that I used when purchasing the memory (watch for
word wrap):

http://www.gigabyte.com.tw/Products...otherboard&ProductID=1579&ProductName=GA-5SMM
 
Could it be a particular memory slot that has the problem?
Inspect the slot for dirt/dust bunnies, etc.

JS
 
TainoV2 said:
I think I need to clear something out here: I do not think the problem is
with the RAM chips... I should have probably been a bit more specific about
this, but I tested all three 256 MB chips, used ALL THREE of them in all
possible pair combinations, and none of them showed any problems when only
using TWO out of THREE in the system...

The problem occurs when I try to use ALL THREE of them together...

Thanks, though...
Click to expand...

With the two memory DIMMs in place, does your machine run Memtest86+
error free for at least two complete passes ? You can get Memtest86+
from www.memtest.org . Also, Microsoft has their own memory test
program, and floppy is an option for this one as well.

http://oca.microsoft.com/en/windiag.asp

An Asus motherboard that uses the SIS530, offers two sets of
frequencies. It allows the processor and the memory to be run
synchronous (CPU 100MHz Memory 100Mhz). It also allows the
memory to be run slower than the processor (CPU 100MHz Memory 75Mhz).
The latter setting might be useful as an experiment, to see
if three sticks work better when run at the lower memory
clock speed.

The assumption I'm going on here, is there is a speed/load
related problem. And if that is the case, maybe you'll see the
odd error with one of those two memory test programs above.

The other possibility, is the memory map is botched some how,
and there is some kind of resource conflict. But I really
don't know how to deal with that.

You might also succeed in running the memory test program with
all three DIMMs, and then the results of the memory test
may be more interesting. But I'd at least start with
a "success" hardware config, to verify the memory test
programs work correctly. Memtest86+ for example, has some
logic for deciding what parts of main memory are reserved for
BIOS use, and what parts are available for test. On an older
motherboard, there are fewer guarantees that the rules
were followed with respect to that function.

Paul
 
I am hoping someone here can help me with this issue, which has been going on
for a while now...

I have a Compaq Presario 5150 PC with the latest BIOS update running with a
AMD K6-2 processor at approx 500 MHz... Yeah, is an old clunker compared to
the newer systems out there, but, hey, takes me where I need to...

My system currently has a total of 512 MB of RAM, however, the systems
motherboard has three RAM slots, which means I could be using 768 MB of
RAM... My system will start up fine as long as I only use two 256 MB chips,
but each time I try adding that third RAM chip, Windows XP will start
rebooting while in start up...

ALL three chips are of the same brand, type and size, and I have used each
possible combination of the RAM chips I have (two out of the three), so I
know all three RAM chips are good... Also, when all three chips are
installed, the computer hardware starts up normally indicating the correct
amount of RAM... The problem usually starts when Windows XP is starting up...
Somewhere during startup it will force the computer to reboot! If I remove
the third 256 MB RAM chip, THEN, it starts up normally...

Can anyone here perhaps point me in the right direction as to wht should I
check into?

By the way, the Windows in question is Windows XP SP2 Home Edition...

If you need any more additional information, please let me know...

Beforehand, thanks for any help any of you can provide...

Eddie
Click to expand...

It doesn't matter WHAT OS you are running - your problems have nothing
to do with the OS. This needs to be addressed with the folks who make
your chips, or the mainboard...but it is out of place HERE.

Ask elsewhere.
 
3 * 256 = 768 therefore 3 modules supported. Contact HP or Gigabyte tech
support for resolution.
 
Ok, maybe I am not being 100% clear stating the problem...

There are no problems relating to the hardware since:

- BEFORE Windows starts, the computer recognizes the correct amount of
memory EACH time (whether I use 1,2, or all three RAM chips). When I power
up the hardware there are not indications that ANY of the chips is defective.

- Each RAM chip, individually or used in combinations, do not keep Windows
XP from booting up as long as I only use only TWO (512 MB) of them. And all
THREE RAM chip are of the same Manufacturer AND type.

- The problem happens AS Windows XP is starting up, NOT BEFORE, which
indicates to me the issue happens when the OS is controlling my computer. I
only wish to find out why the OS shows no problems when the existing RAM in
my system is only 512 MB, but when it goes to any number higher than that, it
literally reboots my computer out of Windows. When the computer memory is at
512 MB, it will start normally, and you can even hear some of the USB
peripherals I have connected react as Windows XP starts. When I go above
that, Windows XP will shows the start up screen, play the welcome sound,
inmediately show the wallpaper I've set up, and about a minute after that, it
reboots the computer!

Hopefully I am not missing anything this time around...
 
Thanks for the 411, Paul! This is the first positive response I've received
so far...

Regarding that 'speed/load' problem, any visual sympthoms (other than the
tests you suggested) that I could look into?

Let me describe to you the scenario... When I start up Windows XP with the
computer using 512MB of RAM, windows will show the usual 'Welcome' screen,
play the welcome sound, then display the Wallpaper I've selected... Shortly
after, icons and Taskbar will appear, I will hear some sounds from the other
peripherals I have connected (specially the scanner), and Windows will
continue and finish start up normally... When the system has 768 MB of RAM
(the 'extra' 256 MB chip), it goes as far as displaying the Wallpaper I've
selected, and about a minute after that (more or less), the system REBOOTS
itself...

Would this behavior be indicative of that 'speed/load' problem you indicated?

Also, if that WAS the case, you mentioned about setting the memory clock
speed to a lower setting, would that be a BIOS setting I need to change?

Again, any info would be appreciated...

And, again, thanks for you all your help...

Eddie
 
have you turned of Automatically Reboot in System Properties, Advanced
Startup and Recovery settings?
 
I'll need to check on that, but if I understand correctly, is this the option
that automatically reboots the system to bypass the BSD (Blue Screen of
Death)?
 
TainoV2 said:
Thanks for the 411, Paul! This is the first positive response I've received
so far...

Regarding that 'speed/load' problem, any visual sympthoms (other than the
tests you suggested) that I could look into?

Let me describe to you the scenario... When I start up Windows XP with the
computer using 512MB of RAM, windows will show the usual 'Welcome' screen,
play the welcome sound, then display the Wallpaper I've selected... Shortly
after, icons and Taskbar will appear, I will hear some sounds from the other
peripherals I have connected (specially the scanner), and Windows will
continue and finish start up normally... When the system has 768 MB of RAM
(the 'extra' 256 MB chip), it goes as far as displaying the Wallpaper I've
selected, and about a minute after that (more or less), the system REBOOTS
itself...

Would this behavior be indicative of that 'speed/load' problem you indicated?

Also, if that WAS the case, you mentioned about setting the memory clock
speed to a lower setting, would that be a BIOS setting I need to change?

Again, any info would be appreciated...

And, again, thanks for you all your help...

Eddie
Click to expand...

The purpose of using memtest86+, is to verify which hardware
configurations are error free. You can try two sticks at 100MHz
and see if any errors are reported. I let it run until the pass
counter at the top of the screen, indicates two complete passes
have been tried.

Next, you could try three sticks at 100MHz. If memtest86+
reports a lot of errors, you should have the option to run the
memory at 75MHz. So, shut down, change the memory speed jumper,
and try again.

Those are the things I'd try. I've spent up to a week characterising
a problem, by doing stuff like that. My Nforce2 based motherboard,
was quite pesky\ with RAM, and I ended up buying some replacement
RAM to fix it. So do some testing with various combinations of sticks
and speed, and before you know it, you'll be an expert :-)

Paul
 
Hello Paul,

Following a suggestion another of the guys here gave me, I disabled the
'Restart Automatically' option in Windows XP in order to find out what kind
of error message I would get given my problem, and this is what I got:

CRQL_NOT_LESS_OR_EQUAL

Under Technical Information, I got the following message:

STOP: 0x0000000A (0x00000001, 0x00000002, 0x00000001, 0x804E7981)

Thought I'd give you this to see if it rings any bells regarding my
problem... Any info would be appreciated...

Thanks,

Eddie
 
Hello Bob,

I did as you suggested, and this was the error message I got:

CRQL_NOT_LESS_OR_EQUAL

Under Technical Information, I got the following message:

STOP: 0x0000000A (0x00000001, 0x00000002, 0x00000001, 0x804E7981)

I'll try to do a search on this error and see what I find, but if you could
provide me any additional info, I'll appreciate it...

Again, thanks for the tip...

Eddie
 
TainoV2 said:
Hello Paul,

Following a suggestion another of the guys here gave me, I disabled the
'Restart Automatically' option in Windows XP in order to find out what kind
of error message I would get given my problem, and this is what I got:

CRQL_NOT_LESS_OR_EQUAL

Under Technical Information, I got the following message:

STOP: 0x0000000A (0x00000001, 0x00000002, 0x00000001, 0x804E7981)

Thought I'd give you this to see if it rings any bells regarding my
problem... Any info would be appreciated...

Thanks,

Eddie
Click to expand...

This page has links for various stop codes. Have
a look through this (menu on upper left has "0A").

"TROUBLESHOOTING WINDOWS STOP MESSAGES"
http://aumha.org/a/stop.htm

"Troubleshooting a Stop 0x0000000A error in Windows XP"
http://support.microsoft.com/?kbid=314063&sd=RMVP

Looks like it was attempting to write memory at address 0x01.
Whatever that means. Bad memory is one possibility, but not
the only possible cause. Memtest86+ tests all the memory,
as no OS is present during the test, and the program actually
moves itself out of the way, to test the small chunk of
RAM that it occupies. The Microsoft version, I believe,
does something similar. (There have been other memory
testers, that run while in Windows, but they wouldn't
be testing the RAM occupied by the kernel. You need a
test that covers all the memory.)

Perhaps someone else can suggest some more reasons
for Stop 0x0A, like maybe a bad driver.

Paul
 
Back
Top