[Solved] Random crashes, faulty d3dx9_43.dll-file [NTSC-U]
#1
Hello, 

Ever since I upgraded to Windows 10, and changed program settings most likely, my PCSX2 has begun crashing at random ("X has stopped working" kind of thing). 
I've only tested it with Tenkaichi 3 so far though. 

I'm running version 1.3.1 with a DirectX 11 renderer, yet the error I get in Event Viewer related to DirectX 9: 


Quote:Faulting application name: pcsx2.exe, version: 0.0.0.0, time stamp: 0x54ca3031
Faulting module name: d3dx9_43.dll_unloaded, version: 9.29.952.3111, time stamp: 0x4bf7318d
Exception code: 0xc0000005
Fault offset: 0x001aa5e0
Faulting process id: 0x1a20
Faulting application start time: 0x01d0dce752b74c62
Faulting application path: G:\Games\Pcsx2\pcsx2.exe
Faulting module path: d3dx9_43.dll
Report Id: e0e65e4a-6d17-4d41-a8ff-06694b82cf1c
Faulting package full name: 
Faulting package-relative application ID: 

Help please  :3
Reply

Sponsored links

#2
Are you sure you are using DX11 as a renderer.
If I start pcsx2 with DX11 already selected and run the bios,pcsx2 is not using that file at all
Try reinstalling DirectX and restart the pc
Try OpenGL if you still have problems after that.

BTW what are your pc specs and pcsx2\gsdx settings
Reply
#3
These are my SSE41 settings, gotten off some YouTube-video.

I have a i5-4690K [email protected], 8 GB RAM and a GTX 970.

I'll try reinstalling DirectX. Appreciate the quick response.
Reply
#4
This is more likely a support issue rather than a Bug report, move to General Discussion and Support forums.
We're supposed to be working as a team, if we aren't helping and suggesting things to each other, we aren't working as a team.
- Refraction
Reply
#5
(08-22-2015, 05:09 PM)silkrobot Wrote: changed program settings most likely

What does this include? What habe you changed?
Reply
#6
^I'm afraid I have no idea. Just followed another setup than last time.

Tried installing DirectX and restarting to no avail.
Switched to OpenGL (Hardware) and found some texture were missing before the program froze altogether (first time for that).
Reply
#7
Does this happen if you try another game OR the bios(select No Disk from CDVD)
Reply
#8
I tried another game and it eventually happened. The log was different though, despite having reverted to my original setting of Direct3D11 (Hardware).

Quote:Faulting application name: pcsx2.exe, version: 0.0.0.0, time stamp: 0x54ca3031
Faulting module name: d3d10warp.dll_unloaded, version: 10.0.10240.16384, time stamp: 0x559f3bd2
Exception code: 0xc0000005
Fault offset: 0x0014a5e0
Faulting process id: 0x15a8
Faulting application start time: 0x01d0dcff3e932224
Faulting application path: G:\Games\Pcsx2\pcsx2.exe
Faulting module path: d3d10warp.dll
Report Id: e550d9fa-84cd-4b66-b969-4fd45e5e67ce
Faulting package full name:
Faulting package-relative application ID:
Reply
#9
(08-22-2015, 06:50 PM)silkrobot Wrote: ^I'm afraid I have no idea. Just followed another setup than last time.

But are you talking about windows settings or pcsx2 settings?
I would just try reinstalling pcsx2 1.2.1 (full installer)
Reply
#10
(08-23-2015, 01:28 PM)willkuer Wrote: But are you talking about windows settings or pcsx2 settings?
I would just try reinstalling pcsx2 1.2.1 (full installer)

Just pcsx2 settings.

I removed my version and installed 1.2.1, using these settings but it happened again, sadly. 

Quote:Faulting application name: pcsx2-r5875.exe, version: 0.0.0.0, time stamp: 0x52ef990f
Faulting module name: d3dx9_43.dll_unloaded, version: 9.29.952.3111, time stamp: 0x4bf7318d
Exception code: 0xc0000005
Fault offset: 0x001aa5e0
Faulting process id: 0x123c
Faulting application start time: 0x01d0dd9d7269d482
Faulting application path: G:\Games\Pcsx2\pcsx2-r5875.exe
Faulting module path: d3dx9_43.dll
Report Id: 299cc045-36f7-46ce-9d7e-34367ac55854
Faulting package full name: 
Faulting package-relative application ID: 

 Also, I'm experiencing the same graphics glitch I had when using OpenGL instead of Direct3D11, where my health bars are replace by some small dots. I've heard this is a Dx9 issue but it shouldn't happen on my Dx11 setup. Are my gsd settings faulty?
Reply




Users browsing this thread: 1 Guest(s)