Kaptain1
asked on
New Win7 install BOOTMGR image corrupt issue
Hi Experts!
I just upgraded my new Latitude E5500 to a Windows 7 64bit (bought new WD 7200rpm hard-drive and tested it for bad sectors), and it was working fast and stable for 1 day, but the next day the Windows won't boot and showed the following error message:
BOOTMGR image is corrupt system can’t reboot.
First I thought that it's a hard-drive, so i took it out and tested it multiple times using different utilities (including WD's own linux utility) throughout the day, and installed Win7 32bit on it, run Sis Sandra for 1 day (hd tests) and hard-drive is fine... so I assume that it's not new hard-drive's fault...
There were no 64bit drivers for Dell on for my laptop, so Win7 installed installed its default drivers, and Windows update found the last remaining one... Could that be an issue?
I didn't do anything unusual with the laptop... it was restarting/working fine the whole day, then start giving me these errors in the evening.
Please advise.
Thanks in advance!
I just upgraded my new Latitude E5500 to a Windows 7 64bit (bought new WD 7200rpm hard-drive and tested it for bad sectors), and it was working fast and stable for 1 day, but the next day the Windows won't boot and showed the following error message:
BOOTMGR image is corrupt system can’t reboot.
First I thought that it's a hard-drive, so i took it out and tested it multiple times using different utilities (including WD's own linux utility) throughout the day, and installed Win7 32bit on it, run Sis Sandra for 1 day (hd tests) and hard-drive is fine... so I assume that it's not new hard-drive's fault...
There were no 64bit drivers for Dell on for my laptop, so Win7 installed installed its default drivers, and Windows update found the last remaining one... Could that be an issue?
I didn't do anything unusual with the laptop... it was restarting/working fine the whole day, then start giving me these errors in the evening.
Please advise.
Thanks in advance!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
update...
I stressed and tested that new WD hard-drive numerous times and it's working fine in my Macbook now, so it wasn't the hard-drive as I thought before.
Now I bought Seagate hard-drive, and reinstalled Win7 on it, it's working fine, but Checkdisk came up once. Perhaps the problem is occuring because of standby/hibernating modes. Not sure.
Thanks
I stressed and tested that new WD hard-drive numerous times and it's working fine in my Macbook now, so it wasn't the hard-drive as I thought before.
Now I bought Seagate hard-drive, and reinstalled Win7 on it, it's working fine, but Checkdisk came up once. Perhaps the problem is occuring because of standby/hibernating modes. Not sure.
Thanks
ASKER
Exact solution is very difficult to pinpoint. All suggested solutions could be the cause. Thanks
ASKER
My worry is that why such thing may occur all of a sudden on a brand new tested hard-drive and new Win7 install. This laptop is for business use, so if such BS happens, it's very very bad for me.
Any clue why that might of happened?
Thanks again!