VPX Crashing

[OzStick]

Hi All,

 

I made a VPX setup for someone which is basically a clone of my own drive then put into his PC. I tested his drive in my cab and had no issues whatsoever, but he is now getting really weird results with the drive in HIS cab.

 

It is running PinballY and we are finding that many (but not all) tables when launched via PBY results in the table not loading and the process returning focus back to PBY as if nothing happened. Starting up the VPX Editor and then loading a table would sometimes work and subsequently, if the table loaded it would then run properly every time. A reboot would sometimes then allow a table to run, however not if it is launched via PBY.

 

Here is the contents from the CRASH.TXT file that is generated after each failed attempt. The contents of the file seem to be exactly the same every time:

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

Crash report VPX rev359 (51ad4d6)

============

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:005F1A37

Attempt to read from 0x7463656A

Thread ID: 0x1430 [5168]

 

Call stack

==========

005F1A37 VPinballX.exe (0x0019E584 0x00548026 0x0884B808 0x0019e31c)

00548026 VPinballX.exe (0x0349A140 0x0019E31C 0x0019E584 0x00000000)

0055BF51 VPinballX.exe (0x0884B808 0x00000410 0x00000000 0x0349a248)

0055EE49 VPinballX.exe (0x00010000 0x0346D790 0x0055E24B 0x0345d408)

0055E24B VPinballX.exe (0x0000004A 0x0019F354 0x0000138B 0x00000000)

005D9CA9 VPinballX.exe (0x00000000 0x00000000 0x005D86F4 0x03467778)

005D86F4 VPinballX.exe (0x0000138B 0x00000000 0x00000111 0x0019f354)

005DCB70 VPinballX.exe (0x00000111 0x0000138B 0x00000000 0x00000111)

005E451D VPinballX.exe (0x004286E0 0x00040444 0x00000111 0x0000138b)

758952AC user32.dll CallWindowProcW + 0xB2C (0x004286E0 0x00000000 0x00000111 0x0000138b)

758943FE user32.dll DispatchMessageW + 0x22E (0x758A9CF0 0x005DB866 0x0019F224 0x00000000)

758AEBB0 user32.dll DispatchMessageA + 0x10 (0x0019F224 0x00000000 0x00400000 0x0019f240)

005DB866 VPinballX.exe (0x00000000 0x00000001 0x0039B000 0x0076dc20)

005C7B75 VPinballX.exe (0x00400000 0x00000000 0x033F27AA 0x00000001)

005F5506 VPinballX.exe (0x0039B000 0x75C36340 0x0019FFDC 0x77aa87a4)

75C36359 KERNEL32.DLL BaseThreadInitThunk + 0x19 (0x0039B000 0xFFFFFFFF82F3C59A 0x00000000 0x00000000)

77AA87A4 ntdll.dll RtlGetAppContainerNamedObjectPath + 0xE4 (0xFFFFFFFFFFFFFFFF 0x77ACA14E 0x00000000 0x00000000)

77AA8774 ntdll.dll RtlGetAppContainerNamedObjectPath + 0xB4 (0x0311E650 0x0039B000 0x00000000 0x78746341)

 

Environment

===========

Date/time: 10/10/2022, 21:13:33:104

Number of CPUs: 4

Processor type: 586

System: Windows 10 (10.0 18363)

 

Memory status

=============

Total Reserved: 67312K (65M) bytes

Total Commited: 214668K (209M) bytes

Total Free: 3912260K (3820M) bytes

Largest Free: 2095472K (2046M) bytes

 

Registers

=========

EAX=7463656A EBX=0019DF88 ECX=07F62F28 EDX=0019DE44

ESI=00000001 EDI=034BA720 EBP=0019FFEC ESP=0019FFE4 EIP=77AA8774

FLG=00010202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

 

 

Mini dump saved successfully.

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

 

I've done some searching re this issue and it seems to happen to quite a few people, but is typically resolved by upgrading or reinstalling various apps. So far we have reinstalled:

- video drivers

- ALL VC Redistributables

- VPinMAME

 

In addition I found a thread here on VPF that suggested enabling Alternative Depth Buffer Processing in the Video/Graphics Options of VPX, only to find that was already checked. This is REALLY weird as I've NEVER used that setting and my friend swears he didn't touch any setting, so I have no idea how it got switched on!!!

 

Any suggestions on what else we should try would be great.

[Thalamus]

When you take the drive over, has VPX at any time run the installer on that machine ? If not, then get the all-in-one - install it and then you can replace what is inside the vp install from your hard drive. As usual, make sure that no anti-virus is running, even defender. Turn the real-time off, and try again. I don't expect it to be that, but it is always a good thing to have tested. Run VP first at windowed mode, and manually. Front end is only to be run when you have something stable. By your post, I believe you've understood this much, but, just want to make sure

 

Also, IF you have installed VP there at one time, make sure that you keep the same path. IF, that has changed, and it should not be installed in any Windows standard folders like Program Files ... then go to install/uninstall programs. Uninstall it, install it again with the all-in-one and do the above.

 

What I'm pointing at is that there might be missing registered dll's and/or wrong registry paths. All should be fixed by doing what I just now told you.

 

I highly suggest that you install (unzip) with the latest 10.7.2RC, and update to the latest pinmame. IF pinmame was already installed before. Use setup.exe, choose "Uninstall", but, DON'T SAY YES TO CLEAR THE REGISTRY, all custom pinmame settings will be lost if you say yes. Then, now press the Install button. This is kind of important, newer version of setup.exe actually does some "important" registry cleaning on the "uninstall", that it didn't do in older versions, I'm told.