Hi !
I get this error every time I start a game, or even when I click on the credit button.
I suppose this is due to an issue with the graphical engine of the game, but running it in compatibility mode doesn't help at all.
I got an ATI hd5870, and I7 860 proc and I run windows 7 64 bits, if that's any help.
I tried to tweak the options in the advanced options menu at start, but no dice.
EDIT: Apparently I can run the game in 1440*900, but not in 1680*1050.
I can start loading levels in 1440*900 and then switch to 1680*1050, and it does work, but then I have the same crash at the next loading

Having this same issue, disabling Direct X 6 commands DOES NOT work for me.
EDIT: Changing the resolution seems to have worked, though now the weapons are extremely shaky.

Hey all,
I get this error too if i try any res higher than 1440x900.
Running Win7 64bit with Radeon 5850(Cat9.4)

I'm getting this problem too. DirectX feature disabling didn't help, keeping the resolution low didn't help (i'm trying to play it at 640x480 and I can't even do that), software and direct3d make no difference, set as admin... :(
Win7 64bit with two Nvidia GTX 295s and an Intel I7.

Same problem here, using Win7, 64Bit. I tried pretty much everything, the only thing that has an effect seems to be the resolution:
640x480 - OK
720x480 - OK
1024x768 - OK
1280x800 - OK
1280x960 - OK
1280x1024 - CRASH ON MAP LOAD
1360x768 - OK
1600x900 - Crashed once on exit, otherwise fine?
1680x1050 - CRASH ON MAP LOAD
1920x1080 - CRASH ON MAP LOAD

Help i get this error on level 3 (Client MFC.exe Has stoped responding)
I cant play on D3D Mode
I have a nivida geforce 2 mx\mx
i have windows xp

uhm, try disabling SLI, I had to disable Crossfire on my machine

Interesting enough, I had direct x6 commands disabled and resolution at 640x480 and I got a crash right at the start of singleplayer. I tried running the game again and I got the error after 2 minutes of gameplay. This is all from a fresh installation of blood 2. I havent got any emails from the gog team yet, cant wait till they fix it :D.

