At Fixya.com, our trusted experts are meticulously vetted and possess extensive experience in their respective fields. Backed by a community of knowledgeable professionals, our platform ensures that the solutions provided are thoroughly researched and validated.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
I would firstly reboot and if that doesn't clear the error run www.iobit.com asc.setup utility to remove crosslinked files and sort out a crosslinked registry. Failing that remove the driver from the Control Panel and let the OS set up a fresh driver. Make sure the driver is the correct one!
If it just started doing this all of a sudden, then it is a good bet that *********** board is fried. If you just installed some memory or a communications card or new drive, then take it out and see if it still does it. If not, check the installation instructions to make sure it was put in right.
You have a n IRQ conflict meaning you have a device that is trying to use an IRQ slot that its not meant to talk on. From the looks of it you have been in the bios already so go back in and set it to factory default.
It might be possible some kinda a BIOS corruption. Let us try this first. ASA computer starts keep on tapping F2, it will enter the BIOS setup utility, then press F9 and then F10, save the seeting and restart the computer. It should resolve the issue. But if the issue still persists, then update the BIOS. Visit the webiste mentioned below:
I did try all that, and it didnt work, on a 5050 acer built on a 3100 gabinet.
I think that the problem is that the cardreader chip is not well glued to the motherboard, that's why it gives you that error. If you try pressing certain points of the computer while booting, it miraculously stops giving that conflict error.
We should be payed back by Acer, as this is an project issue =P
×