cancel
Showing results for 
Search instead for 
Did you mean: 

able to post bios but cannot find boot device

watermoccasin
Level 7
Hi,
I just installed my new CrossHair V & i am able to get into the bios. But i cannot boot into windows.
I do not suspect ram becuase my Dram light is not on & bios says mem test is ok.

I get a message about not being able to find a boot device. Another message i get is something about intel something or other v1.3.51(im at work i can post the full message later) & something about LAN adapter config is corrupt or not initialized boot cannot continue.

What i find wierd is that i can see all 3 hard drives & cd drive in the bios & can change the boot order, but it cant boot. Also sometimes it will try to boot windows(ill see the little windows graphic & load bar) & then fail & resume the boot loop with the above messages.

I will be testing to boot up with a spare hard drive from another pc & test my current drives in another system as well.
Thanks in advance,
Sean

My build:
Antec DF-85 case
Crosshair V mobo
Amd. PhenomII x6 1090t
8gb(2x4) corsair vengeance ram
2 ati 5830 gpu's in crossfire(one sapphire,one xfx)
Wd 600gb hdd
Wd velociraptor 10k rpm 150gb
Crucial 60gb ssd(boot drive)
Xfx black edition 850w psu
2,237 Views
21 REPLIES 21

xeromist
Moderator
Try removing all but one stick of memory and see if that makes a difference. People have been having problems with memory configurations on that board (generally solveable with tweaking) so it's worth a try.
A bus station is where a bus stops. A train station is where a train stops. On my desk, I have a work station…

I'm pretty sure i did try that already & in the slot farthest from the cpu also. I can try again though.
Any other thoughts? What confuses me most is that the devices are listed in the bios & but it says it cant find a boot device

chrsplmr
Level 18
Its booting into the bios..

Try this...[advanced] [sata] [ide]...what drive is os..
have you moved os to ssd from a different system?
what is plugged in exactly?..all that?

or is that bios corrupt, guys?

watermoccasin
Level 7
Quick bactstory...built the system in march. With an msi motherboard, i didnt like it/it was acting up. So i got the crosshair v for my birthday. I didnt change anything else in the system since its build. Os is on the ssd & has been on the ssd since i built the system. It was new for this system.
I have tried with just one gpu & less hard drives also
Was that the kind of info you were asking for?

I believe it is bios version 0404, im pretty sure i saw it somewhere.im not sure if that helps at all

NemesisChild
Level 12
Since you built your sytem in March, I would have to assume that the MSI board was not a 990 chipset.
If you're migrating an HDD with OS from an older chipset (even from the 890), it's unlikely that Windows will boot from the CH5F or any 990 chipset board.
I ran into this problem when I transfered my OS HDD from my 890 CH4F to the CH5F, I had to do a complete reformatt.

Just re-read your post, did that MSI board have an Intel chipset/CPU?

If so, you definitely can't migrate a HDD with an Intel chipset OS to an AMD chipset w/o reformatting.
Intel i9 10850K@ 5.3GHz
ASUS ROG Strix Z490-E
Corsair H115i Pro XT
G.Skill TridentZ@ 3600MHz CL14 2x16GB
EVGA RTX 3090 Ti FWT3 Ultra
OS: WD Black SN850 1TB NVMe M.2
Storage: WD Blue SN550 2TB NVMe M.2
EVGA SuperNova 1200 P2
ASUS ROG Strix Helios GX601

watermoccasin
Level 7
That is a good point, i will look into the msi chipset, i forget which it was. No it was not intel, it was(& still is) the amd 1090t. I may upgrade to the 1100t in the near future just for kicks. If it is just a matter of an older chipset to a newer, would a simple reformat do the trick, or is there anything else i might need to do?

*edit*
Just looked up the old motherboard, the chipsets from the msi are :
North bridge:890fx
South bridge:sb850

NemesisChild
Level 12
Since the MSI board had the 890 chipset, then you will need to reformat when migrating to the 990 CH5F.
I suggest updating your bios to 0705 prior to reformatting/installing the OS.
Once completed, it's always best to clear the CMOS after a bios update.
if you still get that Intel Lan message, check he bios options for it, but make sure that it is not disabled.
Boot into the OS, then install the latest Intel LAN ProSet driver from Intel's support website.
Do not use the Intel LAN ProSet driver that's on the ASUS CH5F disc or from the ASUS support site.
Intel i9 10850K@ 5.3GHz
ASUS ROG Strix Z490-E
Corsair H115i Pro XT
G.Skill TridentZ@ 3600MHz CL14 2x16GB
EVGA RTX 3090 Ti FWT3 Ultra
OS: WD Black SN850 1TB NVMe M.2
Storage: WD Blue SN550 2TB NVMe M.2
EVGA SuperNova 1200 P2
ASUS ROG Strix Helios GX601

watermoccasin
Level 7
Ok, so i updated my bios & reformatted & i seem to be running ok.
Butm i still get the cannot find device message & then the Intel lan message...then it goes to windows. So it says it cant find a boot device...then boots off it?odd.
Now for that lan message...3140

Im thinking my lan device may be bad? In device manager it says the device cannot start (code 10) & when a lan cable is plugged in, no lights go on.

Retired
Not applicable
Glad its finally running I had to reformat when I migrated boards as well. I now make it a habit to reformat when new motherboards are in list.

Some quick questions. Are you only able to boot into safe mode only or regular windows as well? Are you booting off LAN? I know this intel LAN controller seems buggy even with the latest drivers windows reports via Event viewer quite often "Network link is disconnected" lets see it has happened 1 time in the last hour, 2 times in the last 24 hours, and 43 times in the past 7 days ^^; funny part is I don't D/C playing games but have notice some odd errors such as when I try to download some games via their down-loaders errors that seem related to sudden loss of connection occur.

Anyway I found this I don't know if it might work and I would look more into exactly what the utility does but http://h30434.www3.hp.com/t5/Notebook-Hardware/Boot-Agent-GE-v-1-2-28-PXE-E05-cannot-continue/td-p/1...

For quicker instructions search "Wow, thanks for the prompt reply Cadeeja! I figured it out and just went for it as you said. The proboot fix worked great!!!" with Ctrl F.

You may be able to just lookup Intel Boot Agent Utility on its own rather than using proboot. Hope you get it working.

Read the bottom paragraph first it will mention some other possible fixes and reasons for this. The above fix involves setting the NIC EEPROM to default settings.