Seen a Build Engine game crash like this? \ VOGONS

Seen a Build Engine game crash like this?

Topic actions

First post, by boxpressed

Posted on 2015-07-17, 21:04

boxpressed Offline

Rank Oldbie

Rank: Oldbie
Posts: 1438
Joined: 2014-05-20, 18:29
Location: Wisconsin, USA

So I'm testing out an AWE64 Value that recently arrived, and everything seemed to be working just fine with it.

INTEL SE440BX-2
CELERON TUALATIN 1300 (on Powerleap)
NVIDIA QUADRO2 PRO
MS-DOS 7.1
256MB PC100

Then this happens a few minutes into the demo. I haven't tried to replicate it, and I'm not terribly worried about it. I'm just curious what might have caused it. There was a hanging note that persisted until I rebooted.

I'm also running MTRRLFBE instead of Fastvid. Also running at 1600x1200.

Reply 1 of 6, by PhilsComputerLab

Posted on 2015-07-17, 21:08

PhilsComputerLab Offline

Rank l33t++

Rank: l33t++
Posts: 6174
Joined: 2014-09-28, 03:33
Location: Western Australia

Seen lots of crashes like that 😀

Could be a lot of reasons. Too much RAM, trying a new version of the extender, starting with XMS or EMS...

YouTube, Facebook, Website

Reply 2 of 6, by boxpressed

Posted on 2015-07-17, 21:13

boxpressed Offline

Rank Oldbie

Rank: Oldbie
Posts: 1438
Joined: 2014-05-20, 18:29
Location: Wisconsin, USA

Interesting. I just replicated it. Happened after about five minutes of the demo. I'll try with a clean boot and the Creative inits.

Reply 3 of 6, by leileilol

Posted on 2015-07-17, 21:42

leileilol Offline

Rank l33t++

Rank: l33t++
Posts: 12273
Joined: 2006-12-16, 18:03

Blood itself did some crazy workarounds for Build's cache system and has its own replacing it, so most of the random crashes are pretty unique to Blood. Hopefully other Build games don't give you this much trouble.

long live PCem

Reply 4 of 6, by boxpressed

Posted on 2015-07-18, 05:14

boxpressed Offline

Rank Oldbie

Rank: Oldbie
Posts: 1438
Joined: 2014-05-20, 18:29
Location: Wisconsin, USA

Good to know that this might be restricted to Blood. Duke 3D never crashed like this.

Well, after clean booting, I was able to replicate the error with two different video cards, three different sound cards, and two different SDRAM sticks.

The problem, it seems, has to do with the resolution on my system. I switched to 800x600, and the demo has been running fine through several cycles (it always crashed during the second cycle). I'm going to test the game at 1600x1200 on my KT133A board to see if this is a problem with the SE440BX-2 (maybe Powerleap)