Access Violation – FP

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #228568
    topper-2k
    Participant
      @topper-2k

      I’ve run into a few FP tables lately that are crashing immediately after the loading screen. Looking at the BAM error log, they all have a “access violation,” 3 Angels is the latest to do this.

      I’ve made sure I’m running the most recent FP/BAM. I even resorted to a full uninstall/reinstall. I’ve checked that the tables aren’t “read only” or otherwise locked. I’ve tried running FPLoader in compatibility mode. I’ve tried disabling real-time-protection in Windows Defender. Nothing seems to work.

      I’m running other FP tables (Ghostbusters, RetroFlair, Star Wars DSA, Blade Runner) without issue. I’ve tried downloading 3 Angles (and the other tables with this issue) to my regular desktop PC and they play fine there. So I don’t think it’s the table files.

      The full text of the error log is below. Any idea what’s causing this?

       

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

      BAM path: C:\Games\Future Pinball\BAM

      XML:

      table: C:\Games\Future Pinball\Tables\3ANGELS.fpt

      1: TAG: FILE=dllmain.cpp, LINE=710, FUNC=Routed_SwapBuffers

      2: TAG: FILE=dllmain.cpp, LINE=727, FUNC=Routed_SwapBuffers

      SBC: -1

      NFC: 13

      Loaded modules:

      Future Pinball.exe, 1.9.2008.1225 : 00400000 – 01F3F000

      ntdll.dll, 6.2.19041.804 : 77AD0000 – 77C73000

      KERNEL32.DLL, 6.2.19041.804 : 779D0000 – 77AC0000

      KERNELBASE.dll, 6.2.19041.804 : 777A0000 – 779B4000

      apphelp.dll, 6.2.19041.572 : 68CA0000 – 68D3F000

      USER32.dll, 6.2.19041.746 : 76B40000 – 76CD6000

      win32u.dll, 6.2.19041.804 : 765F0000 – 76608000

      COMCTL32.dll, 6.10.19041.746 : 75710000 – 75922000

      GDI32.dll, 6.2.19041.746 : 75F90000 – 75FB3000

      msvcrt.dll, 7.0.19041.546 : 75990000 – 75A4F000

      gdi32full.dll, 6.2.19041.746 : 76410000 – 764EC000

      msvcp_win.dll, 6.2.19041.789 : 76610000 – 7668B000

      ucrtbase.dll, 6.2.19041.789 : 75E70000 – 75F90000

      libcurl.dll, 7.13.1.0 : 10000000 – 1009D000

      ADVAPI32.dll, 6.2.19041.610 : 76350000 – 763CA000

      COMDLG32.dll, 6.2.19041.789 : 76130000 – 761DF000

      sechost.dll, 6.2.19041.789 : 766C0000 – 76736000

      combase.dll, 6.2.19041.789 : 76750000 – 769D2000

      RPCRT4.dll, 6.2.19041.746 : 761E0000 – 762A0000

      WSOCK32.dll, 6.2.19041.1 : 74390000 – 74398000

      shcore.dll, 6.2.19041.746 : 76AB0000 – 76B37000

      WS2_32.dll, 6.2.19041.546 : 769F0000 – 76A53000

      WINMM.dll, 6.2.19041.546 : 6D7C0000 – 6D7E8000

      SHLWAPI.dll, 6.2.19041.746 : 76A60000 – 76AA5000

      SHELL32.dll, 6.2.19041.789 : 771E0000 – 77794000

      ole32.dll, 6.2.19041.746 : 75D40000 – 75E23000

      OLEAUT32.dll, 6.2.19041.804 : 75A50000 – 75AE6000

      DINPUT8.dll, 6.2.19041.1 : 6BFA0000 – 6BFD7000

      GLU32.dll, 6.2.19041.546 : 6BFE0000 – 6C01F000

      Newton.dll,  : 02690000 – 02701000

      fmod.dll, 3.7.4.0 : 02710000 – 027A6000

      DevIL.dll, 0.1.6.5 : 027B0000 – 02923000

      ILU.dll, 0.1.6.5 : 02360000 – 02373000

      ILUT.dll, 0.1.6.5 : 02380000 – 0238D000

      OPENGL32.dll,  : 02930000 – 02C1B000

      MSACM32.dll, 6.2.19041.1 : 68A40000 – 68A59000

      imagehlp.dll, 6.2.19041.546 : 75E30000 – 75E49000

      WININET.dll, 11.0.19041.746 : 73C60000 – 740B8000

      winmmbase.dll, 6.2.19041.1 : 68DC0000 – 68DDD000

      IMM32.DLL, 6.2.19041.546 : 76690000 – 766B5000

      BAM.dll, 1.5.327.0 : 66BF0000 – 67272000

      PSAPI.DLL, 6.2.19041.546 : 76740000 – 76746000

      SETUPAPI.dll, 6.2.19041.546 : 76D40000 – 77174000

      cfgmgr32.dll, 6.2.19041.546 : 763D0000 – 7640B000

      VERSION.dll, 6.2.19041.546 : 75940000 – 75948000

      bcrypt.dll, 6.2.19041.546 : 75E50000 – 75E69000

      HID.DLL, 6.2.19041.546 : 743E0000 – 743EA000

      renderingengine.dll,  : 666C0000 – 66BE8000

      ————————————————–

      Error code C0000005: ACCESS VIOLATION

       

      Address: 00000001 -> UNKNOWN:00000001

      Flags: 00000000

       

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

      with 0B 08 01 F0 02 B4 5E 97 68 28 3A 02

       

      Address: 68DE13A2 -> UNKNOWN:68DE13A2

      ***  0 called from $ADDRESS:68DE13A2

      with

       

      Address: 00439B46 -> Future Pinball.exe:00039B46

      ***  1 called from $ADDRESS:00439B46

      #228681
      topper-2k
      Participant
        @topper-2k

        Well, I’m hesitant to call this “solved” but the problem seems to have gone away.

        On my normal desktop PC, I downloaded three tables I was having this problem with to verify that the tables weren’t the issue. At least one of them wouldn’t load. My home PC isn’t super powerful, so I set the FP video settings to the defaults for “low performance.” Then I was able to run all three tables. I went to my cabinet, did the same, and was able to run all three tables there as well.

        So issue solved? Not quite. I bumped my FP video settings on my cabinet back up to where they were before and am still able to run the tables. So I have no idea what actually fixed the issue. I remain stumped. I don’t like magic fixes, because if I don’t know what was wrong, I won’t know how to fix it the next time something similar happens. But I am glad I’m able to play the tables.

      Viewing 2 posts - 1 through 2 (of 2 total)

      Forums are currently locked.

      ©2025 VPinBall.com

      Log in with your credentials

      Forgot your details?