wing987

Aaaand bad news. It worked for a time, but then I decided to view a larger map. That didn't work. I adjusted the registry to expand the delay time to 8, much higher than I would like. This failed to make any difference. So try to play a small map again and now it will not work. The problem is the same as before. Of note: I had restart the computer and NOT played, so it is possible that it was not the map size but the restart

[quote] Ok, stopped and then recovered may very well be what I am talking about. We'll see if there is something we can do on our side. If this is what's going on. If you really want to dig in and try to fix it yourself, you can read this https://msdn.microsoft.com/en-us/Library/Windows/Hardware/ff569918(v=vs.85).aspx I think TdrDelay is what you could try to

Changing mipstoremove to 2 made no change, nor did selecting a different map, I went from random to another 2 player one. The error I get is that the driver stopped then recovered, not a time out issue. I will say though that when I changed the mips to 2 I get a little more...I actually see the word loading at the bottom of the screen for about a second before everything stops. Found out that my AV is still blocking that file...I will try removing the AV then rein

Still failing. So I tried your modification of the settings INI file. However, problem. I have SkipMovie=0 or MipsToRemove=1 There is no MipsToSkip=1 so I cannot make the change. Should I add?

This was a Windows 10 system, yes. I have since rolled back to 7 (other programs were failing as well). Windows 10 completely botched the roll-back, and nearly destroyed my ability to restore a factory image. I had to resort to external ISO's that I took. Currently the game is installed under windows 7, but all of the updates are still applying. There is an update to the driver for the GPU, so we will see if that works. However my attempts have still fa

Being that this is a laptop, and only a couple of years old, the hardware should still be adequate and supported. However you are right. No this is not an "optimus" system, Dell XPS with 3D. On a side note, my firewall sent an alert that a file was an infection during the install. it was a game file. I will place this in the allowed list, then reinstall the game. Might be the cause.....might not (since this occurs VERY early in the game running) &nbs

I have tried using the CPU, the GPU, and the "automatically choose" within the NVIDIA control panel. I have set each of these settings and tested one at a time both as a global configuration and for the ashes exe specifically. The results are the same. I am considering a rollback to 7 in order to try this but would prefer not to.

------------------ System Information ------------------ Time of this report: 8/21/2015, 22:02:56 Machine name:***Edited Out**** Operating System: Windows 10 Pro 64-bit (10.0, Build 10240) (10240.th1.150810-2333) La

either version. However when using 12 I get a white screen for 5 seconds then back to the desktop. I get further with 11, but never into any game play. I also failed to mention that I ensured my graphics driver was up to date due to the error.

I am unable to start the actual game play. I can starts the game, select single player, and select skirmish. Once the game attempts to load the game shuts down entirely and NVIDI Windows Kernal failure code 355. I am running windows 10 64 bit, with NVIDIA Geforce 555M. I purchased the founders edition with lifetime, yet I haven't been able to play once.