Digerati
In Runtime
- Messages
- 239
- Location
- Nebraska, USA
If it does this within 5 seconds, the boot process hasn't had time to come close to completing POST and hitting the hard drive. So I don't see how it could the drive as looking for an OS is way into the boot process. I would suspect RAM, or the CPU, or the graphics (since loading basic - VGA- graphics is done early too) . Try one stick of RAM at a time.
However, if you normally heard a single beep (which typically signals a successful POST) and now you hear no beeps to indicate a RAM, CPU or graphics failure, that could also indicate a motherboard issue. So with that, I agree also with the repeated suggestions above to reset the BIOS.
However, if you normally heard a single beep (which typically signals a successful POST) and now you hear no beeps to indicate a RAM, CPU or graphics failure, that could also indicate a motherboard issue. So with that, I agree also with the repeated suggestions above to reset the BIOS.