Access Violation

[retrorepair]

Randomly getting an access violation with 149 014b and gauntlet.

It usually runs ok for about 10 mins then randomly crashes and throw up the error.

Code: [Select]

-----------------------------------------------------
Exception at EIP=01CD82F0 (not found): ACCESS VIOLATION
While attempting to read memory at 13D01000
-----------------------------------------------------
EAX=13D01000 EBX=00000150 ECX=0001E784 EDX=13E84F18
ESI=00000000 EDI=00000000 EBP=00000002 ESP=00222940
-----------------------------------------------------
Stack crawl:
  00000002: 01CD82F0 (not found)

This is in XP32 shelled to an autohotkey script which runs "groovymame gauntlet" directly. The PC is an old P4 with DDR RAM, though I tested the RAM and it's ok. It looks to me like a RAM issue but I've no idea what most of it means 

Any ideas?

[retrorepair]

For the record I just tried 147 and does the same thing, here's the error from this attempt:

Code: [Select]

SwitchRes: [gauntlet] (1) horizontal (336x240@59.92)->(672x240@59.92)

-----------------------------------------------------
Exception at EIP=01C8ACC0 (not found): ACCESS VIOLATION
While attempting to read memory at 15691000
-----------------------------------------------------
EAX=15691000 EBX=00000170 ECX=0000F590 EDX=158A87C0
ESI=00000000 EDI=00000000 EBP=00000002 ESP=00222920
-----------------------------------------------------
Stack crawl:
  00000002: 01C8ACC0 (not found)

[Ansa89]

Have you tried with official mame build?

[JDFan]

Randomly getting an access violation with 149 014b and gauntlet.

This is in XP32 shelled to an autohotkey script which runs "groovymame gauntlet" directly. The PC is an old P4 with DDR RAM, though I tested the RAM and it's ok. It looks to me like a RAM issue but I've no idea what most of it means 

Any ideas?

That type of error usually means that the program tried to read\write to a memory location that it was not assigned to be using by the system (which can corrupt the system - so the OS shuts down the program and puts up the error notification.) - could be that the game is using more than the 2GB. that windows programs are assigned ( Does GroovyMame's exe support the >2GB address space allocation ) If it does try using process explorer or similar to set it to App can handle >2GB address space so windows will allow it more memory if that setting is not already active ) - If GroovyMame does not support the setting try using MameUI64 ( I use it and it does support the setting) and see if you still get the error.

[retrorepair]

I started to think it was a hardware problem tbh. I just tried vanilla MAME and got a blue screen. Checked event viewer and found ati2mtag which I assume is my BSOD.

Then I came across this:

http://www.techsupportforum.com/forums/f10/cplib-initialization-failed-to-load-the-library-391509.html

Seems to be the same issue I'm having and updating his gfx driver sorted it. Now I can't do that since I'm using Calamity's 6.3 driver for my 9250. I'm going to go into the bios to see if I can disable any onboard video card stuff.

[retrorepair]

Well nothing really in the bios to change so not sure how to proceed. Obviously this doesnt happen with everyone so it's something to do with my setup.

[Calamity]

Well, ati2mtag.sys is the video driver miniport, which is patched in CRT Emudriver to enable the extra amount of video modes. First, check how many modes are active in your system, theoretically CRT Emudriver 6.5/32-bits is stable with up to 200 modes, but the fact it doesn't crash on my system doesn't mean it can't crash on yours, after all this is a hack and some memory is being overwritten. So try lowering the amount of modes first, to something reasonable. By the way, does it only happen with Gauntlet?

As a side note, one friend of mine started to have similar issues in his cabinet with an ATI 9250 AGP, it started as random crashes upon video mode switching, then it got more frequent and finally it wouldn't enter Windows at all. It turned out the AGP port was broken, probably due to the video card being loose inside his build, damaging the port eventually. I wish it's not the same thing.

[retrorepair]

I only have Gauntlet installed and only 120 modes. Not to say that isn't causing an issue also though I recon it's unlikely.

I'll probably just ditch the ancient P4 and grab a C2D, it'll at least modern enough to be able to stick a PCI-X card in there and just use the 9.3 driver.