problem?

[falcone86]

i recently upgraded my ram and graphics card. i wasnt happy with the performance so i returned them and swapped my old stuff back in. ever since then, the computer will freeze at random points. ctr alt delete doesnt work it doesnt respond to anything. any suggestions on what it could be?

[ShaRkey¬]

what mobo are you using?

[Sylvander]

"any suggestions on what it could be?"
Windows [which version is installed?], when it is installed onto the HDD, is matched to the hardware that was found by Setup at that time.

If you swap hardware on Windows [e.g. the graphics card]...
If you are lucky:
Windows will cope, and still be able to run, and will detect the new hardware, and ask you to supply the driver for that new hardware.

But if Windows cannot cope [because the change is so fundamental, as in this case], it is unable to do the above, and simply doesn't function.
In this situation you would need to...
Either:
(a) Restore an image backup made when all was well and this present particular hardware setup was also then in place.
i.e The hardware now is the same as the hardware then.
OR...
(b) Run a REPAIR installation on the Windows installation now existing on that HDD.

[falcone86]

ill give that a try thanks.

[Sylvander]

How to Perform a Windows XP Repair Install (http://www.michaelstevenstech.com/XPrepairinstall.htm)

[shel]

Hi i'm new to the forum so if my thread is in the wrong place 4give me my problem is i accidentally hook another HD to my pc also set 2 master now i get a drwatson error report wen i try 2 click Accessories i hav hiden files that dont respond wen i try 2 show them and everytime i startup i hav 2 reinstall alcohol120 i did a windows repair that did not help and my xp ser pac 2 cd is demaged i dont hav internet at home yet wat do i do?

[falcone86]

i tried the system restore. seemed to make things worse. so my only option left is the windows repair. just need to find my xp cd.

[Sylvander]

"i tried the system restore. seemed to make things worse"
Was the hardware now connected also then connected, when that "Restore Point" was made?
You wouldn't want to restore a software system that doesn't match the present hardware.
Do you have a restore point made when the hardware was the same as now?
This kind of thing is why I like to make image backups and MOST IMPORTANT...
MAKE A WRITTEN LOG of all relevant info like...
a. HARDWARE CHANGES.
b. Backups/Restores of images.
c. Installs/Uninstalls [of updates, programs etc]
d. Significant configuration changes.

If/when I pick an image to restore...
It restores GLOBALLY [everything on the partition], so [on the Windows partition] Windows & Programs & configurations will all match each other. Only the hardware could be a mismatch, and I'd keep an eye on that situation.

I never use Restore Points, so don't know the detail of how that system works.
Does it work "transparently"?
i.e. Does it allow you to see what is being done, so are you aware of what's what?
Do you know WHEN it's making a restore point?
Do you have control over that?
Is any easily understood record kept like my log?
If Windows doesn't work the whole thing fails doesn't it?

"my only option left is the windows repair"
Hopefully, that will straighten up Windows.
However, I much prefer restoring an image, because...
It's quick [takes minutes to complete] and SURE.
Provided the hardware matches and isn't faulty it is BOUND to quickly produce a fix.
So when YOUR system is once again working well, begin making image backups.

[Sylvander]

To give you an idea...
Here are the latest entries in my log:

2007
June 10 | Restore May 29 IforD Backup of C: D:
June 10 | Installed update for Firefox 2.0.0.4
June 15 | IforD to N: of C: D:
June 18 | Installed "winMD5Sum"
June 18 | Erased "MD5Summer" folder & program
June 19 | "Acronis TI" to N: of "Mandriva Linux 2007" partition set
June 19 | IforW image to internal partition G: of external partition P:

Notice that if the images [of C: and D:] made on June 15th were restored...
Then the install and erase of the MD5 programs would be reversed/undone and things would be put back as they were before the change.
All minor updates [of AVG] not listed would also be undone, but these would be detected by AVG etc and the update automatically re-done.

Once you become aware of this kind of thing, then the kind of problem you are now experiencing would be forestalled.
You just would not allow it to arise. :)