Question Older Win installs go BSOD on old ASRock MB

[stagekraft]

Hey All,

Long time listener, first time caller...
Old and retired, just keeping busy out in my home workshop.
I'm trying to resurrect an old multi-track recording setup I used many years back (have since gone digital).

My setup consisted of two M-Audio Delta 1010LT soundcards, each having 8 analog audio inputs and outputs.
giving me 16 tracks to work with.

I had used these cards with a cheap DAW program called EnergyXT, and successfully installed it in both windows and linux environments.
But the windows version was easier (for me) to work with.

I pulled out the old machine I had used back in the day, as I need 2 PCIX16 slots for the old soundcards.
This PC was built around an ASROCK MB (Presler Conroe Dual Core Something or Another).

I dug through my archives and found the old hard drives with the linux os I had used, as well as a win xp setup.

Every time I tried to boot up the Win xp, the pc would go bsod halfway through boot.
But, will boot up the linux drive every time.
I tried shuffling the RAM around thinking windows saw something it didn't like (but linux didn't care), but no change.
So thinking there was a problem with that HD, I pulled out some old installation media, both xp pro and win 7 and tried a fresh install onto a clean hard drive.

Same results, half way into any install, bsod...

Dug out a pile of old HD's, a mixture of old xp and win7 (and I expected windows to balk somewhere because the install was not originally on that machine, but same deal, every hard drive I tried to boot went bsod...

any suggestions please?

JohnR

 

[TerryLaze]

Linux stress command With Examples - GeeksforGeeks

A Computer Science portal for geeks. It contains well written, well thought and well explained computer science and programming articles, quizzes and practice/competitive programming/company interview Questions.

www.geeksforgeeks.org

If linux runs I would run a stress test on it, just to make sure that it actually does run.
Otherwise it could be crashing due to a driver issue, the mobo might need a driver to see the hdd.
If you find the full model of the mobo you can go to their site and look for sata/chipset driver of a "floppy" driver (floppy sized archive that would be used to load drivers before XP install)

 

[stagekraft]

good point that there may be something wanky with the bios.
now that I think about it, the first time I fired this old pc up the time/date was wrong, so I replaced the battery.
perhaps something else is amiss with the bios settings for this mobo?