Help Solved FP Crashes

[GeorgeH]

Guys,

I never thought I would be using this help option but I keep having FP crash with BAM. When I press play on a table, it goes through the table loading process and then I get a short glimpse of the table and it crashes. I can play tables without BAM without any problem. I have set the FPLoader.exe file to compatibility mode for Windows 8 and it still crashes. I have completely reinstalled FP and BAM using the 2 in 1 installer and it still crashes.

Any ideas?

George

 

[xenonph]

Have you tried right clicking the BAM shortcut on desktop and going to Properties, Compatibility, and checkmark run as administrator?
I have to do this on my setup, otherwise I get meditation error. I never messed with Compatibility mode for Windows. I am using Win 7 64X

 

[GeorgeH]

Have you tried right clicking the BAM shortcut on desktop and going to Properties, Compatibility, and checkmark run as administrator?
I have to do this on my setup, otherwise I get meditation error. I never messed with Compatibility mode for Windows. I am using Win 7 64X

I ran it as administrator but it didn't help.

 

[TerryRed]

Try completely removing FP's settings from the registry. Then run FP and reapply your Video and Editor settings, etc.



When the table is loaded and is about to start, then FP tries to apply registry settings, etc. If there is anything there that it doesn't like or is confused by, it will cause a crash.

I had to do that yesterday when testing my new GPU (RTX 3080 baby!) in VR. Kept crashing until I removed the registry settings to start fresh.

Also... don't assume Defender or other A/V apps are ok with FP, even if it was before. New BAM updates may get flagged... the 4 GB patch may get flagged... and once the table starts, those apps may restrict BAM from working and cause a crash.

 

[GeorgeH]

Try completely removing FP's settings from the registry. Then run FP and reapply your Video and Editor settings, etc.

When the table is loaded and is about to start, then FP tries to apply registry settings, etc. If there is anything there that it doesn't like or is confused by, it will cause a crash.

I had to do that yesterday when testing my new GPU (RTX 3080 baby!) in VR. Kept crashing until I removed the registry settings to start fresh.

Also... don't assume Defender or other A/V apps are ok with FP, even if it was before. New BAM updates may get flagged... the 4 GB patch may get flagged... and once the table starts, those apps may restrict BAM from working and cause a crash.

Terry,

That worked!

Thank you,

George

 

[TerryRed]

Nice!

I think it may have something to do with a Windows update, or a GPU driver update... or a monitor not being turned on before Windows startup (or resuming from sleep) that may cause FP to get confused with which "Display" it needs to use. Same thing can happen for cabinet users when they turn on their cabinets, and their PC boots up before their multiple monitors / tvs are fully powered on and detected.

It's a combination of Windows "pains" and FP old'ness :)

 

[GeorgeH]

I sent a message to Rav about this. He says to try latest v349 version. There were debug leftovers. Now it should work fine.

 

[illrod3k]

I was experiencing the same issue, updated to latest version v349, resolved the issue, thanks guys , appreciate you all :)

 

[GeorgeH]

If anyone else is having this problem, you can download BAM 349 here:

ravarcade.pl - Download

Better Arcade Mode for Future Pinball Cabinet

www.ravarcade.pl

 

[TXT11]

I've just started having this problem too, mainly on the older FP tables. I'm running the latest 1.5.365 version @ 16/1/2024. Have recently updated from Win 7 to Win 10 to allow for GPU upgrade. Should I attempt to remove all the FP settings in the registry? This won't upset all my POV settings for all my installed FP tables will it?

 

[TerryRed]

Some older tables may crash because they weren't built correctly. (rare) Just because they may have run before, doesnt mean they still dont have a problem (some added certain table items with no models which can cause issues)

If newer PinEvent and Fizx based tables are running fine, then you shouldn't need to change anything in FP as long as you are using the exact FP settings I show in my Install Instructions for PinEvent tables (and in my FP and BAM Essentials AIO - Install guide)

 

[GeorgeH]

I've just started having this problem too, mainly on the older FP tables. I'm running the latest 1.5.365 version @ 16/1/2024. Have recently updated from Win 7 to Win 10 to allow for GPU upgrade. Should I attempt to remove all the FP settings in the registry? This won't upset all my POV settings for all my installed FP tables will it?

I have to agree with Terry, your problem is probably caused by something else. I was experiencing crashes on every table that I attempted to load. If you have installed version v349 or later, then it is highly unlikely that this is your problem.

You might try playing the tables that crash with just straight FP with no front end programs at all. If they don't crash, then there must be something in your setup of the front ends. If you still have crashes, I can try playing them on my PC to see if they crash.

 

[TXT11]

It's not all older FP tables, just ones like Die Hard and Knight Rider. Ones that might have been ZED updated, but not much else. Then I can load an oldie like Hawaiian Beauty fine. My PinEvemt and FizX tables load fine. I will try the FP direct (none BAM) load and see if that works. Crash logs seem to mention something about problems with "Newton.dll" but that's a core file for original FP isn't it?

 

[GeorgeH]

It's not all older FP tables, just ones like Die Hard and Knight Rider. Ones that might have been ZED updated, but not much else. Then I can load an oldie like Hawaiian Beauty fine. My PinEvemt and FizX tables load fine. I will try the FP direct (none BAM) load and see if that works. Crash logs seem to mention something about problems with "Newton.dll" but that's a core file for original FP isn't it?

I think Newton.dll is the file that runs Newton physics. I would say FP needs it to run and probably not the cause of your problem since you have some tables that play. The FP direct test would just help to identify where the problem is. If the author says the table needs BAM to run, you will need to use it.

 

[jamosb]

Try completely removing FP's settings from the registry. Then run FP and reapply your Video and Editor settings, etc.

View attachment 25394

When the table is loaded and is about to start, then FP tries to apply registry settings, etc. If there is anything there that it doesn't like or is confused by, it will cause a crash.

I had to do that yesterday when testing my new GPU (RTX 3080 baby!) in VR. Kept crashing until I removed the registry settings to start fresh.

Also... don't assume Defender or other A/V apps are ok with FP, even if it was before. New BAM updates may get flagged... the 4 GB patch may get flagged... and once the table starts, those apps may restrict BAM from working and cause a crash.

worked for me but hint please note your settings before you delete reg entry do a screen shot.