It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like:Chrome,Firefox,Internet Explorer orOpera

×
Frequent and regular crashes (like once every 30 - 60 min), for no apparent reason. Have fiddled with the compatibility settings with no avail. Most crashes occur in combat, but it got to a point where it would crash rather frequently every time I jumped the "waterfall" in the starting island (like every 8 times out of 10 it would crash). I even tried enabling 3D hardware acceleration but then I get screen flicker.

I'm on Win7 x64. Videocard is AMD/ATI. Onboard sound.

Here's the ErrorLog after one of these crashes in case the developer of the patch reads these forums:


Time: 19/11/2012 20:36:10 (19.11.2012 22:36:10 UTC)
Windows Version 6.1 Service Pack 1

Exception EIntOverflow in module mm7.exe at 00085223.
Integer overflow.

Function Calls:

00485223 | E:\Games\Might and Magic VII\mm7.exe + 85223
00487C76 | E:\Games\Might and Magic VII\mm7.exe + 87C76
0048726D ? E:\Games\Might and Magic VII\mm7.exe + 8726D
00487376 ? E:\Games\Might and Magic VII\mm7.exe + 87376
0047A73C ? E:\Games\Might and Magic VII\mm7.exe + 7A73C
00441D3D ? E:\Games\Might and Magic VII\mm7.exe + 41D3D
004412A5 ? E:\Games\Might and Magic VII\mm7.exe + 412A5
00463789 ? E:\Games\Might and Magic VII\mm7.exe + 63789
00463026 ? E:\Games\Might and Magic VII\mm7.exe + 63026
004CD889 ? E:\Games\Might and Magic VII\mm7.exe + CD889
770AE6A3 ? C:\Windows\SysWOW64\ntdll.dll + 2E6A3
754033A8 ? C:\Windows\syswow64\kernel32.dll + 133A8
770B9EF0 ? C:\Windows\SysWOW64\ntdll.dll + 39EF0

Registers:

EAX = 00000000
EBX = 00000587
ECX = 0000B712
EDX = FFFFFE00
ESI = 0080173C
EDI = 7ECD0520
EBP = 0018FDC0
ESP = 0018FD7C

Stack Trace:

