Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

IRQ Allocation Error

Dec 10, 2003 3:39PM PST

Basic PC Specs:
1. Win 98SE
2. 486DX
3. 48 MB RAM
4. CD-ROM
5. Floppy Drives - 3.5 and 5.25
6. Hard Drive - Not sure of size at this time, somewhere around 1-2 GB I believe.


Symptoms:
1. On startup, the BIOS is reporting the following error...
IRQ Allocation Error - Motherboard Function #: 01
(though I can never quite catch what the very last part of the error is, as the screen moves beyond that point quickly. anyway, I believe it to be what I indicate here.)

2. System boots fine and everything appears to work with the exception of the CD-ROM drive.

3. The CD-ROM drive is not recognized by the BIOS and I believe the issue has to do with the IRQ issue.


Wrap Up:
Any thoughts and/or insights on this issue are greatly appreciated. What would cause the allocation error and how does one correct it? Thanks.

Jody Wood

Discussion is locked

- Collapse -
Re:IRQ Allocation Error
Dec 10, 2003 8:25PM PST

You would update the BIOS, clear the BIOS settings and that usually clears up IRQ allocation issues.

CDROM drives have a high failure rate. I've never seen that error affect a CDROM drive in the fashion you write, but often find people that don't know that motherboard drivers are required to be installed (Microsoft doesn't do this for you.)

You would test the CDROM drive on another machine to be sure about it...

Bob

- Collapse -
IRO Error
Dec 18, 2004 11:18AM PST

Basic PC Specs:
1. Win 98SE
2. 486DX
3. 48 MB RAM
4. CD-ROM
5. Floppy Drives - 3.5 and 5.25
6. Hard Drive - Not sure of size at this time, somewhere around 1-2 GB I believe.


Symptoms:
1. On startup, the BIOS is reporting the following error...
IRQ Allocation Error - Motherboard Function #: 01
(though I can never quite catch what the very last part of the error is, as the screen moves beyond that point quickly. anyway, I believe it to be what I indicate here.)