I recently upgraded to a Core i5 and the funny thing is that PCSX2 is working way worse than previously with a Q6600.The latest SVN built version instantly crashes on execution, the 0.9.6 official version displays my processor info as "0 physical ( 4 logical )" after which on certain game boot-ups (Guilty Gear Accent Core) it crashes where the Q6600 worked ok. I would add that I'm on Windows 7 RTM X64, though I don't know if the OS has anything to do with this.

CPU detection is irrelevant, it's just for info. Download the latest beta again, and set it up once more. We had an issue with it for a brief time, and re-uploaded it.

cippyboy: Have you tried with the latest beta? I've noticed there have been quite a few posts with people on windows 7 having issues with 0.9.6 but haven't in the latest betas.

Yes this was a known bug in the Official that caused it to detect cores incorrectly. The crashing should be unrelated to that, but is possibly also fixed. The betas have much better threading support in general, and Windows7 may have problems with 0.9.6 Official's lack of safe threading.

Just built again, noticed the 5 commits in between, still insta-crashing.

Oh yeah and good news, I can run debug builds, but only from Visual Studio. Afterwards I was unable to run from a DVD, no matter what I chose (Run DVD with DVD source -> Iso/Plugin/No Disc) it required me an ISO image, or no matter what plugin I tried.

Also, now it surely changed the way it detects cores, it says I have 8 physical and 4 logical, awesome.

In WinPipeRedirection() ctor

GetStdHandle(STD_ERROR_HANDLE) returns INVALID_HANDLE_VALUE leading to crash on _open_osfhandle

http://pastebin.com/m7b2c5776

cippyboy: You are building the latest from source? That could also be a problem since the new GUI is very unstable. Your best bet is to use build 1888 from the beta thread.

(09-22-2009 12:31 AM)God_Mark Wrote:  In WinPipeRedirection() ctor

GetStdHandle(STD_ERROR_HANDLE) returns INVALID_HANDLE_VALUE leading to crash on _open_osfhandle

http://pastebin.com/m7b2c5776

I've implemented a fix for this in r1902. If the problem persists let me know here: http://code.google.com/p/pcsx2/issues/detail?id=419

Bug fixed. Closed