GPU overload problem

[kretjop]

Sometimes the GPU gets overloaded to 100% and it causes it to crash or freeze. I don't know why. I think its some kind of memory leak. Normally GPU is used at 30%, but it can instantly jump to 100%.

Windows 10, current drivers, no dlc, no mods.

 

[kretjop]

and AMD CPU so its not a Intel problem

 

[kretjop]

Again I see an error that may cause a leak

PdxGuiWidget.FindChild() can u check this?

[00:45:46][pdx_data_callstack.cpp:52]: Promote 'FindChild' returned nullptr, in 'PdxGuiWidget.FindChild('interest_group_top').TriggerAnimation('show')'
[00:45:46][pdx_data_callstack.cpp:52]: Promote 'FindChild' returned nullptr, in 'PdxGuiWidget.FindChild('interest_group_top').TriggerAnimation('show')'
[00:45:46][pdx_data_callstack.cpp:52]: Promote 'FindChild' returned nullptr, in 'PdxGuiWidget.FindChild('interest_group_top').TriggerAnimation('show')'
[00:45:46][pdx_data_callstack.cpp:52]: Promote 'FindChild' returned nullptr, in 'PdxGuiWidget.FindChild('interest_group_top').TriggerAnimation('show')'
[00:45:46][pdx_data_callstack.cpp:52]: Promote 'FindChild' returned nullptr, in 'PdxGuiWidget.FindChild('interest_group_top').TriggerAnimation('show')'
[00:45:46][pdx_data_callstack.cpp:52]: Promote 'FindChild' returned nullptr, in 'PdxGuiWidget.FindChild('interest_group_top').TriggerAnimation('show')'

 

[kretjop]

I just found workaround for this bug, you have to keep pinned group of interest expanded when they are pinned and PdxGuiWidget can find them, so Developers -> you should go in this direction to fix this bug

 

[AndrewT]

Well, 100% is fully loaded, not necessarily overloaded! The GPU ought to be able to run at 100% just fine, normally.

But from that screenshot your GPU is at 72c when at only 2%, which will almost certainly mean it is overheating when full utilised.



Right click on victoria3.exe , properties, compatibility. Tick "disable fullScreen optimisations" untick every other box in that dialog, Apply and exit.
Then in the launcher Game Settings menu, select fullScreen display mode, Vsync off, cap refresh rate at 60.

If those don't help:
DXDIAG is a program you run from the Windows search box on the task bar. After running it will open a window and start collecting info with a progress bar in the lower-left corner. When it completes click the 'save all information' button and save it to a file then attach that file here.
IF dxdiag.txt fails to attach here, rename it to dxdiag.log , or zip it up.

Please attach here your Documents/Paradox Interactive/Victoria3/pdx_settings.json .
From your Documents/Paradox Interactive/Victoria3/logs/ folder, attach here system.log , error.log
From your Documents/Paradox Interactive/Victoria3/crashes/ folder, attach here the latest (only!) exceptions.txt

 

[kretjop]

Well, 100% is fully loaded, not necessarily overloaded! The GPU ought to be able to run at 100% just fine, normally.

But from that screenshot your GPU is at 72c when at only 2%, which will almost certainly mean it is overheating when full utilised.



Right click on victoria3.exe , properties, compatibility. Tick "disable fullScreen optimisations" untick every other box in that dialog, Apply and exit.
Then in the launcher Game Settings menu, select fullScreen display mode, Vsync off, cap refresh rate at 60.

If those don't help:
DXDIAG is a program you run from the Windows search box on the task bar. After running it will open a window and start collecting info with a progress bar in the lower-left corner. When it completes click the 'save all information' button and save it to a file then attach that file here.
IF dxdiag.txt fails to attach here, rename it to dxdiag.log , or zip it up.

Please attach here your Documents/Paradox Interactive/Victoria3/pdx_settings.json .
From your Documents/Paradox Interactive/Victoria3/logs/ folder, attach here system.log , error.log
From your Documents/Paradox Interactive/Victoria3/crashes/ folder, attach here the latest (only!) exceptions.txt

Sure brother I did it before I posted the thread, even on 40c temperature problem was the same. Temporary jump of usage caused a crash, not temperature or anything else.

 

[kretjop]

After expanding group of interest in pinned tab I can play 20 or more minutes with even 82c temperature and 0 crash! @AndrewT thats awesome

 

[PDX_Sosanna]

guiwidget errors in the error log have no relation to any CTDs. The CTD information is stored in the exception log and the minidump inside Documents/Paradox Interactive/Victoria 3/crashes