Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Markatta]

This could be an operative system thing, but I've only encountered it with Dwarf Fortress.

It seems like a random happening, every once and then DF crashes to the blue screen of death giving an error message "IRQL_NOT_LESS_OR_EQUAL" and a bunch of hex numbers, don't know huw much information you can get out of it but I'll post them anyway:

code:

0x0000000A (0x0096F490) 0x0000001C, 0x00000001, 0x804F3AAB

The errorlog in DF doesn't say a word about it.

If this isn't something that can be fixed in DF, can someone give me an idea what to do about it?

Thanks in advance.

[Aquillion]

A quick google search says that it's most likely a hardware issue.  See here.  Seems odd to only get it for Dwarf Fortress, but perhaps the game is causing something to overheat?  It's not that surprising; it's pretty processor-intensive.

According to a post here:

"IRQL_NOT_LESS_OR_EQUAL means that an application with a lower priority is trying to take CPU time away from an application with higher priority. The higher priority process may be an important system application that the machine can't run without, so Windows may not allow it to happen."

Are you using some process priority tweak to speed up Dwarf Fortress?

Another possibly relevent thing is here, which references stop error 0x0000000A specifically.

[ December 05, 2007: Message edited by: Aquillion ]

[mineditall]

yes doing a search on your own is more helpful than posting that DF caused the accident

most of all blue screen crashes are caused by hardware issues
often by pagefiles, video cards, and irq conflicts before general windows issues such as driver failures and i/o errors

[Markatta]

Oh, sorry. I'm so absorbed by DF I forgot that the rest of the internet existed.
 
Will post a note about the fact on my nose.
Thanks anyways!

[mineditall]

secondly any overclocking done on your pc can cause more frequent crashes if you fail to overclock properly

the front side bus and pci/clk divider are major factors with more quickly degrading the hardware of your pc

the only blue screen hardware crash i experience on this pc is from a cold state poweron caused by the video card gpu fan being so old that it takes awhile to spin up to speed
pausing on bios for 5 minutes will resolve my issue for the pc "warming up"
rather annoying to wait but its better than causing hard drive corruption when booting into windows

pc_wizard will give you a comprehensive idea of your hardware exceptions being drivers installed such as video driver will be called by video driver not by hardware id, but most other hardware id will be noticed
keep your pc up to the lastest drivers
if there are no drivers for the last 5 years consider there not to be any newer
but keeping your drivers up to date for the past month is usually a good idea

[SmileyMan]

Other stuff to check is things like loose/dodgy USB cables, and even loose cables in the machine, such as an IDE cable.

Stop A can also be caused by a dodgy driver, especially sound drivers and sometimes video drivers.

DF is very very unlikely to be the primary cause, but it might be stressing your machine enough to make a hidden hardware issue prevalent.