Samsung 750D/950D DisplayPort Functionality

Soldato
Joined
6 Aug 2007
Posts
2,516
Hi,

Now that the 750D and 950D monitors have dropped significantly in price over the past month, I expect a huge increase in owners. I find it important to let people know the issues they could face when using these monitors.

The main issues that surround these monitors are all to do with the DisplayPort. We have pages and pages of threads on the Nvidia forums about these products, A good 6 months has passed and we are still no closer to receiving a proper fix.

The 950D isn't as badly affected due to it having a DVI-D connection, thus providing a workaround for the currently broken DisplayPort. If you want to get one of these monitors I strongly recommend spending the extra and picking up the 950D purely for the DVI-D port.

As for the 750D it only has 2 output sources, HDMI and DisplayPort. Meaning that you can only use HDMI, resulting in no 120Hz and no 3D.. so the main selling point and features of this monitor can't be used.

To get DisplayPort functionality working driver developers (ATI and Nvidia) have to use hacks in order to receive a signal in Windows. The results of these hacks have shown to be extremely random, working for some users but not others, Nvidia confirmed this by saying the following: 'Some users report fixed while others still seem to have issues. Will pass info to our software team.'. Keep in mind that even with a 100% working hack it's very likely you still won't receive any signal for the POST or BIOS screen, so should you want to do a task like install an OS you'll have to use an HDMI connection.

What we know so far:

- It's a problem on Samsung's side of the fence, due to the fact that most users get no DisplayPort signal at all, not even on the POST/BIOS screen.

- Nvidia responded to the issue with the following: 'So it seems the DisplayPort issue with the Samsung monitors reported is due to the fact that the DisplayPort on these monitors is reporting itself as a DisplayPort 1.2 even though it is really just a 1.1. We are sending 1.2 signals in the newer drivers that this monitor is not interpreting correctly because it is not a true DisplayPort 1.2 display. We still have not decided on a final resolution however at least I wanted to provide you all with the root cause that our software team has come up with so far. '.

- Samsung hasn't admitted any responsability for the issue, the best result people have been offered is a replacment, but that is no good due to it being a firmware / driver issue.. the same problem would only occur again.

- Ideally Samsung will need to acknowledge the problem and correct it in a Firmware update.

- The ATI hack seems to be much more effective, most of the users with no signal in Windows are Nvidia users.

- Some people receive signal in POST and BIOS screens, even with a DisplayPort.. but it seems pretty random, in the way that it can start working at any time, as well as stop working.

Thanks.
 
Yeah mine is with Samsung at the moment due to the display port issue weather they can do anything is anyones guess as the day they got it they needed a techy to phone me up as he didn't understand the problem! surely they have heard of it, anyway i think its terrible that hardware can be released with such a high failure rate, what do the people in their R&D deparment get paid for?
Regards
Guy

I really don't think Samsung are aware of the issue, they seem to ignore it and just replace everything in question.. any other time this would be fine, but when it's not a hardware defect but a firmware and driver issue blindly replacing won't help.

But keep me notified on your progress.

Thanks
 
Can you link me to the ATI hack?

I don't have issues with seeing the BIOS, but I do have issues resuming form sleep...

This may land up in me returning the monitor.

The hacks are built into the Catalyst drivers, regarding the resuming from sleep.. I believe that is a side effect.

Only had my 750D a few days now but had no issues with display port, 120hz and 3d works perfectly with my 670

Mine worked for a good month with the 301.24 beta drivers. Now it's totally broke, on all drivers.. even in POST and BIOS screen, which used to work.
 
Last edited:
Side effect of what? The hacks?

Yes it is a side effect of the fix put in place, it happens with the Nvidia drivers too.

And when you say build into drivers, you mean there is nothing that needs to be user enabled, etc?

You shouldn't have to enable anything, if they wasn't working you wouldn't even be able to get a signal.. so you know it's working.

What are these hacks?

I'm not 100% sure how the hack works, it's Nvidia that came up with it.. but it's something to do with sending different signals to the DisplayPort, which isn't really intended.

Nvidia: 'We are sending 1.2 signals in the newer drivers that this monitor is not interpreting correctly because it is not a true DisplayPort 1.2 display. We still have not decided on a final resolution'.

But it's obviously not that simple, as Nvidia confirmed here: Some users report fixed while others still seem to have issues. Will pass info to our software team.

Since that last failed attempt of a fix no news from Nvidia, it seems they are out of ideas, it's getting to the point where they can't do much more about it.. Samsung will have to get their act together and face their mistake.
 
Well, the monitors have been out a while now, so what are the odds of that?

Sigh, tech is beginning to suck.

Indeed they have, i got mine round about the Christmas time and made use of the 5% off offer, as well as free delivery.. i saved quite a lot of cash. Though i still payed £400.. for something that's worth no more than £140 in its current state. No doubt now they've dropped in price, plenty more people will be buying them.. only if they knew the horrors that potentially await.

I waited over 2 month for Nvidia to apply a fix, only for it to stop working after 1 month.

It'll be the last Samsung monitor I'll ever buy, shame because I've always had Samsung monitors and they've always been quality.. This monitor is no different, when it worked.
 
Last edited:
Back
Top Bottom