If I load my save, it won't do that. If I try to lower it after loading the save it crashes right away.

Here's another thing: If I load it up, don't touch anything just let the game demo itself, it doesn't crash.

Eh, another one: http://s1103.photobucket.com/albums/g466/3stest2501/?action=view&current=dosboxcrashagainandagain.jpg

Anyone?

do you have some highspeed mouse or keyboard ?

Mouse and Keyboard are both connected to the USB port. A dude hypothesized that this could cause an Input Buffer Overflow.

In a previous screenshot (dosboxbug5.jpg), it mentions that DOSBox can become unstable with more than 31 MB of RAM yet I seem to remember that GoG allocates DOSBox a full 64 MB. In your dosboxBlood.conf file, you might try editing the memsize so that it runs with the recommended 31 MB, if that works out, you might try increasing it to 38 MB. Blood can only use up to 36 MB of RAM anyway and DOSBox seems to only need 2 MB for a running system.

Did that, still crashes. I'm stumped. And I emailed the tech support at GOG and have talked to other Tech-heads too.

Yeah, I'm starting to get to the bottom of the barrel too.

So far, you have:
• Set DOSBox to run in XP mode
• Tried various graphic modes (ddraw, OpenGL, overlay, surface) with Overlay seeming to work the best
• Configured DOSBox so that it stops closing automatically when Blood crashes
• Gathered screenshots of the error
• Upgraded to DOSBox 0.74
• Disabled the Blood's audio
• Limited your CPU cycles
• Changed the amount of RAM

Am I missing anything else you have tried?

For clarification, after following Qbix' advice to limit your CPU cycles, you said it was choppy, but did it crash on you? If you just closed out, you might try just running around in game with godmode on to see if it still crashes on you.

Also, earlier you mentioned that it wasn't letting you configure your 2 mouse button as alt fire. Have you tried running Blood with no mouse at all? You can set this in the blood.cfg file by setting your controller type to 0 (keyboard only):

ControllerType = 0

Also for clarification, When you disabled sound, what method did you use? You can edit this directly in your blood.cfg file by setting the values of FXDevice, and MusicDevice to 13:

FXDevice = 13
MusicDevice = 13

I've never used D-Fend Reloaded, but from the screenshots, it looks like you can edit the values a particular game is set to use with its profile settings.

I tried disabling the sound effects (music still played) and it seemed to run fine, but again, a random crash after about 2-3 minutes of playing.

I emailed GOG directly almost a week ago and no response. I'm not impressed with their customer service and will be avoiding them in the future.

So change the IRQ value and how much memory it's using.

I changed IRQ value and no difference.

I changed memory consumption multiple times with no effect.

I think I figured it out. The music causes the crashing. Because I can let it load, and the music gets to a certain point where it'll crash. Some music from the game doesn't cause any crashing, which explains why I was able to get through certain levels without a hitch.

Here's the thing: I went into Setup and disabled music (kept Sound Effects) and even turned music and CD audio volume all the way down in the in-game options. And the music STILL plays. Really weird. But at least we know why it crashes now.

Okay, so I did something a little more direct. I manually took out the Music files from the Directory. Didn't delete them, but the game can't access them.

And what do ya' know? The Game works now for the most part. It will still crash sometimes, but not nearly as often. Some other sound files must cause the crash. But I can't play the game completely mute and I save often enough that the crashing doesn't impact me that badly.