[B460] Error on startup: Unable to create the Direct3D m_Device3d

[gdir]

Hi,

I'm running B460 on a Dell XPS 15 (L502x) laptop with Win7 x64. The laptop has a nVidia Optimus configuration with an Intel HD Graphics 3000 and a nVidia GeForce GT540M. The command.exe is set up to use the nVidia graphics.

Since B460 I have got two times an error message on startup. The error message appears after the splash screen when the main window should be displayed. It only happened twice, while at least 10 startups were successful. I don't recognize a pattern when or why this happens. I have attached ascreen shot. More attachments in the next posts.

For me this is low priority problem.

[gdir]

Next image:

[gdir]

Content of the problem signature:

[thewood1]

I have exactly the same issue until I rebooted my system. I usually sleep my system and it took a reboot for this to stop.

[gdir]

Finally, the dxdiag file. I guess it's rather useless because it shows only the information about the Intel graphics while Command is started with the nVidia graphics. I tried to force dxdiag.exe to run with the nVidia graphics, but that setting is ignored.

[gdir]

ORIGINAL: thewood1

I have exactly the same issue until I rebooted my system. I usually sleep my system and it took a reboot for this to stop.

Yes, similiar here. I reboot rarely and usually put my system only into hibernation. When the error appeared for the first time I rebooted the system. After that I could start Command.

Today the error appeared for the second time again after waking from hibernation. But after taking the screen shots, running dxdiag.exe and looking after some settings in the nVidia configuration window, I suddenly was able to start Command without rebooting.

And I have run it several times after waking up from hibernation without any problems. I have no clue when or why this happens.

[thewood1]

I have found Command very touchy with Sleep or Hibernation. I have stopped playing it if it was up when my PC went to sleep. I make sure to close it down and restart it. I have a couple programs like that.

[Anathema]

Exact same error here with the same dialog appearing. Dxdiag attached.

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: command.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 527e4197
Problem Signature 04: Microsoft.DirectX.Direct3DX
Problem Signature 05: 9.12.589.0
Problem Signature 06: 442d82b0
Problem Signature 07: a40
Problem Signature 08: c
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 3081
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

[Anathema]

Reboot doesn't fix it either.

[Plodder]

Same error here as well.Also intermittent. Dxdiag attached.

[mikmykWS]

Logged. We'll take a look.

Thanks guys for the reports!

Mike

[Anathema]

Still getting the same error with build 469.

[Dimitris]

ORIGINAL: Anathema
Still getting the same error with build 469.

Consistently? Intermittently?

[gdir]

Hi Sunburn,

I have the same issue with B469 as I had with B460. The error message looks slightly different, but I think it's still the same problem. In most cases the first attempt to start Command after waking up from hibernation throws this error. The next attempt to start is successful in most cases.

[gdir]

Entries from the Windows application log:

Anwendung: Command.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund eines Ausnahmefehlers beendet.
Ausnahmeinformationen: System.NullReferenceException
Stapel:
bei Microsoft.DirectX.Direct3D.Font.OnLostDevice()
bei Microsoft.DirectX.Direct3D.Font.OnParentLost(System.Object, System.EventArgs)
bei System.EventHandler.Invoke(System.Object, System.EventArgs)
bei Microsoft.DirectX.Direct3D.Device.raise_DeviceLost(System.Object, System.EventArgs)
bei Microsoft.DirectX.Direct3D.Device.Finalize()



Name der fehlerhaften Anwendung: Command.exe, Version: 1.0.0.0, Zeitstempel: 0x52986a7b
Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x136c9228
ID des fehlerhaften Prozesses: 0x18ec
Startzeit der fehlerhaften Anwendung: 0x01cef0c7621b86b3
Pfad der fehlerhaften Anwendung: C:\Matrix Games\Command Modern Air Naval Operations\Command.exe
Pfad des fehlerhaften Moduls: unknown
Berichtskennung: b38de98a-5cba-11e3-b998-028037ec0200

[Anathema]

ORIGINAL: Sunburn

ORIGINAL: Anathema
Still getting the same error with build 469.

Consistently? Intermittently?

I had it consistently with 460 and couldn't get it to run apart from a couple of times, 469 has worked without problem until now, but I am experiencing the problem consistently again with 469 and haven't been able to get it to run successfully since it first appeared. The dialog seems to be slightly differently as seen in the more recent screenshots, with non-alpahbetical characters and ascii garbage mostly, although you can still make out enough to see it is the same dialog with the reference to direct3D and worldwind files that has somehow been scrambled. It is also the same problem signatures and event.

I haven't made any changes at all to my system, apart from installing the 469 release.

[thewood1]

I have found that any directx games I use have issues coming out of sleep/hibernation. Not sure if this is related.

btw, I haven't had the issue since 469.

[Anathema]

I have a desktop PC that has the power settings set to never sleep/hibernate and issue occurs after reboot/restart as well.

[Anathema]

Still occurs with build 474 and have not been able to get it to start succesfully yet. An example of the dialog is attached.

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: command.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 52a0bd14
Problem Signature 04: Microsoft.DirectX.Direct3DX
Problem Signature 05: 9.12.589.0
Problem Signature 06: 442d82b0
Problem Signature 07: a40
Problem Signature 08: c
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 3081
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

[Dimitris]

ORIGINAL: Anathema

Still occurs with build 474 and have not been able to get it to start succesfully yet. An example of the dialog is attached.

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: command.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 52a0bd14
Problem Signature 04: Microsoft.DirectX.Direct3DX
Problem Signature 05: 9.12.589.0
Problem Signature 06: 442d82b0
Problem Signature 07: a40
Problem Signature 08: c
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 3081
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Can you please re-install the Direct-X component from the \PreRequisites folder?