• Google Translate to French or Other Languages Click on the link and a new tab will open with this page translated into French.
    Click on the "To:" pull down option to select a different language. Users will not be logged in on the new Google tab.

bam 338 crash

hellrzr2k1

Pinball Wizard
In win10 I never needed to run anything on compatibility mode.

BUT I do recall that some problems were solved by running as Administrator... @TerryRed BAM+FP install guide maybe?

Side note: As far as I know FPLoader calls FuturePinball.exe, hence the name. running one or the other as Admin or compatibility mode it's all the same if you ask me.
In win 10 it was the latest update within the last month or so I never had issues until that update.
 

hellrzr2k1

Pinball Wizard
bam refuses to start
the window appears then disappears immediately.
is this due to recent update of win 10, and preparation for the transition to win 11? (kernel.dll)
no problem before the start of the week.....!!!!!!

Code:
------------------- BAM crash-report -------------
  BAM path: C:\Games\Future Pinball\BAM
       XML:
     table:
         1: TAG: FILE=dllmain.cpp, LINE=1033, FUNC=Routed_CreateFileA
         2: TAG: FILE=dllmain.cpp, LINE=4134, FUNC=DllMain
       SBC: -1
       NFC: 0
Loaded modules:
Future Pinball.exe, 1.9.2008.1225 : 00400000 - 01F3F000
ntdll.dll, 6.2.19041.1288 : 76F80000 - 77123000
KERNEL32.DLL, 6.2.19041.1202 : 76C60000 - 76D50000
KERNELBASE.dll, 6.2.19041.1288 : 76830000 - 76A45000
apphelp.dll, 6.2.19041.928 : 6FC00000 - 6FC9F000
USER32.dll, 6.2.19041.1288 : 76570000 - 76710000
win32u.dll, 6.2.19041.1288 : 75F40000 - 75F58000
GDI32.dll, 6.2.19041.1202 : 75940000 - 75964000
gdi32full.dll, 6.2.19041.1110 : 760D0000 - 761AC000
COMCTL32.dll, 6.10.19041.1110 : 74980000 - 74B90000
Newton.dll,  : 10000000 - 10071000
msvcp_win.dll, 6.2.19041.789 : 76BE0000 - 76C5B000
ucrtbase.dll, 6.2.19041.789 : 76D50000 - 76E70000
msvcrt.dll, 7.0.19041.546 : 764B0000 - 7656F000
COMDLG32.dll, 6.2.19041.906 : 76780000 - 7682F000
combase.dll, 6.2.19041.1288 : 761B0000 - 76431000
RPCRT4.dll, 6.2.19041.1288 : 74E40000 - 74EFF000
shcore.dll, 6.2.19041.1266 : 76A90000 - 76B17000
SHLWAPI.dll, 6.2.19041.1023 : 76730000 - 76775000
SHELL32.dll, 6.2.19041.1266 : 75970000 - 75F23000
ADVAPI32.dll, 6.2.19041.1052 : 75780000 - 757FA000
sechost.dll, 6.2.19041.906 : 75800000 - 75875000
ole32.dll, 6.2.19041.1202 : 75FE0000 - 760C3000
OLEAUT32.dll, 6.2.19041.985 : 75050000 - 750E6000
DINPUT8.dll, 6.2.19041.1 : 6D330000 - 6D367000
GLU32.dll, 6.2.19041.1081 : 74940000 - 7497F000
OPENGL32.dll, 6.2.19041.1081 : 6FCA0000 - 6FDA3000
fmod.dll, 3.7.4.0 : 02680000 - 02716000
libcurl.dll, 7.13.1.0 : 02720000 - 027BD000
DevIL.dll, 0.1.6.5 : 027C0000 - 02933000
ILU.dll, 0.1.6.5 : 020D0000 - 020E3000
ILUT.dll, 0.1.6.5 : 02180000 - 0218D000
WINMM.dll, 6.2.19041.546 : 6F730000 - 6F758000
MSACM32.dll, 6.2.19041.1 : 74920000 - 74939000
WSOCK32.dll, 6.2.19041.1 : 748E0000 - 748E8000
WS2_32.dll, 6.2.19041.546 : 76440000 - 764A3000
winmmbase.dll, 6.2.19041.1 : 748C0000 - 748DD000
WININET.dll, 11.0.19041.1202 : 6C9F0000 - 6CE40000
IMM32.DLL, 6.2.19041.546 : 74F00000 - 74F25000
BAM.dll, 1.5.338.0 : 6C370000 - 6C9E7000
PSAPI.DLL, 6.2.19041.546 : 75020000 - 75026000
SETUPAPI.dll, 6.2.19041.1237 : 750F0000 - 7552C000
cfgmgr32.dll, 6.2.19041.1151 : 76A50000 - 76A8B000
bcrypt.dll, 6.2.19041.1023 : 75030000 - 75049000
VERSION.dll, 6.2.19041.546 : 74DC0000 - 74DC8000
HID.DLL, 6.2.19041.546 : 6D9F0000 - 6D9FA000
renderingengine.dll,  : 6BE40000 - 6C368000
--------------------------------------------------
Error code 40010006: (unknown)

   Address: 7695B5B2 -> KERNELBASE.dll:0012B5B2
     Flags: 00000000

  Fault Occured At $ADDRESS:7695B5B2 ->KERNELBASE.dll:0012B5B2
         with 06 00 01 40 00 00 00 00 02 00 00 00 64 D5 19 00 81 91 D7 2F

   Address: 76927A46 -> KERNELBASE.dll:000F7A46
***  0 called from $ADDRESS:76927A46
         with C4 4B C6 6A F0 64 6B 08 D0 DF C6 04 44 06 00 00 F0 00 00 00

   Address: 6A4C951F -> UNKNOWN:6A4C951F
***  1 called from $ADDRESS:6A4C951F
         with 20 50 89 6A 44 55 C2 04 00 00 00 00 E0 42 C2 04 00 00 00 00

   Address: 6A446B19 -> UNKNOWN:6A446B19
***  2 called from $ADDRESS:6A446B19
         with 48 DC 19 00 E0 42 C2 04 D0 B4 70 08 1C 93 00 8F 00 00 00 00

   Address: 6A5CFE6D -> UNKNOWN:6A5CFE6D
***  3 called from $ADDRESS:6A5CFE6D
         with A0 98 07 6B 14 E0 19 00 F0 E9 C0 04 00 00 00 40 D0 B4 70 08

   Address: 6A5D0343 -> UNKNOWN:6A5D0343
***  4 called from $ADDRESS:6A5D0343
         with 01 C0 00 00 C4 DE 19 00 48 DC 19 00 A0 98 07 6B 40 70 5A 6A

   Address: 6A5A707A -> UNKNOWN:6A5A707A
***  5 called from $ADDRESS:6A5A707A
         with 00 00 00 00 B1 E5 8C 13 00 00 00 00 A4 A3 13 6B 60 FF 19 00

   Address: 6B0BC3D5 -> UNKNOWN:6B0BC3D5
***  6 called from $ADDRESS:6B0BC3D5
         with 14 E0 19 00 F0 E9 C0 04 00 00 00 00 00 00 00 40 00 00 00 00

   Address: 6B169E36 -> UNKNOWN:6B169E36
***  7 called from $ADDRESS:6B169E36
         with F0 F1 19 00 80 1E 16 6B 18 DE C0 04 00 00 00 00 70 C8 00 00

   Address: 6B169A09 -> UNKNOWN:6B169A09
***  8 called from $ADDRESS:6B169A09
         with 1F 0C 01 1C 80 1E 16 6B 80 1E 16 6B 74 EB 19 00 00 00 00 00

   Address: 6B16486A -> UNKNOWN:6B16486A
***  9 called from $ADDRESS:6B16486A
         with 00 00 00 00 FF FF FF FF 80 1E 16 6B 00 00 00 00 00 00 00 00

   Address: 6B1690E6 -> UNKNOWN:6B1690E6
*** 10 called from $ADDRESS:6B1690E6
         with 00 00 00 00 00 00 02 00 00 00 00 00 10 63 59 76 00 00 00 00

   Address: 6B18DEF9 -> UNKNOWN:6B18DEF9
*** 11 called from $ADDRESS:6B18DEF9
         with 00 00 00 00 C4 98 D2 05 D4 05 54 00 00 00 00 00 00 00 40 00

   Address: 0044A4A6 -> Future Pinball.exe:0004A4A6
*** 12 called from $ADDRESS:0044A4A6
         with

   Address: 00240360 -> UNKNOWN:00240360
*** 13 called from $ADDRESS:00240360
Yeah buddy, its the latest win 10 F***date
 

GeorgeH

Flippered Out
Staff member
Site Supporters
In win10 I never needed to run anything on compatibility mode.

BUT I do recall that some problems were solved by running as Administrator... @TerryRed BAM+FP install guide maybe?

Side note: As far as I know FPLoader calls FuturePinball.exe, hence the name. running one or the other as Admin or compatibility mode it's all the same if you ask me.
It has been awhile since I experimented with it, but my experience has shown that if you change one, the other changes also.
 

TerryRed

Pinball Master
Simply put... never EVER change the futurepinball.exe to run as Admin...ever. If you do that... and FPLoader.exe is NOT set to run as Admin.... then BAM can never work properly because you have elevated the FP EXE above it in Windows, so it can't have full access to it (this also restricts other apps from accessing it). I have seen people do this so many damn times after I've specifically told them not to... and they always have problems.

"Sometimes", you may need to run only the FPLoader.exe as admin at least "once" to properly allow it access within Windows... but after that you can change it back. You may need to do this after updating BAM, but not normally. This has worked for pretty much everyone (and is what Baller installer does - changes to admin, run once, then change back). As long as you don't have other Windows restrictions in place (like Defender,etc)

I'm on the newest update for Win 10, and I still have never needed to use any compatibility mode for FP or BAM.
 
Last edited:

hellrzr2k1

Pinball Wizard
Simply put... never EVER change the futurepinball.exe to run as Admin...ever. If you do that... and FPLoader.exe is NOT set to run as Admin.... then BAM can never work properly because you have elevated the FP EXE above it in Windows, so it can't have full access to it (this also restricts other apps from accessing it). I have seen people do this so many damn times after I've specifically told them not to... and they always have problems.

"Sometimes", you may need to run only the FPLoader.exe as admin at least "once" to properly allow it access within Windows... but after that you can change it back. You may need to do this after updating BAM, but not normally. This has worked for pretty much everyone (and is what Baller installer does - changes to admin, run once, then change back). As along as you don't have other Windows restrictions in place (like Defender,etc)

I'm on the newest update for Win 10, and I st
I used ballerinstaller never ran as admin or set compat mode. never had a issue until that last win10 update.
maybe its a hardware issue / update combo.
amdfx, nvidia1070... im banking its nvidia...

BamXrashlog when i remove compat mode on fp.exe

