Page 1 of 2
Blue KingAir of death
Posted: Fri Sep 23, 2016 3:53 pm
by KL-666
For the first time in the 4 year lifetime of my Asus G75vx win 8.1 laptop something managed to give me a blue screen of death. It was while trying the KingAir, and windows mentioned something about bad IRQ addressing. Is this plane trying to tap directly into my hardware or so?
Kind regards, Vincent
Re: Blue KingaAir of death
Posted: Fri Sep 23, 2016 3:54 pm
by IAHM-COL
No, the plane does not tap into hardware
Re: Blue KingAir of death
Posted: Fri Sep 23, 2016 3:58 pm
by SHM
Its the Voodoomaster doing its thing
P.S I know that its not there in kingair.
Re: Blue KingAir of death
Posted: Fri Sep 23, 2016 4:00 pm
by jwocky
She doesn't even have Voodoomaster;-)
Re: Blue KingAir of death
Posted: Fri Sep 23, 2016 4:36 pm
by KL-666
Well if there are no other reports of the kind, then it may have been some other glitch. But still i stay away from flying that plane for a while.
Kind regards, Vincent
Re: Blue KingAir of death
Posted: Fri Sep 23, 2016 4:47 pm
by IAHM-COL
Is it consistent? or did it only happen once?
Re: Blue KingAir of death
Posted: Fri Sep 23, 2016 4:52 pm
by KL-666
You don't think i try this again, do you? I'll get consistency out of not having a blue screen in the next month. And in the mean time see if there any other reports about this.
Kind regards, Vincent
Re: Blue KingAir of death
Posted: Fri Sep 23, 2016 5:02 pm
by IAHM-COL
makes sense
Just wanted to reassure whether the plane was culprit. But no need ---
Hopefully other Windows OS testers can give it a ride; just for the increased Sample size
Re: Blue KingAir of death
Posted: Fri Sep 23, 2016 10:16 pm
by Octal450
My Windows Vista Buisness x64 is very stable on FGFS 2016.1.2 is very stable on the KingAir.
Re: Blue KingAir of death
Posted: Sat Sep 24, 2016 3:21 am
by jwocky
Did you install anything else lately, Vincent?
I ask, because an IRQ is not directly sent by anything in FG. No FG aircraft, including the KingAir can directly cause an IRQ. So, bad IRW would indicate two resources are fighting for the same IRQ or there ia another software that occasionally and probably only in combination of its own paramters send an IRQ via the same number.
The other option is even less nice, it means, something in your hardware is maybe dying.