EmuNewz Network - Grand Theft Auto IV [BLES00229]

This game don't show anything so i don't know where can i post it. If a moderator think that i posted in wrong section move or delete it.
It's locked on "E {PPU[0x1] Thread (main_thread)[0x00e76ecc]} cellSpurs: cellSpursTaskGetContextSaveAreaSize" but the CPU is on 75 % of usage, after 15 minutes of start.
[attachment=19736]

New log:
[attachment=20793]
i am using rpcs3-ReleaseLLVM-8e12c4cb

(01-15-2016, 04:01 PM)supergatto Wrote: [ -> ]New log:

i am using rpcs3-ReleaseLLVM-8e12c4cb

Could you please try with cellSpurs and cellSpursJq LLE?

(01-15-2016, 04:11 PM)tambre Wrote: [ -> ]
(01-15-2016, 04:01 PM)supergatto Wrote: [ -> ]New log:

i am using rpcs3-ReleaseLLVM-8e12c4cb

Could you please try with cellSpurs and cellSpursJq LLE?

How?
Anyway new log:
[attachment=21195]
I am using rpcs3-ReleaseLLVM-7584f29e

(03-15-2016, 12:47 PM)supergatto Wrote: [ -> ]
(01-15-2016, 04:11 PM)tambre Wrote: [ -> ]
(01-15-2016, 04:01 PM)supergatto Wrote: [ -> ]New log:

i am using rpcs3-ReleaseLLVM-8e12c4cb

Could you please try with cellSpurs and cellSpursJq LLE?

How?
Anyway new log:

I am using rpcs3-ReleaseLLVM-7584f29e

You NEED to LLE the two modules specified above to get anything at all.
Check the guide in my signature.
Also, your game folder isn't named to the Game's ID.

#Sent from my phone

I did it and here my log.
[attachment=21200]

When i stop it, he write another error:
[attachment=21201]

No more crashes in this game but it doesn't show anything.
Here log.
Modules loaded:
-CellSre
-CellSpursJQ
[attachment=21316]

Different log, now there is a memory error.
[attachment=21332]

Now it show

Code:
{PPU[0x3] Thread (main_thread) [0x00e765f0]} class std::runtime_error thrown: Function not registered (index 2974)

(in file C:\rpcs3\rpcs3\Emu\Cell\PPUModule.cpp:57)

[attachment=21338]

Fatal error:

Code:
E {PPU[0x1000000] Thread (main_thread) [0x01085000]} PPU: Unregistered function called (LR=0xa15f18)

F {PPU[0x1000000] Thread (main_thread) [0x01085f98]} MEM: Access violation writing location 0x400

Different log:
[attachment=27072]