|
batek688 -> Update on my crashes (12/28/2014 2:53:33 PM)
|
As I promised, I started looking at things on multiple systems. My desktop is the machine where i'd sent in the plethora of crash reports. The second machine is my laptop. I won't get into machine specifics in this post; however, I wanted to share some interesting info in advance.
Rather than re-install, I copied from desktop to laptop and on both I launch by double clicking on "command.exe." For both, I set the game settings/options identically and select the same scenario (the big stick). One at a time, I toggle to run 1:1 and let run for 60 seconds so the initial map drawing is setup after which I pause. I then select the US CVBG and use "F1" to strike all targets on the coastline. I then select the SSGN to the west and repeat.
With both machines now "set" and running no apps other than whatever background stuff was installed (no browsers going/etc), I start up the windows task manager and lock onto command.exe in the process tree and then set both back to run at 15 second accel. They run at different speeds at this point since the CPUs and hardware are different performance (desktop is a 6 core FX chip from 3 years ago and laptop is a 1st gen AMD A8).
Watching peak working set (PWS), the desktop PWS value for command is 150-200k higher than the laptop. Laptop is sitting around 667k and desktop at 790k as the tomahawks fly over open ocean. As they get close enough to start detecting and the Syrians to launch SA-5s the desktop PWS shoots up into the mid-high 900s (957-990k) while the laptop rises to 740-5k. As the t-hawks hit, desktop crashes out of memory. Laptop runs happy as a clam with PWS never getting into the 800ks.
Clearly the out of memory crashes, blank screen with red X, etc. which I (and others) have reported is due to something underlying like a device driver/directX thing. I have a couple other things I want to try first after which I will send you just the "delta" of the configurations and perhaps others in the community with similar problems and diversity in configurations can help narrow down to which drivers/external components are the culprit and we can then beat up on the vendors rather than you guys so the only thing crummy is your shirt after eating cookies (reference to line by Mikmyk in the specify refueling tanker thread).
Happy holidays.
Bill
|
|
|
|
