04-26-2009 10:43 AM
When powering pc on I receive the following message:
Award Bootblock Bios v1.0
Copyright (c) 2000, Award Software, Inc.
Bios Rom Checksum Error
Detecting IDE ATAPI device ...
Found CDROM, try to Boot from it ...(Pass) - when i have the HP Recovery disk in drive
While holding down or tapping F1, F5 & F10 keys (FYI - I've tried every Function key, ESC and DEL); I receive the last message:
"No physical memory is available at the location required for the Windows Boot Manager. The system can not continue." Just Hangs!
HP Pavillion Media Center TV m8020n Desktop PC
Windows Vista Home Premium
Motherboard: Manufacturer - Asus; Motherboard Name - P5LP-LE; HP/Compaq motherboard name: Leonite-GL8E
I have been checking several website sources about flashing; and if so, is that an option and how or perhaps just replacing the motherboard. This problem is 4 months and counting...busy person and havent been able to spend a lot time trying to fix this. Any assistance will be greatly appreciated.
04-26-2009 11:00 AM - edited 04-26-2009 11:05 AM
If it showed "Detecting IDE ATAPI device" Try F-11 at boot up and see if you can perform a recovery. If nothing, Try a new hard drive. Then go from there.
Flashing the bios will probably not help. The read-only memory ROM containing the BIOS program is protected by a checksum value as a double-check that the ROM code is correct. This checksum is compared against the values in the ROM each time the PC is booted and if there is a mismatch, this code is generated.
"The only reason for time is so that everything doesn't happen at once"
- Albert Einstein
04-26-2009 11:12 AM
04-27-2009 08:53 AM - last edited on 04-18-2016 09:52 AM by OscarFuentes
I would advice you to replace the CMOS battery and resetting the BIOS to factory default.
You may look into the following HP document:
04-27-2009 09:26 PM
04-28-2009 04:30 AM
dmhoo29, the HP document provided in the previous post talks about the same issue.
Whistle, if the issue still persists, the PC may need to be serviced for motherboard issue or BIOS may have become corrupt.