19 replies to this topic

[licwip]

I tried to grab a more updated version of the Elvis table, only to find that both the older and newer versions no longer work for me.

 

The playfield and backglass will load, and the DMD appears to start loading, but I never see any text on it. After three seconds, the table just exits, without any error message given. I'm using the basic "elvis" ROM.

 

My crash document says this:

 

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:33A00002

Attempt to read from 0x33A00002

Thread ID: 0x28E4 [10468]

 

Any idea, anyone? Thank you!

[wiesshund]

what is the rest of the crash.txt dialog?

 

it might list something important

[licwip]

Crash report VPX rev3788

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

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:33A00002

Attempt to read from 0x33A00002

Thread ID: 0x28E4 [10468]

 

Call stack

==========

33A00002  (0x1D9264D0 0x00000000 0x00003415 0x33a00002)

22D39813 vpinmame.dll (0x00003415 0x00000000 0x00000001 0x231bcdb8)

22C6D3B9 vpinmame.dll (0x1D4F2318 0x22C7FB73 0x00000001 0x22c7fa62)

22C6B772 vpinmame.dll (0x00000001 0x22C7FA62 0x000004CF 0x2319d0a8)

22C7FB73 vpinmame.dll (0x000004CF 0x2319D0A8 0x2865FF70 0x00000001)

22C7FA62 vpinmame.dll (0x1CD9EAB0 0x00000000 0x76EE06C0 0x00000006)

22C7F79A vpinmame.dll (0x00000006 0x77BD53FE 0x00000000 0x2865fef8)

77BD53FE ntdll.dll RtlAllocateHeap + 0x3E (0x00000004 0x23199150 0x231990B0 0x230eedcc)

22DEF7FC vpinmame.dll DllUnregisterServer + 0xAF7C (0x00000000 0x1D355718 0x1D355718 0x230eedcc)

22DEF7FC vpinmame.dll DllUnregisterServer + 0xAF7C (0x2305A294 0x1D355718 0x2865FF70 0x00000000)

22DEF7FC vpinmame.dll DllUnregisterServer + 0xAF7C (0x00000000 0x1CD9EAB0 0x76EE06C0 0x22ddd9e7)

 

Environment

===========

Date/time: 30/12/2020, 18:50:17:213

Number of CPUs: 6

Processor type: 586

System: Windows 10 (10.0 19041)

 

Memory status

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

Total Reserved: 202280K (197M) bytes

Total Commited: 935124K (913M) bytes

Total Free: 3056836K (2985M) bytes

Largest Free: 2095296K (2046M) bytes

 

Registers

=========

EAX=33A00002 EBX=00000040 ECX=33A00002 EDX=00003415

ESI=00000000 EDI=00003415 EBP=00000000 ESP=2865FF24 EIP=22DE5F13

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

 

 

Failed to save minidump.

[wiesshund]

Ok not being Toxie, i reserve the right to be wrong but

 

It appears that pinmame is crashing so...

 

1) try renaming the elvis.nv file in vpinmame\nvram to elvis-old.nv

no good?

 

2) download a new copy of the elvis ROM (and clear the nvram file)

still no go?

 

Download Vpinmame

https://www.vpforums...&showfile=11571

unpack it into the vpinmame folder

over write existing files

run setup and click install to re-register the DLL's

[licwip]

Tried the first two with no joy. Before I try the third:

 

When I try to load the newer table (v3.0), it fails with no window error message. When I try to load the older table (v1.1.0), it gives me a VBScript window error message for a split second:

 

VPMflips error: Variable is Undefined.

 

My script for both tables has "elvis" as its cGameName. I did not change the VPMAlias file for this, but it's not as if a different table is using the same ROM.

[licwip]

Just did the third step as well, but no change. Neither table works. Same bounce-out as before.

 

I can't find any other table with the same issue.

[wiesshund]

VPMflips error: Variable is Undefined.

 

 

Seems your core.vbs is not running

because it is defined in core.vbs

 

Has your AV taken a hatred of vbs?

 

as far as the ROM

run pinmame's setup.exe

click test

pick elvis ROM and try to launch it

 

this will at least show if the rom runs or not

And strangely enough, i know someone else having issue with the elvis table, and core.vbs functions not loading

[licwip]

The Elvis (5.00) ROM runs just fine from the test.

 

I saw that other Elvis issue. In case it helps, my scripts currently don't call for core.vbs or for anything SAM-related, but for:

 

LoadVPM "01560000", "SEGA.VBS", 3.26

 

I tried the other LoadVPM command mentioned in that topic, but no joy.

[wiesshund]

Sega.VBS also calls core.vbs

 

it just loads some sega / stern-whitestar functions

 

wonder what is up with this elvis table?

[licwip]

Let me know if you need any more info that I can provide. I appreciate the help!

[wiesshund]

Maybe @toxie might see the crash text you posted here

 

I know it tells WHY it crashed, but i do not know you to read that from it, i can only see what crashed

 

and it does not feel like it is your over all setup or all tables would start taking a dump

[wiesshund]

Hey Wait a minute....

 

 

... Lucy! You have some Splainin to do

 

 

What ancient installation do you have there, that has revision 3788

Is that possibly 10.6.0 ? or 10.5?

OK 1st, i recommend this

VPinballX61_Minimal.zip

 

as that would update 10.6.0 to 10.1
If that is older than 10.6.0 then i suggest
VPX 10.6.0 installer 1st, then the update

 