0018FD7C: 00000037
0018FD80: 7ECD0520
0018FD84: 0080173C
0018FD88: 00000132
0018FD8C: 00002AFE
0018FD90: 0000FC5D
0018FD94: FFFEE46A
0018FD98: 0000304E
0018FD9C: FFFF1FBA
0018FDA0: 00000002
0018FDA4: FE000000
0018FDA8: 00000001
0018FDAC: 0000B712
0018FDB0: 0000029A
0018FDB4: FE000000
0018FDB8: 00000008
0018FDBC: 000000D6
0018FDC0: 00000528 | Last EBP
0018FDC4: 00487C7B | E:\Games\Might and Magic VII\mm7.exe + 87C7B
0018FDC8: FFFF872A
0018FDCC: 00000000
0018FDD0: 006A0C70
0018FDD4: 0018FE38
0018FDD8: 00000001
0018FDDC: 0000002F
0018FDE0: 00000000
0018FDE4: 0000ED68
0018FDE8: 00128C20
0018FDEC: 0000002E
0018FDF0: 000000AA
0018FDF4: 0018FE1C
0018FDF8: 00487272 ? E:\Games\Might and Magic VII\mm7.exe + 87272
0018FDFC: 00000000
0018FE00: 006A0C70
0018FE04: 0078178C
0018FE08: 0000002D
0018FE0C: 00000001
0018FE10: 0048737B ? E:\Games\Might and Magic VII\mm7.exe + 8737B
0018FE14: 007819A4
0018FE18: 00000000
0018FE1C: 006A0C70
0018FE20: 0047A741 ? E:\Games\Might and Magic VII\mm7.exe + 7A741
0018FE24: FFFFFF4C
0018FE28: 00DF1A68
0018FE2C: 00000000
0018FE30: 0000FC5D
0018FE34: 00000018
0018FE38: 0050BA60
0018FE3C: 00441D42 ? E:\Games\Might and Magic VII\mm7.exe + 41D42
0018FE40: 004412AA ? E:\Games\Might and Magic VII\mm7.exe + 412AA
0018FE44: 00DF1A68
0018FE48: 00000001
0018FE4C: 00000000
0018FE50: 00000018
0018FE54: 0000FC5D
0018FE58: 00F78F58
0018FE5C: 0050BA60
0018FE60: 0046378E ? E:\Games\Might and Magic VII\mm7.exe + 6378E
0018FE64: 00000000
0018FE68: 005E4FC0
0018FE6C: 00ACCE38
0018FE70: 00000000
0018FE74: 00000000
0018FE78: 00000000
0018FE7C: 622E7265
0018FE80: 00006E69
0018FE84: 0018FEBC
0018FE88: 00000000
0018FE8C: 0070063C
0018FE90: 00000200
0018FE94: 00000000
0018FE98: 00B80115
0018FE9C: 15383FBD
0018FEA0: 00000115
0018FEA4: 000000B8
0018FEA8: 00000120
0018FEAC: 00000000
0018FEB0: 00000000
0018FEB4: 00000000
0018FEB8: 00000000
0018FEBC: 7EC20010
0018FEC0: 00001300
0018FEC4: 00ACCE38
0018FEC8: 0046302B ? E:\Games\Might and Magic VII\mm7.exe + 6302B
0018FECC: 00000000
0018FED0: 0018FF88
0018FED4: 00000000
0018FED8: 004DF174
0018FEDC: 00000000
0018FEE0: 00000000
0018FEE4: 00000000
0018FEE8: 00000000
0018FEEC: 00000000
0018FEF0: 00000000
0018FEF4: 00000000
0018FEF8: 00000000
0018FEFC: 00000000
0018FF00: 004CD88E ? E:\Games\Might and Magic VII\mm7.exe + CD88E
0018FF04: 0000000E
0018FF08: 00000000
0018FF0C: 00000000
0018FF10: 00000001
0018FF14: 00000000
0018FF18: 00000000
0018FF1C: 7EFDE000
0018FF20: C0000095
0018FF24: 010E25E7
0018FF28: 770AE6A8 ? C:\Windows\SysWOW64\ntdll.dll + 2E6A8
0018FF2C: 00000044
0018FF30: 0110CF68
0018FF34: 01109638
0018FF38: 0110DB78
0018FF3C: 00000000
0018FF40: 00000000
0018FF44: 00000000
0018FF48: 00000000
0018FF4C: 00000000
0018FF50: 00000000
0018FF54: 00000000
0018FF58: 00000401
0018FF5C: 00000001
0018FF60: 00000000
0018FF64: 00000000
0018FF68: 00010001
0018FF6C: 00000000
0018FF70: 0018FF14
0018FF74: 0018F950
0018FF78: 0018FFC4 | TExcFrame.next
0018FF7C: 004D0F20 | E:\Games\Might and Magic VII\mm7.exe + D0F20
0018FF80: 004DB160
0018FF84: 00000000
0018FF88: 0018FF94
0018FF8C: 754033AA ? C:\Windows\syswow64\kernel32.dll + 133AA
0018FF90: 7EFDE000
0018FF94: 0018FFD4
0018FF98: 770B9EF2 ? C:\Windows\SysWOW64\ntdll.dll + 39EF2
0018FF9C: 7EFDE000
0018FFA0: 6220F91F
0018FFA4: 00000000
0018FFA8: 00000000
0018FFAC: 7EFDE000
0018FFB0: 00000000
0018FFB4: 00000000
0018FFB8: 00000000
0018FFBC: 0018FFA0
0018FFC0: 00000000
0018FFC4: FFFFFFFF | TExcFrame.next
0018FFC8: 770F71D5 | C:\Windows\SysWOW64\ntdll.dll + 771D5

================================================================================
No posts in this topic were marked as the solution yet. If you can help, add your reply
I am experiencing crashes as well, with the same error in the log;

Exception EIntOverflow in module mm7_exe at 00085223.
Integer overflow.

I'm using the 1_6_2 unofficial patch.

It seems to me that the crash occurs when I press the 'interact' key frequently, such as when I'm looting multiple corpses. If I can't get this resolved, I won't be able to play the game, which would suck since it's my favorite in the series.

