INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Error drawing using Direct3D (device lost)  (Read 3240 times)

Kevmoso

  • Recent member
  • *
  • Posts: 7
Error drawing using Direct3D (device lost)
« on: April 02, 2018, 02:16:58 pm »

Greetings all,

I have seen similar situations posted with no real resolutions found.

JRiver had always worked fine in theater mode on my HTPC until the Fall update to Windows 10.
I cannot roll back out of this update as I did a fresh install after the problems started in an attempt to fix things.
After Fall update JRiver theater mode blanks out and tells me "Error drawing using Direct3D (device lost)"
After this error my video card (onboard intel HD 530 with multiple driver versions tried) reports "Windows has stopped this device because it has reported problems. (Code 43)"
I can then restart the machine or use device manager to disable/enable the video card to eliminate the code 43.

Two scenarios avoid the whole problem:

1. Setting the HTPC video resolution to 720p. I prefer to run the video at 1080i (Sony 34XBR960 CRT tv) but at 1080i Theater mode borks out (breaks everything).

2. While accessing the HTPC with VNC everything behaves normally regardless of resolution setting. No device lost and no code 43 occurs.
I don't even need to use the HTPC through VNC, simply having VNC active and using the HTPC as usual works fine.

This all applies to 64 and 32 bit JRiver versions.

Other softwares that can be used with no problems:
Zoomplayer Max 12.7
PowerDVD Ultra 16
Winamp 5.66 (still whipping the llamas ass)
Kodi 17.6
Eventghost listening to usbuirt to control everything.

I LOVE JRiver Theater mode on my HTPC and hope to be able to fix this problem especially since I already purchased the JRiver version 24 prerelease.

Any ideas or suggestions would be most welcomed.
Thanks for reading.
Logged

muzicman0

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1239
Re: Error drawing using Direct3D (device lost)
« Reply #1 on: April 02, 2018, 06:25:41 pm »

apologies for the simplistic suggestion, but have you tried replacing the cable?  When you have a VNC connection, there is a virtual display attached to the PC (oversimplification), but that may be what is keeping the disconnects from happening.  The lower resolution requires lower bandwidth in the HDMI connection, so that could be why it works.  I know you mentioned other software seems to work, but I think it would still be worth trying.
Logged

tij

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1563
Re: Error drawing using Direct3D (device lost)
« Reply #2 on: April 02, 2018, 08:24:30 pm »

 using OpenGL with theatre view?
Logged
HTPC: Win11 Pro, MC: latest 31(64b), NV Driver: v425.31, CPU: i9-12900K, 32GB RAM, GeForce: 2080ti
Screen: LG 2016 E6
NAS: FreeNAS 11.1, SuperMicro SSG-5048R-E1CR36L, E5-1620v4, 64GB ECC RAM, 18xUltrastar He12-SAS3 drives, 2x240GB SSD (OS)

Kevmoso

  • Recent member
  • *
  • Posts: 7
Re: Error drawing using Direct3D (device lost)
« Reply #3 on: April 03, 2018, 06:34:49 pm »

apologies for the simplistic suggestion, but have you tried replacing the cable?  When you have a VNC connection, there is a virtual display attached to the PC (oversimplification), but that may be what is keeping the disconnects from happening.  The lower resolution requires lower bandwidth in the HDMI connection, so that could be why it works.  I know you mentioned other software seems to work, but I think it would still be worth trying.


No apologies needed! I didn't even think of trying this. I love simple solutions but alas in this case it didn't work. I have five hdmi cables of varying qualities, six if you include an hdmi to dvi cable connected to a dvi to hdmi adapter. All combinations result in the same problem.

Which leads me to:

using OpenGL with theatre view?

I had tried this before my reinstall of windows and it just caused JRiver to crash all together (had to ctrl-shift-esc, kill and then uninstall to fix that). Because of that I didn't think to try it again after reinstalling everything.
Trying it now and IT IS WORKING! Thank you for suggesting this tij. It looks like it's going to hold. Multiple launches/closes and fiddling about and she is still working.

Makes me wonder what advantages or disadvantages there are to opengl and why it is labeled experimental?
Logged

tij

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1563
Re: Error drawing using Direct3D (device lost)
« Reply #4 on: April 04, 2018, 12:35:01 am »

