7 replies to this topic

[CobraGuy]

While playing jpsalas' Attack From Mars table, VPX has crashed on me half a dozen times when a specific set of circumstances are met. (I have tried testing GRONI's table as a comparison, but I am finding it much more difficult to get multiball on the second ball per the circumstances below):

1. Destroy at least one ship.
2. Achieve multiball on the second ball (maybe on first as well, but so far I have always done it on second)
3. Activate (or achieve?) "extra ball" and(?)/or(?) "start martian attack" through video mode.

After firing ball three (after draining any existing extra balls from ball two), before the ball makes it around the top-right corner and goes out of sight, both video and audio freeze and VPX crashes.

 

 

 

Here is one report:

 

Crash report
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:01771BE4
Attempt to read from 0x01771BE4
Thread ID: 0x23E4 [9188]

Call stack
==========
01771BE4  (0x1429A8A0 0x3DCCCCCD 0x0018F81C 0x1429a8a0)
0044ADA8 VPinballX.exe (0x1429A8A0 0x1429AA00 0x00000005 0x0000000a)
004B153A VPinballX.exe (0x3DCCCCCD 0x0000000A 0x3DCCCCCD 0x3f90da80)
004B0ED7 VPinballX.exe (0x01685C60 0x0DA8DCC0 0x00000000 0x00000000)
004B1FE2 VPinballX.exe (0x004B6939 0x01685C60 0x00000000 0x75a250fd)

 

Environment
===========
Date/time: 7/11/2016, 20:08:10:341
Number of CPUs: 8
Processor type: 586
System: Unknown Windows version - 6.1 (Service Pack 1)

Memory status
=============
Total Reserved: 93376K (91M) bytes
Total Commited: 396520K (387M) bytes
Total Free: 3704344K (3617M) bytes
Largest Free: 2096656K (2047M) bytes

Registers
=========
EAX=01771BE4 EBX=1429A8A0 ECX=1429B160 EDX=1429B160
ESI=1429AA00 EDI=1429B160 EBP=00000000 ESP=0018FB5C EIP=004B6A7C
FLG=00210202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

 

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

 

And another:

 

Crash report
============
Process: VPinballX.exe
Reason: 0xC0000005 - EXCEPTION_ACCESS_VIOLATION at 0023:0044AD7C
Attempt to read from 0x2BCE18EC
Thread ID: 0x684 [1668]

Call stack
==========
0044AD7C VPinballX.exe (0x1419B0D0 0x1419B230 0x00000005 0x0000000a)
004B153A VPinballX.exe (0x3DCCCCCD 0x0000000A 0x3DCCCCCD 0x3f87338e)
004B0ED7 VPinballX.exe (0x01645C60 0x0DA2DCC0 0x00000000 0x00000000)
004B1FE2 VPinballX.exe (0x004B6939 0x01645C60 0x00000000 0x75a250fd)

Environment
===========
Date/time: 8/11/2016, 01:03:25:31
Number of CPUs: 8
Processor type: 586
System: Unknown Windows version - 6.1 (Service Pack 1)

Memory status
=============
Total Reserved: 94016K (91M) bytes
Total Commited: 390020K (380M) bytes
Total Free: 3710204K (3623M) bytes
Largest Free: 2096656K (2047M) bytes

Registers
=========
EAX=2BCE18E8 EBX=1419B0D0 ECX=0018F81C EDX=01668AC0
ESI=1419B230 EDI=01668AC0 EBP=00000000 ESP=0018FB5C EIP=004B6A7C
FLG=00210202 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

Edited by CobraGuy, 09 November 2016 - 04:59 AM.

[MrKnister]

Hmmm .. never had any Problems with this Table .. is it only this Table which causes crashes ? Did you maybe already tried a different Rom ?

[fuzzel]

What version of VPX do you use?

[CobraGuy]

Hmmm .. never had any Problems with this Table .. is it only this Table which causes crashes ? Did you maybe already tried a different Rom ?

 

I have not tried another ROM other than the one told to me by the game.

 

 

What version of VPX do you use?

 

I am running 10.1.0 r2660.

 

 

I have been having difficulty replicating the exact circumstances of the crash to acquire more data, but it just crashed on me under completely different circumstances. Since no one else is reporting any issues, I suppose I just have to leave the issue as unique to myself and hope that the crash does not happen when I am getting close to a high score!

[flipperkastje]

I have the same problem with this wonderful table...  

Running VisualPinball 10.2.1 with Attack from Mars 1.2.0 and VpinMame 2.8. on windows 10 pro

It Crashes mostly with multiball and sometimes at another moment.

I have no problems with other tables.

 

I dont know where to find the Crash Report like Hobbyist did above, but I can provide this :

 

Crash Report

 

Log Name:      Application

Source:        Application Error

Date:          27/05/2017 11:28:58

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      DESKTOP-QRC1H26

Description:

Faulting application name: VPinballX.exe, version: 10.2.1.0, time stamp: 0x586445a5

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x05080746

Faulting process ID: 0x12f4

Faulting application start time: 0x01d2d6c96840af58

Faulting application path: C:\Visual Pinball\VPinballX.exe

Faulting module path: unknown

Report ID: 416e2ef4-7ccc-4f0b-8a98-c5e4f6808bb4

Faulting package full name: 

Faulting package-relative application ID: 

Event Xml:

<Event xmlns="http://schemas.micro...08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2017-05-27T09:28:58.055803200Z" />

    <EventRecordID>1684</EventRecordID>

    <Channel>Application</Channel>

    <Computer>DESKTOP-QRC1H26</Computer>

    <Security />

  </System>

  <EventData>

    <Data>VPinballX.exe</Data>

    <Data>10.2.1.0</Data>

    <Data>586445a5</Data>

    <Data>unknown</Data>

    <Data>0.0.0.0</Data>

    <Data>00000000</Data>

    <Data>c0000005</Data>

    <Data>05080746</Data>

    <Data>12f4</Data>

    <Data>01d2d6c96840af58</Data>

    <Data>C:\Visual Pinball\VPinballX.exe</Data>

    <Data>unknown</Data>

    <Data>416e2ef4-7ccc-4f0b-8a98-c5e4f6808bb4</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

[BigHein]

Same problem here

[Rajo Joey]

Just make a few games with the actual 10.3 beta and Vpinmame 2.9 and everything works as it should be.

I have also Win10 Pro 64bit.

[Thalamus]

If I remember correctly - JP did mention a fix in the support thread for this table. And, I've had crashed for Dozer' AFM, but, that is fixed in the upcoming 10.3.

Edited by Thalamus, 27 May 2017 - 08:27 PM.