8 replies to this topic

[djm468]

Using latest BAM/FP, Access Denied crashes on opening control configuration and launching tables:

 

Appears to be the same error on both occasions and the weird thing is that I initially had BAM/FP working on this particular PC (as well as a few others using the same source). I was not using the latest AIO on those occasions. The only issue I had was stretched tables.

 

So I copied the default.cfg, reality.dat, etc. from the AIO package on the other (still working) PCs, which fixed the stretching and all was well with them.

 

Then I tried this on the latest PC and it went from stretched tables to this error:

 

------------------- BAM crash-report -------------

  BAM path: D:\Emulators\Future Pinball 2\BAM

       XML: 

     table: 

         1: TAG: FILE=C:\work\github\BAM\BAM\BAM.cpp, LINE=1457, FUNC= BAM::FirstFrame

         2: TAG: FILE=C:\work\github\BAM\BAM\dllmain.cpp, LINE=4382, FUNC= DllMain

       SBC: -1

       NFC: 0

Loaded modules:

BAM-Tracker.exe, 1.0.0.1 : 005E0000 - 00615000

ntdll.dll, 6.2.19041.4355 : 77990000 - 77B34000

KERNEL32.DLL, 6.2.19041.4355 : 77330000 - 77420000

KERNELBASE.dll, 6.2.19041.4412 : 75930000 - 75B6A000

apphelp.dll, 6.2.19041.3636 : 740A0000 - 7413F000

USER32.dll, 6.2.19041.4412 : 769A0000 - 76B3D000

win32u.dll, 6.2.19041.4412 : 75E20000 - 75E38000

GDI32.dll, 6.2.19041.4355 : 777A0000 - 777C3000

gdi32full.dll, 6.2.19041.4412 : 765A0000 - 76686000

msvcp_win.dll, 6.2.19041.3636 : 776C0000 - 7773B000

ucrtbase.dll, 6.2.19041.3636 : 777D0000 - 778F0000

ADVAPI32.dll, 6.2.19041.4355 : 77210000 - 7728D000

msvcrt.dll, 7.0.19041.3636 : 768E0000 - 7699F000

sechost.dll, 6.2.19041.4355 : 766B0000 - 76728000

RPCRT4.dll, 6.2.19041.4412 : 767C0000 - 7687C000

bcrypt.dll, 6.2.19041.3636 : 776A0000 - 776B9000

SHELL32.dll, 6.2.19041.4412 : 76B40000 - 77117000

ole32.dll, 6.2.19041.4355 : 77120000 - 77203000

combase.dll, 6.2.19041.4412 : 77420000 - 776A0000

OLEAUT32.dll, 6.2.19041.3636 : 77290000 - 77326000

COMCTL32.dll, 6.10.19041.4355 : 74250000 - 74460000

BAM.dll, 1.5.373.0 : 6D2C0000 - 6DCAC000

COMDLG32.dll, 6.2.19041.4355 : 75880000 - 7592F000

shcore.dll, 6.2.19041.4355 : 76730000 - 767B7000

SHLWAPI.dll, 6.2.19041.4355 : 76550000 - 76595000

PSAPI.DLL, 6.2.19041.3636 : 75E10000 - 75E16000

SETUPAPI.dll, 6.2.19041.4355 : 76110000 - 76548000

cfgmgr32.dll, 6.2.19041.3996 : 778F0000 - 7792B000

VERSION.dll, 6.2.19041.3636 : 755B0000 - 755B8000

GLU32.dll, 6.2.19041.3636 : 756C0000 - 756FF000

OPENGL32.dll, 6.2.19041.4355 : 75700000 - 75803000

DINPUT8.dll, 6.2.19041.1 : 75680000 - 756B7000

HID.DLL, 6.2.19041.3636 : 70180000 - 7018A000

WINMM.dll, 6.2.19041.3636 : 752F0000 - 75318000

AVIFIL32.dll, 6.2.19041.1 : 75660000 - 7567B000

AVICAP32.dll, 6.2.19041.1 : 75640000 - 75654000

MSVFW32.dll, 6.2.19041.1 : 75610000 - 75632000

MSACM32.dll, 6.2.19041.1 : 701C0000 - 701D9000

winmmbase.dll, 6.2.19041.1 : 701A0000 - 701BD000

IMM32.DLL, 6.2.19041.4355 : 75D80000 - 75DA6000

renderingengine.dll,  : 6CD90000 - 6D2B8000

FreeTrack.dll,  : 755F0000 - 7560B000

icom.dll,  : 755C0000 - 755D2000

VCRUNTIME140.dll, 14.29.29917.0 : 75570000 - 75584000

MSVCP140.dll, 14.29.29917.0 : 75500000 - 7556D000

PinballHighScore.dll,  : 6CCA0000 - 6CD86000

