GP4 destroyed my day - Freezing Error [SOLVED]

salvasirignano écrivait:
-------------------------------------------------------
> > I have got a question: Is it possible to rename
> > the track wads like the gp4 files? My idea was
> to
> > rename my tracks wads like the original wads
> order
> > and names.
>
>
> That doesn't help I'm afraid! That's how I install
> my tracks, renaming the wad and all the .gp4,
> .bin, etc files inside it to the slot they are
> replacing.
> I don't use gpx patch or TSM to change tracks.
> The freezes still happen.

Thank you. Could you tell me which soundcard do you have?
And another thing: did you install your track via TSM?

____________________________________________________________________________________________________________________________________________

Does it freeze also if you use GPxTrack to 'install' the track?

René Smit, Independent Software Developer.
Download my GPx tools here.

If you use the Process Explorer tool, go to the properties of the hanging gp4.exe, go to the Threads tab, and view the stack of each thread, what does it show?

René Smit, Independent Software Developer.
Download my GPx tools here.

SDI écrivait:
-------------------------------------------------------
> Does it freeze also if you use GPxTrack to
> 'install' the track?

@René, I am using TSM to install tracks (I don't use CSM btw). So, I will try with GPxTrack ! I will let you know.
PS: I see that the tracks I have loaded via tsm are also automatically loaded into GPxTrack (the dat files). Do you recommend me to use GPxTrack only?

____________________________________________________________________________________________________________________________________________

Yes, I recommend to use GPxTrack only, with an unmodded gp4 installation.

René Smit, Independent Software Developer.
Download my GPx tools here.



Edited 1 time(s). Last edit at 04/11/2015 04:12PM by SDI.

SDI écrivait:
-------------------------------------------------------
> If you use the Process Explorer tool, go to the
> properties of the hanging gp4.exe, go to the
> Threads tab, and view the stack of each thread,
> what does it show?

I see my dat list order. Some are named as S1CT0X and others are named differently: Here is the list:


____________________________________________________________________________________________________________________________________________

Excalibur Wrote:
-------------------------------------------------------
> salvasirignano écrivait:
> --------------------------------------------------
> -----
> > > I have got a question: Is it possible to
> rename
> > > the track wads like the gp4 files? My idea
> was
> > to
> > > rename my tracks wads like the original wads
> > order
> > > and names.
> >
> >
> > That doesn't help I'm afraid! That's how I
> install
> > my tracks, renaming the wad and all the .gp4,
> > .bin, etc files inside it to the slot they are
> > replacing.
> > I don't use gpx patch or TSM to change tracks.
> > The freezes still happen.
>
> Thank you. Could you tell me which soundcard do
> you have?
> And another thing: did you install your track via
> TSM?


I think mine is an onboard realtek device. I don't use TSM - I install my tracks by renaming and replacing....

One interesting thing is that if I give my brother a race on LAN, if it happens it happens on both computers simultaneously, both computers freeze together!

===================================================================================
Tahitian GP Circuit
[www.grandprixgames.org]
Easter Island Circuit
[www.grandprixgames.org]

salvasirignano écrivait:
-------------------------------------------------------
> Excalibur Wrote:
> --------------------------------------------------
> -----
> > salvasirignano écrivait:
> >
> --------------------------------------------------
>
> > -----
> > > > I have got a question: Is it possible to
> > rename
> > > > the track wads like the gp4 files? My idea
> > was
> > > to
> > > > rename my tracks wads like the original
> wads
> > > order
> > > > and names.
> > >
> > >
> > > That doesn't help I'm afraid! That's how I
> > install
> > > my tracks, renaming the wad and all the .gp4,
> > > .bin, etc files inside it to the slot they
> are
> > > replacing.
> > > I don't use gpx patch or TSM to change tracks.
>
> > > The freezes still happen.
> >
> > Thank you. Could you tell me which soundcard do
> > you have?
> > And another thing: did you install your track
> via
> > TSM?
>
>
> I think mine is an onboard realtek device. I don't
> use TSM - I install my tracks by renaming and
> replacing....

The interesting thing is that I thought it could related to the sound. I have got an integrated Realtek, too. I know that , by the past, I had some issue with another computer and GP4 due to the sounds and another Realtek card. I didn't remember how I fixed it but I have disabled some options into Gpxsound, if I remember...
>
> One interesting thing is that if I give my brother
> a race on LAN, if it happens it happens on both
> computers simultaneously, both computers freeze
> together!

Ok. The 2 computers had the same specs and same installations?

____________________________________________________________________________________________________________________________________________

Excalibur Wrote:

> Ok. The 2 computers had the same specs and same
> installations?

Well the installations were exact duplicates, but the computers were slightly different specs. Both have onboard realteks however...

===================================================================================
Tahitian GP Circuit
[www.grandprixgames.org]
Easter Island Circuit
[www.grandprixgames.org]

Excalibur, I don't think you understood me right
I mean something like this:



René Smit, Independent Software Developer.
Download my GPx tools here.

Yes, sorry René. I was thinking about something else. Do you want me to show you the stack when the game runs normally or when it freezes? Or it doesn't matter?

Edit: I have loaded a game save. Here is the stack for thread lines:

ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x682
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!PsIsSystemProcess+0x88
ntoskrnl.exe!KeStackAttachProcess+0x11b9
ntoskrnl.exe!ObReferenceObjectByPointerWithTag+0x22b
wow64cpu.dll!CpuSuspendLocalThread+0x8a8
d3d9.dll!DebugSetLevel+0xf4a48
wow64cpu.dll!CpuSuspendLocalThread+0x8a8
nvd3dum.dll+0x61d0fb
d3d9.dll!DebugSetMute+0x382e
d3d9.dll!DebugSetMute+0x376b
gp4.exe+0x6a5f3
gp4.exe+0x6829f
d3d9.dll!DebugSetMute+0x11832
gp4.exe+0x8952b

Edit2: Something has changed. In order to use the Process Explorer tool, I ran the game in windowed mode. I tried to make the freeze happen once again by launching a race, exiting and speed up the time. No more freeze.... I tried it twice. For informations, I didn't modify my resolutions settings (1920x1080 [RELEASE] ) and (1024x768 [DEBUG]. I have just enabled " Run in window ". Strange...

____________________________________________________________________________________________________________________________________________





Edited 6 time(s). Last edit at 04/11/2015 05:16PM by Excalibur.

I meant the trace for when it freezes. It could reveal where it is freezing.

René Smit, Independent Software Developer.
Download my GPx tools here.

I tried. Unfortunately it happens in fullscreen mode. When it freezes, I can open the task manager and see Process explorer tool but it won't show up on my screen. I have only got a black screen and when I click on the process explorer tool, it seems that it opens behind the black one. I am trying to get the freeze in windowed mode but it doesn't happen!

____________________________________________________________________________________________________________________________________________

Ok. I finally got it to work. So, windowed mode is not the solution. Here is a capture when the game freezes:



____________________________________________________________________________________________________________________________________________





Edited 1 time(s). Last edit at 04/11/2015 06:24PM by Excalibur.

Thanks for the trace. It's hanging in a driver, as expected. Further down the stack I see it is processing tyre marks. Not sure if this is related. You might try to let it hang again to see if the addresses are the same again.
If it is indeed related to tyre marks, this might explain why it happens after a while, since more and more marks are added to the track during the race. You can try to make some donuts for a while to see if this triggers the freeze sooner.

Do you have extended track length enabled by the way?

René Smit, Independent Software Developer.
Download my GPx tools here.

SDI Wrote:
-------------------------------------------------------
> Thanks for the trace. It's hanging in a driver, as
> expected. Further down the stack I see it is
> processing tyre marks. Not sure if this is
> related. You might try to let it hang again to see
> if the addresses are the same again.
> If it is indeed related to tyre marks, this might
> explain why it happens after a while, since more
> and more marks are added to the track during the
> race. You can try to make some donuts for a while
> to see if this triggers the freeze sooner.
>
> Do you have extended track length enabled by the
> way?

Would tyre marks also cause a crash when the race is simulated under accelerated time? On circuits that are a problem for myself and others, the crash happens during accelerated time also....

===================================================================================
Tahitian GP Circuit
[www.grandprixgames.org]
Easter Island Circuit
[www.grandprixgames.org]

SDI écrivait:
-------------------------------------------------------
> Thanks for the trace. It's hanging in a driver, as
> expected. Further down the stack I see it is
> processing tyre marks. Not sure if this is
> related. You might try to let it hang again to see
> if the addresses are the same again.
> If it is indeed related to tyre marks, this might
> explain why it happens after a while, since more
> and more marks are added to the track during the
> race. You can try to make some donuts for a while
> to see if this triggers the freeze sooner.
>
> Do you have extended track length enabled by the
> way?


René, first of all, thanks a lot for spending your time trying to analyse and solve this problem.

Interesting thing about tyre marks. I don't know since when but it is true that they are longer than before. I didn't install anything than new tracks. The new ones are Bahrein night (from Tumyeto) and Nordschleife (by Drt01) but longer tyre marks appears on all the tracks (I will try to post a picture later).

About the track lenght, I let it by default in GPxTrack (never modified) = 8km

As you recommended, I will make donuts on track until something happen and let you know if the freeze appears sooner.

I will also post the trace.

Edit: Test 1: Donuts all the time at the start of a race: Nothing hapenned but before I break my engine, I have decided to accelerate the time. The freeze happened sooner (lap3)
Here is the trace:
ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x682
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!PsIsSystemProcess+0x88
ntoskrnl.exe!KeStackAttachProcess+0x11b9
ntoskrnl.exe!ObReferenceObjectByPointerWithTag+0x22b
gp4.exe+0x10c206
gp4.exe+0x2380d8
gp4.exe+0x10c206
gp4.exe+0x10cb63
gp4.exe+0x11f29f
gp4.exe+0x17fc3
gp4.exe+0x18036

Test2: I Made donuts until it freezes on Kleine NordsCheifle: It was on lap 1 after 1 min approximatively.

ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x682
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!PsIsSystemProcess+0x88
ntoskrnl.exe!KeStackAttachProcess+0x11b9
ntoskrnl.exe!ObReferenceObjectByPointerWithTag+0x22b
gp4.exe+0x10c1e1
gp4.exe+0x2380d8
gp4.exe+0x10c1e1
gp4.exe+0x10cb63
gp4.exe+0x11f29f
gp4.exe+0x17fc3
gp4.exe+0x18036
gp4.exe+0x18745
gp4.exe+0x48fbc2

Edit: Test3: Before to launch the game, I have uninstalled Pinnacle Game Profiler that I have installed recently. I started a championship save, made 1 lap, quit and speed up the time. The freeze happened
The trace is different now:

ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x682
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!PsIsSystemProcess+0x88
ntoskrnl.exe!KeStackAttachProcess+0x11b9
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x88d
ntoskrnl.exe!KeWaitForMutexObject+0x19f
ntoskrnl.exe!IoRegisterFsRegistrationChange+0x306
ntoskrnl.exe!KeSynchronizeExecution+0x3a43
ntdll.dll!NtWaitForDebugEvent+0xa
wow64.dll!Wow64EmulateAtlThunk+0x1c41b
wow64.dll!Wow64SystemServiceEx+0xd7
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x24
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x429
ntdll.dll!LdrGetKnownDllSectionHandle+0x1a7
ntdll.dll!RtlInitCodePageTable+0xe8
ntdll.dll!LdrInitializeThunk+0xe
ntdll.dll!ZwWaitForDebugEvent+0x12
kernel32.dll!WaitForDebugEvent+0x21
GPxPatch.exe+0x2332f

____________________________________________________________________________________________________________________________________________





Edited 4 time(s). Last edit at 04/12/2015 04:33PM by Excalibur.

You got the freezing error already after one minute of making donuts?

TGF1DRIVER écrivait:
-------------------------------------------------------
> You got the freezing error already after one
> minute of making donuts?

It appears randomly and not on all tracks. As René suggested, that was to force the freeze to appear sooner, if possible... It could give some informations on the problem

____________________________________________________________________________________________________________________________________________

Your second freeze is also while processing tyre marks...

Your last dump is from gpxpatch.exe, not gp4.exe

With these traces, and since it happens earlier when making donuts, I'm quite sure it is related to tyre marks. And yes, they are also processed during accelerated time. They are just added to the track surface, even when they are not being rendered. So if you accelerate time through the whole race and go back to the cockpit in the last lap, you'd see a lot more tyre marks.

While working on the extended track length I already experienced problems with tyre marks, including freezes (might be the same freezes you have now).
I had to extend a tyre mark buffer to avoid crashes, that's why I asked if you had it enabled. The freezes seem to be related to another tyre mark buffer, which I haven't touched at all. It's hard to see what's going on exactly.

Maybe something to try: set the maximum track length to 10 or 20km and see if it helps.

René Smit, Independent Software Developer.
Download my GPx tools here.