Topic: SFC3 Unhandled Exception STILL (Read 4128 times)

Mosquito · « **on:** October 16, 2003, 02:42:58 pm »

Unhandled Exception! in Version 1.01 Beta 2 Build 500
SFC3.exe caused an EXCEPTION_ACCESS_VIOLATION in module ModelRendererR.DLL at 001B:02C43FBE

EAX=00000D65 EBX=06A83D50 ECX=0000000C EDX=00000030 ESI=07A1DFF0
EDI=07AE62F0 EBP=0012E76C ESP=0012E5F0 EIP=02C43FBE FLG=00010216
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000

001B:02C43FBE (0x03000000 0x06A71088 0x06A71088 0x00000000) ModelRendererR.DLL
001B:02C445EC (0x06A83D50 0x02000000 0x06A71088 0x06A71088) ModelRendererR.DLL
001B:02C3163F (0x001FD020 0x00000000 0x06A80564 0x00000000) ModelRendererR.DLL

No other games on my system crash, but this one does all the time.

GRRRRRRRR

I HOPE this gets fixed as this game is entirely unenjoyable for me thus far (and I've owned it since March). I have only played off and on because of junk like this.

Pestalence · « **Reply #1 on:** October 17, 2003, 05:40:46 am »

What video card is your system running? If it is ATI Radeon, then downgrade your drivers to either the 2.3 catalist or the 2.6 catalist.. however you may need to upgrade your drivers again for other games.. just a problem with ATI Graphic card drivers...

Also, you may want to recheck your game installation and or game resolution.. if running an ATI Graphics card, you may need to downgrade your desktop color resolution from 32 bit to 16 bit.. and or lower the game to render at 800x600 for best performance...

If you are using a different video card, you may want to check for newer drivers for the card and / or adjust your monitor rendering settings (Color and size resolution) to something lower than you are using now... Also check for newer drivers for your system monitor and sound card (Render also includes sound)...

Hope that this helps...

Mosquito · « **Reply #2 on:** October 17, 2003, 12:37:03 pm »

Unhandled Exception! in Version 1.01 Beta 2 Build 500
SFC3.exe caused an EXCEPTION_ACCESS_VIOLATION in module TAL3DEngineR.DLL at 001B:028F777E

EAX=25C31758 EBX=02B10048 ECX=00000000 EDX=00000000 ESI=02B10048
EDI=000003E8 EBP=0012FD18 ESP=0012FD08 EIP=028F777E FLG=00010293
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000

001B:028F777E (0x25C31758 0x00000000 0x02B10048 0x00A531F0) TAL3DEngineR.DLL
001B:004C33C9 (0x25C31758 0x77D44D4D 0x0170F200 0x00000000) SFC3.exe
001B:004C04E9 (0x02B10048 0x00405920 0x02B10048 0x0040178A) SFC3.exe
001B:004786DE (0x009A1680 0x00407231 0x77D447E8 0x00634F55) SFC3.exe
001B:0040585E (0x00400000 0x00142371 0x00000001 0x00000000) SFC3.exe
001B:00635A43 (0x631AF1AB 0x80000002 0x7FFDF000 0xAEF14CF0) SFC3.exe
001B:77E814C7 (0x007BC5C9 0x00000000 0x78746341 0x00000020) kernel32.dll, GetCurrentDirectoryW()+0068 byte(s)

My system is not the problem here. I know a lot of people say that, but I actually know what I'm talking about.

AMD 2100+ @ 2289MHz
512MB PC2700 DDR @ 350Mhz
GeForce4 Ti-4600 @ 320/665Mhz
SB Audigy 1
Epox 8k5a3+ Motherboard

I am using the absolute latest drivers for everything I own, and they are all WHQL where appropriate. This is the only (ONLY!) game that crashes on my computer. Prime 95 runs for hours and hours so I know the system is as stable as a rock. This is poor programming.

I am merely posting these here so that someone who can (maybe) release a patch someday has this brought to their attention as well.

-Jason

David Ferrell · « **Reply #3 on:** October 17, 2003, 01:21:23 pm »

When does this error happen? Can you give any more details
to enlighten us as to the nature of the problem, or are you content
just calling it "poor programming"?

Thanks,

Dave

Mosquito · « **Reply #4 on:** October 17, 2003, 07:39:49 pm »

Sorry for the implied insult. I am angry that due to the Activision/Paramount issues the patch is still beta.

It occurs when switching between the countdown screen (mission pre-breifing) and the "Loading" screen.

It also sometimes occurs when going from the "Loading" screen to the actual battle (when the .dll is evidently being called upon to start giving graphics instructions I'd guess).

I just had it happen again, I am unsure which of the two occurances it happens more frequently on. I will be sure to check next time so I can give you an exact time.

Unhandled Exception! in Version 1.01 Beta 2 Build 500
SFC3.exe caused an EXCEPTION_ACCESS_VIOLATION in module TAL3DEngineR.DLL at 001B:028F777E

EAX=099A00E0 EBX=02B10048 ECX=00000000 EDX=00000000 ESI=02B10048
EDI=000003E8 EBP=0012FD18 ESP=0012FD08 EIP=028F777E FLG=00010293
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000

001B:028F777E (0x099A00E0 0x00000000 0x02B10048 0x00A531F0) TAL3DEngineR.DLL
001B:004C33C9 (0x099A00E0 0x77D44D4D 0x0170F200 0x00000000) SFC3.exe
001B:004C04E9 (0x02B10048 0x00405920 0x02B10048 0x0040178A) SFC3.exe
001B:004786DE (0x009A1680 0x00407231 0x77D447E8 0x00634F55) SFC3.exe
001B:0040585E (0x00400000 0x00142371 0x00000001 0x00000000) SFC3.exe
001B:00635A43 (0x631AF1AB 0x80000002 0x7FFDF000 0x00450058) SFC3.exe
001B:77E814C7 (0x007BC5C9 0x00000000 0x78746341 0x00000020) kernel32.dll, GetCurrentDirectoryW()+0068 byte(s)

Pestalence · « **Reply #5 on:** October 17, 2003, 08:52:21 pm »

I just noticed that you are running a geforce 4 Ti-4600 vid card.. the last drivers that were made WHQL for that video card were in Nov. 2002.. all drivers after November are WHQL for FX video cards, so if you are running the latest NVidia Detonator driver for your Geforce 4 TI-4600 card, then it is not WHQL certified for your card.. downgrade the driver to version 40.72 which is the latest Geforce 4 WHQL certified driver.. at least the latest recommended by NVidia as their Dec 2002 were for the Geforce 4 cards, but the driver was bugged and caused CTD on most games... NVidia stated in their Forums that the best and latest driver that they recommend for the Geforce 4 is the Nov. 11, 2002 v40.72 WHQL Detonator driver.. 98/ME driver was made Sept. 26, 2002.. XP version was made Nov. 11, 2002.

This information was posted on the NVidia web site next to the first set of FX drivers in Jan. 2003 (at least what part of the drivers are WHQL) the Geforce 4 cards were no longer WHQL supported after Nov. 2002.. the newer drivers will work for Geforce 4, however you may experience problems that you are currently having.. try reverting to the drivers i listed above by going to this Direct DL link and give it a whirl.. if it don't work, just roll back to your current driver (if you are running ME or XP).. takes 10 min at most to apply it, test the game, then uninstall if it doesn't work... If it does work, then congrats, it was a driver conflict after all.

Direct Driver Download Address :

XP version :

http://www.nvidia.com/object/winxp-2k_40.72.html

Win 98/ME version :

http://www.nvidia.com/object/win9x_40.72.html

Actual release date was Oct 26, 2002...

the December Geforce 4 drivers were WHQL, however, they proved to be bugged and as such, nVidia recommended reverting to the 40.72 drivers for the Geforce 4 Video cards...

try this and see what happens, even if you think it won't work.. I'm willing to bet that this is the problem.. you are running a FX card driver on your Geforce 4 video card...

Thanks

David Ferrell · « **Reply #6 on:** October 18, 2003, 12:21:44 am »

Are you able to run several missions and then you get the
error or does it happen the 1st time you run a mission in a
SFC3 session?

If it happens after several missions, you may have to save
and shutdown then restart the game more frequently. We do
have a memory leak issue that we haven't been able to plug.
My apologies for this but at least a part of it is a fundamental
flaw in the .gf system.

Thanks,

Dave

Mosquito · « **Reply #7 on:** October 20, 2003, 06:01:10 am »

Well...I have taken a break while the campaign I play finishes up. I can almost guarantee that it has never happened during the first mission.

I still plan on reporting back when exactly it occurrs.

-Jas

WaterTiger · « **Reply #8 on:** October 20, 2003, 08:33:10 am »

Sir,

That is line-by-line the EXACT error I have, and I also have a G-Force card.

There were G-force Nvidea updates put out in July. Nvidea's latest update includes an option for "best performance", and when I chose this option, many of these errors were limited. Mind you, they periodically occured, but the frequency was less.

Also, try this: Go to your Activision/SFC3 folder, then go to ASSETS, then SCRIPTS folder. Open it. You will see a small file named "AllScripts.cache" ... delete that. It will reappear after you log off. Delete it again. That file seems to be the core of another problem, but once deleted, the game crashes less for sure.

Before my G-Force, there were issues with the ATI card and game compatability.

A patch is coming soon -- have faith. I used to be as critical in these very forums, and I can tell you it does no good.

Chin up and try what I told you.

WaterTiger

Founder and council member,

Brotherhood of Trans-Atlantic Knights

Mosquito · « **Reply #9 on:** October 22, 2003, 03:13:14 am »

Unhandled Exception! in Version 1.01 Beta 2 Build 500
SFC3.exe caused an EXCEPTION_ACCESS_VIOLATION in module ModelRendererR.DLL at 001B:02C43FBE

EAX=00000437 EBX=059DAEF8 ECX=0000000C EDX=00000030 ESI=061D7FF0
EDI=06217110 EBP=0012E76C ESP=0012E5F0 EIP=02C43FBE FLG=00010216
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000

001B:02C43FBE (0x03000000 0x059D1C10 0x059D1C10 0x00000000) ModelRendererR.DLL
001B:02C445EC (0x059DAEF8 0x02000000 0x059D1C10 0x059D1C10) ModelRendererR.DLL
001B:02C3163F (0x04F915A0 0x00000000 0x059D493E 0x00000000) ModelRendererR.DLL

This was immediately after the "Loading" screen (bar was full) during a skirmish. I never saw the rendered battlefield.

Tombstone · « **Reply #10 on:** October 24, 2003, 05:47:39 pm »

I had this problem once myself. Here is what I did to fix it:

Search your SFC3 folder for "*.x" (that's all files with a .x extension) and delete them. There should be 2 in each folder for each model.

These appear to be just cache files used by the game for the models. It will recreate them as needed.

After I did this, I never had the problem again. Hope this helps.

Tombstone

emsgoof · « **Reply #11 on:** October 24, 2003, 10:11:02 pm »

Are you running in 16 or 32 bit color? I ask because my FX5200 card gave me the same problems when I installed it (same exception error), and someone mentioned on the sfc3.net forums that switching to 16 bit color fixed it for the ATI cards... sure enough, that did it!

*edit*
That'll teach me to reply to posts with only 3 hours of sleep and a 15 hour work day...
Different exception error than I had, but heck, give it a try anyways!

Mosquito · « **Reply #12 on:** October 16, 2003, 02:42:58 pm »

Unhandled Exception! in Version 1.01 Beta 2 Build 500
SFC3.exe caused an EXCEPTION_ACCESS_VIOLATION in module ModelRendererR.DLL at 001B:02C43FBE

EAX=00000D65 EBX=06A83D50 ECX=0000000C EDX=00000030 ESI=07A1DFF0
EDI=07AE62F0 EBP=0012E76C ESP=0012E5F0 EIP=02C43FBE FLG=00010216
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000

001B:02C43FBE (0x03000000 0x06A71088 0x06A71088 0x00000000) ModelRendererR.DLL
001B:02C445EC (0x06A83D50 0x02000000 0x06A71088 0x06A71088) ModelRendererR.DLL
001B:02C3163F (0x001FD020 0x00000000 0x06A80564 0x00000000) ModelRendererR.DLL

No other games on my system crash, but this one does all the time.

GRRRRRRRR

I HOPE this gets fixed as this game is entirely unenjoyable for me thus far (and I've owned it since March). I have only played off and on because of junk like this.

Pestalence · « **Reply #13 on:** October 17, 2003, 05:40:46 am »

What video card is your system running? If it is ATI Radeon, then downgrade your drivers to either the 2.3 catalist or the 2.6 catalist.. however you may need to upgrade your drivers again for other games.. just a problem with ATI Graphic card drivers...

Also, you may want to recheck your game installation and or game resolution.. if running an ATI Graphics card, you may need to downgrade your desktop color resolution from 32 bit to 16 bit.. and or lower the game to render at 800x600 for best performance...

If you are using a different video card, you may want to check for newer drivers for the card and / or adjust your monitor rendering settings (Color and size resolution) to something lower than you are using now... Also check for newer drivers for your system monitor and sound card (Render also includes sound)...

Hope that this helps...

Mosquito · « **Reply #14 on:** October 17, 2003, 12:37:03 pm »

Unhandled Exception! in Version 1.01 Beta 2 Build 500
SFC3.exe caused an EXCEPTION_ACCESS_VIOLATION in module TAL3DEngineR.DLL at 001B:028F777E

EAX=25C31758 EBX=02B10048 ECX=00000000 EDX=00000000 ESI=02B10048
EDI=000003E8 EBP=0012FD18 ESP=0012FD08 EIP=028F777E FLG=00010293
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000

001B:028F777E (0x25C31758 0x00000000 0x02B10048 0x00A531F0) TAL3DEngineR.DLL
001B:004C33C9 (0x25C31758 0x77D44D4D 0x0170F200 0x00000000) SFC3.exe
001B:004C04E9 (0x02B10048 0x00405920 0x02B10048 0x0040178A) SFC3.exe
001B:004786DE (0x009A1680 0x00407231 0x77D447E8 0x00634F55) SFC3.exe
001B:0040585E (0x00400000 0x00142371 0x00000001 0x00000000) SFC3.exe
001B:00635A43 (0x631AF1AB 0x80000002 0x7FFDF000 0xAEF14CF0) SFC3.exe
001B:77E814C7 (0x007BC5C9 0x00000000 0x78746341 0x00000020) kernel32.dll, GetCurrentDirectoryW()+0068 byte(s)

My system is not the problem here. I know a lot of people say that, but I actually know what I'm talking about.

AMD 2100+ @ 2289MHz
512MB PC2700 DDR @ 350Mhz
GeForce4 Ti-4600 @ 320/665Mhz
SB Audigy 1
Epox 8k5a3+ Motherboard

I am using the absolute latest drivers for everything I own, and they are all WHQL where appropriate. This is the only (ONLY!) game that crashes on my computer. Prime 95 runs for hours and hours so I know the system is as stable as a rock. This is poor programming.

I am merely posting these here so that someone who can (maybe) release a patch someday has this brought to their attention as well.

-Jason

David Ferrell · « **Reply #15 on:** October 17, 2003, 01:21:23 pm »

When does this error happen? Can you give any more details
to enlighten us as to the nature of the problem, or are you content
just calling it "poor programming"?

Thanks,

Dave

Mosquito · « **Reply #16 on:** October 17, 2003, 07:39:49 pm »

Sorry for the implied insult. I am angry that due to the Activision/Paramount issues the patch is still beta.

It occurs when switching between the countdown screen (mission pre-breifing) and the "Loading" screen.

It also sometimes occurs when going from the "Loading" screen to the actual battle (when the .dll is evidently being called upon to start giving graphics instructions I'd guess).

I just had it happen again, I am unsure which of the two occurances it happens more frequently on. I will be sure to check next time so I can give you an exact time.

Unhandled Exception! in Version 1.01 Beta 2 Build 500
SFC3.exe caused an EXCEPTION_ACCESS_VIOLATION in module TAL3DEngineR.DLL at 001B:028F777E

EAX=099A00E0 EBX=02B10048 ECX=00000000 EDX=00000000 ESI=02B10048
EDI=000003E8 EBP=0012FD18 ESP=0012FD08 EIP=028F777E FLG=00010293
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000

001B:028F777E (0x099A00E0 0x00000000 0x02B10048 0x00A531F0) TAL3DEngineR.DLL
001B:004C33C9 (0x099A00E0 0x77D44D4D 0x0170F200 0x00000000) SFC3.exe
001B:004C04E9 (0x02B10048 0x00405920 0x02B10048 0x0040178A) SFC3.exe
001B:004786DE (0x009A1680 0x00407231 0x77D447E8 0x00634F55) SFC3.exe
001B:0040585E (0x00400000 0x00142371 0x00000001 0x00000000) SFC3.exe
001B:00635A43 (0x631AF1AB 0x80000002 0x7FFDF000 0x00450058) SFC3.exe
001B:77E814C7 (0x007BC5C9 0x00000000 0x78746341 0x00000020) kernel32.dll, GetCurrentDirectoryW()+0068 byte(s)

Pestalence · « **Reply #17 on:** October 17, 2003, 08:52:21 pm »

I just noticed that you are running a geforce 4 Ti-4600 vid card.. the last drivers that were made WHQL for that video card were in Nov. 2002.. all drivers after November are WHQL for FX video cards, so if you are running the latest NVidia Detonator driver for your Geforce 4 TI-4600 card, then it is not WHQL certified for your card.. downgrade the driver to version 40.72 which is the latest Geforce 4 WHQL certified driver.. at least the latest recommended by NVidia as their Dec 2002 were for the Geforce 4 cards, but the driver was bugged and caused CTD on most games... NVidia stated in their Forums that the best and latest driver that they recommend for the Geforce 4 is the Nov. 11, 2002 v40.72 WHQL Detonator driver.. 98/ME driver was made Sept. 26, 2002.. XP version was made Nov. 11, 2002.

This information was posted on the NVidia web site next to the first set of FX drivers in Jan. 2003 (at least what part of the drivers are WHQL) the Geforce 4 cards were no longer WHQL supported after Nov. 2002.. the newer drivers will work for Geforce 4, however you may experience problems that you are currently having.. try reverting to the drivers i listed above by going to this Direct DL link and give it a whirl.. if it don't work, just roll back to your current driver (if you are running ME or XP).. takes 10 min at most to apply it, test the game, then uninstall if it doesn't work... If it does work, then congrats, it was a driver conflict after all.

Direct Driver Download Address :

XP version :

http://www.nvidia.com/object/winxp-2k_40.72.html

Win 98/ME version :

http://www.nvidia.com/object/win9x_40.72.html

Actual release date was Oct 26, 2002...

the December Geforce 4 drivers were WHQL, however, they proved to be bugged and as such, nVidia recommended reverting to the 40.72 drivers for the Geforce 4 Video cards...

try this and see what happens, even if you think it won't work.. I'm willing to bet that this is the problem.. you are running a FX card driver on your Geforce 4 video card...

Thanks

David Ferrell · « **Reply #18 on:** October 18, 2003, 12:21:44 am »

Are you able to run several missions and then you get the
error or does it happen the 1st time you run a mission in a
SFC3 session?

If it happens after several missions, you may have to save
and shutdown then restart the game more frequently. We do
have a memory leak issue that we haven't been able to plug.
My apologies for this but at least a part of it is a fundamental
flaw in the .gf system.

Thanks,

Dave

Mosquito · « **Reply #19 on:** October 20, 2003, 06:01:10 am »

Well...I have taken a break while the campaign I play finishes up. I can almost guarantee that it has never happened during the first mission.

I still plan on reporting back when exactly it occurrs.

-Jas

News:

Topic: SFC3 Unhandled Exception STILL (Read 4128 times) var addthis_config = {"data_track_clickback":true};

Mosquito

Pestalence

Mosquito

David Ferrell

Mosquito

Pestalence

David Ferrell

Mosquito

WaterTiger

Mosquito

Tombstone

emsgoof

Mosquito

Pestalence

Mosquito

David Ferrell

Mosquito

Pestalence

David Ferrell

Mosquito

Topic: SFC3 Unhandled Exception STILL (Read 4128 times)