View Issue Details

IDProjectCategoryView StatusLast Update
0002211Dwarf FortressTechnical -- Generalpublic2010-08-10 00:12
Reportertatterdemalian Assigned Touser6 
PrioritynormalSeveritycrashReproducibilityalways
Status resolvedResolutionno change required 
PlatformAMD Turion64 x2OSWindows VistaOS VersionService Pack 2
Product Version0.31.05 
Summary0002211: Sudden Shutdown Bug
DescriptionOkay, this is something completely new to me as a programmer. Apparently either a 31.05 driver, some trojan/rootkit that my system picked up since the update, or maybe a combination of both, is making my computer abruptly switch itself off whenever I play Dwarf Fortress 31.05. It does not happen when I play 31.04, nor has this ever even happened before on any computer I've ever owned. No BSOD, no soft/hard reset, no dump log, no sign of any problem, just *CLICK* my computer switches off as if someone had pulled the power plug and I didn't have a UPS installed. I've tested this both with the UPS and with the computer plugged into a simple surge protector, so it's not some glitch in the UPS either.
Steps To ReproduceAttempt to use my computer to play Dwarf Fortress 31.05. Sudden shutdown occurs after a random amount of time, but always within thirty minutes of opening the game application.
Additional InformationThe only sign (maybe?) of what could be causing the problem is a set of messages in the System Event Log that are always logged just prior to the shutdown. I don't know if they're related or not, but there doesn't seem to be anything else to go on... as far as Windows Vista seems to be able to tell, I was the one who flipped the power switch and caused an abnormal shutdown.

The messages are (in chronological order):

File System Filter 'FileInfo' (6.0, 2008-01-19T00:34:27.000Z) has successfully loaded and registered with Filter Manager. (Log Name: System, Source: FilterManager, Event ID: 6, User: SYSTEM)
File System Filter 'Lbd' (6.0, 2009-08-28T04:02:18.000Z) has successfully loaded and registered with Filter Manager. (Log Name: System, Source: FilterManager, Event ID: 6, User: SYSTEM)
The system detected that network adapter Loopback Pseudo-Interface 1 was connected to the network, and has initiated normal operation. (Log Name: System, Source: Tcpip, Event ID: 4201, User: N/A)
The system detected that network adapter Loopback Pseudo-Interface 1 was connected to the network, and has initiated normal operation. (Log Name: System, Source: Tcpip, Event ID: 4201, User: N/A)

The fact that DF shouldn't be able to access the SYSTEM account would usually indicate a rootkit of some kind, but the fact that it only occurs while playing DF 31.05 makes me wonder. If you determine this can't possibly be related in any way to DF, feel free to remove this report.
TagsNo tags attached.

Activities

user6

2010-06-07 15:10

  ~0007906

Try updating your graphics drivers. 31.05 uses different OpenGL calls from 31.04, which means it uses different parts of the drivers, and buggy drivers can (unlike DF) directly cause a system crash.

Logical2u

2010-06-07 17:08

manager   ~0007908

It might be possible that DF's bump in the CPU usage is enough to cause an overheat, but you should be able to test this by running a few intensive programs (Virus scanners and video encoders come to mind, although any new games should also do the trick)

tatterdemalian

2010-06-07 19:23

reporter   ~0007912

Last edited: 2010-06-08 17:31

I doubt it's an overheat, because I have temperature monitoring software and an extra cooling fan. I've run several virus scans (F-Protect and Ad Aware) and neither killed my CPU, though they did cause the expected CPU spikes. I'm going to try the graphics driver update, and see if that helps any. It would be weird for even an outdated display driver to blow up my machine that suddenly, and sometimes several minutes after I start it, but it would be better than finding out my computer is rooted.

UPDATE: Nope, all drivers are still current. I updated them about three months ago.

user6

2010-06-21 12:08

  ~0008891

Does this still occur in 31.08 SDL and 31.08 Legacy?

user6

2010-06-28 07:58

  ~0009229

Reminder sent to: tatterdemalian

Does this still occur in 31.08 SDL and 31.08 Legacy?

tatterdemalian

2010-07-03 22:08

reporter   ~0009607

Nope, seems to be working fine now (just upgraded to 31.08, and switched from MalwareBytes to Trend Micro antivirus). Not sure what was interacting so strangely, but it's cleared up.

user6

2010-07-03 22:14

  ~0009608

Cool.

Issue History

Date Modified Username Field Change
2010-06-07 14:34 tatterdemalian New Issue
2010-06-07 15:10 user6 Note Added: 0007906
2010-06-07 17:08 Logical2u Note Added: 0007908
2010-06-07 19:23 tatterdemalian Note Added: 0007912
2010-06-08 17:31 tatterdemalian Note Edited: 0007912
2010-06-21 12:08 user6 Note Added: 0008891
2010-06-21 12:08 user6 Tag Attached: AWAITING UPDATE
2010-06-28 07:58 user6 Note Added: 0009229
2010-06-29 07:38 user6 Category Technical => Technical -- General
2010-07-03 22:08 tatterdemalian Note Added: 0009607
2010-07-03 22:14 user6 Note Added: 0009608
2010-07-03 22:14 user6 Status new => resolved
2010-07-03 22:14 user6 Resolution open => no change required
2010-07-03 22:14 user6 Assigned To => user6
2010-08-10 00:12 user11 Tag Detached: AWAITING UPDATE