Dell Dimension 4550 Memory Problems?

A friend of mine asked me to try figure out what was wrong with their 2 year
old Dell Dimension 4550 computer running Windows XP Home Edition. Over the
last year it has been inclined to have a blank screen (monitor is an
E151FPp) while booting up, and even when the computer boots up successfully,
it invariably will get to a point where the screen freezes, sometimes
preceded by a psychodelic deterioration of the colors. They could never tell
how long it would take until it would freeze up, so they would try to get on
and off as quick as possible.
When I first attempted to boot up the computer, I got a blank screen. With
the monitor powered on, I pushed on some of the other monitor buttons and
got a message that said that the monitor was in some kind of power save
mode, and that I should move the mouse or push any key on the keyboard. That
didn't work. However, I was able to get the monitor to work, by first
disconnecting it completely from the computer, and then allowing the
computer to boot up to what sounded like completion. I then powered down the
computer, hooked the monitor back up, kept the monitor powered down, and
booted the computer up. After the computer had booted up completely, I then
powered up the monitor and there was the Windows XP desktop. In the course
of doing this there were a few occasions where things didn't quite boot up
correctly, and I would get a GGGY (Green-Green-Green-Yellow) diagnostic
light code on the back of the computer. I checked all the IDE connections,
but everything seemed in order. Despite this, I was still able to boot the
computer up. But it seemed that it would eventually freeze up anyway. So I
figured that I would reinstall reinstall XP using the XP Reinstallation CD
in the hopes od eliminating some kind of software issue. I attempted twice
to reinstall XP using the "r" command that would just repair the files that
may have been corrupted. Near the end of both of these attempts, the screen
would deteriorate into a "psychodelic image" followed by a freeze up. I then
decided to choose the option to overwrite Windows XP over the existing
Windows XP installation, and the same thing happened; a "psychodelic
freezeup" at the end of the installation. I suspect that this last attempt
may have deleted some of the configuration files for the existing Windows XP
installation. Also, I suspect that I either created a new problem or broke
something that was failing anyway. Now when I attempt to boot up, I get
nothing on the monitor, and when I look at the diagnostic lights I get a
YYGG configuration implying some kind of memory issue. I attempted to reseat
the existing 256MB memory stick in either of the two banks, and in both
cases the boot process is short-lived and I get nothing at all on the
monitor. I have ordered another memory stick with the hopes that this will
solve the problem, assuming that it is the only problem.

Here are some of my questions:

1)Does this sound like a memory problem that may have been just getting
worse for the last year? Was the GGGY code a precursor to the YYGG code?
Does this imply something other than a memory problem?

2)If new memory solves the problem, how should I go about reinstalling XP?
Is it possible that a virus ruined the first memory stick? Can that happen?
If so, should I totally zero out the hard drive and install XP from scratch
so the virus doesn't ruin the new memory? If not, is there some way of
retrieving the configuration files that I may have deleted on my last
attempt? It would be nice to have the original XP, even though my friend
said it doesn't matter.

3)Should I just format the C drive and just reinstall XP on that. I suspect
that it might be simpler. Would that remove the antivrus program?

4)If the AGP card (I think it's an ATI Radeon 128) was not working properly,
would it cause symptoms like this? I recently removed the AGP card and
attempted to boot up the computer, and I still got the memory error YYGG.

Any thoughts appreciated.

Gary

On Thu, 20 Jan 2005 18:53:17 -0500, "Gary Kaucher"
<> wrote:

>A friend of mine asked me to try figure out what was wrong with their 2 year
>old Dell Dimension 4550 computer running Windows XP Home Edition. Over the
>last year it has been inclined to have a blank screen (monitor is an
>E151FPp) while booting up, and even when the computer boots up successfully,
>it invariably will get to a point where the screen freezes, sometimes
>preceded by a psychodelic deterioration of the colors. They could never tell
>how long it would take until it would freeze up, so they would try to get on
>and off as quick as possible.
>When I first attempted to boot up the computer, I got a blank screen. With
>the monitor powered on, I pushed on some of the other monitor buttons and
>got a message that said that the monitor was in some kind of power save
>mode, and that I should move the mouse or push any key on the keyboard. That
>didn't work. However, I was able to get the monitor to work, by first
>disconnecting it completely from the computer, and then allowing the
>computer to boot up to what sounded like completion. I then powered down the
>computer, hooked the monitor back up, kept the monitor powered down, and
>booted the computer up. After the computer had booted up completely, I then
>powered up the monitor and there was the Windows XP desktop. In the course
>of doing this there were a few occasions where things didn't quite boot up
>correctly, and I would get a GGGY (Green-Green-Green-Yellow) diagnostic
>light code on the back of the computer. I checked all the IDE connections,
>but everything seemed in order. Despite this, I was still able to boot the
>computer up. But it seemed that it would eventually freeze up anyway. So I
>figured that I would reinstall reinstall XP using the XP Reinstallation CD
>in the hopes od eliminating some kind of software issue. I attempted twice
>to reinstall XP using the "r" command that would just repair the files that
>may have been corrupted. Near the end of both of these attempts, the screen
>would deteriorate into a "psychodelic image" followed by a freeze up. I then
>decided to choose the option to overwrite Windows XP over the existing
>Windows XP installation, and the same thing happened; a "psychodelic
>freezeup" at the end of the installation. I suspect that this last attempt
>may have deleted some of the configuration files for the existing Windows XP
>installation. Also, I suspect that I either created a new problem or broke
>something that was failing anyway. Now when I attempt to boot up, I get
>nothing on the monitor, and when I look at the diagnostic lights I get a
>YYGG configuration implying some kind of memory issue. I attempted to reseat
>the existing 256MB memory stick in either of the two banks, and in both
>cases the boot process is short-lived and I get nothing at all on the
>monitor. I have ordered another memory stick with the hopes that this will
>solve the problem, assuming that it is the only problem.
>
>Here are some of my questions:
>
>1)Does this sound like a memory problem that may have been just getting
>worse for the last year? Was the GGGY code a precursor to the YYGG code?
>Does this imply something other than a memory problem?
>
>2)If new memory solves the problem, how should I go about reinstalling XP?
>Is it possible that a virus ruined the first memory stick? Can that happen?

Your problem may be memory; nothing software-based can usually ruine
memory; it was either made correctly or it wasn't. The problem could
be bad memory, but it could also be a bad hard disk (windows uses the
hard disk as memory when it runs low), a bad power supply, or
something else. Download memtest86, and make a bootable floppy or cd
with it installed, run it over night. If it gives you no errors, you
can bet the memory is fine. If the memory is fine, open the machine
up, find out who made the hard disk, download their diagnostics and
test the drive. If the drive is fine, find a spare power connector
and check the voltages, there should be one around 12 volts (grounds
are the two middle black pins). If the 5v is below 4.85, you need a
power supply, from dell because theirs are proprietary.

