Bad axe 1 memory issue i think

[Justintime]

I recently built a system usin an older bad axe 304 board, problem is when the pc is turned on for the first time, everything boots and windows starts to load but the boot screen is veeeeeeeery slow i.e the blue bar barley moves then wham! bluescreen, resets itself, loads up again this time with the windows has been interrupted error etc.. then proceeds to load fine if you click start windows normally or leave it to countdown. Tried everything, even have the memory set to super conservative timings and underclocked to 266Mhz (its crucial PC5300 333MHz). A bit annoying but it seems fine after it resets the first time. Any ideas?
Dangit and its the wrong forum please move if not too much trouble
TIA.

 

[Corasik]

That could be a lot of different things, First thing I would try is downloading and installing the latest bios. After installing the bios, try downloading and installing all the lastest drivers, including the motherboard chipset driver.

If your using SATA drives in RAID, or AHCI mode, then make sure you have the lastest drivers for these as well. How many hard drives/CD/DVD drives do you have, if you have more than one, its possible the PC is starting to boot before the secondary drive has had time to powerup fully. There is a bios option to add a short delay before booting to ensure all the SATA/IDE devices are fully powered up and ready to go before booting windows.

While windows boots, it initialises a lot of hardware, so try disabling everything in bios... disable floppy controller, serial/parallel ports, onboard sound, onboard lan.. etc etc etc.. Remove any PCI expansion cards. You could even remove all bar 1 stick of ram.

At this stage your PC should just be a total minimalist system, just enough hardware to boot windows. If this doesnt get you into windows without a glitch then you'll need to take even more drastic measures... however if (with a bit of luck) windows boots normally and consistantly, you can then reinstall your full compliment of ram, reboot & test, start reactivating the hardware you disabled one item at a time, each time rebooting and testing and if at any point the error returns, at the very least you will have found out what hardware is causing it.

 

[Justintime]

Latest BIOS didn't solve it. Changed the memory to some Geil stuff and that did the trick I tried everything you outlined before posting here, even tried another hdd and an IDE one etc.. weird issue this but seems sorted.