Home

Advertisement

Phil - [entries|archive|friends|userinfo]
Phil

[ website | Pixelnation.cc ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

[Apr. 27th, 2008|12:46 am]
Previous Entry Add to Memories Tell a Friend Next Entry
Bought my computer (or rather, its parts) today.. I've got it screwed together and all, but I can't seem to get it to boot properly. Firstly, it says "Intel CPU uCode loading error", which I think might resolve itself if I update the BIOS, since the CPU (Duo E8400) is newer than the MB (P5K-VM). Besides, the CPU stats in BIOS recognize it perfectly.
But it doesn't seem to want to boot from the Windows CD... I don't even think it's recognizing the DVD drive properly. I've got my old Slimdrive hooked up to the IDE controller (no jumpers, Master port), it's spinning but not reading. Any ideas? I tried to boot it off my old HDD on USB, but it stalled and rebooted at after exiting the black Windows boot screen..
I'm going to do a more extensive search tomorrow, but first I need to go to sleep cause I have a rather important field competition in the morning... Anyone hear of problems like this before, let me know.
linkReply

Comments:
From: (Anonymous)
2008-04-27 01:07 am (UTC)

Shin:

(Link)

Does your BIOS recognise your DVD drive?

and... where does it say CPU uCode Loading error?
I think your mobo can't take the new generation E's X3; but if you update bios it should be perfecly fine -> that is if you can get a floppy in or a bios from somewhere @w@

Though it might be Shin's opinion, but when a computer boots up it's really important that the system build that that windows is installed on doesn't have critical hardware elements that are missing {Sometimes using an old windows partition to boot a new Mobo/system can corrupt your windows -- though I don't think its always the case, but its a suggestion}
[User Picture]From: [info]phil_knall
2008-04-27 09:27 am (UTC)

Re: Shin:

(Link)

Ya, I was using my laptop's hdd anyway, so there's no problem with the windows partition getting bombed. Anyway, problem solved anyway, it was the jumper settings on the ATAPI drive.

Advertisement