Page 1 of 1

WTF?! unhandled PIC interrupt

PostPosted: Thu May 24, 2012 9:35 pm
by shonnex
unhandled PIC interrupt IRQD
smx LQ OVERFLOW
:shock:
mixer is d8b

Re: WTF?! unhandled PIC interrupt

PostPosted: Thu May 24, 2012 9:56 pm
by Crash
shonnex wrote:unhandled PIC interrupt IRQD
smx LQ OVERFLOW
:shock:
mixer is d8b


Where are you seeing that? On the GUI? Have you reset bios at all?

Re: WTF?! unhandled PIC interrupt

PostPosted: Fri May 25, 2012 12:06 am
by Petersueco
Replace battery and reset BIOS settings.

Re: WTF?! unhandled PIC interrupt

PostPosted: Fri May 25, 2012 1:00 am
by shonnex
batt replaced and reset bios...
i installed new os and error is still present.
I think my mobo is death.. replacement is too hi price. but I don't know why, this mobo real price is 5 box... old mobo but hi price.... shit I don't know what to do....
thanks for answers...
my skype name is nenad.petrovich and if you boys can help me, please contact me.

Re: WTF?! unhandled PIC interrupt

PostPosted: Fri May 25, 2012 1:02 am
by shonnex
Crash wrote:
shonnex wrote:unhandled PIC interrupt IRQD
smx LQ OVERFLOW
:shock:
mixer is d8b


Where are you seeing that? On the GUI? Have you reset bios at all?

this message is on my screen when booting mackie os...

Re: WTF?! unhandled PIC interrupt

PostPosted: Fri May 25, 2012 1:49 am
by Petersueco
Maybe a RAM issue?

Re: WTF?! unhandled PIC interrupt

PostPosted: Fri May 25, 2012 9:50 am
by BJG
You might also try reseating everything; RAM, cards, CPU, pull them all out and plug them back in. When you reset the BIOS make sure you go through the approved D8B settings for your particular motherboard manually instead of just selecting "Optimal" or default. See here -

http://www.sonido-7.com/d8b/maintenance.html#Post1

Re: WTF?! unhandled PIC interrupt

PostPosted: Sun May 27, 2012 3:49 pm
by synthjoe
That's a pretty bad message. It means that the BIOS is not processing an interrupt (math coprocessor) that it should by the original configuration. It might happen if you have the wrong BIOS, got another motherboard or maybe a different type of processor. Maybe something else also, but these are the three prime causes if nothing else fails.

Try to figure out the BIOS version or ID and/or date (should be somewhere on the screen at startup), maybe that'll explain...