• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Not a temperature problem then. Without any clues in dxdiag, the game logs or WEV we have no evidence to point to where the problem is at all!

I was expecting something in WEV in the minute or two leading up to these crashes.

Do you have CK3, if so does it see any similar issue?
 
I haven't had a campaign of ck3 in a long while, i'll give it a try and see if it acts oddly at all.

I was able to play ck3 for about an hour lastnight, without noticing any strange behavior, cpu temps didnt exceed 47c, and gpu floated around 50c.
 
Last edited:
I got home from work today to find that not only had an update for vic3 been pushed, but also an update for the nvidia drivers.
I let the game run in speed 5 while I was AFK making dinner and it ran all the way into the 1900s without exploding my operating system,

I'm not sure which update to thank for the stability improvements, but either way, thanks for bearing with me
 
  • 1Like
Reactions:
I'm here to report that it's happening again. I've changed nothing but allowed steam to update the game. entire desktop freezes about 2 minutes into the campaign, hardware temps and usage are low, no error or crash logs generated. happens on my 4070 desktop with amd cpu and my 2060 laptop with intel
 
So it was okay for 2 weeks, and now it's back? Jeez.

Can we get new dxdiag and log files please.
 
no decent logs were generated, i wiped the shader cache and went through the event viewer. the only errors that were flagged, besides vic3 becoming unresponsive, were a series of issues from the logitech lamp array service. I read that it's involved in allowing applications to take control of the RGB lighting on my peripherals. Knowing pdx games don't generally bother with that, i was pretty confused as to why the error 'application failed to gain full access / driver failure'' from the service would take place when vic3 was running.

I disabled the logi_lamparray service and set it to manual start only, and was able to play a campaign for about an hour without any weird freezes. The general inconsistency in the freezing over the last few days though doesn't allow me to be convinced that i've found the issue. Just an interesting note.

i'll give the campaign another go in the morning and see if i can generate any logs or more info for you
 
  • 1Like
Reactions:
made it all the way to 1870s with my russia campaign before the computer froze up again. it was on a fresh shader cache, running on moderate graphics and barely taxing the hardware. As russia i was at war with the usa and france, and as I was ordering a naval invasion of california the game became unresponsive, discord froze, youtube on my other monitor froze, my cursor and keyboard become unresponsive, and i have to manually reboot.

Event viewer doesnt really have any helpful information at this time, only showing the improper shutdown, and I'm honestly doubting that the game's error logs would generate anything useful while the game is unresponsive - but i don't know any better.
 

Attachments

  • DxDiag.txt
    152,7 KB · Views: 0
  • error.log
    6,6 KB · Views: 0
  • system.log
    956 bytes · Views: 0
  • warning.log
    5 KB · Views: 0
  • game.log
    68,2 KB · Views: 0
You are right - with a hard-hang like that, nothing can generate any logs recording it. I was just hoping WEV would record some precursor event that in turn triggered the hang.

I don't suppose you have CK3? That is the game most like this one, I wonder if it would trigger the problem too.

Try this Windows repair tool:

Please install and run the free utility Speccy. Send its output to a text file and attach that here please.
https://www.ccleaner.com/speccy/download
 
the windows repair tools were unable to find any issues, but when i installed speccy i noticed instantly that my ram was reported as operating way below the specifications of the hardware. I dug around in the bios for a bit and found that the automatic ram clocking profile had the ram running at something like 2600mhz. I manually adjusted the timings to match those provided by the ram manufacturer (nearer to 6000mhz) and was able to boot into my os with no notable instability.

I'm going to give the game another try in the morning and see if that was indeed the issue. something so major would seem odd to not have been causing issues across the entire system, and of course only relates to my desktop and not the laptop's problem.

In the meantime I did manage about an hour of an adventurer's campaign in ck3 with no issues (before correcting the ram)


update dec/25 -
after correcting the ram i was able to play a few hours of ck3 with no issues or hangs (as usual), but vic3 hardfroze the system after less than 2 minutes of gameplay
 

Attachments

  • DESKTOPDREDGEAMD.txt
    132 KB · Views: 0
Last edited:
just an update, i was looking at related issues, and found the threads regarding windows update 24h2.
one of the people on the thread had suggested changing the game's processor affinity, disallowing it from using core 0 and 1. With those settings, when the game freezes, it doesnt lock up the entire PC and the system can be recovered.

running the game like this I am able to at least keep my computer on. The game runs very choppy, freezing up and hanging every 2 or 3 months, with constant crashes that leave no error logs aside from the 'application hang' reported by windows event viewer
 
  • 1Like
Reactions:
We did have one report that a very recent Windows update fixed - or apparently fixed - they 24H2 issues, but I'm waiting for more confirmation before suggesting that to possibly affected users such as yourself.
 
my desktop is already reporting that it's upto date as far as windows is concerned, nothing appears when I refresh it, at least. I decided I would try replacing the geforce gaming driver with the nvidia studio driver, to see if that makes any notable difference in stability. I'll let you know what happens
 
hey, so i'm back.

after a while of basically giving up on playing anything running vulkan, i realized the nvidia app was failing to install recent drivers.
on a whim i decided to run the DDU application to completely remove all nvidia drivers from my system - to atttempt a fresh install directly from the manufacturer's page.
that install failed as well...

curious, i decided to run the DDU again, but this time - disregard 20 years of pc experience - DO NOT download the nvidia drivers - let windows update install their generic driver for my card...

I can now play vic3 until end date, in single player and multiplayer. vulkan games seem to run fine, and the newly added (but not requested) windows os features like auto HDR, also seem to be functional.


I'm wondering if my case is unique, or if this information can help others
 
  • 1Like
Reactions: