How would I check that the power supply is freaking out? Thanks for the
ideas, both of you. I will see if Norton AV is causing the problem, but
something tells me it's some sort of memory leak or RAM issue. My stuff is
fairly old, and it might be time for an upgrade. I'll check to see if there
are any memory leaks in my task manager when i get home, because I'm positive
that it will be glitching out when I check it out.
Any programs that allow me to diagnose my RAM? If it helps at all, this
problem only happens on Vista. When I downgrade it to XP, the PC runs
completely fine. Perhaps one of Vista's features is sucking up memory?
"JW" wrote:
> Your power supply is possibly overheating and having trouble putting out
> constant voltages and when you shut down the computer and then turn off the
> computer in the back the power supply is resetting itself so that the
> problem does not occur again till it overheats again. I have had a similar
> problem on occasion with my power supply not starting up properly on a boot
> if I did not unplug it in the back so that it reset what ever problem caused
> not to supply the correct voltages at boot time.
> "Ken Adams NSA" <Ken Adams > wrote in message
> news:25E1588D-FCD6-4F65-BE73-...
> > Hey all,
> >
> > After searching the 'net for months, I have yet to come up with a solution
> > to my dilemma. Here's the deal. I have a Vista Ultimate 32-bit desktop,
> > running an Intel 3.0 GHZ CPU and 1 GB of RAM. Everytime I leave my
> > computer
> > on for hours (typically overnight) it starts this odd, stuttering
> > behavior,
> > where EVERYTHING stops for a split second, every second. Music, mouse,
> > video,
> > EVERYTHING. The entire computer just skips. The only fix I have is turning
> > the power off on the back of the computer, then unplugging and replugging
> > the
> > power cord in. I am positive this is not a great thing for my computer,
> > and I
> > need to find a solution before any real damage is done. This only happens
> > after a long time, and is not after a specific time (i.e. after 3-4 hours
> > EVERY time). Any suggestions? I was thinking it could be the RAM, but I
> > don't
> > know.
> >
> > Any help would be greatly appreciated!
>