|
ACCESS VIOLATION at Mame start
#396883 - 08/21/23 05:12 PM
|
|
|
Hi,
I have a fresh install of the latest MAME (0257b), using Windows 10 with an AMD 5700G CPU and an additional NVidia NVS 310 (for extra displays).
It seems that the NVidia is causing problems with MAME. If I disable the NVidia in the device manager, MAME uses the Radeon GPU build into the CPU and everything works fine. But that cannot be a final solution.
Attempting load of mame.ini
Starting plugin data...
Attempting load of mame.ini
Attempting load of mame.ini
Attempting load of source\empty.ini
Attempting load of ___empty.ini
Video: Monitor 65537 = "\\.\DISPLAY1" (primary)
Video: Monitor 65539 = "\\.\DISPLAY2"
Video: Monitor 65541 = "\\.\DISPLAY6"
Direct3D: Using Direct3D 9
Physical width 1920, height 1080
Direct3D: Initialize
Direct3D: Configuring adapter #0 = NVIDIA NVS 310
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 1920x1080
Direct3D: Initialize HLSL
-----------------------------------------------------
Exception at EIP=00007ff8d0214bf4 (__cxa_throw_bad_array_new_length+0x6a2b3f64): ACCESS VIOLATION
While attempting to read memory at 0000000000000000
-----------------------------------------------------
RAX=0000000000000000 RBX=0000024d4cc86a90 RCX=0000024d4cc86a90 RDX=0000024d4f7ad000
RSI=0000000000000000 RDI=0000024d4cc9b800 RBP=000000ded61ff7d0 RSP=000000ded61ff6c8
R8=0000000000000078 R9=0000024d4ccdef00 R10=000000000001fa14 R11=0000000000000001
R12=0000024d584be75c R13=0000024d4fa2e760 R14=0000000000000008 R15=0000024d4fa10870
-----------------------------------------------------
Stack crawl:
000000ded61ff6c0: 00007ff8d0214bf4 (QueryOglResource+0x545c4)
000000ded61ffb10: 00007ff8d01ba794 (__cxa_throw_bad_array_new_length+0x6a259b04)
000000ded61ffb70: 00007ff98488eb53 (Direct3DShaderValidatorCreate9+0x6b023)
000000ded61ffba0: 00007ff98488e669 (Direct3DShaderValidatorCreate9+0x6ab39)
000000ded61ffbd0: 00007ff98e5f7614 (BaseThreadInitThunk+0x0014)
000000ded61ffc50: 00007ff9901c26b1 (RtlUserThreadStart+0x0021)
Edited by thrust26 (08/21/23 05:20 PM)
|
Have fun!
thrust26
|
|
|
Re: ACCESS VIOLATION at Mame start
[Re: thrust26]
#396884 - 08/21/23 05:39 PM
|
|
|
Hi. Looks like a possible HLSL issue with Nvidia. I use Nvidia but do not use HLSL and have no issues running any games.
Edit mame.ini and disable HLSL
See if that helps.
|
|
|
|
Re: ACCESS VIOLATION at Mame start
[Re: Jason]
#396885 - 08/21/23 05:50 PM
|
|
|
Maybe I am blind, but there is no mame.ini in the directory. I remember there used to be one on my old PC.
BTW: I tried -video opengl and that works.
|
Have fun!
thrust26
|
|
|
Re: ACCESS VIOLATION at Mame start
[Re: thrust26]
#396886 - 08/21/23 05:55 PM
|
|
|
I created a mini mame.ini which only contains:
hlsl_enable 0
Same result.
|
Have fun!
thrust26
|
|
|
Re: ACCESS VIOLATION at Mame start
[Re: thrust26]
#396887 - 08/21/23 09:55 PM
|
|
|
If you are using command-line MAME, go to your MAME directory and:
delete the current mame.ini file del mame.ini
create a new mame.ini mame -cc
try again. Hopefully something good
|
|
|
|
Re: ACCESS VIOLATION at Mame start
[Re: Jason]
#396888 - 08/21/23 10:07 PM
|
|
|
Thanks, but unfortunately it doesn't help, even with hlsl_enable 0. Anyway, I think I will use -opengl as workaround.
|
Have fun!
thrust26
|
|
| John IV |
|
IV/Play, MAME, MAMEUI
|
|
|
|
|
Reged: 09/22/03
|
|
Posts: 1969
|
|
Loc: Washington, USA
|
|
|
|
Send PM
|
|
|
Re: ACCESS VIOLATION at Mame start
[Re: thrust26]
#396889 - 08/22/23 12:20 AM
|
|
|
|
|
|
Re: ACCESS VIOLATION at Mame start
[Re: John IV]
#396891 - 08/22/23 06:48 AM
|
|
|
Yes, but that made no difference.
|
Have fun!
thrust26
|
|
|
Re: ACCESS VIOLATION at Mame start
[Re: thrust26]
#396892 - 08/22/23 01:22 PM
|
|
|
> Yes, but that made no difference.
This has to do with Nvidia. Nvidia and MAME, has never been friends. To make it work, you need to use the last Nvidia drivers, that supported Direct X 9.0. From what I remember the version number is at least below 300.xx, so something like 295.xx should work.
For whatever stupid reason, Nvidia ditched the Direct X 9.0 support pretty early, unlike other vendors. ATI supports it till today. MAME devs blame Windows Direct X for no reason. Must be the 2500$ Nvidia cards they can’t use with MAME and Windows properly.
But a promising new renderer rewriting is on the way. Just Desserts has taken this challenge, so that MAME users can use Direct X 12 in the future. I wish him everything good for this and I hope it will include the vector renderer and fx as well (from version 0.179), which was the last version that supported rendering of vector points in a object. Since vector rendering never maked it into bgfx, I have hope, that it will be included into the Direct X 12 support. If a person can make this a reality, then it is Just Desserts.
|
|
|
|
Re: ACCESS VIOLATION at Mame start
[Re: uman]
#396893 - 08/22/23 04:31 PM
|
|
|
That tip did it! Thanks a lot!
The latest version I was able to download is 377.83. Now MAME works like charm. 
|
Have fun!
thrust26
|
|
|
Re: ACCESS VIOLATION at Mame start
[Re: thrust26]
#396897 - 08/23/23 01:15 AM
|
|
|
I run the latest drivers NVIDIA offers for my GTX 1660 Super (537.13) and don't have any issues running even DirectX8 software on my system.
|
|
|
|
Re: ACCESS VIOLATION at Mame start
[Re: jonwil]
#396912 - 08/24/23 02:34 PM
|
|
|
Yeah, I was just about to post about that. I have an Nvidea GPU (GeForce GTX 1650) with the latest drivers, and do not seem to experience this issue with mame (0.248, or earlier versions). For example, "mame -video d3d pacman" works as expected. I wonder what I am doing different here that I do not run into this ?
-- EDIT --
For what it's worth: 'dxdiag' explicitly claims support for Direct X 9.
Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Edited by mhoes (08/24/23 04:24 PM)
|
|
|
| R. Belmont |
|
Cuckoo for IGAvania
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 9716
|
|
Loc: ECV-197 The Orville
|
|
|
|
Send PM
|
|
|
Re: ACCESS VIOLATION at Mame start
[Re: uman]
#397068 - 09/12/23 04:57 PM
|
|
|
> For whatever stupid reason, Nvidia ditched the Direct X 9.0 support pretty early,
> unlike other vendors.
False. DX7/8/9 games still run fine on the latest Nvidia drivers. -video d3d9 is considered unsupported by MAMEdev at this point, you should generally run -video bgfx as it's both more capable and more compatible.
|
|
|
|
Re: ACCESS VIOLATION at Mame start
[Re: R. Belmont]
#397069 - 09/12/23 06:20 PM
|
|
|
> > For whatever stupid reason, Nvidia ditched the Direct X 9.0 support pretty early,
> > unlike other vendors.
>
> False. DX7/8/9 games still run fine on the latest Nvidia drivers. -video d3d9 is
> considered unsupported by MAMEdev at this point, you should generally run -video bgfx
> as it's both more capable and more compatible.
bgfx still seems to have an extra couple of frames of latency though.
I stream with bgfx, because of the shaders, but I can tell it's not as responsive as when playing d3d mode in my own time.
I've been tempted to just switch back to d3d mode for my streams and ditch bgfx + the shaders for that reason alone.
Honestly I'd recommend against using bgfx unless you're really, really addicted to those shaders.
|
|
|
Index 
Threaded 
ACCESS VIOLATION at Mame start
Reply
[Re: 
