home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
Changing to Full HD causes crash of Video Driver
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Bernie_W" data-source="post: 1249246" data-attributes="member: 158775"><p>Hi Sebastii,</p><p></p><p>just wanted to share my further findings. I bought a new GPU and added it, but no luck, driver crashed again. The I reinstalled Win 10 (of course creating an image first) with version 1803 and reinstalled 1.20. Still no luck. Still 720 worked, but 1080 crashed the GPU driver. Of course I tested different driver versions for the new GPU, but taking the driver through windows update nor the nvidia driver solved the issue.</p><p>Final test was to install an older version of windows - in my case 1703 which worked in the past - and suddenly all was fine! Crazy.</p><p></p><p>I guess windows changed something concerning the detection of the connected display (in my case the Sony AV receiver connected to a TV). When set to 1080, it seems that windows was not really able to find the attached display and ended up thinking there is no display (maybe a timeout or something that could possibly changed in MP to give it more time?). We saw some indication in the log file where there were some entries looking for \\DISPLAY 8 or others. I had tried of course all possible settings like v-sync, 3D settings etc.</p><p>But only changing back to old windows and disabling all these updates solved the issue.</p><p></p><p>Interesting is also that I have a second PC (same mainboard, just different GPU, also Intel Skylake) connected to a normal PC monitor works flawless with 1.20 and 1803 (latest updates).</p><p>So my conclusion would carefully be that the AV receiver causes some faulty reply to the display driver or takes simply too long to switch "something" which causes the driver to crash. Not sure this helps you anyhow for the development. Just wanted to share this.</p></blockquote><p></p>
[QUOTE="Bernie_W, post: 1249246, member: 158775"] Hi Sebastii, just wanted to share my further findings. I bought a new GPU and added it, but no luck, driver crashed again. The I reinstalled Win 10 (of course creating an image first) with version 1803 and reinstalled 1.20. Still no luck. Still 720 worked, but 1080 crashed the GPU driver. Of course I tested different driver versions for the new GPU, but taking the driver through windows update nor the nvidia driver solved the issue. Final test was to install an older version of windows - in my case 1703 which worked in the past - and suddenly all was fine! Crazy. I guess windows changed something concerning the detection of the connected display (in my case the Sony AV receiver connected to a TV). When set to 1080, it seems that windows was not really able to find the attached display and ended up thinking there is no display (maybe a timeout or something that could possibly changed in MP to give it more time?). We saw some indication in the log file where there were some entries looking for \\DISPLAY 8 or others. I had tried of course all possible settings like v-sync, 3D settings etc. But only changing back to old windows and disabling all these updates solved the issue. Interesting is also that I have a second PC (same mainboard, just different GPU, also Intel Skylake) connected to a normal PC monitor works flawless with 1.20 and 1803 (latest updates). So my conclusion would carefully be that the AV receiver causes some faulty reply to the display driver or takes simply too long to switch "something" which causes the driver to crash. Not sure this helps you anyhow for the development. Just wanted to share this. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Changing to Full HD causes crash of Video Driver
Contact us
RSS
Top
Bottom