Windows XP Professional- ACPI error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
I just installed Win XP Pro for my Laptop running in Mobile Pentium III
processor 800 MHz previously was running at Windows 2000 Pro. everything is
working fine except that my laptop auto powers down suddenly. when i check my
event viiewer i see this
" ACPI BIOS is attempting to create an illegal memory OpRegion, starting at
address 0x1000000, with a length of 0x1000000. THis region lies in the
operating system's protected memory address range (0x1000000-0xfff0000). This
could lead to systm instability. Please contact your system vendor for
technical assistance."

I checked with my computer manufacturer (Compaq) there is no Bios update for
me.

I am using Compaq Presario 1700 Model: 17XL562

Bios Provider: Phoniex Technologies

can any one help me??
 
Laptops have lots of proprietary power
management stuff in them that often requires
manufacturer-specific hardware and software
support.

If Compaq does not say specifically that XP is
supported on this machine, and does not offer
an upgrade path, probably your only option is to go
back to W2K.
 
Hi, Thanks for the reply I checked at Compaq website they do have Windows XP
as one of the OS supported on my system.

Any suggetions why is happening to me. could this be due to overheating? but
i am using a notebook cooling pad.

Alex
 
Alex-SG said:
Hi, Thanks for the reply I checked at Compaq website they do have
Windows XP as one of the OS supported on my system.

Any suggetions why is happening to me. could this be due to
overheating? but i am using a notebook cooling pad.
Click to expand...

This is one of those situations where you should go back to the
operating system that was originally installed per Mr./Ms. Green's
suggestion. There are some motherboards that just don't do well
otherwise. I had one that would simply not take an NT-based OS and
would fail with the same error as yours. Compaq may have XP files on
their site, but I'd listen to your machine instead.

The only "cure" for the error is a BIOS update and since there isn't
one, you just ought to accept the situation and go back to the OS that
worked.

Malke
 
Back
Top