D3DError - CreateDevice failed: D3DERR_DEVICELOST

[Sir Tawmis]

Not sure if you answered (I may have missed it?) - that if you change the options to Windowed Mode (rather than Full Screen or Borderless) does it still happen?

Digging around, I found a few sites:
http://msdn.microsoft.com/en-us/library ... 85%29.aspx

One thing - in your config - it says:
resolution = "1920 x 1080"

Is that your native screen resolution? If not, change the size settings to your native screen resolution. See if that works?

[mindragon73]

Hi!

Well, I´ve tried changing the displayMode from 1 to 2 and to 3, but that gives me a "D3DError - D3DXXompileShader failed: ERROR_BAD_EXE_FORMAT".
DisplayMode 1 gives the original error: "D3DError - CreateDevice failed: D3DERR_DEVICELOST"

My native (and recommended) resolution is 1920 x 1080.
Thanks for the link!
I didn´t really understand all of it, but it seems like (and judging by the comments) the site doesn´t really give anwers as to how to solve the problems.

[Dr.Disaster]

Well at least we got a new error messages

MS says this about ERROR_BAD_EXE_FORMAT:

The most common problems with 32-bit applications on 64-bit Windows involve image mismatch. An image mismatch occurs when a 64-bit process tries to load a 32-bit DLL or a 32-bit process tries to load a 64-bit DLL. Image mismatch errors that cause a worker process to fail during startup are logged in the Windows Events log as 0xC1: ERROR_BAD_EXE_FORMAT. Image mismatch errors that do not cause the worker process to fail during startup are logged in the IIS log files as Win32 error 0xC1: ERROR_BAD_EXE_FORMAT.

followed by some ramblings about IIS

LoG2 is a 32-bit application running on your 64-bit Windows and for some strange reason your system goes for the 64-bit DirectX libraries while LoG2 has to call their 32-bit versions.

Does "dxdiag" give you any errors in the 32 bit part?

[mindragon73]

Hi again!

I´ve run DXDIAG a couple of times, and it says that everything is ok.
But, there could very well be problems anyway I guess, so
I put the full info on pastebin.

http://pastebin.com/LStnTN94 (32-bit)
and
http://pastebin.com/D0SwDvAp (64-bit)

I´m thinking that perhaps I somehow have a faulty dll-file somewhere. Maybe a 32-bit version of a 64-bit file or something like that?
As I recall it that was the case with Ethan Carter, as I mentioned earlier in the thread.

If I run Dependency Walker (http://www.dependencywalker.com/) ,just like I was told to to when I had the Ethan Carter-problems, it seems to find a lot of problematic 64-bit dll-files.
At least if I understand the program correctly, which I´m not at all sure I do. There are a lot of files marked with red anyway.
I can´t however find a way to export/save the results from that program.