Command Crash at Start-up

Post bug reports and ask for game support here.

Moderator: MOD_Command

Post Reply
Sigma8510
Posts: 91
Joined: Sat Apr 15, 2006 3:26 am

Command Crash at Start-up

Post by Sigma8510 »

Not sure what has changed, but Command crashes immediately on the splash screen on every attempt to run the game. This did not happen as recently as a week and a half ago. I am not aware of any major changes on my system other than updating to the latest Nvidia drivers(388.43) for my GTX1080. Running Windows 10 Creators Update.

In the effort to troubleshoot, I completely uninstalled CMANO, including following all the steps in post #7 here:

tm.asp?m=4165203&mpage=1&key=reinstall�

No joy. Game crashes at start-up every time even with a fresh install. Hoping not to have to go back to a restore point.

I am at a total loss now as to what to do next. Appreciate any assistance in figuring out what is going on with my install.

Thanks!!

Dimitris
Posts: 15420
Joined: Sun Jul 31, 2005 10:29 am
Contact:

RE: Command Crash at Start-up

Post by Dimitris »

This is strange indeed.

Is the Event Viewer telling anything ?
Sigma8510
Posts: 91
Joined: Sat Apr 15, 2006 3:26 am

RE: Command Crash at Start-up

Post by Sigma8510 »

ORIGINAL: Dimitris

This is strange indeed.

Is the Event Viewer telling anything ?

Didn't think of that. Here is an entry from the latest start attempt:

Faulting application name: Command.exe, version: 1.0.0.0, time stamp: 0x591977f3
Faulting module name: d3d9.dll, version: 10.0.16299.98, time stamp: 0xe2fbf0fc
Exception code: 0xc0000096
Fault offset: 0x000481d1
Faulting process id: 0x2be8
Faulting application start time: 0x01d371d993431dc3
Faulting application path: B:\Matrix Games\Command Wargame of the Year Edition\Command.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll
Report Id: fbe26f48-baaf-4cda-8c09-c1ff7436141e
Faulting package full name:
Faulting package-relative application ID:
Sigma8510
Posts: 91
Joined: Sat Apr 15, 2006 3:26 am

RE: Command Crash at Start-up

Post by Sigma8510 »

ORIGINAL: jbaxter1964

ORIGINAL: Dimitris

This is strange indeed.

Is the Event Viewer telling anything ?

Didn't think of that. Here is an entry from the latest start attempt:

Faulting application name: Command.exe, version: 1.0.0.0, time stamp: 0x591977f3
Faulting module name: d3d9.dll, version: 10.0.16299.98, time stamp: 0xe2fbf0fc
Exception code: 0xc0000096
Fault offset: 0x000481d1
Faulting process id: 0x2be8
Faulting application start time: 0x01d371d993431dc3
Faulting application path: B:\Matrix Games\Command Wargame of the Year Edition\Command.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll
Report Id: fbe26f48-baaf-4cda-8c09-c1ff7436141e
Faulting package full name:
Faulting package-relative application ID:

.dll issue?
Dimitris
Posts: 15420
Joined: Sun Jul 31, 2005 10:29 am
Contact:

RE: Command Crash at Start-up

Post by Dimitris »

This line:
Faulting module name: d3d9.dll, version: 10.0.16299.98, time stamp: 0xe2fbf0fc

...suggests a possible issue with DirectX. Command currently uses DirectX 9.0, and the new graphics drivers may have messed up something.

Can you manually re-install the DX redistributable? (It should be in the \PrRequisites folder).
Sigma8510
Posts: 91
Joined: Sat Apr 15, 2006 3:26 am

RE: Command Crash at Start-up

Post by Sigma8510 »

Re-installed DX from pre-req folder. No change: Event Viewer results:

Faulting application name: Command.exe, version: 1.0.0.0, time stamp: 0x591977f3
Faulting module name: d3d9.dll, version: 10.0.16299.98, time stamp: 0xe2fbf0fc
Exception code: 0xc0000096
Fault offset: 0x000481d1
Faulting process id: 0x508
Faulting application start time: 0x01d371fa21fc113e
Faulting application path: B:\Matrix Games\Command Wargame of the Year Edition\Command.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d9.dll
Report Id: e2f99ac0-2026-4bba-a48c-816df1eed634
Faulting package full name:
Faulting package-relative application ID:

