[plato]

it is a hradware prob but also softwre prob.

microsoft blames the hardware (bios) but in fact it is XP that is at fault blocking 0x70 and 0x71.

i am talking about event ID4, and 5.


ACPI BIOS has attempted to read/write to protected memory sector 0x70 and or 0x71.

WTF?


there is nothing one semengly can do to fix this ***** of a problem.

-got newest bios

Abit BE6 II v2.0
celeron 566
512MB RAM
RADEON 8500
IBM GXP 60 60gB

[Xiven]

If all else fails, try disabling ACPI. There are countless topics on this message board that explain the process in detail.

[BladeRunner]

The fault does not lie with Microsoft.
Microsoft publish the specifications for ACPI, it is then down to the BIOS writers to make sure they meet these specifications.
The BE6-II is hardly the newest motherboard available and my guess is that no new fully ACPI compatible BIOS has ever been released for it.

If it was an MS issue everybody would be getting the errors you list, they aren't.

[plato]

well the board was the #1 board about a year ago. My board is diff from BE6 II. It is essentially BE6III,,, BE6 II v.2.0 as they decided to call it, but who cares.

so "hardly the newest"... we r in deep **** if we start thinking like that. I mean if it was 2 years old or 3 i would say OK, but c'mon... this is outrageous.

don't wory i am getting new sys.

thanx

[BladeRunner]

It is very possible that the ACPI specifications changed between Windows 2000 and Windows XP although I'm not aware of any changes.
If changes were made Microsoft would not have kept them quiet, they will be publically available for the very reason that motherboards would require BIOS updates.
The ball then firmly rests in ABit's court, it is their job to speak to AMI, Phoenix, Award etc and ask them to make the relivant changes to the BIOS for a new release.
Alas, most companies cannot be bothered to offer support on anything but their latest models.

[Dirty Harry]

I recall having ACPI up and running on a Abit BE-6 (rev 1) board, but not on XP. On my KG7, I have a vague feeling that ACPI is not working quite as well under XP as under W2K, but it could of course be some tweaking that is causing the issues

Plato, if you are just seeing this in your system log, without other problems I wouldn't worry about it.


H.

[plato]

thanx for ur coments.

all is well.

after fully testing everything it turns out my processor is dying and is to blame for all problems, well almost all.

i did not select PnP OS in bios.

[BladeRunner]

PnP OS in the BIOS should be set for No under both Win2k & WinXP.
I'll edit this message later if I can and add the URL to the MS Knowledge Base article on said subject.

[plato]

ohhh.


thanx. that is strage isn't it?

[BladeRunner]

Extremely.
There is a reason for it, but I cannot for the life of me remember what that is.
Must try to find that knowledge base article.

[Dirty Harry]

Its long ago, and I'm not sure I got this right. Anyhow I've understood that this is due to some PnP standard / white paper which Bill decided wasn't that cool at all, at the end of the day. So he made his PnP OS to work a bit differently.

Now, my understanding is that if you set PnP OS to enabled, the BIOS will try to give the OS an early start by assigning some resources to the very basic stuff, videocards etc. MS decided that they do this better, so their OS will (maybe) attempt to reassign them. If you set PnP OS to disabled, the OS does it all, which is what MS wants.

Anyhow, When you use a MS (PnP) operating system you should definately set the PnP Operating System in the bios to disabled or no sorta because the OS is more PnP than the BIOS. Confused ? Never mind, just set it to no.

As BladeRunner implies, this is (was) MS recommendation. I've seen that knowledgebase article too, but it was nowhere to be found when I just looked.

H.

[CyberGenX]

Just change your setting in Device Manager to read Standard PC instead of ACPI. Unless you absolutely have to use Stand By. I have always, with the exception of NT 4.0, used PNP set to YES. Some devices are not detected properly by the OS with it set to NO.

[rjs82vette]

I made a DOC file that explians how to disable ACPI and manually assign IRQ's it has screen shots and more... email me and I'll send it to you....

[BladeRunner]

At last!!!
Got it, try this knowledge base article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314068

[rjs82vette]

Actualy I have made a DOC that takes you step by step on how to disable the ACPI and issign IRQ manualy weather you are doing a new install or you just want to change an existing install....

