I’ve reinstalled Windows Vista probably 20 times now, and two of those times it worked! Then ran into a issue with a chipset on the board and cause the whole thing to come crumbling down, restarted the whole OS install process and then ran into a blue screen issue, restored to a restore point and started seeing the issue all over again.
OS - Vista Ultimate 64 bit
CPU - AMD Athlon 64 x2 6400+
MoBo - ASUS M2A-MVP (on BIOS v0511)
RAM - (4x2GB) OCZ 800mt/s C4 Reaper
SSD - (changing soon) SanDisk 5000 32GB SATAI (waiting on OCZ 120GB SATAII drive to arrive)
HDD - Western Digital 1TB Black
I think that’s enough detail.
Loading the OS;
So, I can’t get my SATA optical drive to work. I have a USB optical drive, but for some reason either the CD Rom works, and the drives aren’t seen, or the drives are seen, but the USB optical drive doesn’t work. This may be a large part of the issue!
Pop the SSD in a older laptop w/ Intel Centrino CPU. Start the Windows Vista install, once it gets to the first restart point after preparing files, installing updates and features I power down the laptop, pull the drive, put it into the computer, and start it up to where it finishes the install.
Has it worked;
It worked two times since I did the above method of pulling the drive after the install. Except I ran into two issues;
- I installed a device driver which caused constant GPU driver crashes. (went back to fresh OS install)
- Started getting random blue screens, rolled back to a good restore point, but all of a sudden started seeing the 2nd CPU core being pegged once again.
How can I track down what hung/zombie process is pegging the 2nd core? Windows Task Manager shows NOTHING is using CPU time, I can’t get a command prompt string to show me PID’s and CPU usage, so I’m kind of stuck in a perpetual loop here.
Why Vista? It came out in 2007 like all the other hardware I’m using (aside from OCZ SSD and WD HDD) which is the whole point to the retro rig. Plus the hardware I’m using is no longer supported with newer OS’s, and can’t get older drivers to work.
Thanks for any possible help!
SOLVED - some how issue ended up being the chipset on the board. I replaced the motherboard with a different one, and issue is now gone.