Print

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

[Fourth Triad]

I've had this happen twice now both times after it restarts it tells me the system has recovered from a serious error, the first time I just had it on the title screen for a while, the second time I was sitting around in adventure mode at the bottom of the sea doing nothing for 2hrs cuz I got locked out of my house.

[kuro_suna]

what OS are you running?

[Fourth Triad]

windows xp sp2

[ November 09, 2007: Message edited by: Fourth Triad ]

[avari]

I had this happen also. I had been running dwarf mode for 12+ hours (paused, forgot it was running), then played for a few minutes, saved, quit --> hardware reboot. I was running other programs and alt-tabbing like hell, though, so can't be sure if the cause was DF.

Oh yeah, windows XP sp2.

[ November 09, 2007: Message edited by: avari ]

[Stromko]

I'd expect it was overheating based on my experiences with my own machines, and what the root cause was for coming back up with that particular error ("recovered from a serious error) though this was not particularly happening with Dwarf Fortress. Happened to me with all sorts of programs, until I ended up leaving my case open with a high-powered fan (at a safe distance) blowing air over my CPU and especially GPU. DF will max out your processor nearly constantly so it's more likely to be the CPU overheating.

[Fourth Triad]

I haven't had this happen to me with any of the other cpu guzzling games I play... but then again df does seem to use more mem and shit than they do... Also when sitting around underwater df only uses 0% to 5% of the cpu.

[ November 09, 2007: Message edited by: Fourth Triad ]

[Tormy]

quote:Originally posted by Fourth Triad:
<STRONG>windows xp sp2

[ November 09, 2007: Message edited by: Fourth Triad ]</STRONG>

I have WinXP SP2 also and never had this problem so far. This sounds like a hardware related problem imo.

[Koji]

If you're running an AMD Athlon, pop open your case and take a look at your processor. You know those little battery-shaped things positioned around it? Those are capacitors. Check the tops of them--they should be flat. If they're bulging out, they've blown from overheating.

It's a common problem with hot-running processors. Even if you don't have an Athlon, check it out anyway. The only fix is to get a new motherboard.

[Fourth Triad]

I can't tell if there the ones right next to the cpu are bulging cuz theres a fan over that area, but all the ones I could see looked flat.

[Stromko]

There are heat-monitoring programs that could be useful in diagnosing this problem. Here's what I use: http://www.majorgeeks.com/download4181.html

If you install that, open the program, click on Computer on the left screen, and then Sensor. The second section should be Temperatures, and anything over 80 degrees Celsius is definitely in the danger zone for crashing. At least, temps around that range is when my old ATI X800 card would crash my computer and it'd come up with "recovered from serious error".

I've had crashes from CPU overheating too, but that was because the fan was unseated (therefore the heatsink wasn't touching the processor just perfect) and it'd crash while Windows was still booting. There should be a temperature sensor in your BIOS, and that's how I recognized that problem.

[Sowelu]

That happened to me (not in DF, though) when my heatsink was installed upside down somehow, so it only touched half the chip.  No, I don't get it either.

My first guess would have been video card, but that's not a well-supported guess.  I just tend to always blame video cards first.  Maybe it's an overheated video card!  (no.)

[Fourth Triad]

It isn't giving me a temp read out and says my cpu isn't supported in the current edition. I tried another temp reader program, but it didn't work for the cpu either...

[ November 10, 2007: Message edited by: Fourth Triad ]