Windows 10 upgrade

Hi,

has anyboby noticed that after last windows 10 upgrade Galciv III has started to cause windows 10 crash. It had happened me couple of times in last two days.

 

11,063 views 14 replies
Reply #1 Top

Nope. Upgraded to Win 10 about two months ago and haven't had any real problems. But if you have some older hardware in your rig, then it can cause some instability.

Reply #2 Top

I have not  had any issues with Windows 10. Game seems better optimized on memory better. When I start having crash or CTD issues I go and check and see if Nvidia has released  new drivers which they have since 2 weeks ago. I would do the basics first. Check Drivers, Clean the drive or Optimize it and see if that helps. 

 

Also check and see if you have maleware. I use 'Malewarebytes' for this. It seems to do a FAR better job on finding crap than usual virus software..

 

 

Reply #3 Top

They are not normal CTD, the whole windows crash, so I have to booted the whole machine. I haven't have that kind of issues never earlier. I also had a newest NVIDIA drivers and I also have had Malewarebytes for couple of years.

Reply #4 Top

One thing to clarify. This crash started to happend after windows 10 uprage Version 1511. November upgrade.

Reply #5 Top

Sounds like you have your bases covered. Hardware? Powersupply or connectivity to video card? ...

Reply #6 Top

Also consider running Prime95 from Mersenne.org.  It will stress your CPU/RAM in ways that very few other tools will and often uncovers instability that others miss.  My general rule-of-thumb is that if you can run Prime95 overnight without any errors, then you're probably in good shape.

Reply #7 Top

Quoting Larsenex, reply 5

Sounds like you have your bases covered. Hardware? Powersupply or connectivity to video card? ...
End of Larsenex's quote

 

Doubt it's hardware; if he's only started getting the problem since last week's update then it's much more likely MS released a bum patch that disliked something that was already installed in the PC. Again.

Reply #8 Top

1st base virus checker pay

2nd base malwarebytes pay

3rd base cleaner free

shortstop add block pro free

outfield never ever use

Microsoft virus service $486 evil Malevolent Microsoft

remote access show to expensive programs like $150 virus checkers and slow

runs fine on 8 loose some old programs going to 8 no KOTR or Empire Earth

Stardock stuff Works just fine

Reply #9 Top

Quoting naselus, reply 7

Doubt it's hardware; if he's only started getting the problem since last week's update then it's much more likely MS released a bum patch that disliked something that was already installed in the PC. Again.

End of naselus's quote

Probably a bum patch, but it could also be that drivers are now getting loaded into a dodgy section of RAM due to updates.  And power supplies do go bad over time, which leads to all sorts of fun as they put out voltage that is slightly out of spec.

Reply #10 Top

I'm seeing the same behavior after updating to patch 1511, haven't been able to play the game since.  Any hope there'll be a fix?

Reply #11 Top

I'm having the same issue.  There is a thread in the support section I started called Launch Crash with brand new systm

 

If you are having similar issues with not being able launch the game, please reply on this thread and on the one I started.  The more people who report this issue the faster it will get fixed.  The most common thread is the recent upgrade to Windows 10, 1511.

 

Thanks
Frankle

Reply #12 Top

Have also problems since the november update of windows 10. GalCiv3 is not starting anymore... I get the start window but then game is not responding anymore... Can't start other game either. (X-Com)

 

 

so here is the solution. just make a rollback on windows 10 and return to an earlier build. you can do it in the update center. i just did it and it works... can start both games again... now i make sure to turn off the damn autoupdate in windows...

Reply #13 Top

Upgrading to AMD's newest beta driver fixed it for me.  No more crashing.

Reply #14 Top

I had the same problem and solution as MScottowczarek.  After the BETA driver everything's been working fine.