MSVCR120.dll, 12.0.40664.0 : 6CBB0000 - 6CC9E000

MSVCP120.dll, 12.0.40664.0 : 75480000 - 754F1000

PuPPlugin.dll,  : 74B80000 - 74BBE000

d3d11.dll, 6.2.19041.4355 : 6E730000 - 6E910000

dxgi.dll, 6.2.19041.4355 : 6E660000 - 6E722000

TrackIR.dll,  : 74B70000 - 74B77000

MSVCR100.dll, 10.0.40219.325 : 6F180000 - 6F23F000

inputhost.dll, 6.2.19041.4355 : 6F950000 - 6FA3D000

CoreUIComponents.dll, 6.2.19041.3636 : 6F5F0000 - 6F86F000

CoreMessaging.dll, 6.2.19041.4355 : 6F550000 - 6F5EB000

wintypes.dll, 6.2.19041.4355 : 6F870000 - 6F94D000

PROPSYS.dll, 7.0.19041.4355 : 74A50000 - 74B12000

ntmarta.dll, 6.2.19041.3636 : 74BD0000 - 74BF9000

WS2_32.dll, 6.2.19041.3636 : 75810000 - 75873000

bcryptPrimitives.dll, 6.2.19041.3636 : 77740000 - 7779F000

kernel.appcore.dll, 6.2.19041.3758 : 74BC0000 - 74BCF000

uxtheme.dll, 6.2.19041.4355 : 75320000 - 75394000

MSCTF.dll, 6.2.19041.4355 : 75B80000 - 75C53000

DEVOBJ.dll, 6.2.19041.4355 : 6FA40000 - 6FA69000

WINTRUST.dll, 6.2.19041.4355 : 77930000 - 7797C000

CRYPT32.dll, 6.2.19041.4412 : 76010000 - 76110000

MSASN1.dll, 6.2.19041.3636 : 6FAA0000 - 6FAAE000

textinputframework.dll, 6.2.19041.4355 : 6EE20000 - 6EED9000

windows.storage.dll, 6.2.19041.4412 : 74C30000 - 75243000

Wldp.dll, 6.2.19041.4355 : 74C00000 - 74C25000

TextShaping.dll,  : 6FBD0000 - 6FC65000

--------------------------------------------------

Error code C0000005: ACCESS VIOLATION

 

   Address: 00000000 -> UNKNOWN:00000000

     Flags: 00000000

 

  Fault Occured At $ADDRESS:00000000 ->UNKNOWN:00000000

         with 01 00 00 00 41 8A 32 6D 01 00 00 00 1E 5E 5E 00 01 00 00 00 

 

   Address: 6D39D347 -> BAM.dll:000DD347

***  0 called from $ADDRESS:6D39D347

         with EC 36 B2 00 01 00 00 00 EA A1 5E 00 01 00 00 00 08 00 00 00 

 

   Address: 005E6E02 -> BAM-Tracker.exe:00006E02

***  1 called from $ADDRESS:005E6E02

         with 00 00 5E 00 00 00 00 00 EC 36 B2 00 01 00 00 00 1E 8B 0B 66 

 

   Address: 005EA2F1 -> BAM-Tracker.exe:0000A2F1

***  2 called from $ADDRESS:005EA2F1

         with 00 40 8F 00 B0 FC 34 77 

 

   Address: 7734FCC9 -> KERNEL32.DLL:0001FCC9

***  3 called from $ADDRESS:7734FCC9

         with 00 40 8F 00 CF B3 80 7A 00 00 00 00 00 00 00 00 00 40 8F 00 

 

   Address: 779F7CBE -> ntdll.dll:00067CBE

***  4 called from $ADDRESS:779F7CBE

         with FF FF FF FF 34 8D A1 77 

 

   Address: 779F7C8E -> ntdll.dll:00067C8E

***  5 called from $ADDRESS:779F7C8E

         with 

 

   Address: 00000000 -> UNKNOWN:00000000

***  6 called from $ADDRESS:00000000

 

This is almost certainly my fault, as I didn't realize that BAM and FP should not be set to run as administrator (apparently running FPLoader once as administrator does the trick). So I flailed around a bit, with DOFLinx crashing with a similar error, due to the elevated privileges of FP. After I unchecked those boxes and had the  BAM CFG files from the AIO package where they belonged, I figured all would be well, but now all is very much not well.

 

Any clues would be most appreciated. I've tried seemingly everything at this point, including disabling real-time protection (already had an exclusion for the drive it is on, but figured why not?)

 

Also tried creating fresh folders, using the latest AIO, following all of the instructions to the letter (pretty much know them by heart at this point). I even scoured the registry for everything I could find FP-related and deleting it and then starting over.

 