then i suggest
VPINMAME 3.3

Cause if your VPX is out of date, possible your pinmame is as well

 

If you want the most up to date scripts, easiest way is to pull them out of the beta download
since all of its scripts are up to date
 VPX_7_beta_rev4368.zip

 

Im not suggesting you use the VpinballX.exe from the beta, it is a beta after all
the rest of the files are perfectly useable though

If you want to try it, rename the exe to VpinballX 10.7 beta.exe so it does not remove your normal one.
 

[licwip]

Ricky, I blame the Vitameatavegamin.

 

Already got VPinMAME at 3.3, but I'll go 10.6.1 with VPX now.

[wiesshund]

I am kinda surprised that you are only now beginning to run into issues

 

guess it depends on if you look at new tables a lot

and what newer functions the author is using in them

 

I look lots

i dont keep lots, but i look lots

Edited by wiesshund, 31 December 2020 - 03:43 AM.

[licwip]

Wish I had better news, but no. With fresh VPX and VPinMAME and the NV file names either "elvis" or "elvis-old" I still get:

 

 

Crash report VPX rev4188

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

Process: VPinballX.exe

Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:33FE0002

Attempt to read from 0x33FE0002

Thread ID: 0x3A30 [14896]

 

Call stack

==========

33FE0002  (0x00000000 0x0EAECBD0 0x000000C3 0x33fe0002)

1FFB7229 vpinmame.dll (0x2048A468 0x2048CCC0 0x1FDD03F4 0x0000038b)

1FDD03F4 vpinmame.dll (0x0000038B 0x00000020 0x0EBF99B0 0x2884fdf8)

1FDD03F4 vpinmame.dll (0x0EBF99B0 0x1FDE3FB0 0x00000001 0x2048f970)

1FDCFCB2 vpinmame.dll (0x000004E5 0x2041DA68 0x2884FF70 0x00000001)

1FDE3E92 vpinmame.dll (0x067A7408 0x00000000 0x76EE06C0 0x00000006)

1FDE3BBE vpinmame.dll (0x00000006 0x77BD53FE 0x0EE8B508 0x762ec1b0)

77BD53FE ntdll.dll RtlAllocateHeap + 0x3E (0x00000004 0x20419AC8 0x20419A28 0x2036e33c)

2007BDBC vpinmame.dll DllUnregisterServer + 0xB34C (0x00000000 0x0ECC2ED8 0x0ECC2ED8 0x2036e33c)

2007BDBC vpinmame.dll DllUnregisterServer + 0xB34C (0x202D7D2C 0x0ECC2ED8 0x2884FF70 0x00000000)

2007BDBC vpinmame.dll DllUnregisterServer + 0xB34C (0x00000000 0x067A7408 0x76EE06C0 0x20069dd2)

 

Environment

===========

Date/time: 30/12/2020, 21:40:19:549

Number of CPUs: 6

Processor type: 586

System: Windows 10 (10.0 19041)

 

Memory status

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

Total Reserved: 209832K (204M) bytes

Total Commited: 889248K (868M) bytes

Total Free: 3095160K (3022M) bytes

Largest Free: 2095296K (2046M) bytes

 

Registers

=========

EAX=33FE0002 EBX=2884FDC4 ECX=33FE0002 EDX=000000C3

ESI=0EAECBD0 EDI=0000038B EBP=00000000 ESP=2884FF38 EIP=20071DC3

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

 

 

Failed to save minidump.

You think running a new table can corrupt old tables?

[Thalamus]

Try this : https://vpinball.com...-onoff-at91jit/

[wiesshund]

Thalamus, could this be a directdraw = 1 issue

guess if he is checking jit he could also may sure ddraw is 0

 

i only ever had 1 rom turn up with ddraw on, and still dont know if i did it by mistake or it just

wound up that way as a  default

Wish I had better news, but no. With fresh VPX and VPinMAME and the NV file names either "elvis" or "elvis-old" I still get:

 

 

Crash report VPX rev4188

 

You think running a new table can corrupt old tables?

Well that is better news
VPX is now a good version

 

And no, running a new table file can not harm an old table file

I suppose in some cases it might muss up the nvram, but that is  as simple as deleting the nvram
and usually does not result in a vpm crash anyways

[Thalamus]

The ddraw has to do with forced fullscreen. at91jit is sometimes needed, especially for Win7, Stern and dmddevice combo. Win10 has it too, but, not as often I'm told. Also, a way around it for me at least. Load vpx manually, and from there use file -> open. Much less crashes, but, can still happen, turning at91jit off, is normally not a big issue if not the computer itself is rather old. Meaning, fast machines can easier overcome the negative effect of turning that off it seems.

 

A frontend is actually loading the tables, somewhat that way too. So, troublesome at91jit might get solved running a FE.

Edited by Thalamus, 31 December 2020 - 04:10 AM.

[licwip]

Success! ddraw was at 0, but at91jit was at 1. Now at 0, it works! If at91jit changed at some point, I don't know why it changed. If it didn't change, I don't know why it became a problem.

 

Thanks a bunch, wiesshund and Thalamus!

[Thalamus]

at91jit doesn't normally change - except, if you delete the registry hive and you have at91jit set to 1 as default, or, maybe this is a modified game, using a different rom, still getting the default ?! Well, anyway - happy to hear that it is now working.