Jump to content

Recommended Posts

Posted (edited)

We have a desktop that won't boot to Windows, the network or any external device, including bootable usb stick (so can't flash the BIOS). It hangs on a black screen with E7 in the lower right corner about 10-15 seconds after pressing the on/off button. There are no beep codes. I can get into the BIOS but I can't boot into safe mode, I have reset the BIOS to default, swapped out the HDD and SATA cable, changed the memory and it has onboard graphics. Has anyone come across this problem and if so did you resolve it? The computer is out of warranty. I will try swapping out the power supply and processor next. Anyone have any other ideas?

 

Thanks

 

Sue

Edited by ict_adeyfield
Posted

Well I assume that this is an Intel motherboard, the E7 message is an error code for "Waiting for user input" (not helpful I know) and can be caused by a large range of faulty components.

I see you have tried swapping out a number of things but also try things like the CD drive and I have also read that someone got past this by booting without the monitor attached! Also read reports of faulty CPUs causing this.

Posted
Well, I have tried all of the above, it will not do a BIOS recovery, have swapped out every component, tried a graphics card :frusty:. Just don't know, so I think I'll just replace the motherboard, that'll fix it!! :noidea:
Posted
Seen this quite a few times lately. Sometimes a memory slot clean and reseat gets round it. Check for BIOS update as there is a know issue with the Intel D945GTP board, I have had to update a few of these.
Posted
Well, I have tried all of the above, it will not do a BIOS recovery, have swapped out every component, tried a graphics card :frusty:. Just don't know, so I think I'll just replace the motherboard, that'll fix it!! :noidea:

 

Ick, Intel boards, I'd be looking somewhere else for relibility given my experiences with them. Maybe ASUS (full ATX) for something a little more reliable.

Posted

I asked around the office and someone has had this before. In their case it was that the hardware vendor had forecefully applied an incompatible chipset to the board. So in that case the board was being reported incorrectly by board id tool.

 

In short it's a faulty board.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...