It's seemingly impossible to launch an FP table on this thing now. I know that can't be the case, but am seriously considering replacing the entire drive (and the Windows drive) at this point.

 

Using Windows 10 Pro with a nice NVidia graphics card and a very capable CPU. Of course, I can run FP all day on a crappy mini PC with no video card at all without issue.

 

Please let me know if you need more details. I'm keen to know how to fix this issue, not just for the sake of this one PC, which is the outlier in my experience, but in case something like this comes up again.

 

Thanks in advance!

Edited by djm468, 04 June 2024 - 05:28 AM.

[fhjui]

According to the xC000005 access denied error, I guess thats the reason is located in windows itself

• please check all these executable FP files (exe, dll and table file) that they are unblocked
• disable defender completely
• set UAC to lowest level
• a vpin should not have a connection to the internet, to avoid updates, new OS etc.
  block internet acces in the router configuration
• you can remote access the vpin using tools like TightVNC

Edited by fhjui, 04 June 2024 - 09:25 AM.

[GeorgeH]

I suggest checking the folders also to be sure they are unblocked.  You just right click on the file or folder and click on Properties.  Look at the General>Advanced option and be sure option index contents is checked.  Also check the security tab to be sure you have full edit abilities. 

 

Also, don't install the FP program to the programs folder.  FP/BAM needs to be able to save files to the folder and the programs folder does not allow that. 

Edited by GeorgeH, 04 June 2024 - 05:43 PM.

[djm468]

Replies inline, as can't figure out how to break up the quotes.

 

 

According to the xC000005 access denied error, I guess thats the reason is located in windows itself

• please check all these executable FP files (exe, dll and table file) that they are unblocked

< They are, but will check again.

• disable defender completely

< The Internet can't seem to agree on how to do that, but I had turned off real-time protection and tamper protection. Is that what you mean? AFAIK, they may come back on their own. I also have an exclusion for the D: drive.

• set UAC to lowest level

That I haven't tried. Will do.

• a vpin should not have a connection to the internet, to avoid updates, new OS etc.
  block internet acces in the router configuration

This one definitely connects to the Internet, but I typically block major updates by policy.

 

• you can remote access the vpin using tools like TightVNC

< Thanks for the advice! Will post back...

Replies inline, as can't figure out how to break up quotes. (?)

 

I suggest checking the folders also to be sure they are unblocked.  You just right click on the file or folder and click on Properties.  Look at the General>Advanced option and be sure option index contents is checked.  Also check the security tab to be sure you have full edit abilities. 

 

< Indexing turned on? Yes, I assume it is, but not sure why that would help. (?)

 

Also, don't install the FP program to the programs folder.  FP/BAM needs to be able to save files to the folder and the programs folder does not allow that. 

 

< It's on the D: drive; Windows is on C:

 

< Thanks for the advice!

Edited by djm468, 04 June 2024 - 06:25 PM.

[GeorgeH]

I suggest checking the folders also to be sure they are unblocked.  You just right click on the file or folder and click on Properties.  Look at the General>Advanced option and be sure option index contents is checked.  Also check the security tab to be sure you have full edit abilities. 

 

< Indexing turned on? Yes, I assume it is, but not sure why that would help. (?)

 

Also, don't install the FP program to the programs folder.  FP/BAM needs to be able to save files to the folder and the programs folder does not allow that. 

 

< It's on the D: drive; Windows is on C:

 

< Thanks for the advice!

 

You missed this "Also check the security tab to be sure you have full edit abilities."

[djm468]

 

I suggest checking the folders also to be sure they are unblocked.  You just right click on the file or folder and click on Properties.  Look at the General>Advanced option and be sure option index contents is checked.  Also check the security tab to be sure you have full edit abilities. 

 

< Indexing turned on? Yes, I assume it is, but not sure why that would help. (?)

 

Also, don't install the FP program to the programs folder.  FP/BAM needs to be able to save files to the folder and the programs folder does not allow that. 

 

< It's on the D: drive; Windows is on C:

 

< Thanks for the advice!

 

You missed this "Also check the security tab to be sure you have full edit abilities."

 

 

It's an admin user and admin users have "Full Control" per the Security tab. Only thing unchecked is "special" permissions (whatever that means).

 

I've pretty much given up and I don't think it's any coincidence that so many people out there seem to be having mysterious problems with BAM/FP. It can get hosed up in Windows and it seems that all you can do is start over on a clean install.

 

But I should stress that I probably brought this on myself by not following the instructions to the letter. I suspect that running FP and/or BAM as admin was its downfall. Or could possibly have been a Windows update, but seems unlikely, as it is "pegged" to the current major version in the Policy Editor.

 

