A picky unhandled exception

[Lugubrious Hatchling]

Hey dudes!

So I tried to get back into I76 and thanks to your tutorials I managed to get it to work quite well on windows 10.
The game runs perfectly fine, however, if I fire certain weapons the game will crash with the infamous "Unhandled Exception" error.
For example; I am able to use cannons just fine, but If I use any type of MG, rockets or even caltrops, as soon as I fire, the sound will trigger, I see the tracer but then the game will freeze and immediatly crash. Funnily enough, if other cars use these weapons nothing will happen, the game just runs normally. I can hear them perfectly fine as well by the way.

I've tried many things for a couple of days now to no success. I have both the gog and standard version of nitro, and they both have the same problem.

Any ideas?

Thanks in advance.

[Lightfoot]

I'd guess you're running the unapproved NITSHELL.DLL or you didn't get the permissions right when you were installing the patches.

Check those.

[Lugubrious Hatchling]

Hey Lightfoot, thanks for the reply.

I tried deleting the NITSHELL and replacing it with the original like you said, but exact same behaviour.
I also tried reinstalling the game to do it all over again on a new folder to rule out any permission I might have messed up but I think I did everything correctly. It shows my name there on the Activision folder with full access to everything, granted before updating the game.

Also tried another clean install on another drive using a GOG copy but it acts the same way.

What am I missing here?

[Lightfoot]

We don't support the GOG installation in any way shape or form but considering you're having the same issues across versions I'd say it has something to do with your video renderer. Check the Application error logs and find out which DLL is causing fault in NITRO.EXE and go from there. If it's faulting in the EXE change your video mode from -glide to -d3d or remove the switch.

[Lugubrious Hatchling]

According to the log, "I7_SFRCE.DLL" is the source of the problem. No idea what this one does.
Tried different rendering modes, including software but problem persists.

[Lugubrious Hatchling]

Okay so I tried replacing the dll from a fresh install and tried replacing it with a gold edition dll but its the same, so, guess what? I removed the file and it just worked!
I'm gonna run some tests tonight and see if there are any more issues.

Thanks for the help Lightfoot!

[Lightfoot]

No worries, my dude.

Let us know.

[Lugubrious Hatchling]

I guess that's it. Tested it all night on SP and tested it on MP and it works just fine.
For future reference, problem fixed by removing the faulty "I7_SFRCE.DLL"

Problem solved.

[456CYR]

I get a rare blackscreen followed by "blahblahblah has stopped responding" when blowing up a car in an auto melee. in both base I76 and Nitro. Eventvwr log doesn't point to any .dlls. My guess is some DGVoodoo related shit.
"Faulting application name: nitro.exe, version: 1.0.0.1, time stamp: 0x351c24ce
Faulting module name: nitro.exe, version: 1.0.0.1, time stamp: 0x351c24ce
Exception code: 0xc0000005
Fault offset: 0x0006efc0"

[456CYR]

Should mention that it's also followed by an "Unhandled Exception" in Nitro's case, but not in the base game. Weird.

[Lightfoot]

My first question would be: "Which car?"

My second question would be: "Can you reproduce it at will"?

Let me know and I'll help you troubleshoot it.

TBH - It sounds like a paint problem.

[456CYR]

Fairly certain limiting my game to 25 fps via the .exes patched by immi fixed it. I'll do some more testing and report back eventually.

[456CYR]

Right as I was about to deal the finishing blow to a Moth Cargo Truck with a Napalm Turret:
Faulting application name: nitro.exe, version: 1.0.0.1, time stamp: 0x351c24ce
Faulting module name: nitro.exe, version: 1.0.0.1, time stamp: 0x351c24ce
Exception code: 0xc0000005
Fault offset: 0x000189c5

[KIV 6051 [SH]]

I'm fairly certain this is the same sound bug that plagued Windows XP(?) users, which I can only describe by listing how it was produced:

1. Install the game from the original disc using the original install exe files (with the inevitable warnings of course)
2. Launch game (yay it launched )
3. Click any button (wait wut)
4. KaBLaM!

This bug had something to do with the sound code, or cheap, built-in sound cards with crappy Windows XP drivers. I just remember the solution being a lengthy, hit-and-miss workaround.