System event

Hello

My Winxp computer has been very unstable of late. Keeps getting bluescreens and then reboots. I never have enough time to read what the bluescreen says but when I look in event viewer under system I have two reported errors.

Nr 1.
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume D:

Have run chkdsk a couple of times, winxp even runs it automaticlly after every 'reboot'. Have also run Partition magic and checked for errors. No help.

Nr 2.
AMLI: ACPI BIOS is attempting to read from an illegal IO port address (0xcfc), which lies in the 0xcf8 - 0xcff protected address range. This could lead to system instability. Please contact your system vendor for technical assistance.

Have installed all security updates.

Hoping for any input.

 

 
The second error is often remedied by a BIOS update. Maybe the first will follow.

 

I say it so much it sounds like a broken record!

CLEANUP! Temp internet with offline files, windows temps!

Reboot!

Go to CMOS/BIOS!

Find plug & play OS installed! Make sure it says YES! If so there should be an entry here to reset configuration or it may say reset ESCD! Tell it to reset!

If this does not help reverse the P&P OS to no!

Let use know!

Mike

 

Forgot!

Do with cleanup!

Note swap file settings! Resize to zero!

Reboot set back to correct settings!

Mike

 

Excellent suggestions both. And do both.

After that, you will still need to deal with any damaged files/folders/structures you picked up while it was giving problems.

For that

start~run~cmd and then
c: (to put you on your system drive for sure) and
chkdsk /r (and it will tell you it can't be done and ask about doing it at reboot - say yes and then reboot). This will take a while since it not only does a file repair but a surface scan and repair if needed of the drive.

If you have multiple drives/partitions, do the chkdsk to each. It will do any other than the system drive and, if you moved it, the partition with the pagefile right after you issue the command. No reboot needed. But start with the system partition.

 

This morning :
I did the clean up, delete internet temp files and windows temp files. Set swap = 0

I went into the bios and set P&P to yes, then I 'reset configuration\reset ESCD'.

Rebooted, did start->run->'cmd'-> 'd:'-> 'chkdsk /r'
(it didnt ask me to reboot like someone pointed out but it did go through 5 test and everything was ok)

I reset swap and rebooted again.

Four hours later :
Still get the second error (the one with the bios).
Whats next ? A bios upgrade ? I've got a abit mobo, so I went to Abit and looked for a bios upgrade, after a bit looking around I found a place to download a bios upgrade for my model (KT7) - Bios upgrade

I copyed the files onto a bootable floppy and tryed to flash the bios only to recive a message saying I cant use the .bin file for my bios.

Hoping for some input.

Cheers

 

Lasunde

This sounds like it detects the wrong BIOS or revision!

Double check this!

It may be time to consider a more drastic approach such as a reinstall!

But Follow thru on finding the correct bios revision.

Just maybe!!!!!
Clean all temps and TIFs!
Get adaware and spybot and do full scans!

Mike

 

I have done the cleanup again, including running adaware (found 49 components).

Im a bit unsure about the bios upgrade.

Not sure but I think this is my bios id and date :
07/20/2000 8371-686A-6A6LKA1AC-TY

If I goto
Abit Bios Download page Im not really sure which 'program' to download. Last time I selected bios id : A9 coz it was the newst version.

Anyway, will report back if I get more errors.

 

 
There seems to be something wacky here. The "TY" designation is for the KA7 mb rather than the KT7. If you indeed have the KT7, you may have an incorrect BIOS for your machine. See here:

http://www.abit.com.tw/abitweb/webjsp/english/download_content.jsp?pTITLE=KA7+/+KA7-100&#Bios

That would explain why the KT7 update won't take. If you do have the KA7, the latest update is just a little newer than the one you have, judging by the date.

In any case, sometimes an error in the AMLI (ACPI Machine Language Interface) seems to be remedied by changing your machine type from ACPI-compliant to standard.

 

"In any case, sometimes an error in the AMLI (ACPI Machine Language Interface) seems to be remedied by changing your machine type from ACPI-compliant to standard. "

Please explain.

Will check-up mobo model tomorrow.

 

 
From what I have seen from other posts, the machine can be changed from ACPI to standard fairly easily by selecting the Standard from Device Manager, Computer. Some people mentioned IRQ problems afterward, and others said that they had no problems at all.

Changing back from Standard to ACPI is not really possible---a complete reinstallation is necessary. (Got this from MS).

Apparently, pressing F5 during setup at the "RAID devices" prompt gives you some options on mb type and whether to choose ACPI.

This is all gathered from other posts and is nothing I have first-hand experience with.

I'd definitely still pursue the updated BIOS route until that proves to be a definite dead-end.

 

"Rebooted, did start->run->'cmd'-> 'd:'-> 'chkdsk /r'
(it didnt ask me to reboot like someone pointed out but it did go through 5 test and everything was ok) "

The only time you will be required to reboot to run chkdsk with either /f or /r which may make changes is with a drive/partition that is "in use ". Which ever partition holds the XP OS will require that and if you have put your pagefile on a different partition than the OS (which helps performance) the partition holding the pagefile will also be considered "in use ".

All other partitions can be done "on the fly" or when you run the command.

 

Oh my god...

"My Winxp computer has been very unstable of late. Keeps getting bluescreens and then reboots. I never have enough time to read what the bluescreen says but when I look in event viewer under system I have two reported errors. "

"CLEANUP! Temp internet with offline files, windows temps!

Reboot!

Go to CMOS/BIOS! "


"Do with cleanup!

Note swap file settings! Resize to zero! "

"Rebooted, did start->run->'cmd'-> 'd:'-> 'chkdsk /r' "

"I reset swap and rebooted again.

Four hours later :
Still get the second error (the one with the bios). "

Blah Blah Blah Yadda Yadda Yadda

I got news for ya, a BIOS upgarde probably won't do squat to help. Hey, lets face it, this is probably going to go on forever if you continue to use the same soft... XP is an unstable OS, why can't the biggest co. in the world make a satble OS, thats what I want to know. There are better, *way more stable* OSes for free! I think the most logical thing to do here is to go in and get either Win2K or Linux...Then you'll either have half as many problems (the former) or no problems (the latter).

BDBD

 

BuckDeath : I must agree that win2k was a tad more stable (for me anyway) and Im starting to regret installing winxp. Linux on the other hand isnt as good as I thought it would be, atleast not for a beginner, adding ntfs support to kernel and setting up my video card was a bitch.

 

Well, laasunde , I had the unenviable experience of receiving the same AMLI error on a Compaq I was installing XP on today.

Following my own advice, I updated the BIOS. No difference, and a dangerous thing to do anyway, though a new chip only costs around $20, it takes a while to arrive.

So, I took the second part of my advice. I went to Device Manager and clicked to Update the computer type. Instead of letting it do it automatically, I chose manual and was presented with 2 choices: ACPI or Standard. Chose Standard, rebooted, waited a while after login while the hardware was detected anew, rebooted again, and, guess what?
It worked!

Everything works fine and no more AMLI errors.