The article referanced above says that you have to reinstall the OS but I have found that this is NOT the case... I run all my PC as standard PC's with the ACPI off and have no problems with any of them other that the cant hybernate or turn themselves off... I leave my systems on all the time and the ones that are turned off are my childrens and they just hit the power button.....Hard shut down!!! Agghhh bad for the OS!!! I dont know my system crashes more than theirs.....Maybe because windows doesnt get to save all the setting that they have changed....I understand that the article says that windows can do this IRQ sharing with everything on IRQ 9...but all of my hardware is not the latest and greatest....so it ended up having alot of conflicts....during all my years as a computer geek I have been taught that IRQ sharing is BAD and have dealt with IRQ conflict and I am sorry to disagree with MS but I still have IRQ conflict...and I have found a way to fix them....I really dont see the need to put share an IRQ when i have 3,4,5,7,9,11 open and free...Irq sharing would be fine if it happened after all of the IRQ were used... But it doesnt it just sticks 10 devices on one IRQ...so that poor IRQ end up in a circle jerk with all these devices pushing it around... I still think that picking on the single IRQ is a bad thing...

[rjs82vette]

also the PNP OS setting in your BIOS does this

if set to yes or enable - the bios only assignes IRQ's to the hardware that is required to boot....IE hard drive...
and allow the OS to assign the rest...

if set to no then the BIOS assigns IRQ to all hardware that requires them... Which windows XP then reassigns to IRQ 9....

[Dirty Harry]

Right,
turn OFF ACPI, use a ISA Video Card and switch back to 5,25 inch floppies. WTF ?

There is no point with current PnP hardware to stubbornly trying to assign IRQ yourself. Unless you have very old or very exotic hardware, you should of course install XP with ACPI if you are planning on using any power saving options. If you install from scratch, you have to resort to mild violence not to install ACPI.

H.

[BladeRunner]

When Windows 2000 was first released to the public these forum's were immediately filled with threads along the lines of "All my devices are on one IRQ, how do I sort?" & "WTF is up with my PC?".
However in 90% of these cases the user wasn't having a problem, but the cosmetic view of all devices on the same IRQ "freaked" them out.

As long as you have the hardware then ACPI is one of the best things ever to come from Microsoft/Intel.
No more limited by 16 physical IRQ's.
No more have to shift things around whenever I wanted to add new ahrdware.
No more sitting with pencil & paper for hours on end trying to work out which devices could use which resources, which could share, which couldn't.
It's now just plug everything in and go.

I'm sure people must be aware that although all hardware devices appear to be using the same physical address (usually IRQ 9) they are in fact using virtual addresses.
For example my NIC is running on IRQ44 if I remember correctly.

If somebody has older hardware or more than one ISA card then I can see the logic behind choosing "Standard PC".
You are using legacy devices and should set your OS to run in "legacy" mode.
However if you've got relatively new hardware then ACPI has to be the way to go, purely from it's simplicity.

[rjs82vette]

Quote:

Right,
turn OFF ACPI, use a ISA Video Card and switch back to 5,25 inch floppies. WTF ?

There is no point with current PnP hardware to stubbornly trying to assign IRQ yourself. Unless you have very old or very exotic hardware, you should of course install XP with ACPI if you are planning on using any power saving options. If you install from scratch, you have to resort to mild violence not to install ACPI.

H.

1. if you disable ACPI you dont have to assign IRQ yourself, your PNP BIOS and Windows can still assign IRQ and most of the time this works fine.... But it allows you to change them if you need to... and it allow Windows to assign your devices to IRQ's other than 9..

2. In the realm of PC's any thing older than six months is old and alot of people are installing XP on 400 or 500Mhz machines that may not be 100% compliant with ACPI... (IE E machines are a prime example)

3. ACPI and APM are differant if you disable your ACPI only hybernation and auto shutdown are affected as they require ACPI the other power saving features (monitor off, hard drive off) are unaffected)

4. If you istall from scratch you have to hit F5....????if that is mild violence then I guess I need anger management counseling...

[Dirty Harry]

Sigh,

the point is there is normally, on a PCI card /Windows based system, no reason to disable ACPI. The hardware and software is built to use it. And ACPI is not really assigning IRQ 9 to anything, read BladeRunners post, doesn't really need any elaboration.

H.