Skygunner + GSDX = system lockup/bsod/etc

[GoogleCodeExporter]

1) Did the game ever work correctly (i.e. not have this problem) on the
Official PCSX2 build or an earlier version of PCSX2 playground?
(If so, please specify the latest pcsx2-playground or Official revision
that last worked.)
This bug has been occurring since I first tested Skygunner (around 2 years ago)

2) What steps will reproduce the problem?
1. Use any build of pcsx2 as well as any build of gsdx
2. Run Skygunner
3. Get a bsod/system lockup...
4. hard reboot your pc and try again 6months from now :p

3) What exactly happens when you experience this issue (listing any console
errors or screen output you recieve)?
can't really tell, I'm on win7 now, and apparently the debugging dx9 runtimes 
are borked.
If I can debug gsdx in dx10/dx11 mode, it'd be great to know how.

4) What version of PCSX2 are you using? On what operating system?
tested up to r1767, with corresponding gsdx plugin
win7 ultimate x64, gtx280 - 190.62 drivers

5) Please provide any additional information below.
The SkyGunner.dump file created is 0bytes in length
This game runs pretty well in ZeroGS

Original issue reported on code.google.com by godisgovernment on 7 Sep 2009 at 2:50

[GoogleCodeExporter]

BSOD is really weird and very hard to be caused just by the plugin. Can you test
again with the latest SVN (the new GUI) and the latest GSdx?

Original comment by pcsx2gu...@gmail.com on 2 Dec 2009 at 9:43

• Added labels: Plugin-Gsdx

[GoogleCodeExporter]

This games makes pcsx2 crash as soon as it boots with GSdx on HW mode, but it 
works
with SW, I can leave a blockdump...though seeing the issue is about the 
particular
BSOD it is only going to bring more confusion.

Original comment by shadow0...@mail.com on 2 Dec 2009 at 8:01

[GoogleCodeExporter]

Well I filed the issue quite some time ago. Just tested, and "only" got a 
system hang 
so bad that I had to hard-reboot. During this, I can hear my hdd thrashing - so 
I can 
only assume that it's some fucking huge memleak in gsdx. (4GB of ram here...)
I don't really have time to be risking system freezes atm, so someone else will 
have to 
test and such...good luck :)

Original comment by godisgovernment on 3 Dec 2009 at 2:51

[GoogleCodeExporter]

I've never run into a bsod running that game. With some versions (probably some
betas, I don't remember which, pre 0.9.6) I've gotten past the initial hang up, 
the
opening has played and then hangs again getting into the menus. It takes several
minutes to clear the system hangs although I've only gotten past the first one.

Original comment by vongovero@gmail.com on 22 Dec 2009 at 7:41

[GoogleCodeExporter]

There's a good chance enabling 8 bit textures in GSdx will "fix" this problem.  
It's 
not so much a memory leak as very "liberal" texture cache allocation by GSdx, 
to the 
point that it consumes all ram on your PC while trying to cache whatever 
bizarre 
pattern of texture access/modification the game employs.

If 8 bit textures fixes it, great.  if not, then we'll mark it down as another 
game 
(along with Xenosaga 2 and some other games Bositman knows of) that kill 
computers with 
the "4gb allocated to textures" problem.

Original comment by Jake.Stine on 23 Dec 2009 at 5:41

[GoogleCodeExporter]

Sadly (last test on r2408), 8bit textures doesn't help at all. Altough, it 
works with
either Software mode.

In hardware modes however, using Dx9 makes it crash, while using Dx10 makes the
computer unusable for a few min until it crashes by the error of unresponsive 
thread.
I guess that could trigger a BSOD if the computer is not really stable.

I remember it worked at some point with GSDX, I'll try to pin-point the 
revision.

Original comment by KrossX3 on 2 Jan 2010 at 3:27

[GoogleCodeExporter]

Dang... I can't find any. I was probably playing on Software then. >_<

Original comment by KrossX3 on 2 Jan 2010 at 4:30

[GoogleCodeExporter]

Chances are this is working by now. And if not, try to set skipdraw to 100, 
then 
test again.

Original comment by ramapcsx2 on 3 Apr 2010 at 5:24

• Changed state: Accepted

[GoogleCodeExporter]

Now it eats up 2.xGB of ram and then pcsx2 crashes.
Dunno how chnge skipdraw.

Original comment by godisgovernment on 4 Apr 2010 at 4:11

[GoogleCodeExporter]

As of r3012 it still crashes. And setting skipdraw to 100 on the next test, 
made the
display driver restart itself... while memory was being eaten.... so it couldn't
restart properly and gave a nice BSOD.

@godisgovernment: You'll need to add allowHacks=1 on GSDX.INI file so the 
options
will appear on the GSDX config window. Or, just use the INI itself while you're 
at it.

Original comment by KrossX3 on 16 May 2010 at 11:36

[GoogleCodeExporter]

still crashing on r3878...working on gsdx dx10 software mode but freezing at 
tranning mode loading screen...

Original comment by bernardo...@gmail.com on 20 Nov 2010 at 1:55

[GoogleCodeExporter]

As of r4427, it still wreaks havoc when started with GSDX in hardware mode.

Original comment by KrossX3 on 14 Mar 2011 at 1:24

[GoogleCodeExporter]

Well, no point in tracking this anymore.
We know what the problem is, it'll be fixed with a new GSdx texture cache.

Original comment by ramapcsx2 on 9 Apr 2011 at 6:34

• Changed state: YesWeKnow

[GoogleCodeExporter]

^ ummm 9.8 and skygunner is still crashing 5min system freeze,,and refuse to go 
past the black screen

Original comment by WyattR.H...@gmail.com on 13 Jul 2011 at 7:55

[GoogleCodeExporter]

Still crashing.

Original comment by Gearo...@gmail.com on 11 Sep 2011 at 12:31