..:: PCSX2 Forums ::..

Full Version: Explain Gran Turismo 4 NTSC-J (SCPS-17001) International B License 5 Crash
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I'm not looking for the solution to fix the problem, but I'm looking for an explanation for this problem.
You see every time I'm trying to take the International B License 5; (The Costa di Amalfi Peugeot 206 RC follow the Nissan Pace Car License Test)
the game crashes all of a sudden leaving a complicated error status messages.
[Image: GranTurismo4NTSC-JSCPS-17001Crash1_zpsfc69abad.jpg]

This one I can copy and paste.
Code:
(EE pc:0059C390) TLB Miss, addr=0x2000000 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000001 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000002 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000003 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000004 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000005 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000006 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000007 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000008 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000009 [load]
(EE pc:0059C390) TLB Miss, addr=0x200000a [load]
(EE pc:0059C390) TLB Miss, addr=0x200000b [load]
(EE pc:0059C390) TLB Miss, addr=0x200000c [load]
(EE pc:0059C390) TLB Miss, addr=0x200000d [load]
(EE pc:0059C390) TLB Miss, addr=0x200000e [load]
(EE pc:0059C390) TLB Miss, addr=0x200000f [load]
(EE pc:0059C390) TLB Miss, addr=0x2000010 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000011 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000012 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000013 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000014 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000015 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000016 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000017 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000018 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000019 [load]
(EE pc:0059C390) TLB Miss, addr=0x200001a [load]
(EE pc:0059C390) TLB Miss, addr=0x200001b [load]
(EE pc:0059C390) TLB Miss, addr=0x200001c [load]
(EE pc:0059C390) TLB Miss, addr=0x200001d [load]
(EE pc:0059C390) TLB Miss, addr=0x200001e [load]
(EE pc:0059C390) TLB Miss, addr=0x200001f [load]
(EE pc:0059C390) TLB Miss, addr=0x2000020 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000021 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000022 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000023 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000024 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000025 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000026 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000027 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000028 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000029 [load]
(EE pc:0059C390) TLB Miss, addr=0x200002a [load]
(EE pc:0059C390) TLB Miss, addr=0x200002b [load]
(EE pc:0059C390) TLB Miss, addr=0x200002c [load]
(EE pc:0059C390) TLB Miss, addr=0x200002d [load]
(EE pc:0059C390) TLB Miss, addr=0x200002e [load]
(EE pc:0059C390) TLB Miss, addr=0x200002f [load]
(EE pc:0059C390) TLB Miss, addr=0x2000030 [load]
(EE pc:0059C390) TLB Miss, addr=0x2000031 [load]
..\..\FiFo.cpp(47) : assertion failed:
    Function:  ReadFIFO_VIF1
    Thread:    EE Core
    Condition: vif1Regs.stat.FQC != 0
    Message:   FQC = 0 on VIF FIFO READ!

[00] 0x01563417                                  
[01] 0x0156420E                                  
[02] 0x01564787                                  
[03] 0x012A8555                                  
[04] 0x0124D3CE                                  
[05] 0x012FB63E                                  
[06] 0x01274F41                                  
[07] 0x0127566E                                  
[08] 0x012756A6                                  
[09] ptw32_throw                                
[10] endthreadex                                
[11] endthreadex                                
[12] BaseThreadInitThunk                        
[13] RtlInitializeExceptionChain                
[14] RtlInitializeExceptionChain

After that an error window will appear and telling me to terminate the program.
[Image: GranTurismo4NTSC-JSCPS-17001Crash2_zps093bd923.jpg]

If I choose yes, the program will terminate.
If I choose no, nothing will happen.
If I choose ignore, some more error statuses will appear.
I cannot copy paste them because the error statuses are really fast.

[Image: GranTurismo4NTSC-JSCPS-17001Crash4_zps4f939b38.jpg]
[Image: GranTurismo4NTSC-JSCPS-17001Crash5_zpsf401d6c9.jpg]
[Image: GranTurismo4NTSC-JSCPS-17001Crash3_zpseb980599.jpg]

And it will going to be an infinite loop on the last picture.
May somebody please explain these to me? Thank you very much.
Also if somebody are asking for my specs:
CPU: Intel Core 2 Duo 2.66Ghz
GPU: Nvidia GeForce GT430
RAM: 4GB
OS: Windows 7 Ultimate x64

And these are my emulator and plugins:
PCSX2 1.0.0 r5350
GS: GSDX32-SSE4-r5350
PAD: Lilypad-r5350
SPU: SPU2-X-r5350
CD DVD: P.E.Op.S. CDVD
USB: USBnull
FW: FWnull
DEV9: DEV9null
kind of misreading from pcsx2.
means some data is corrupted on your disc
(06-25-2013, 09:00 AM)jesalvein Wrote: [ -> ]kind of misreading from pcsx2.
means some data is corrupted on your disc

I see.
Thank you very much for your response.
(06-25-2013, 09:02 AM)popon01 Wrote: [ -> ]I see.
Thank you very much for your response.

That or you are trying incorrect cheat codes.
or the fact this is a known crash and you need to disable "automatic game fixes" then make sure your clamping for EE/VU is set to normal or none, then it works ;p

text will look freaky/missing letters, but it won't crash.
(06-25-2013, 10:19 AM)nosisab Ken Keleh Wrote: [ -> ]That or you are trying incorrect cheat codes.
Sadly I played this without cheating and it still crashes.

(06-25-2013, 06:26 PM)refraction Wrote: [ -> ]or the fact this is a known crash and you need to disable "automatic game fixes" then make sure your clamping for EE/VU is set to normal or none, then it works ;p

text will look freaky/missing letters, but it won't crash.
Tried them, but the results are still the same.
Thanks for the possible solutions, I really think this is a corrupted data error.
That happen to me too. it means its a glitch/bug within PCSX2. I tried it in versions 0.9.8 and 1.0.0, same thing happened. I wonder if it happens in vrsion 1.1.0 r5366? they must have a new update that fixes this problem