Same problem here.
Only way to play it is choosing 640*480 resolution or switching to "lithtech renderer" in the display options. Looks worse than blood 1 though. :(
I would really like to play this in 1680*1050 if possible.
Back in the day Blood2 was an unfinished, buggy and therefore disappointing mess. Looks like some things never change.
Edit: Allright, looks like it works in 1280*960, too.
Edit2 : Deleted dxdiag.txt from my post. It was not my intention to spam this thread.

Way to totally waste space there swebb.
FYI, blood2 does not give you increased FOV using widescreen resolutions.
All this information is available on WSGF.
1400x900 is the maximum WS res you can use without crashing.
However, as an alternative you can run 1600x1200 and stretch it on a widescreen monitor.
Same FOV is being used regardless of resolution.
If you're a FOV purist, run the game in 4:3 and forget about widescreen, because it just doesn't work.

How did you get 1600x1200? It doesn't work for me :( 1400x900 works fine but it's a waste of space on my 24" :(

I just wanted to chime in by stating that I'm having the same problem with this "MFC" crash. I'm using Win XP 32, ATI Radeon 4770 card and dual core AMD. It was somewhat bearable at first because it didn't crash _that_ much, although it almost always generates the error upon exit.
However, I'm now fighting the Chapter 1 boss and find myself mashing F6 quite a bit; About 10-20% of the time it crashes upon quick load. I'll keep fiddling with it, but it's become quite annoying.
I thought the MFC is used primarily for Win32 GUI elements. As a DirectX game, I don't know why Blood 2 (Client.exe) would use it unless it was trying to bring up the app launcher (BLOOD2.EXE) from the game once in a while.

Like the rest of you, I can't get the game working.
As a matter of fact I've tried everything I can think of and all I get is the ridiculous 'Client MFC Application' error...
I happen to of been playing computer games for over 15 years now and it is rare that I come across a game that is close to impossible to run properly.
And it really has nothing to do with the requirements. If your computer is fast enough to play a game than it should work, done deal. There have only been a few games in my life where I would truly consider to be crap because the idiots who made the games couldn't fix all the bugs and program the source code right.
I used to have a big problem trying to run old DOS games on newer systems, but DOSBox pretty much solved all my problems trying to run them.
I enjoyed the first Blood and it provided a fun experience in much the same way Duke Nukem 3d did. I never had any problems running those games. But this, this is just unacceptable. Especially for Blood 2, which is supposed to be working, and when I saw the gameplay and features, I felt that I had to play it. But I can't, because every time I run the game I get the client error.
Could it be the system, the video card? I have ATI Radeon Xpress 200 Series, not sure if that is old or just not that good. I tried every resolution and advanced feature, nothing happened. Just a black screen.
I am running Windows XP and pretty soon I may have to move on to Windows 7. For all I know it could just be my computer system. Antivirus programs may have something to do with the problem but that is highly unlikely. I don't know if people had trouble playing Blood 2: The Chosen in 1998 just as much as people are having trouble today.
I didn't get the chance to play the game when it came out, and it feels silly to struggle to play a game that is over 10 years old that SHOULD work on modern systems. Lith really needs to consider adding a troubleshoot section for 'clients', if you ask me they shouldn't of been made for a FPS like Blood 2.
The only time I had trouble like this was when I was playing Might and Magic VII. It had a client that was somewhat similar to Blood 2, and the problem was I couldn't get the game running under hardware settings. So I decided to play it under software settings and the game worked fine.
But I've done the same thing for Blood 2: The Chosen. It didn't work. All this time I've been getting a black screen, "CLIENT MFC APPLICATION has encountered a problem and needs to close. Sorry for the inconvenience" error message, and lots of lag from my computer. Am I really doing something wrong?

Its most definitely not what you are doing, and its unlikely your system's fault. Mainly because back when the game was considered abandonware I got blood 2 working 100% fine on my current computer at least if I remember correctly. I dont really remember what I did, if I did anything that would fix the error. I think I used a unofficial patch, but I doubt it because ive been searching for anything that would fix it for over a month now. Speaking of "over a month" my first support message to gog.com was sent on April 30, 2010 and has still not been answered(recent message sent on May 27, 2010, sending another one right now). Im very sorry to all who have not been able to play this game without the error, and I will continue hoping for it to be fixed, attempting to find solutions, and continue sending messages to gog. Im surprised no one has "raged" at this point, its actually been a bit long since that first message.
Here is my newest message for support:
Subject:
No support for my last messages. Client MFC has stopped working.
Message:
Its been more than a month since my first message sent about this error and even after sending extra messages I still have not recieved any support. This error has been effecting a nice amount of people and its unfortunate we have not been able to play the game with full success for a long time now. This error appears randomly, (more quickly)in a high resolution(or reportedly certain resolutions), the start of a singleplayer/multiplayer game, or at the exiting of the game. Blood 2 has crashed when the error appears. Lastly, the gog community has also been reporting of the error and their attempts at fixing it. This is the page: http://www.gog.com/en/forum/blood_series/client_mfc_application_has_stopped_working_error_with_blood_2 . I am running on Vista 64-bit. I have included a DxDiag report...

Update: I decided to try testing the demo of Blood 2. It got the error. This probably means that its not gog's build of the game. As I was looking through some search results of "Blood 2 on Vista" on google, I found out that many of the people who have played Blood 2 on Vista got it working first try and never experienced the client mfc error. These posts are from 2009 usually. It may be that our updated systems are causing this(so maybe it is our systems DryMango). Another thing I thought that may be the cause is Vista's bad judgement for non-responding software. Vista may think that there is something wrong with blood 2 as its loading in a different resolution. But then again people who are using other os are also getting the error. Please Gog fix this damn error! or maybe monolith should get on the job!

(sorry forgot to respond to you)Thats possible but the error happens more commonly with higher resolutions. So it wouldent really add up unless the scripting for one of the files for blood 2(a dll or the blood2.exe itself I suppose) was made to run the launcher more quickly on a higher resolution. but then again, that brings up what I said before about testing the blood 2 demo and still getting the error(unless both builds of blood 2 are messed up).

Can someone who has the game working 100%(no error at all when using the highest resolution or not) post their specs here. Something that seems to be fairly common in our posts are quad core cpu's and 64-bit os's. Maybe we could see if our specs are effecting the game.