Stable?

[DKlein]

Alright I ran Prim95, SETI@Home, and 3dMark03 for 55 hours this weekend. Got back and found that everything had worked, no Prime95 errors, no blue screen, temps were 50C (about normal for full load), just Windows XP was a good bit laggy. So I closed everything up and went to shut down Windows, and as it was shutting down I got that good old blue screen. Would this system be considered stable?

I kept my old motherboard and HDD and just switched the CPU, RAM, and CD-ROM drive. Afterwards Windows made me reactivate it, which was odd. Do you think I might just need to do a reinstall?

Specs:
Abit NF7-S r2
AMD XP-M 2600+ 2.55GHz@1.8V (42C/49C)
OCZ 2x512MB PC3500 (2.5-3-3-7 @213MHz)
nVidia GeForce3 Ti 200
Maxtor 80GB HDD
Windows XP Pro

 

[Avalon]

You typically only need to reinstall if you put in a different motherboard. I'm not sure why you got the BSOD. Perhaps it was just a random glitch. Try overnighting Prime, Seti, and 3dmark, and in the morning close them out and try to shut down again and see if it will BSOD. If it does, something is amiss, but I'm tending to think your system is stable and it was just a quirk.

 

[DKlein]

Alright. Any clue as to why I had to reactivate Windows?

 

[BonzaiDuck]

XP "activation" takes hardware ID numbers from ten -- or up to ten -- components at the time of activation. It then uses a hashing algorithm to convert all the data to a single number.

When XP does "activation" checks on hardware (for Windows Update visits, for instance) -- it samples seven out of the ten. If you switched your CPU, RAM and CDROM drive all at once, that may explain why you had to re-activate. I think the characteristic used about RAM is less specific -- it is a number representing "memory size range".

.

 

[DaNorthface]

you got almost the same rig as me.. anyways the blue screen could be because you didn't reinstall windows..