snedo - 12-26-2002 at 11:26 AM
SYSDUMPs are generated by the game when the game tells Windows (using DirectX) to perform a function. Windows then instructs the hardware (using the
hardware's drivers) to generate the image or sound. If for any reason there is confusion in the process, you receive a sysdump.
We have also found that Athlon and Duron motherboards with VIA and AMD chipsets are much more sensitive to proper driver installation than any other
configuration. Be sure to update all of the following to the most recent available from each manufacturer:
- The latest BIOS for your particular motherboard
- The latest Chipset drivers for your motherboard, including the latest AGP Miniport driver
- The most recent video card and soundcard drivers for your system
Make sure that no anti-virus software is running in Windows when you play the game (especially Norton Anti-Virus). These programs conflict with the
normal processes of the game and may be the source of your system crashes
DeadBolt - 12-30-2002 at 11:41 PM
There are more causes for sysdumps than just those.
Maps, alt-tabbing, coding errors, corrupted files, invalid ban file, etc.
A sysdump is NL's general wrapper around any fatal error. In most other programs you will get an "This application has performed...". The game
directory contains two files related to the last game crash (SYSDUMP.TXT and SYSDUMP.BIN).
Help us all out.
KnightRaven - 1-1-2003 at 02:42 AM
Additionally, you can send the sysdump file to NL for analysis. This will help us have a better gaming experience by allowing NL to see what problems
we're having as gamers (and hopefully allow them to provide patches). My DFBHD Demo directory has an .exe that will automatically send the sysdump
file to NL. I have attached the .exe. I do not know if it works for other DF games, but it seems to work fine for BHD.