terminator uploaded file logs.zip (2.4 KiB)

terminator commented

nvidia driver 365.10, win7sp1 64bit.

Cyp changed status from new to closed

Cyp changed blocking which not transferred by tractive

Cyp changed blockedby which not transferred by tractive

Cyp changed resolution from `` to external

Cyp commented

From the stack trace, it looks like there's nothing we can do, since it doesn't crash in any of the Warzone game code. If I'm mistaken, please reopen.

Your graphics driver is 11 days old, you could try updating your driver to the latest from today and hope.

Call stack:
00020052
6A3D2CEC  C:\Windows\system32\nvoglv32.DLL:6A3D2CEC
6A3D2E16  C:\Windows\system32\nvoglv32.DLL:6A3D2E16
6A3D2DC5  C:\Windows\system32\nvoglv32.DLL:6A3D2DC5
6A5C7F75  C:\Windows\system32\nvoglv32.DLL:6A5C7F75  DrvPresentBuffers
6A66B9CF  C:\Windows\system32\nvoglv32.DLL:6A66B9CF  DrvPresentBuffers
69C4A872  C:\Windows\system32\nvoglv32.DLL:69C4A872
69C2DA91  C:\Windows\system32\nvoglv32.DLL:69C2DA91
69C2368C  C:\Windows\system32\nvoglv32.DLL:69C2368C
6A66BF6A  C:\Windows\system32\nvoglv32.DLL:6A66BF6A  DrvPresentBuffers
69C236A0  C:\Windows\system32\nvoglv32.DLL:69C236A0
69C21E03  C:\Windows\system32\nvoglv32.DLL:69C21E03
69C40A54  C:\Windows\system32\nvoglv32.DLL:69C40A54
69C20E91  C:\Windows\system32\nvoglv32.DLL:69C20E91
6A599894  C:\Windows\system32\nvoglv32.DLL:6A599894  DrvValidateVersion
6A65704E  C:\Windows\system32\nvoglv32.DLL:6A65704E  DrvPresentBuffers
6A647D83  C:\Windows\system32\nvoglv32.DLL:6A647D83  DrvPresentBuffers
69C4348C  C:\Windows\system32\nvoglv32.DLL:69C4348C
69C43407  C:\Windows\system32\nvoglv32.DLL:69C43407
6A5A72CF  C:\Windows\system32\nvoglv32.DLL:6A5A72CF  DllMain
6A5A7419  C:\Windows\system32\nvoglv32.DLL:6A5A7419  DllMain
6A5A7256  C:\Windows\system32\nvoglv32.DLL:6A5A7256  DllMain
6A5A6DE1  C:\Windows\system32\nvoglv32.DLL:6A5A6DE1  DllMain
6A594922  C:\Windows\system32\nvoglv32.DLL:6A594922  DrvSwapLayerBuffers
6A59467D  C:\Windows\system32\nvoglv32.DLL:6A59467D  DrvSwapBuffers
6B4FC79F  C:\Windows\system32\OPENGL32.dll:6B4FC79F  wglGetProcAddress
6B505E90  C:\Windows\system32\OPENGL32.dll:6B505E90  wglSwapBuffers
772C5A20  C:\Windows\syswow64\GDI32.dll:772C5A20  SwapBuffers
00718386  D:\Games\Warzone 2100-3.2.0_beta1\warzone2100.exe:00718386  SDL_LogCritical
00698314  D:\Games\Warzone 2100-3.2.0_beta1\warzone2100.exe:00698314  SDL_LogCritical

terminator commented

D:\Games\Warzone 2100-3.2.0_beta1\warzone2100.exe:00622A60  wzScreenFlip  /home/wz2100/build/warzone2100-3.2.0_beta1/lib/sdl/main_sdl.cpp:445
005F1412  D:\Games\Warzone 2100-3.2.0_beta1\warzone2100.exe:005F1412  pie_ScreenFlip  /home/wz2100/build/warzone2100-3.2.0_beta1/lib/ivis_opengl/piemode.cpp:98