------------------- BAM crash-report -------------
BAM path: C:\vPinball\FuturePinball\BAM
XML:
table:
1: TAG: FILE=dllmain.cpp, LINE=1033, FUNC=Routed_CreateFileA
2: TAG: FILE=dllmain.cpp, LINE=4134, FUNC=DllMain
SBC: -1
NFC: 0
Loaded modules:
Future Pinball.exe, 1.9.2008.1225 : 00400000 - 01F3F000
ntdll.dll, 6.2.19041.1288 : 77D10000 - 77EB3000
KERNEL32.DLL, 6.2.19041.1348 : 762D0000 - 763C0000
KERNELBASE.dll, 6.2.19041.1348 : 766E0000 - 768F4000
apphelp.dll, 6.2.19041.1320 : 71690000 - 7172F000
USER32.dll, 6.2.19041.1348 : 76540000 - 766E0000
win32u.dll, 6.2.19041.1320 : 77630000 - 77648000
COMCTL32.dll, 6.10.19041.1110 : 73610000 - 73820000
GDI32.dll, 6.2.19041.1202 : 75CA0000 - 75CC4000
gdi32full.dll, 6.2.19041.1320 : 774F0000 - 775CC000
msvcrt.dll, 7.0.19041.546 : 76F50000 - 7700F000
fmod.dll, 3.7.4.0 : 10000000 - 10096000
msvcp_win.dll, 6.2.19041.789 : 76D40000 - 76DBB000
ucrtbase.dll, 6.2.19041.789 : 77700000 - 77820000
ADVAPI32.dll, 6.2.19041.1052 : 77AD0000 - 77B4A000
COMDLG32.dll, 6.2.19041.906 : 77650000 - 776FF000
sechost.dll, 6.2.19041.906 : 764C0000 - 76535000
combase.dll, 6.2.19041.1348 : 77010000 - 77291000
RPCRT4.dll, 6.2.19041.1288 : 75BE0000 - 75C9F000
shcore.dll, 6.2.19041.1320 : 76DC0000 - 76E47000
ole32.dll, 6.2.19041.1202 : 779C0000 - 77AA3000
SHLWAPI.dll, 6.2.19041.1023 : 77CB0000 - 77CF5000
MSACM32.dll, 6.2.19041.1 : 66D60000 - 66D79000
SHELL32.dll, 6.2.19041.1320 : 75D10000 - 762C3000
WINMM.dll, 6.2.19041.546 : 73500000 - 73528000
OLEAUT32.dll, 6.2.19041.985 : 763C0000 - 76456000
WSOCK32.dll, 6.2.19041.1 : 71D00000 - 71D08000
WS2_32.dll, 6.2.19041.546 : 77850000 - 778B3000
winmmbase.dll, 6.2.19041.1 : 66F30000 - 66F4D000
DINPUT8.dll, 6.2.19041.1 : 6F290000 - 6F2C7000
GLU32.dll, 6.2.19041.1081 : 71CC0000 - 71CFF000
OPENGL32.dll, 6.2.19041.1081 : 618D0000 - 619D3000
Newton.dll, : 02230000 - 022A1000
libcurl.dll, 7.13.1.0 : 026C0000 - 0275D000
ILU.dll, 0.1.6.5 : 02760000 - 02773000
ILUT.dll, 0.1.6.5 : 022B0000 - 022BD000
DevIL.dll, 0.1.6.5 : 02780000 - 028F3000
WININET.dll, 11.0.19041.1320 : 71F20000 - 72376000
IMM32.DLL, 6.2.19041.546 : 77820000 - 77845000
BAM.dll, 1.5.337.0 : 61250000 - 618C7000
PSAPI.DLL, 6.2.19041.546 : 75BD0000 - 75BD6000
SETUPAPI.dll, 6.2.19041.1237 : 76900000 - 76D3C000
cfgmgr32.dll, 6.2.19041.1151 : 75CD0000 - 75D0B000
bcrypt.dll, 6.2.19041.1023 : 76EB0000 - 76EC9000
VERSION.dll, 6.2.19041.546 : 73A30000 - 73A38000
HID.DLL, 6.2.19041.546 : 70CC0000 - 70CCA000
renderingengine.dll, : 60D20000 - 61248000
--------------------------------------------------
Error code 40010006: (unknown)

Address: 7680B502 -> KERNELBASE.dll:0012B502
Flags: 00000000

Fault Occured At $ADDRESS:7680B502 ->KERNELBASE.dll:0012B502
with 06 00 01 40 00 00 00 00 02 00 00 00 64 D5 19 00 05 D6 F1 9F

Address: 767D79D6 -> KERNELBASE.dll:000F79D6
*** 0 called from $ADDRESS:767D79D6
with B4 5B F3 5E B0 AF D6 04 90 F6 D5 04 94 06 00 00 F0 00 00 00

Address: 5E79951F -> UNKNOWN:5E79951F
*** 1 called from $ADDRESS:5E79951F
with A0 5C B6 5E F4 0D D4 04 00 00 00 00 90 FB D3 04 00 00 00 00

Address: 5E716B19 -> UNKNOWN:5E716B19
*** 2 called from $ADDRESS:5E716B19
with 48 DC 19 00 90 FB D3 04 28 73 D3 04 9E 3C 00 A2 00 00 00 00

Address: 5E89FE7D -> UNKNOWN:5E89FE7D
*** 3 called from $ADDRESS:5E89FE7D
with A0 98 21 65 14 E0 19 00 60 33 D3 04 00 00 00 40 28 73 D3 04

Address: 5E8A0353 -> UNKNOWN:5E8A0353
*** 4 called from $ADDRESS:5E8A0353
with 01 C0 00 00 C4 DE 19 00 48 DC 19 00 A0 98 21 65 90 70 87 5E

Address: 5E8770CA -> UNKNOWN:5E8770CA
*** 5 called from $ADDRESS:5E8770CA
with 00 00 00 00 BE EB D5 8B 00 00 00 00 A4 A3 2D 65 60 FF 19 00