I've gotten FP (with and without BAM) running on lots of PCs and had no issues for years. This is only the third or so with BAM and the others used old versions. This one is the first time I tried the AIO package and it seems that it can't salvage the situation (or it's just going to be too much trouble to do so). It's a shame, as there are some really nice tables on that system, including some you can't get anywhere else.

 

Going to just hide the FP playlist in Popper and call it a cabinet (unless there are other suggestions).

 

Thanks all!

[fhjui]

from the distance I have no "golden" idea to point at the cause of the error, only some suggestions...it would be too much effort to dive into the system using sysinternal tools

• the first thing that should be done before installing vpin software is to install the VC runtime versions, they an be downloaded https://www.techpowe...age-all-in-one/
• you have recognized not to run FP as admin, thats correct. In former windows versions (Win7) and older FP versions it was necessary in most cases to run them as admin
• you can delete the registry hive of FP "HKEY_CURRENT_USER\Software\Future Pinball", perhaps there are some nonsens values saved. Before deletion its a good idea to export this hive into a file. If not successful the values can be imported again. Otherwise the configuration has to be repeated.
  At the next start of FP the standard values are created autom.
• try to reinstall FP+BAM using the package from ravarcade.pl
• I think you read the BAM info guide from TerryRed. In the new version its integrated within the AIO package (in the directory Setup and Guides)
  Here are some videos with install instructions https://vpuniverse.c...de-by-terryred/

Edited by fhjui, 06 June 2024 - 02:01 PM.

[GeorgeH]

My guide is here:

 

https://pinballnirva...art-here.20851/

 

TerryRed has a different approach on his guide.

[djm468]

Replies inline.

 

 

from the distance I have no "golden" idea to point at the cause of the error, only some suggestions...it would be too much effort to dive into the system using sysinternal tools

• the first thing that should be done before installing vpin software is to install the VC runtime versions, they an be downloaded https://www.techpowe...age-all-in-one/

 

< That is done every time for sure. Same "all-in-one" BAT file as always.

• you have recognized not to run FP as admin, thats correct. In former windows versions (Win7) and older FP versions it was necessary in most cases to run them as admin

< Yep, I think it can actually be a disaster for various reasons. Certainly it breaks DOFLinx (for valid reasons).

 

• you can delete the registry hive of FP "HKEY_CURRENT_USER\Software\Future Pinball", perhaps there are some nonsens values saved. Before deletion its a good idea to export this hive into a file. If not successful the values can be imported again. Otherwise the configuration has to be repeated.

< Did that many times. I have REG files for all of that as well, but I just used the AIO REG files for the later attempts, after the original started fouling up.

• At the next start of FP the standard values are created autom.

< Not sure what you mean, but I import either my own or the AIO REG files before running FPLoader for the first time (once as admin, right?)

• try to reinstall FP+BAM using the package from ravarcade.pl

< Well, I never messed with the installers (if that's what you mean), but I used the stuff in AIO, which seems to work for a lot of people (and seemingly not some others, like me on this one PC). I think I also tried the ones on that site, but that may have been on another machine.

• I think you read the BAM info guide from TerryRed. In the new version its integrated within the AIO package (in the directory Setup and Guides)
  Here are some videos with install instructions https://vpuniverse.c...de-by-terryred/

< Oh, right. Yes, I tried a couple of times to start from scratch with a new folder, copy over the files in the ZIP, etc.

 

< Anyway, it "came back to life" today. Here's what I think was going on: I was testing by running FPLoader and opening tables manually. Today, just by chance, I used my "standard" BAT file to launch a table from a shortcut and it came right up. So I think that whatever happened, it just broke the GUI experience. I expect I hadn't tried launching with a command line argument throughout the whole ordeal. No idea if the controls configuration dialog is still broken, but don't care. Will just re-import my control settings (after backing this whole thing up, of course).

 

< Thanks all!

 

< EDIT: The BAM/FP that ended up working again was the one I've always used in the original directory that "broke". It's not from the AIO package, though may well be the same file versions. I had added more folders (e.g. Future Pinball 2, 3, etc.) with AIO, but they didn't turn out to be necessary. Frankly, I'm surprised the original files still worked after all of the rigmarole. Would seem to indicate that it is not as fragile as I thought. I never went back and ran the first FPLoader again (after running others once as admin), so the registration didn't seem to matter. I'm sure there's all sorts of crap in the Registry at this point, referencing at least a few different folders. Whatever.

My guide is here:

 

https://pinballnirva...art-here.20851/

 

TerryRed has a different approach on his guide.

 

I've used it with success in the past, but I do prefer TerryRed's AIO package, as it has the pre-patched EXEs, CFGs (which were crucial to make the tables look right, at least in arcade mode), etc. Thanks!

 

PS. See my other reply, as I did get it sorted out. Seems I may have only broken the GUI experience with my previous flailings.

Edited by djm468, 07 June 2024 - 01:24 AM.