FP TABLES CRASH...

[Grover5]

HEY ALL.  I dont  think this has been mentioned..   I can load and play all tables but after some play time 1-3 minutes the screen freezes then crashes... tried a reload and tried Administration on or off but continues.  I loaded a few more tables and same thing.   They act like they are on a trial basis or something... or like it hits a certain memory limit then shuts down.   Varies on complexity of table.  Any ideas??

[JimmyCoupe]

I have joined the gang on Future Pinball\Bam crashing to the desktop after 5-10 minutes.  Before you give your generic response "TerryRed" yes I have run the program once as an Administrator, no its not in Windows 8 compatibility mode, no I don't have the "Nahimic" driver so its clearly not that and yes its always related to a pinup video tables.  No I don't run shortcuts from the desktop, yes I do close and open for a new table, yes I do always run FPLoader, yes I have reinstalled and finally  yes I have bought new hardware.  It did it on my last PC and it does it on my new PC.  Can anyone else share the magic of what is going on here and how do I make BAM\Future pinball stable so it doesn't crash to the desktop after 5-10 minutes when running a pinup table?   oh and finally I do the the most recent version installed from the link you provided :-).

 

A good example is Terminator 2 its like its in demo mode and the timing of the crash is super consistent.

 

I have just applied the 4gb patch, still does it :-), its like I am being terminated by the Terminator.  To me this smells of a AMD driver issue and nothing to do with the generic response.   Faulting module name: atioglxx.dll, version: 31.0.21921.1000

 

This is the crash info from Windows Event viewer:

 

Log Name:      Application
Source:        Application Error
Date:          27/02/2025 21:02:40
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:      
User:          PinCab\jrg19
Computer:      PinCab
Description:
Faulting application name: Future Pinball.exe, version: 1.9.2008.1225, time stamp: 0x4d1d68d3
Faulting module name: atioglxx.dll, version: 31.0.21921.1000, time stamp: 0x66bb7bd9
Exception code: 0xc0000409
Fault offset: 0x01e245c0
Faulting process id: 0x27C8
Faulting application start time: 0x1DB89595D5D5D8C
Faulting application path: C:\FuturePinball\Future Pinball.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\u0407052.inf_amd64_84d15514ad17ffa0\B406619\atioglxx.dll
Report Id: de1da800-01ac-4094-a076-a77b63410516
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
    <EventID>1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2025-02-27T21:02:40.5530533Z" />
    <EventRecordID>3072</EventRecordID>
    <Correlation />
    <Execution ProcessID="8940" ThreadID="4568" />
    <Channel>Application</Channel>
    <Computer>PinCab</Computer>
    <Security UserID="S-1-5-21-1795354413-2490247556-4135708773-1001" />
  </System>
  <EventData>
    <Data Name="AppName">Future Pinball.exe</Data>
    <Data Name="AppVersion">1.9.2008.1225</Data>
    <Data Name="AppTimeStamp">4d1d68d3</Data>
    <Data Name="ModuleName">atioglxx.dll</Data>
    <Data Name="ModuleVersion">31.0.21921.1000</Data>
    <Data Name="ModuleTimeStamp">66bb7bd9</Data>
    <Data Name="ExceptionCode">c0000409</Data>
    <Data Name="FaultingOffset">01e245c0</Data>
    <Data Name="ProcessId">0x27c8</Data>
    <Data Name="ProcessCreationTime">0x1db89595d5d5d8c</Data>
    <Data Name="AppPath">C:\FuturePinball\Future Pinball.exe</Data>
    <Data Name="ModulePath">C:\WINDOWS\System32\DriverStore\FileRepository\u0407052.inf_amd64_84d15514ad17ffa0\B406619\atioglxx.dll</Data>
    <Data Name="IntegratorReportId">de1da800-01ac-4094-a076-a77b63410516</Data>
    <Data Name="PackageFullName">
    </Data>
    <Data Name="PackageRelativeAppId">
    </Data>
  </EventData>
</Event>

Edited February 27, 2025 by JimmyCoupe

[WaRcLaWz]

I have the same issue. Tables play great for 5-10 minutes and then FP hard crashes to the Desktop.

[TerryRed]

HOW TO RUN FP and PLAY THE TABLE

 

• only use FPLoader.exe (this is BAM) in the BAM folder to play this table
• DO NOT run directly from the FuturePinball.exe
• don't trust start menu or desktop icons (they may point to FuturePinball.exe)
• you “may” need to run FPLoader.exe as Administrator “once” for BAM to work correctly
• DO NOT keep FPLoader.exe set to Run as Administrator
• DO NOT set FPLoader.exe to Windows 8 compatibility mode
• ALWAYS completely close Future Pinball after exiting a table, or loading another table
• Future Pinball needs to start “fresh” every time you load or start a table

 

If you are having regular crashing problems when running Future Pinball:

 

·       some users may need to remove / disable the "Nahimic driver" or some of it's processes if they have this installed (it's known to cause problems)

·       Windows Defender or other anti-virus apps can cause problems with FP, and may need to be disabled, or at the very least have the FP folder added to their exceptions

 

Most crashing problems (on a properly setup FP on a capable PC) are the result of Windows restricting access to FP or some other app / driver is interfering or causing the crash.

 

If it's a PinEvent table, try disabling PinEvent (in TABLE OPTIONS in the table script) which will disable DOF / PUP, etc and see if you still have problems.

 

Edited November 15, 2023 by TerryRed

[Morgus_uy]