Did you ever find a solution OP?

If not, does anyone else have any idea how to fix this?

*replaced .s with _s due to gog complaining that I was posting links
Post edited January 18, 2013 by KrugSmash
First - sorry for a bit of necromancy (this is an old thread...)

I just bought & installed M&M 7 and I am experiencing the same issue (Exception EIntOverflow in module MM7.exe at 00085223.). This is with Greyface's patch installed (version 1.6.2).

Everything went mostly fine (though I had to use Software 3D to prevent constant screen flickering in game & menus). But once I started doing some combat the game started crashing. This would match KrugSmash's description - quick a repeated usage of "interaction" key may have triggered these crashes.

Did any of you experience similar issues ? And did you find a solution to them ?
avatar
JanRo: First - sorry for a bit of necromancy (this is an old thread...)

I just bought & installed M&M 7 and I am experiencing the same issue (Exception EIntOverflow in module MM7.exe at 00085223.). This is with Greyface's patch installed (version 1.6.2).

Everything went mostly fine (though I had to use Software 3D to prevent constant screen flickering in game & menus). But once I started doing some combat the game started crashing. This would match KrugSmash's description - quick a repeated usage of "interaction" key may have triggered these crashes.

Did any of you experience similar issues ? And did you find a solution to them ?
What OS and what 3d card...? I'm running MM7 with Win8.1x64 and an AMD 7850 2GB card, running the 14.3b Catalysts.
I'm also running the game @ 1600x1200 via MMRestool (I've posted a couple times in this forum about my very good experiences with that mod.) Game runs great--by far the best looking M&M game, imo--when using MMRestool to boost the D3d resolution far beyond what it is normally capable of. Really stunning in places.

The only thing that occurs to me is that maybe you haven't properly set up your D3d mode for the game--it's rather sensitive under a current OS (Win7/8) as to how you do that. I have a post in this forum somewhere in which I describe how I did it. If I can find the post I'll come back here and link it for you.

Edit: OK, I cannot find the original post I made--it's undoubtedly buried in a thread somewhere....;)

Here's what I remember for setting up D3d mode under Win8.1x64:

1) Run MM7setup.exe, enabling the 16-bit color, "disable high dpi," and "run as admin" compatibility options for the mm7setup executable
2) When mm7setup runs, if you have set the compatibility options for it as described here, then you will see under the "Video" heading that the "hardware accelerated 3d" radio button has been selected, and right below that you'll see the name of your 3d card
3) Under "Audio" my preference is to select the Miles 2d option
4)Then select the "Launch M&M VII" button and the game will run in D3d mode
5) Once the game loads in D3d mode then quit out of it.
6) Go to your MM7 game startup shortcut icon, and select "properties" in the context menu via a right-click
7) Edit the "Target:" box under the "shortcut" tab to say: "?:\Might and Magic VII - For Blood and Honor\MM7.exe" (? being the drive letter where the game is installed in your system)
8)Still in the "shortcut" tab, edit the "start in:" box to say: "?:\Might and Magic VII - For Blood and Honor\"

[note that 7 & 8 above assume you've used the installation default name of the game folder: Might and Magic VII - For Blood and Honor --if not, then change "target" and "start in" accordingly.]

9) This step may vary depending on your OS, possibly, but in Win8.1x64 I have *no* compatibility options at all set for MM7.exe, none at all, not even admin mode--and the game runs perfectly.

[note that MM7setup is only run once to set up D3d mode, and then only run again if you want for some reason to switch to software mode, etc.]
Post edited March 27, 2014 by waltc
Thank you Waltc :)

I use 64 bit Windows 7 and ATI Mobility Radeon 5870HD (I have a notebook).

Setting the system color depth to 16 bits seems to have helped me (along with game re-installation). When I loaded my previous saved game (in which the crash was 100% reproducible before) everything went smoothly. I am currently running the game with compatibility setting for XP service pack 3, "run as admin" and "disable display scaling on high dpi settings".

However, D3d hardware acceleration is not for me (unfortunately). If I choose this option in MM7setup.exe my screen flickers constantly (several white flashes per second). So I chose Software acceleration instead (and it seems to work fine for now).
avatar
JanRo: Thank you Waltc :)

