• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

fun with bsod

cheezyflier

Charter Member
this morning i took off to fly vfr from the worlds greatest airplane collection heading north in the carenado 152. i flew for about 15 min and got a bsod.
it said
"IRQL not_less_or_equal"

OXOOOOOOOOA
(OX962B7B98, OXOOOOOOOO2, OXOOOOOOOO1, OX8O4DBC9A)

can anyone tell me what is the deal here?
 
If it's an IRQ issue (Interrupt Request) then that would normally imply a hardware driver issue.

Not always, as it could be an error in a piece of software calling a bit of device driver, but I'd start by reinstalling the major hardware drivers like graphics cards and RAID/SATA drivers and see if that helps.
 
Let me guess: Vista?

"IRQL not_less_or_equal"

Try googling that, you'll get an infinite list of people with the same problem and an equally long list of solutions. Seems to be a generic Vista error code.

Used to get a whole lot of those in the two months I used Vista; my 'fix' was to install Windows 7. Never had that problem again..
 
I had this problem with a ram stick. I changed the stick and the problem has never come back.
 
That is typically related to a vid driver..but as stated can be ram too...It may never happen again ..
It was very common with SLI setups a while back too...Driver has stopped, and recovered bull...
 
Back
Top