"Gary Kaucher" <> wrote in message
news:...
>A friend of mine asked me to try figure out what was wrong with their 2
>year
> old Dell Dimension 4550 computer running Windows XP Home Edition. Over
> the
> last year it has been inclined to have a blank screen (monitor is an
> E151FPp) while booting up, and even when the computer boots up
> successfully,
> it invariably will get to a point where the screen freezes, sometimes
> preceded by a psychodelic deterioration of the colors. They could
> never tell
> how long it would take until it would freeze up, so they would try to
> get on
> and off as quick as possible.
> When I first attempted to boot up the computer, I got a blank screen.
> With
> the monitor powered on, I pushed on some of the other monitor buttons
> and
> got a message that said that the monitor was in some kind of power
> save
> mode, and that I should move the mouse or push any key on the
> keyboard. That
> didn't work. However, I was able to get the monitor to work, by first
> disconnecting it completely from the computer, and then allowing the
> computer to boot up to what sounded like completion. I then powered
> down the
> computer, hooked the monitor back up, kept the monitor powered down,
> and
> booted the computer up. After the computer had booted up completely, I
> then
> powered up the monitor and there was the Windows XP desktop. In the
> course
> of doing this there were a few occasions where things didn't quite
> boot up
> correctly, and I would get a GGGY (Green-Green-Green-Yellow)
> diagnostic
> light code on the back of the computer. I checked all the IDE
> connections,
> but everything seemed in order. Despite this, I was still able to boot
> the
> computer up. But it seemed that it would eventually freeze up anyway.
> So I
> figured that I would reinstall reinstall XP using the XP
> Reinstallation CD
> in the hopes od eliminating some kind of software issue. I attempted
> twice
> to reinstall XP using the "r" command that would just repair the files
> that
> may have been corrupted. Near the end of both of these attempts, the
> screen
> would deteriorate into a "psychodelic image" followed by a freeze up.
> I then
> decided to choose the option to overwrite Windows XP over the existing
> Windows XP installation, and the same thing happened; a "psychodelic
> freezeup" at the end of the installation. I suspect that this last
> attempt
> may have deleted some of the configuration files for the existing
> Windows XP
> installation. Also, I suspect that I either created a new problem or
> broke
> something that was failing anyway. Now when I attempt to boot up, I
> get
> nothing on the monitor, and when I look at the diagnostic lights I get
> a
> YYGG configuration implying some kind of memory issue. I attempted to
> reseat
> the existing 256MB memory stick in either of the two banks, and in
> both
> cases the boot process is short-lived and I get nothing at all on the
> monitor. I have ordered another memory stick with the hopes that this
> will
> solve the problem, assuming that it is the only problem.
>
> Here are some of my questions:
>
> 1)Does this sound like a memory problem that may have been just
> getting
> worse for the last year? Was the GGGY code a precursor to the YYGG
> code?
> Does this imply something other than a memory problem?
>
> 2)If new memory solves the problem, how should I go about reinstalling
> XP?
> Is it possible that a virus ruined the first memory stick? Can that
> happen?
> If so, should I totally zero out the hard drive and install XP from
> scratch
> so the virus doesn't ruin the new memory? If not, is there some way of
> retrieving the configuration files that I may have deleted on my last
> attempt? It would be nice to have the original XP, even though my
> friend
> said it doesn't matter.
>
> 3)Should I just format the C drive and just reinstall XP on that. I
> suspect
> that it might be simpler. Would that remove the antivrus program?
>
> 4)If the AGP card (I think it's an ATI Radeon 128) was not working
> properly,
> would it cause symptoms like this? I recently removed the AGP card and
> attempted to boot up the computer, and I still got the memory error
> YYGG.
>
> Any thoughts appreciated.
>
> Gary

1. Either a memory or a video card(memory on it0 if you have one.
2. Viruses don't attack hardware. A check in the recycle bin may have
some deleted files, however, an install over the existing
shouldn't have deleted any
configuration things, but some updates may be gone.
3. If you reformat everything is gone, including programs and
personal files
from that drive.
4. Didn't you just answer your own question.

You've been attacking a hardware problem with software changes.


>
>
>

"Gary Kaucher" <> wrote in message
news:...
> A friend of mine asked me to try figure out what was wrong with their 2
year
> old Dell Dimension 4550 computer running Windows XP Home Edition. Over the
> last year it has been inclined to have a blank screen (monitor is an
> E151FPp) while booting up, and even when the computer boots up
successfully,
> it invariably will get to a point where the screen freezes, sometimes
> preceded by a psychodelic deterioration of the colors. They could never
tell
> how long it would take until it would freeze up, so they would try to get
on
> and off as quick as possible.
> When I first attempted to boot up the computer, I got a blank screen. With
> the monitor powered on, I pushed on some of the other monitor buttons and
> got a message that said that the monitor was in some kind of power save
> mode, and that I should move the mouse or push any key on the keyboard.
That
> didn't work. However, I was able to get the monitor to work, by first
> disconnecting it completely from the computer, and then allowing the
> computer to boot up to what sounded like completion. I then powered down
the
> computer, hooked the monitor back up, kept the monitor powered down, and
> booted the computer up. After the computer had booted up completely, I
then
> powered up the monitor and there was the Windows XP desktop. In the course
> of doing this there were a few occasions where things didn't quite boot up
> correctly, and I would get a GGGY (Green-Green-Green-Yellow) diagnostic
> light code on the back of the computer. I checked all the IDE connections,
> but everything seemed in order. Despite this, I was still able to boot the
> computer up. But it seemed that it would eventually freeze up anyway. So I
> figured that I would reinstall reinstall XP using the XP Reinstallation CD
> in the hopes od eliminating some kind of software issue. I attempted
twice
> to reinstall XP using the "r" command that would just repair the files
that
> may have been corrupted. Near the end of both of these attempts, the
screen
> would deteriorate into a "psychodelic image" followed by a freeze up. I
then
> decided to choose the option to overwrite Windows XP over the existing
> Windows XP installation, and the same thing happened; a "psychodelic
> freezeup" at the end of the installation. I suspect that this last attempt
> may have deleted some of the configuration files for the existing Windows
XP
> installation. Also, I suspect that I either created a new problem or broke
> something that was failing anyway. Now when I attempt to boot up, I get
> nothing on the monitor, and when I look at the diagnostic lights I get a
> YYGG configuration implying some kind of memory issue. I attempted to
reseat
> the existing 256MB memory stick in either of the two banks, and in both
> cases the boot process is short-lived and I get nothing at all on the
> monitor. I have ordered another memory stick with the hopes that this will
> solve the problem, assuming that it is the only problem.
>
> Here are some of my questions:
>
> 1)Does this sound like a memory problem that may have been just getting
> worse for the last year? Was the GGGY code a precursor to the YYGG code?
> Does this imply something other than a memory problem?
>
> 2)If new memory solves the problem, how should I go about reinstalling XP?
> Is it possible that a virus ruined the first memory stick? Can that
happen?
> If so, should I totally zero out the hard drive and install XP from
scratch
> so the virus doesn't ruin the new memory? If not, is there some way of
> retrieving the configuration files that I may have deleted on my last
> attempt? It would be nice to have the original XP, even though my friend
> said it doesn't matter.
>
> 3)Should I just format the C drive and just reinstall XP on that. I
suspect
> that it might be simpler. Would that remove the antivrus program?
>
> 4)If the AGP card (I think it's an ATI Radeon 128) was not working
properly,
> would it cause symptoms like this? I recently removed the AGP card and
> attempted to boot up the computer, and I still got the memory error YYGG.
>
> Any thoughts appreciated.
>
> Gary


Thanks for your responses. I am still waiting for the new memory. Currently,
I can't bring up anything on the monitor. Hopefully, the new memory will
solve that and I will be able to run some of the suggested tests. Here's
what I've done in the mean time to try and sort thing out:

I removed the modem card, AGP card, and the one 256MB memory module. There
are 4 ribbon cables, one for the CD-ROM and CD-RW, one for the FDD, one for
the HDD, and one for the USB ports on the front of the box. I disconnected
all four cables at their motherboard connectors only. I left each of their
respective power cables connected. I then closed the box and pushed the
power button, and nothing happened; no power. After some trial and error, it
appears that I need to have the USB (Power Switch?) ribbon cable connected
to the motherboard in order to get the power to work. None of the other
ribbon cables will suffice to enable computer to power up. I hope that is
normal. Anyway, here's what happens:

With everything removed as stated, and with all ribbon cables disconnected
at the motherboard I get no power at all when I push the power button.

With everything removed as stated, and with just the USB (Power Switch?)
ribbon cable connected at the motherboard it powers up and I get 6 long
beeps and a GYYY diagnostic light code. The same thing occurs if I connect
all the ribbon cables to the motherboard. My manual says that GYYY means no
memory modules detected, which is correct since the module has been removed.

If I then add the single 256 memory module to the above scenario, I get no
beeps and a YYGG diagnostic light code. The same thing occurs if I transfer
the memory module to the other memory slot. I believe YYGG implies some kind
of memory issue.

I ordered the other memory module and it is being shipped. I hope that is
the only problem. When I removed the AGP card (ATI 128 RAGE) I noticed that
the gold colored "heat dissipator" had a slight discoloration to it. For
what it's worth, the CD-ROM, CD-RW, and HDD are all set to cable select.

Gary

"Chris Hill" <> wrote in message
news:...
> On Thu, 20 Jan 2005 18:53:17 -0500, "Gary Kaucher"
> <> wrote:
>
> >A friend of mine asked me to try figure out what was wrong with their 2
year
> >old Dell Dimension 4550 computer running Windows XP Home Edition. Over
the
> >last year it has been inclined to have a blank screen (monitor is an
> >E151FPp) while booting up, and even when the computer boots up
successfully,
> >it invariably will get to a point where the screen freezes, sometimes
> >preceded by a psychodelic deterioration of the colors. They could never
tell
> >how long it would take until it would freeze up, so they would try to get
on
> >and off as quick as possible.
> >When I first attempted to boot up the computer, I got a blank screen.
With
> >the monitor powered on, I pushed on some of the other monitor buttons and
> >got a message that said that the monitor was in some kind of power save
> >mode, and that I should move the mouse or push any key on the keyboard.
That
> >didn't work. However, I was able to get the monitor to work, by first
> >disconnecting it completely from the computer, and then allowing the
> >computer to boot up to what sounded like completion. I then powered down
the
> >computer, hooked the monitor back up, kept the monitor powered down, and
> >booted the computer up. After the computer had booted up completely, I
then
> >powered up the monitor and there was the Windows XP desktop. In the
course
> >of doing this there were a few occasions where things didn't quite boot
up
> >correctly, and I would get a GGGY (Green-Green-Green-Yellow) diagnostic
> >light code on the back of the computer. I checked all the IDE
connections,
> >but everything seemed in order. Despite this, I was still able to boot
the
> >computer up. But it seemed that it would eventually freeze up anyway. So
I
> >figured that I would reinstall reinstall XP using the XP Reinstallation
CD
> >in the hopes od eliminating some kind of software issue. I attempted
twice
> >to reinstall XP using the "r" command that would just repair the files
that
> >may have been corrupted. Near the end of both of these attempts, the
screen
> >would deteriorate into a "psychodelic image" followed by a freeze up. I
then
> >decided to choose the option to overwrite Windows XP over the existing
> >Windows XP installation, and the same thing happened; a "psychodelic
> >freezeup" at the end of the installation. I suspect that this last
attempt
> >may have deleted some of the configuration files for the existing Windows
XP
> >installation. Also, I suspect that I either created a new problem or
broke
> >something that was failing anyway. Now when I attempt to boot up, I get
> >nothing on the monitor, and when I look at the diagnostic lights I get a
> >YYGG configuration implying some kind of memory issue. I attempted to
reseat
> >the existing 256MB memory stick in either of the two banks, and in both
> >cases the boot process is short-lived and I get nothing at all on the
> >monitor. I have ordered another memory stick with the hopes that this
will
> >solve the problem, assuming that it is the only problem.
> >
> >Here are some of my questions:
> >
> >1)Does this sound like a memory problem that may have been just getting
> >worse for the last year? Was the GGGY code a precursor to the YYGG code?
> >Does this imply something other than a memory problem?
> >
> >2)If new memory solves the problem, how should I go about reinstalling
XP?
> >Is it possible that a virus ruined the first memory stick? Can that
happen?
>
> Your problem may be memory; nothing software-based can usually ruine
> memory; it was either made correctly or it wasn't. The problem could
> be bad memory, but it could also be a bad hard disk (windows uses the
> hard disk as memory when it runs low), a bad power supply, or
> something else. Download memtest86, and make a bootable floppy or cd
> with it installed, run it over night. If it gives you no errors, you
> can bet the memory is fine. If the memory is fine, open the machine
> up, find out who made the hard disk, download their diagnostics and
> test the drive. If the drive is fine, find a spare power connector
> and check the voltages, there should be one around 12 volts (grounds
> are the two middle black pins). If the 5v is below 4.85, you need a
> power supply, from dell because theirs are proprietary.

Thanks for suggestions. I just installed new memory, and it didn't make any
difference. I'm still getting YYGG errors with or without AGP installed.
With no memory installed I get 6 beeps. I checked the voltages and I got 12
volts and 4.95 volts. I can't really test the HDD since I don't have
anything on the monitor. The monitor is OK. I checked that on it's own. Hope
I didn't trash the motherboard or CPU.

Gary