I use 64 bit Windows 7 and ATI Mobility Radeon 5870HD (I have a notebook).

Setting the system color depth to 16 bits seems to have helped me (along with game re-installation). When I loaded my previous saved game (in which the crash was 100% reproducible before) everything went smoothly. I am currently running the game with compatibility setting for XP service pack 3, "run as admin" and "disable display scaling on high dpi settings".

However, D3d hardware acceleration is not for me (unfortunately). If I choose this option in MM7setup.exe my screen flickers constantly (several white flashes per second). So I chose Software acceleration instead (and it seems to work fine for now).
You honestly ought to be able to run this in D3d mode even in 32-bit color if you want to (certainly in software mode)--you definitely have the hardware to support it. The game is very lightweight compared with current games, and your system should be able to burp and run this game at the same time, no sweat...;)

A lot of people prefer the software mode, though, so it's really a matter of personal choice. Grey Face has stated that he prefers the software versions of these games--he and I disagree on D3d and something like MMrestool...;) The only thing I can think of that you might need to do is to install new drivers for your gpu if you haven't already done so. But, gosh, I hate to see you have to set your windows screen depth to 16-bits even while you run in software mode!

One last thing: did you say that you had downloaded the game from Gog recently? The reason I ask is because with the 2.x installer versions of their games, Gog has made a few relatively minor file changes that greatly enhance compatibility with Windows 7 and Windows 8. If you still have the 1.x Gog installer versions of the games you need to download the newer 2.x installer versions ASAP. I had a couple of Gog titles that I had difficulty running under 8.1x64 that ran fine after I installed the newer versions from Gog. Definitely do this if you haven't already.

Good luck!
I always knew that this issue wasn't about hardware's performance.

And regarding Software acceleration vs D3d. I tried to run the game in D3d & windowed mode and when I did this the screen flickering disappeared. So to summarize things: 32 bit color depth simply crashes no matter what and if I use 16 bit I have to avoid D3d fullscreen because it causes screen flickering.

Also - I downloaded the game just a couple of days ago. So I have the new installer.

Your suggestion about updating GPU drivers seems like a logical choice and I would have done it a long time ago if it had been possible. However, things aren't so easy with mobile GPUs. ATI (I guess it is the same with NVIDIA) never releases new drivers for specific mobile GPUs - just a generic mobile GPU driver (and this one tends to crash with my Mobility 5870HD on some occasions - I tried several versions over the past 2 years). And notebook manufacturers (ASUS in my case) just don't update drivers for specific notebook models too much so I have been stuck with the same driver for 2.5 years. Time to upgrade to desktop PC :) but I am still waiting for Witcher 3 with that :)
avatar
JanRo: I always knew that this issue wasn't about hardware's performance.

And regarding Software acceleration vs D3d. I tried to run the game in D3d & windowed mode and when I did this the screen flickering disappeared. So to summarize things: 32 bit color depth simply crashes no matter what and if I use 16 bit I have to avoid D3d fullscreen because it causes screen flickering.

Also - I downloaded the game just a couple of days ago. So I have the new installer.

Your suggestion about updating GPU drivers seems like a logical choice and I would have done it a long time ago if it had been possible. However, things aren't so easy with mobile GPUs. ATI (I guess it is the same with NVIDIA) never releases new drivers for specific mobile GPUs - just a generic mobile GPU driver (and this one tends to crash with my Mobility 5870HD on some occasions - I tried several versions over the past 2 years). And notebook manufacturers (ASUS in my case) just don't update drivers for specific notebook models too much so I have been stuck with the same driver for 2.5 years. Time to upgrade to desktop PC :) but I am still waiting for Witcher 3 with that :)
Yes, sounds good--you'll be much happier with a desktop! Everything is much simpler, easier, better--and frankly cheaper, too. I think desktops are the best deals going because they use standardized components and it's so easy to upgrade them to whatever extent you want, whenever you want. Laptops are just not suitable gaming platforms, imo. And, yes, I know about the problems with laptop gpu drivers--often you do have to go through the laptop OEM to get your drivers! Just another good reason to avoid laptops like the plague...;)

Well, good luck, and I hope you can get your desktop soon!