Error 0x000007b
#1
I have been using older builds of PCSX2 r5672 and below.
I decided to try the newer version 1.2.1 and when I try to start the .exe I get this message,"The application was unable to start correctly(0x000007b)".

The older builds of PCSX2 run fine it's just this newer one that gives me this message.

I already searched around and found no solution.
I have updated all of visual studio packs and everything else I could think of.

Need help solving this issue.
Reply

Sponsored links

#2
Try deleting PCSX2/langs/ar_SA (only if your system is set to Arabic)
[Image: XTe1j6J.png]
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Reply
#3
(08-19-2014, 01:35 AM)Blyss Sarania Wrote: Try deleting PCSX2/langs/ar_SA (only if your system is set to Arabic)

That does not help.
And my system was not set to Arabic.
Reply
#4
Dis you install vc++ 2013 x86 redist ?
CPU : AMD Ryzen 7 3800X
Mobo : Asus PRIME B450-PLUS
GPU : NVIDIA GeForce RTX 3070
RAM : 16 Go
Reply
#5
(08-19-2014, 07:10 AM)jesalvein Wrote: Dis you install vc++ 2013 x86 redist ?

Yup Installed it.
Reply
#6
Wierd.
What if you delete lang\Ar ?
CPU : AMD Ryzen 7 3800X
Mobo : Asus PRIME B450-PLUS
GPU : NVIDIA GeForce RTX 3070
RAM : 16 Go
Reply
#7
(08-19-2014, 11:07 AM)jesalvein Wrote: Wierd.
What if you delete lang\Ar ?

Tried it and the problem still persists.
Not sure what is causing it because the older versions work fine.
Reply
#8
Update plug-ins maybe?
CPU:
Intel Core2 Duo T5450 (1.666 GHz)
[Image: gzztty.png]
GPU:
Mobile Intel® 965 Express Chipset Family (500 MHz)
GPU-Z Validation
Other:
RAM: DDR2-666 (2 GB)
---
Not a gaming PC, but I'll try to get a better one in the future.
Reply
#9
What happens if you delete\rename the w32pthreads.4.dll file?
On what OS are you?
You are using the portable version or the installer?
Reply
#10
(08-19-2014, 10:11 PM)vsub Wrote: What happens if you delete\rename the w32pthreads.4.dll file?
On what OS are you?
You are using the portable version or the installer?

I got it to work finally.
I had to rename the w32pthread.3.dll file.
Not sure why that was causing an issue.
Reply




Users browsing this thread: 2 Guest(s)