Driver Samsung Monitor
Bridgette Kubis
I've been running a 2 screen setup on an Nvidia card for a while but a few days ago had to give it up for a family member. I don't play games, so I thought I can still use my on CPU graphics to power my 2 screens. Nope, that didn't work out. Until Windows 10 loads up, I have 2 screens working but when Intel drivers kick in (latest installed) I lose my Samsung s24d330h monitor. I've established that it is not about a faulty cable or the wrong socket. Once Windows 10 loads my Samsung monitor is simply not recognised beyond a PNP monitor. The computer can clearly feel that monitor but Intel drivers can't do something that works for the other monitor.
Please attach the Intel Graphics and SSU report so we can verify further details about the components in your platform, please check all the options in the report including the one that says "3rd party software logs":
The monitor was not use on this computer without an Nvidia card. It was used on that and then I tried the inbuilt GPU. The monitor still works on this computer in both video ports up until the moment that Windows starts.
Based on the information showing in the SSU report, as you mentioned, currently the graphics driver version installed on your computer is 30.0.100.9684, which is the latest Intel graphics driver version we have available on our website:
I looked in ASUS's website, and the latest graphics driver version they have available tested and validated by them as the proper one for your system is 26.20.100.6952. Using the monitor that works after booting to Windows*, please try a clean installation of that graphics driver following the instructions in the links below:
I also check on Samsung's website if there might be a driver that the Samsung monitor may need to be recognized beyond a "PNP monitor", and actually there is one, using again the monitor that works, please try to install that driver on your machine. Scroll down at the bottom of the page to where it says "Manual Download", it is the second file listed in there:
Well, this didn't work either. I've done the BIOS, downgraded the VGA driver, installed the Samsung monitor driver but this didn't revive my monitor in Windows. Just as before it stops working when Windows loads up.
There seems to be a driver bug that usually hits Monitors that only support DP1.2. With this bug it help to set the monitor to 30 Hz (with the help of another monitor) maybe this helps in this case to.
We noticed that you mentioned, "have tried connecting via the HDMI and DVI (with an adapter)". Just to make sure regarding HDMI*, did you mean you tested using a straight-through connection HDMI-to-HDM with a single cable and an HDMI connector on both sides of the cable? (meaning no video adapters or converters for HDMI?). Please let us know the outcome.
In addition, we would like to inform you that we have released a new version of the graphics driver. Please perform a Clean Installation of Intel Graphics Drivers in Windows* using Intel Graphics DHC driver Version 30.0.100.9805 (Latest). During the process, please make sure all steps are followed, including disconnecting from the Internet and making sure you get to the Microsoft Basic Display Adapter before trying to install the graphics driver.
Hi, the HDMI to DVI adapter is nothing more than a basic port shape changer. I have also mentioned that using a DVI to DVI cable also makes no difference. I did also mention that I have 2 monitors and I have switched them around the connectors. The problem with Samsung monitor follows it on different ports and cables. Just to reiterate (since I'm at it now), the Samsung monitor is working fine on another computer and also on this computer up until the moment that Windows 10 starts and drivers kick in.
There is an unexpected twist though... I now have frequent mouse cursor choppy moves. It is as it it freezes for a fraction of a second before carries on moving. This seems to coincide with HDD activity. Hmm... Should I start a new thread?
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
After that, I've rebooted and installed drivers using EXE-installer downloaded from the link you provided. As I understand, before the driver installation was finished, Windows 10 has managed to install driver by her own. However, after that Intel installer has finished the installation succesfully.
I've looked throug the monitor manual, but it looks like the recommended option of changing resolution is "Open Control Panel, open Display settings, change resolution" - which is not working in my case. Is there any other option?
Ivan, do you have any idea why the image is broken (shown in the last picture of the first message of this thread) every time when I select the "Center" scaling option in Intel HD Graphics control tool? Any piece of advice would be highly appreciated.
However, I'm curious about one thing regarding scaling options. According to the monitor "Information" window (it is displayed by the monitor itself, not transmitted through cable), now it is working with such parameters: "55.9kHz 60Hz NP 1440x900". I believe that if the problem was in low bandwidth of the cable, then I would have trouble with higher resolutions. But the image is broken even if I try to select "Center" scaling at 1024x768 resolution.
I am very surprised by the fact that the cable appears to cause the problem. I was sure that it cannot be the source of this problem, but with the old cable I can reproduce the problem, and with the new cable everything is fine. So the evidence is unbeatable.)
So, to best explain: I have bought a new monitor on September 3rd (Samsung Odyssey Neo G7), and roughly a pair of days after I started using it, the driver timeouts began. At first I thought it was GPU OC-related, but troubleshooting, research, and the causes for the issues began putting a target on the HW Acceleration on my browser (and presumedly, anything like Discord, that also had it).
All of the above took more than a week to troubleshoot through, and in the end the only way to stop the issue from occurring (it's been almost 48 hours now, VS it happening every 4 hours on average before) was disabling HW Acceleration.
The issue always occurred when interacting via Chrome with any web content that leveraged said acceleration (Tweetdeck, Youtube's recommended, Destiny Item Manager - or DIM being notable examples of this).
Now, I do not quite know on who is more at fault, here. The obvious first one is AMD drivers, as this might very well be a low-priority kink in them (not unlike the whole HEVC issue they have). Second one is Microsoft, as it'd not be the first time something about an update of theirs messed it for others. Third one is Samsung, given that this issue began ever since I started using their display.
Use driver 22.5.1. It is listed as the recommended WHQL driver. You should always stay on that. Anything that says it's optional, or not WHQL, is unstable for many people. I have a G7 and had all sorts of issues like gray screens and way more game crashes and driver timeouts and 22.5.1 solved everything. Also update the firmware on the monitor if you haven't (I didn't read your entire post).
There are many posts everywhere about instability and driver issues around high refresh displays and hardware acceleration and what not. All your troubleshooting items listed above I have enabled/on/turned up/etc. HW accel is enabled on everything. All my issues are solved. Even in an alpha game I play all the random crashes where the display driver would time out etc are gone (star citizen). I had issues with that every day, and now it's smooth, stable, and I can have chrome/discord/steam, etc everything that uses hw accel running with no issues.
I believe 22.5.1 is "Recommended WHQL" for good reason. Even if you think your issue is different from everyone else, it may be good to base all your troubleshooting on that version, and not an optional driver.
To be clear on my side: this issue happened only in what might as well be GPU idle states - when I wasn't playing anything, or when maybe I was alt-tabbing to a browser, with the issue happening shortly after.
The likelihood that the Cleanup Utility will help address something more compared to DDU is incredibly small, when all of the attempts have not had the minimum difference. We shall see when the next driver release comes out - I plan to keep things up to date on that front, if I can help it.
Issue has not presented itself in any way ever since my original post, due to disabling Hardware Acceleration in places where this was used most (Google Chrome, Discord, Microsoft Teams).
Issue has however reared its head again today due to two specific aspects I have been using more lately, which are related to Hardware Acceleration: Steelseries GG, Windows 10 Video Player. Both of these are aspects where disabling HW Acceleration is close to unfeasible (only for Windows, possibly).
This issue did not occur prior to the new monitor, the RAM was not a factor in this, and neither are the PSU cables (this is the 'ensured no cable issues' mention in my original post).
Software-wise: Chipsets were up to date when I created this thread and they still are.
The issue only began with the new monitor, and only with hardware acceleration, which has already been pointed as the fault here, AKA software, not hardware. The fact this is potentially the one shown in the latest driver notes as known issues is a good thing, but the confirmation would be great as well.