Address: 6525C3D5 -> UNKNOWN:6525C3D5
*** 6 called from $ADDRESS:6525C3D5
with 14 E0 19 00 60 33 D3 04 00 00 00 00 00 00 00 40 00 00 00 00

Address: 60639E36 -> UNKNOWN:60639E36
*** 7 called from $ADDRESS:60639E36
with F0 F1 19 00 80 1E 63 60 88 27 D3 04 00 00 00 00 2D AE 00 00

Address: 60639A09 -> UNKNOWN:60639A09
*** 8 called from $ADDRESS:60639A09
with 83 18 01 6B 80 1E 63 60 80 1E 63 60 74 EB 19 00 00 00 00 00

Address: 6063486A -> UNKNOWN:6063486A
*** 9 called from $ADDRESS:6063486A
with 00 00 00 00 FF FF FF FF 80 1E 63 60 00 00 00 00 00 00 00 00

Address: 606390E6 -> UNKNOWN:606390E6
*** 10 called from $ADDRESS:606390E6
with 00 00 00 00 00 00 02 00 00 00 00 00 60 60 56 76 00 00 00 00

Address: 6065DEF9 -> UNKNOWN:6065DEF9
*** 11 called from $ADDRESS:6065DEF9
with 00 00 00 00 C4 98 09 06 D4 05 54 00 00 00 00 00 00 00 40 00

Address: 0044A4A6 -> Future Pinball.exe:0004A4A6
*** 12 called from $ADDRESS:0044A4A6
with

Address: 003709BE -> UNKNOWN:003709BE
*** 13 called from $ADDRESS:003709BE
 

TerryRed

Pinball Master
I'm running a GTX 1080.

Be sure you manually update the Nvidia drivers yourself. Everytime there is a big Win 10 update... you need to manually update your drivers as Win 10 rolls back to its own crappy drivers.
 

hellrzr2k1

Pinball Wizard
I'm running a GTX 1080.

Be sure you manually update the Nvidia drivers yourself. Everytime there is a big Win 10 update... you need to manually update your drivers as Win 10 rolls back to its own crappy drivers.
just installed the latest 10 min ago. still crashes if I remove the compat mode.
who knows, could be hardware, bios, amd isuue . atleast it works.
btw have you all notices the price double or more on all video cards.
i paid 225.00 about 2 1/2 years ago for a 8gb 1070 superclock black ed. they are 450 to 600.00 now
 

hellrzr2k1

Pinball Wizard
Yup... chip shortages has increased prices for everything...especially gpus. Damn asshole bitcoin
We have a big outlet here when the new rtx cards came out you couldnt get to the store traffic was so bad. There was a line atleast 100 yards to the entrance. They changed bit mining, theres a new way to do it.
 

AnonTet

Pinball Hall of Famer
Site Supporters
I don't see any but if there's other than whatever is normal for PF it's still doesn't beat the fact that without compatibility mode (win8 for me) I can't run it :)

/edit to mention again:
- i'm on win11
- same as popotte below. While in win10 i used no compatibility mode. It just worked.
 
Last edited:

fastdraw

Inserted Coin
it is OK for me. đź‘Ť
disables administrator mode (fploader), no compatibility mode.
update win10. (19044.1348)

win.jpg
 

AnonTet

Pinball Hall of Famer
Site Supporters
@halen
Run fploader.exe in windows 8 compatibility mode
Run fploader as administrator at least once (no need to always have it running as administrator)
 

AnonTet

Pinball Hall of Famer
Site Supporters
just had a couple of updates (one was big) in win11. For those of you who use it, it seems to solve some issues, namely, no need to run fploader.exe in win8 compatibility mode.

I'm actually doing heavy I/O operations and CPU operations right now and it still loaded heavy tables and no crashes (obviously there are hiccups because I'm using my PC resources with higher priority) but proves that it is, at least for now, more stable.
 

pcraenme

Pinball Nudger
I am experiencing the same crashes as @hellrzr2k1. I recently updated to Windows 10 Pro 21H2 and NVIDIA driver version 496.76. I maty be a coincidence, but my graphics card is a GTX 1070 as well. Sometimes it will start though, but when playing a table it will crash after a while.
 
General chit-chat
Help Users
  • No one is chatting at the moment.
    There are no messages in the chat. Be the first one to say Hi!
    Top