Could it be the problem here ?

I've tested few previous driver versions and the latest for Doom release. But all the same. :(

Cyp commented

Do you mean that you can't take screenshots in Doom either? If so, then I'd think it's extra likely to be the driver.

terminator commented

Replying to Warzone2100/old-trac-import#4377 (comment:4):

Do you mean that you can't take screenshots in Doom either? If so, then I'd think it's extra likely to be the driver.

Nope, Doom its just a driver release name or something of latest verion 365.19-notebook-win8-win7-64bit-international-whql.exe (optimizations for doom ). I believe its only crashes in warzone.

klasskill commented

1600x900 is the problem

Berg changed _comment0 which not transferred by tractive

Berg commented

make sure your screen resolution is correct I edited my master res by hand as its true screen resolution was not available in options now no crash for me that is.
In the .warzone2100 config file

Cyp changed status from closed to reopened

Cyp changed resolution from external to ``

Cyp commented

If it crashes for multiple people on multiple OSs, then maybe there is a bug somewhere after all. Weird that I can't reproduce it, though…

Cyp commented

Would someone else please attach crash logs? (Especially if running Linux?)

I don't see anything in the crash logs showing what triggered it, hopefully other crash logs would.

klasskill commented

I tried 1600x900 but it still works here

Cyp commented

Can someone who can reproduce the issue test if the patch in #4421 fixes the issue?

terminator commented

Just tested on warzone2100-master-20160619-225501-6744ea2 , but windows7sp1 64 GT740 driver 368.22

checked warzone's config file, resolution same as in ..everywhere.

Same crash still uppers.

terminator uploaded file Warzone2100.RPT (7.9 KiB)

terminator commented

3.2 release still have this bug. 3.1.5 - works fine.

p.s.
too early Per, too Early

Cyp commented

The problem is if noone that would be able to fix the bug can reproduce it, and the stack traces don't give any useful information at all, just that it crashes somewhere in the NV graphics driver, in some thread created by the graphics driver, so there's nowhere to even start looking.

Is there anyone that can reproduce it, who can try to fix it?

Berserk Cyborg commented

I ran cppcheck 1.79 recursively through warzone and it did yield these warnings with the latest master and could be helpful:

[ivis_opengl/png_util.cpp:319]: (warning) Size of pointer 'buffer' used instead of size of its data. This is likely to lead to a buffer overflow. You probably intend to write 'sizeof(*buffer)'.
[ivis_opengl/png_util.cpp:334]: (warning) Size of pointer 'jpeg' used instead of size of its data. This is likely to lead to a buffer overflow. You probably intend to write 'sizeof(*jpeg)'.
[ivis_opengl/png_util.cpp:323]: (error) Memory leak: buffer
[ivis_opengl/png_util.cpp:339]: (error) Memory leak: jpeg

Cyp commented

The first two are weird but harmless, unless you are on a 8-bit or 16-bit machine; see the comment on the same lines. The last two look like bugs in cppcheck.

Berserk Cyborg commented

Marked #4714 as duplicate.

Quenton commented

Still doing it in latest master build warzone2100-master-20180124-215933-d49d9de.exe and just updated video drivers yet again and it has the exact same issue and the exact same crash dump.

It crashes the moment you press F10.

Tried 8 different driver versions and they all crash. It does not seem like a driver bug if this does it through all these versions and no other game crashes when you take screenshots.

terminator commented

yesterday made a screenshot. & its wroks for master version. However my hardware has been completly changed (new CPU & Gpu)

Forgon changed status from reopened to closed

Forgon changed resolution from `` to external

Forgon commented

Replying to [comment:19 terminator]:

yesterday made a screenshot. & its wroks for master version. However my hardware has been completly changed (new CPU & Gpu)

So this is most likely an external problem, as Cyp said. The ticket is thus closed.