Hi everyone! I have Visual Pinball installed with Pinup Popper and it works perfectly, I installed future pinball + BAM to configure a kinect, but after starting a table I cannot close the application, it remains unresponsive, I tried in compatibility mode, as administrator, outside of pinup, etc. . but nothing works. I also tried updating to Windows 11, I don't know what I can do.

[TerryRed]

45 minutes ago, JimmyCoupe said:

I have joined the gang on Future Pinball\Bam crashing to the desktop after 5-10 minutes.  Before you give your generic response "TerryRed" yes I have run the program once as an Administrator, no its not in Windows 8 compatibility mode, no I don't have the "Nahimic" driver so its clearly not that and yes its always related to a pinup video tables.  No I don't run shortcuts from the desktop, yes I do close and open for a new table, yes I do always run FPLoader, yes I have reinstalled and finally  yes I have bought new hardware.  It did it on my last PC and it does it on my new PC.  Can anyone else share the magic of what is going on here and how do I make BAM\Future pinball stable so it doesn't crash to the desktop after 5-10 minutes when running a pinup table?   oh and finally I do the the most recent version installed from the link you provided :-).

 

A good example is Terminator 2 its like its in demo mode and the timing of the crash is super consistent.

 

 

No one likes to help anyone who starts off with a pissy "Before you give your generic response TerryRed" response. You aren't entitled to anything and any help or guidance given from me or anyone is done out of kindness with the intent to help... and should be treated with more respect than that. You're more than welcome to continue on your own. I have better things I could be doing.

 

 

What has been causing this problem for the people who do have it is the result of a few things:

 

- your PC has an AMD GPU

- you are running with the FP Backbox enabled

- you may have DOFLinx running in the background (if installed) when it needs to be closed when running PinEvent tables

 

For whatever reason, for some people, AMD GPUs and their (problematic as always) drivers have this issue of causing FP to crash after a short amount of play time, but this seems to only happen if the FP Backbox screen is enabled in FP video settings. nVidia / other GPUs don't have this problem (everyone who reported this issue have AMD GPUs).

 

 

The only solutions are:

 

- disable the FP Backbox (this was "required" anyway if using PinEvent pup features)

- enable PUP features on PinEvent V2 tables and display their pup dmd / backbox displays on your 2nd and 3rd screens

- for other DMD based tables use DMDext to mirror the FP DMD to another monitor

- ensure DOFLinx is not running at all while running PinEvent tables

 

To disable the FP Backbox the easy way (when not using a front-end), use the "Start FP - PinEvent.bat" files to run FP. This will automatically disable the FP Backbox for you before FP starts, and also will set the required settings for FP as well.

 

If using Popper as a front-end, be sure you are entering PinEvent in Games Manager for each table to disable the FP Backbox (as described in my PinEvent and Popper guides and Install Instructions for each table)

 

If running one of those bat files (to disable the FP Backbox) does not fix the problem... then beyond going with an nvidia gpu (assuming you do have an AMD gpu), there's no known solution to get around this AMD related problem.

 

 

Edited February 27, 2025 by TerryRed

[JimmyCoupe]

Thanks Terry :-). the post was to dodge the standard response and try to understand the cause which seemed to work.  Now I know the issue its time to give up on my mission to get it working.  I have no choice but to run my system using the built in AMD GPU but its good to finally get to the core of the issue.

 

It kind of feels like some kind of memory leak being caused by the driver due to the consistent timing on an effected table.  If it helps at all my old Ryzen 3200G CPU used the much older AMD driver and my new Ryzen 5700G CPU is using the new AMD driver, both have the exactly the same issue but I do honestly appreciate your response.

[TerryRed]

28 minutes ago, JimmyCoupe said:

Thanks Terry :-). the post was to dodge the standard response and try to understand the cause which seemed to work.  Now I know the issue its time to give up on my mission to get it working.  I have no choice but to run my system using the built in AMD GPU but its good to finally get to the core of the issue.

 

It kind of feels like some kind of memory leak being caused by the driver due to the consistent timing on an effected table.  If it helps at all my old Ryzen 3200G CPU used the much older AMD driver and my new Ryzen 5700G CPU is using the new AMD driver, both have the exactly the same issue but I do honestly appreciate your response.

 

Sorry for jumping the gun.

 

If you are enabling the FP Backbox, then try the suggestions I posted to disable it. If that fixes it, then at least all the DMD / PinEvent tables should still work without crashing and you have alternate display options for them.

Edited February 27, 2025 by TerryRed

[JimmyCoupe]

Thanks Terry and no need to be sorry at all.  Really I should be sorry as well :-).  I will have another look tomorrow evening and let you know how I get on and once again thanks for the help as its appreciated.

[JimmyCoupe]

TerryRed, I have made some good progress today.  "I ran the Start FP - PinEvent PuP-Pack - DMDExt.bat" to turn off the backglass and DMD as you suggested and I setup DMDext to my backglass monitor.  I am using PinballX frontend so I then added the "DMDExt_FP.bat" to the launch before section.   I then untick the "Hide Backglass" for the table in the PinballX game manager to use the backglass picture that is used in the pinballX frontend.  

 

Is this the correct approach?  it seems to work 🙂

 

I am not seeing a save position of the DMDext for the game, only globally.  In the documentation it say this:

 

"use the table's [GAMENAME] in Popper to allow the option to manually save "per table" settings (for style, colour, size position, etc)"  

 

but I am using PinballX so a little confused.

 

** I am no longer getting any crash to desktops, finally I have stability on my AMD GPU 🙂 **

Edited February 28, 2025 by JimmyCoupe