d3d9.dll file is present in the faulty module path folder referred to. Not sure if the file is corrupt somehow. Could try deleting it and re-installing? Or try rolling back Nvidia driver?
RoryAndersonCDT
Posts: 1828
Joined: Mon Jun 15, 2009 11:45 pm

RE: Command Crash at Start-up

Post by RoryAndersonCDT »

Do you have Corsair CUE or Raptr running in your application tray? Could be some other program on your computer interfering with direct x.
Command Dev Team
Technical Lead
Sigma8510
Posts: 91
Joined: Sat Apr 15, 2006 3:26 am

RE: Command Crash at Start-up

Post by Sigma8510 »

ORIGINAL: Baloogan

Do you have Corsair CUE or Raptr running in your application tray? Could be some other program on your computer interfering with direct x.

Neither one. Going to try deleting the .dll and will report back.
Sigma8510
Posts: 91
Joined: Sat Apr 15, 2006 3:26 am

RE: Command Crash at Start-up

Post by Sigma8510 »

ORIGINAL: jbaxter1964

ORIGINAL: Baloogan

Do you have Corsair CUE or Raptr running in your application tray? Could be some other program on your computer interfering with direct x.

Neither one. Going to try deleting the .dll and will report back.

System will not let me delete the file. Anyone know how to uninstall DX 9.0c?
mikmykWS
Posts: 7185
Joined: Tue Mar 22, 2005 4:34 pm

RE: Command Crash at Start-up

Post by mikmykWS »

Hi

Before you make any big changes to your OS or DX could you work the list below? You might have done some of these but want to make sure the easy stuff is covered before the hammer is brought out.

1. Can you verify that you've run this file B:\Matrix Games\Command Wargame of the Year Edition\PreRequisites\directx_June2010_redist\DXSETUP.exe ? If you haven't give it a run.
2. If you applied any manual updates have you pointed the installer at the correct directory? B:\Matrix Games\Command Wargame of the Year Edition\ instead of the default one which is C:
3. Does the game start if you run Command.exe from the Command folder instead of the shortcut? If it works and the shortcut launcher doesn't its good evidence of #2.
4. Have you been faithful to Windows updates? If not please do.
5. Driver updates?
6. Are you employing any overlay or recording/streaming software of any sort that you can think of?

Hope this helps!

Mike
Sigma8510
Posts: 91
Joined: Sat Apr 15, 2006 3:26 am

RE: Command Crash at Start-up

Post by Sigma8510 »

ORIGINAL: mikmykWS

Hi

Before you make any big changes to your OS or DX could you work the list below? You might have done some of these but want to make sure the easy stuff is covered before the hammer is brought out.

1. Can you verify that you've run this file B:\Matrix Games\Command Wargame of the Year Edition\PreRequisites\directx_June2010_redist\DXSETUP.exe ? If you haven't give it a run.
2. If you applied any manual updates have you pointed the installer at the correct directory? B:\Matrix Games\Command Wargame of the Year Edition\ instead of the default one which is C:
3. Does the game start if you run Command.exe from the Command folder instead of the shortcut? If it works and the shortcut launcher doesn't its good evidence of #2.
4. Have you been faithful to Windows updates? If not please do.
5. Driver updates?
6. Are you employing any overlay or recording/streaming software of any sort that you can think of?

Hope this helps!

Mike
Mike,
As always, you have come through with very helpful recommendations when I am about to tear out what little hair I have trying to figure this out. At my day job right now, but will work this list when I get to the house and report back.

Thank you!!
Sigma8510
Posts: 91
Joined: Sat Apr 15, 2006 3:26 am

RE: Command Crash at Start-up

Post by Sigma8510 »

Mike,
Appreciate the steers, but my compulsion to research this issue as I watched the clock for quitting time got the best of me. It appears your question at step 6, and Baloogan's question were on the right track. After many Google searches, I came across this:

http://www.tomshardware.com/answers/id- ... error.html

The thing that got me was the Afterburner and RivaTuner references, which is exactly what I am running to OC my GPU. Turns out adding the Command.exe to the application list in RivaTuner and setting detection to None fixed my issue. I now can run Afterburner and run Command with no problems. The funny thing is, I have been running this configuration for at least a year with no issues. Something changed recently (maybe the Nvidia drivers or some update with Afterburner/RivaTuner), but either way, I don't care. I am BACK!!!!
Post Reply

Return to “Tech Support”