DarkVoid666 Posted September 10, 2025 Posted September 10, 2025 (edited) Hi there, i suddenly have a problem that vpx is crashing. It was working yesterday and now it suddenly crashes for an unknown reason. I am on Win11 with latest update as of today. Maybe the latest Win 11 is causing the problem, but i'm not sure. I have uninstalled the latest update, but that didn't fix it. All the tables that are not using PinMame are still working. I am on vpx v10.8.0 Final and latest VPinMAME-3.7.0-46-2b48173-win-x64. The crash stack is mentioning VPinMAME64.dll as the source of the error. But i don't know what could suddenly causes the problem since i haven't change anything, except adding some pup tables today and adding new lines to the VPMAlias.txt I have all Visual-C-Runtimes-All-in-One-Jul-2025 installed and i am on the latest Nvidia Drivers. Everything was working fine yesterday, Here is the crash.txt Crash report VPX - v10.8.0 Final (Rev. 2051 (28dd6c3), windows DirectX 64bits) ============ Process: VPinballX64.exe Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0033:000000004B0C01A1 Attempt to write to 0x4DBB9000 Thread ID: 0x1C38 [7224] Call stack ========== 000000004B0C01A1 VPinMAME64.dll (0x00015D9D 0x00015DA0 0x00015DA0 0x00015d9c) Environment =========== Date/time: 10/9/2025, 15:10:12:861 Number of CPUs: 32 Processor type: 8664 System: Windows 10 (10.0 26100) Memory status ============= Total Reserved: 655724K (640M) bytes Total Commited: 1893036K (1848M) bytes Total Free: 1645480K (1606M) bytes Largest Free: 3732928K (3645M) bytes Registers ========= RAX=00000000 RBX=676D2F65 RCX=00000E60 RDX=DA094E3A RSI=00000E60 RDI=A30E2986 RBP=F502F2DE RSP=0A3DFBD0 RIP=4B0C01A1 FLG=00010202 CS=0033 DS=002B SS=002B ES=002B FS=0053 GS=002B Failed to save minidump. Strangely it says Windows 10 in the text also i'm on Win 11. Any suggestions of what could cause the problem would be highly appreciated. Edited September 10, 2025 by DarkVoid666
Cliffy Posted September 10, 2025 Posted September 10, 2025 yeah I had crashes with newest vpinmame dll's too. I'm sticking with 3.7.0.47 from June 20th.
DarkVoid666 Posted September 10, 2025 Author Posted September 10, 2025 Yeah thanx, going back to a previous version of pinmame fixed it. Never thought of that, lol. Thanx a lot man, you saved me. 🙂
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now