..:: PCSX2 Forums ::..

Full Version: god of war settings
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
nexxuno, even if your CPU passes hours and hours of Orthos, PCSX2 could still crash because of it, I know from personal experience. Do a test with your CPU at stock settings and see if the crashes persist to rule it out for sure
Yup, Bositman's right, I had the same issue when I was experimenting with OC. PCSX2 proved itself to be a good testing app Wink
um....i'd like to try and lower the multiplier but i don't have much time to do much testing...maybe one day....damn pcsx2 why should it crash if it passes prime95 and everest....jeez maybe one day i should look into pcsx2 code to understand it a bit more

and it is not even stressing the CPU...is there any easy way to debug it when it stops?VS2008?

too much programming on my thesis...can't stand any more c++ or wathever it is Tongue2
It just uses unusual processor functions, so if your CPU is unstable at those it will crash. Proof that even the most 'stable' overclocks are rarely 100% stable.
um...actually this CPU could be considered not overclocked since i am at default FSB just used the unlocked multiplier and cooled it with a Vendetta2....
Interesting though!
these are the two errors...means anything?guess it is too generic...
Firma problema:
Nome evento problema: APPCRASH
Nome applicazione: pcsx2.exe
Versione applicazione: 0.0.0.0
Timestamp applicazione: 4b90518c
Nome modulo con errori: pcsx2.exe
Versione modulo con errori: 0.0.0.0
Timestamp modulo con errori: 4b90518c
Codice eccezione: c0000005
Offset eccezione: 00026914
Versione SO: 6.0.6002.2.2.0.768.3
ID impostazioni locali: 1040
Informazioni aggiuntive 1: fd00
Ulteriori informazioni 2: ea6f5fe8924aaa756324d57f87834160
Ulteriori informazioni 3: fd00
Ulteriori informazioni 4: ea6f5fe8924aaa756324d57f87834160

and:
Firma problema:
Nome evento problema: APPCRASH
Nome applicazione: pcsx2.exe
Versione applicazione: 0.0.0.0
Timestamp applicazione: 4b90518c
Nome modulo con errori: w32pthreads.v3.dll
Versione modulo con errori: 2.8.3.0
Timestamp modulo con errori: 4b904e5c
Codice eccezione: c0000005
Offset eccezione: 00003da0
Versione SO: 6.0.6002.2.2.0.768.3
ID impostazioni locali: 1040
Informazioni aggiuntive 1: 3604
Ulteriori informazioni 2: feb767aa63067060f392a30bd46c388a
Ulteriori informazioni 3: 5d0b
Ulteriori informazioni 4: ce0e3608fd8e870b0dd5777fab930eb1

Should i translate?

another one :

Firma problema:
Nome evento problema: APPCRASH
Nome applicazione: pcsx2.exe
Versione applicazione: 0.0.0.0
Timestamp applicazione: 4b90518c
Nome modulo con errori: StackHash_87a5
Versione modulo con errori: 0.0.0.0
Timestamp modulo con errori: 00000000
Codice eccezione: c00000fd
Offset eccezione: 74fe9bb4
Versione SO: 6.0.6002.2.2.0.768.3
ID impostazioni locali: 1040
Informazioni aggiuntive 1: 87a5
Ulteriori informazioni 2: 7e8ffdec047eb53b22ce02f8026097d5
Ulteriori informazioni 3: e0b7
Ulteriori informazioni 4: fd7ff13c0c2df1f4ab8515d0572cf854
Can u explain more detail before the application crash ?
There is not much to say it crashes randomly every 15-20 mins....it is not related to anything in particular; anything u want to know ask for it...

this is the crash message:
Version of the module with errors: 2.8.3.0
Timestamp: 4b904e5c
Exception Codice: c0000005
Exception Offset: 00003da0

there other one happened only once
Is it because u unlocked the multiplier ?
(03-22-2010, 05:18 PM)nexxuno Wrote: [ -> ]um...actually this CPU could be considered not overclocked since i am at default FSB just used the unlocked multiplier and cooled it with a Vendetta2....
Interesting though!
Just so you know, changing multiplier is also considered as overclocking( in such case you're changing only cpu clock and leave other components unchange), and I think you may want to check out some overclocking guide for more information about overclocking. If you lower your FSB and increase the multiplier, you will probably get the same result assuming you haven't changed your pcsx2 settings. If that is the case, change back your cpu to stock clock if you haven't done it yet. Then, try again and see if the problem is still there. If it does, show all of the pcsx2 settings for the game so that we have a better idea about the problem.
Pages: 1 2 3