eventually I think they will replace it with OpenGL (read it somewhere don't remember where) ... then implementation of Theatre View will be uniform across platforms (aka Linux and osx) ... and developers only have to maintain one code

developers constantly improving OpenGL ... so problem might have been fix for some time ago after your initial bad encounter with it (non OpenGL Theatre View is probably getting neglected atm lol)
Logged
HTPC: Win11 Pro, MC: latest 31(64b), NV Driver: v425.31, CPU: i9-12900K, 32GB RAM, GeForce: 2080ti
Screen: LG 2016 E6
NAS: FreeNAS 11.1, SuperMicro SSG-5048R-E1CR36L, E5-1620v4, 64GB ECC RAM, 18xUltrastar He12-SAS3 drives, 2x240GB SSD (OS)

Kevmoso

  • Recent member
  • *
  • Posts: 7
Re: Error drawing using Direct3D (device lost)
« Reply #5 on: April 11, 2018, 03:56:12 pm »

I have spoken too soon...

JRiver has stopped working again to the point that I will have to uninstall/reinstall to fix it.
Right now I have it set to launch into opengl theater mode and it simply crashes.
I cannot even ctrl1 to get back to standard mode.
This sucks...

Is there anything else I can do here to get this working?
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72536
  • Where did I put my teeth?
Re: Error drawing using Direct3D (device lost)
« Reply #6 on: April 11, 2018, 04:53:03 pm »

Video driver problem?  Theater View uses 3D drawing, and that's not common in other programs.
Logged

Kevmoso

  • Recent member
  • *
  • Posts: 7
Re: Error drawing using Direct3D (device lost)
« Reply #7 on: April 11, 2018, 05:11:29 pm »

Video driver problem?  Theater View uses 3D drawing, and that's not common in other programs.

I believe this may be so. I've tried every driver version that there is for this onboard chip and have no room for a proper graphics card.
How can I test this in such a way that Intel can be made to fix the driver? lol!
It all fell apart after the windows fall creators update. Maybe hold Microsoft liable? HAH!


Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72536
  • Where did I put my teeth?
Re: Error drawing using Direct3D (device lost)
« Reply #8 on: April 11, 2018, 05:28:44 pm »

Did you try an Internet search for similar problems?

Usually, when a driver is broken, an earlier version will work.

Drivers can be available both through Microsoft and direct from the manufacturer. 
Logged

Kevmoso

  • Recent member
  • *
  • Posts: 7
Re: Error drawing using Direct3D (device lost)
« Reply #9 on: April 12, 2018, 05:25:37 am »

Did you try an Internet search for similar problems?

Usually, when a driver is broken, an earlier version will work.

Drivers can be available both through Microsoft and direct from the manufacturer.

Lots of internet searches.
Lots of earlier drivers from Asrock Intel and Microsoft.

As far as I can tell, JRiver is simply incompatible with the fall creators version of Windows 10.
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7887
  • Long cold Winter...
Re: Error drawing using Direct3D (device lost)
« Reply #10 on: April 12, 2018, 05:51:10 am »

As far as I can tell, JRiver is simply incompatible with the fall creators version of Windows 10.

Likely it's an issue with the Fall Creators Update itself. It caused all kinds of different issues (not JRiver related) - hopefully the "Spring Creators Update" or whatever it ends up being called solves some of those issues, but I wouldn't hold my breath on it. From what I've read on these forums from users already running it, it's caused new issues. You're using the Intel onboard graphics, correct? Which CPU are you using? Some details about the hardware in your HTPC would probably help.

Random thought, have you tried installing the DirectX 9.0c end-user runtime (assuming MC uses this) and see if that makes any difference (obviously disable OpenGL Theater View)?
Logged
I don't work for JRiver... I help keep the forums safe from "male enhancements" and other sources of sketchy pharmaceuticals.

Windows 11 24H2 Update 64-bit + Ubuntu 24.10 Oracular Oriole 64-bit | Windows 11 24H2 Update 64-bit (Intel N305 Fanless NUC 16GB RAM/500GB M.2 NVMe SSD)
JRiver Media Center 33 (Windows + Linux) | iFi ZEN DAC 3 | JBL 306P MkII Studio Monitors | Audio-Technica ATH-M50x Headphones

Kevmoso

  • Recent member
  • *
  • Posts: 7
Re: Error drawing using Direct3D (device lost)
« Reply #11 on: April 12, 2018, 06:24:10 am »

Likely it's an issue with the Fall Creators Update itself. It caused all kinds of different issues (not JRiver related) - hopefully the "Spring Creators Update" or whatever it ends up being called solves some of those issues, but I wouldn't hold my breath on it. From what I've read on these forums from users already running it, it's caused new issues. You're using the Intel onboard graphics, correct? Which CPU are you using? Some details about the hardware in your HTPC would probably help.

Random thought, have you tried installing the DirectX 9.0c end-user runtime (assuming MC uses this) and see if that makes any difference (obviously disable OpenGL Theater View)?

Good point hardware info.
Motherboard is Asrock fatal1ty z170 gaming - itx
Cpu intel core i5 6400t no overclock
Gskill memory 16gb (unsure model. Is on the asrock list of compatible modules)
All sitting in a Streacom FC5 (I love this case)

Crossing fingers on the spring creator update.
Logged

Kevmoso

  • Recent member
  • *
  • Posts: 7
Re: Error drawing using Direct3D (device lost)
« Reply #12 on: April 16, 2018, 09:03:01 am »

Fwiw
Couldn't wait for spring update.
Did a fresh windows 10 1703 install.
Problem fixed.
Logged
Pages: [1]   Go Up