Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Working on Windows 8.1?
#1
Does anyone have this damn thing working on Windows 8.1? No matter what I do or how many times I Re-install I get this:

[Image: 557beb1961.png]

I have the credist x86 and 64. And all the basic stuff. I even tried a mobile version where it was all in a RAR and you unzip and use it and it still did this.

I have no other ideas here. Windows 8.1 AMD FX 8150 3.6 GHz, Radeon HD 7850 2GB, 16GB RAM.
Reply

Sponsored links

#2
try running pcsx2 as admin
[Image: gmYzFII.png]
[Image: dvedn3-5.png]
Reply
#3
(08-06-2014, 06:51 AM)Nobbs66 Wrote: try running pcsx2 as admin

Doesn't do crap. I am dual booting with 2 HDD's and PCSX2 works fine on my Windows 7 HDD but the thing is I don't keep that one as up to date with updates and important files because Windows 8.1 is my main HDD. So this Win 8 HDD is as up to date as it can be which boggles my mind.

If I have to I will boot into Windows 7 but it just takes SO LONG compared to Windows 8 and I don't wanna do that because most of my stuff is on Windows 8.
Reply
#4
I had this error too. Mainly because I got my builds from the buildbot and EmuCR.

I solved it by installing the PCSX2 installer.

http://pcsx2.net/download/releases/windo...ndows.html
Reply
#5
(08-06-2014, 07:38 AM)devina40 Wrote: I had this error too. Mainly because I got my builds from the buildbot and EmuCR.

I solved it by installing the PCSX2 installer.

http://pcsx2.net/download/releases/windo...ndows.html

I got mine from here though and it's still doing it after many reinstalls and even installing to a different folder.
Reply
#6
Quote:I have the credist x86 and 64
The 2013 ones ?
CPU : I7 2600K Oc'ed @ 4.2Ghz
Mobo : Intel P67 southbridge
GPU : NVIDIA Geforce GTX 750 Ti
RAM : 6 Go
Reply
#7
(08-06-2014, 07:55 AM)jesalvein Wrote: The 2013 ones ?

Yes the 2013 ones. Is it because I have both? Btw my OS is 64bit.
Reply
#8
Quote:PCSX2 1.3.0.r5919 - compiled on Feb 28 2014
Savestate version: 0x9a0a0000

Host Machine Init:
Operating System = Microsoft (build 9200), 64-bit
Physical RAM = 16332 MB
CPU name = Intel® Core™ i3-2120 CPU @ 3.30GHz
Vendor/Model = GenuineIntel (stepping 07)
CPU speed = 3.290 ghz (4 logical threads)
x86PType = Standard OEM
x86Flags = bfebfbff 1d9ae3bf
x86EFlags = 28100000

x86 Features Detected:
MMX.. SSE.. SSE2.. SSE3.. SSSE3.. SSE4.1.. SSE4.2.. AVX

Quote:Microsoft Windows [Version 6.3.9600]
© 2013 Microsoft Corporation. All rights reserved.

C:\Users\Saiki>ver

Microsoft Windows [Version 6.3.9600]

C:\Users\Saiki>
Reply
#9
It should not matter if you run the x86 and the x64 together, but you always can try the older VC ones like 2012/2008 Smile
Reply
#10
(08-06-2014, 08:00 AM)BunnyBoy21 Wrote: Yes the 2013 ones. Is it because I have both? Btw my OS is 64bit.

Having both is fine. This is an odd error indeed... although I've seen it somewhere before, I can't remember the fix.

Did you try updating directx, just to see?
[Image: vwah44]
Gaming: Intel i7 3770k @ 4.2Ghz | R9 290 | 16GB RAM | 480GB(240GB+240GB RAID0) SSD | 3 TB HDD | 1 TB HDD | 500GB HDD
Server: AMD FX 6300 @ 4.4Ghz | GTX 670 | 16GB RAM | 240GB SSD | 320GB HDD
PCSX2 General Troubleshooting FAQ
Reply




Users browsing this thread: 1 Guest(s)