Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[BrianS]

Hello,

As of yesterday my previously trouble free installation of build 18.0.195 will no longer successfully launch the Theater View GUI. I receive the "Error starting Direct3D engine (error creating Direct3D device (0x8876086C)) notification discussed in a few threads over the years. I installed no updates of any kind prior to receiving the error. That said, the core problem lies within my Win7 x64 OS, not JRiver. I verified this via a complete uninstall, reboot and reinstall of JRiver. A clean install generates the same error message when attempting to launch Theater View.

I have been unable to track down the culprit for this error. So far, I've:

Verified the expected D3Dxx.dll files reside in the System32 directory.

Verified there are no reported DirectX errors via the dxdiag tool.

Reinstalled DirectX11.

Reinstalled the ATI Catalyst video driver that I had been using with success.

Updated the ATI driver to the latest build.

I'm open to additional suggestions.

Thanks, folks.

Brian

[RussellS]

Hi, I've got pretty much the same problem. This is on my Media Center server which doesn't normally get used as a client but just as a server. Therefore the only time I go into TheaterView on it is to test the views and to check that season posters are working ok.

The last time I used Theaterview on the server was a few weeks ago and it was working fine then. However, now Theaterview won't launch and posts the same error as Brian: "Error starting Direct3D engine (error creating Direct3D device (0x8876086C))". I've tried all the same things as Brian but to no avail. The only difference between mine & Brian's is that I'm running Windows Server 2008 R2 x64.

Any suggestions as to what could be causing this.


#Brian: Did you manage to get yours sorted and if so how.


Many thanks

[JimH]

Try 18.0.211:
http://yabb.jriver.com/interact/index.php?topic=82271.0

A fix for XP 3D was in build 206.

[BrianS]

Russell,

No, I have not found a solution yet. Build 193 works fine. Any build after 193, including 211, generates the error. I've chalked it up to some subtle conflict within my build as the phenomenon does not appear to be widespread. In the rare event I want to use Theatre View, a quick temporary install of build 193 is effortless.

Brian

[RussellS]

Try 18.0.211:
http://yabb.jriver.com/interact/index.php?topic=82271.0

A fix for XP 3D was in build 206.

Thanks for the reply Jim. Unfortunately I have updated to build 211 and I still have the problem.

Russell,

No, I have not found a solution yet. Build 193 works fine. Any build after 193, including 211, generates the error. I've chalked it up to some subtle conflict within my build as the phenomenon does not appear to be widespread. In the rare event I want to use Theatre View, a quick temporary install of build 193 is effortless.

Brian

That's interesting Brian. I may try going back to build 193 to test.

[JimH]

What OS?

[RussellS]

I can now confirm what Brian said. I didn't have build 193 to try but I have just installed build 189 and Theaterview works fine. So it does appear that the later builds have some problem with both mine & Brians configuration.

I've tried reinstalling the video drivers & DirectX to no avail.


(I'm running Windows Server 2008 R2 X64)

[BrianS]

I am running Windows 7 x64.