Install a New Motherboard .. Win XP Pro SP2

[vrbaba]

Havent done it in a while... 3 yrs or so. But if I remember correctly, it wasnt a plug and play thing.

My existing mobo is corrupted (i think) and wanna test a new one. (It keeps rebooting randomly without any BSOD or error messages). It had an Antec PSU which went bad, and guess is that it screwd up the mobo or some other component. Its not the RAM (tested), and doesnt seem to be the video card or cpu.

Ok, that said...

Will i have to repair windows? What exactly does it entail?

any suggestions or help is welcome.

 

[MagnusTheBrewer]

Installing a new MB in an existing system with XP will most likely require a repair/install of Windows. Also, Windows will need to be reactivated. The repair/install just requires putting the OS CD in the drive, rebooting and, selecting that option. I'm assuming you verified the previous MB is bad and not virus/spyware, heat issue or, failing hdd.

 

[vrbaba]

i have verified that its not a heat issue and not a RAM issue. It cannot possibly be a virus issue (that would be just weird).
So question is:

How can i verify that it is/not a failing hdd issue??

Also, a repair instlal of windows will leave the programs and files intact on my install partition, right?

 

[Abix]

Goto the website for the manufacturer of your HD. Under the support section, there will be a diagnostic tool(SeaTools,DFT,etc). Throw it on a floppy and test the HD.

 

[MagnusTheBrewer]

Go to the hdd manufs site and DL their utility to check the hdd.

Yes, a repair/install will leave the programs and files intact.

A virus or spyware/malware problem could indeed cause 'random' reboots and is not 'weird.'

Driver issues have also been known to cause this problem.

 

[Abix]

A virus/spyware/malware problem *could* cause "random" reboots, but then again it *could* also cause your computer to dial a phone-sex hotline and have crazy phonesex for 45 minutes. Which is to say, that its much more probable that a virus/spyware/malware problem would simply slow a machine down considerably and not give it "random" reboots.

Personally, Id check the HD and the RAM(use MemTest86). If theyre good, and you want the machine up and running soon, then just reformat the HD and start from scratch.

 

[MagnusTheBrewer]

Originally posted by: Abix
A virus/spyware/malware problem *could* cause "random" reboots, but then again it *could* also cause your computer to dial a phone-sex hotline and have crazy phonesex for 45 minutes. Which is to say, that its much more probable that a virus/spyware/malware problem would simply slow a machine down considerably and not give it "random" reboots.

Personally, Id check the HD and the RAM(use MemTest86). If theyre good, and you want the machine up and running soon, then just reformat the HD and start from scratch.

Please read the entire thread before replying. Checking the hdd has already been reccomended and the OP has already checked the ram.

The point of the thread is to determine if the old MB truly is the problem and to try and avoid losing files and programs.

 

[vrbaba]

well...considering...

My PC has been absolutely virus/spyware/malware free forEVER pretty much. I take good care of it and know wht i am doing. after moving it to my new apt, I start it up and it starts having this problem without doing anything, i would hardly say its cus of spyware.
Also, investigating led me to go to the PSU and found out the bad caps problem with Antec. Replaced the psu, and now it still does that randomly... leads me to believe its still some hardware issue. most likely bad current/voltage being sent to the mobo or other compoenents.

My drives are Maxtor ... and looking at their website as i write for the diagnostic program.

The other thing is i have a Fusion HDTV 5 lite tv tuner, which could have driver issues, but my computer shows the symptoms even when i remove the card (along with my other pci sound card).

Will report back in after running hard drive diagnostics.

What are the chances that a repair install doesnt work, and I may have to reinstall Win XP completely (in which case i would need to spend a LOT of time looking for things to backup). Although every "file" i would need is not on the main partition, but will still need to look around. (which i dont wnana do)

 

[MagnusTheBrewer]

Having built and upgraded quite a few rigs, I would say chances are very good that the repair install will work. However, if the repair install does not work, chances are exremely small that you will be worse off than before. Also when you removed the tv tuner card and sound card did you also remove their drivers?

 

[vrbaba]

Ok, so tried the Powermax, and the drives seem fine. tests passed. Also, extended test on my main drive passed too.

Now, I am back to the mobo issue.

MagnusTheBrewer, i did not uninstlal the tv tuner cand sound card drivers. But they have been working well for 8 straight months. I am not inclined to try that unless there are even slight indications that might be the problem.

So, i guess i have no choice but to try a new mobo. :/ I hope repair windows install works as expected.

Is there ANY way before/after changing the mobo that I can figure out what exactly went wrong with my current motherboard ??

 

[John]

[*]Check your event viewer for any issue(s) that are causing you to reboot.
[*]You can also try unchecking 'restart on error' in the system properties.
[*]FWIW you can still pass Memtest 86 and have an unstable system.
[*]How hot does your cpu get under load?
[*]When is the last time you reapplied thermal compound and verified the heatsink installation?
[*]Try running Stress Prime for 24 hours and see what happens.
Stress Prime 2004 - single core
Stress Prime 2004 - dual core

 

[vrbaba]

Originally posted by: John
[*]Check your event viewer for any issue(s) that are causing you to reboot.

wha?

[*]You can also try unchecking 'restart on error' in the system properties.

I guess i havent been there. someone point me to it

[*]FWIW you can still pass Memtest 86 and have an unstable system.

Havent ran memtest, but tested with a fresh new ram. well, they both could be faulty. Again, there are NO BSODs, which makes me think its NOT a ram or cpu issue.

[*]How hot does your cpu get under load?

Temps are stable. I had it overclocked (35-40c), but since the problem started, its running at normal (34-36c)

[*]When is the last time you reapplied thermal compound and verified the heatsink installation?

That was the First thing i tried since the problem started. few days ago.

[*]Try running Stress Prime for 24 hours and see what happens.

Well, again, why reboots without BSODs if it is the CPU thats faulting. Also, i havent played games in a while, and the cpu barely gets any constant load. Will try that though

Stress Prime 2004 - single core
Stress Prime 2004 - dual core

 

[vrbaba]

bump