Yes I know this thread is 3+ years old. Am posting here because I have acquired 6 of these monitors, and I found 3 of them to have the
exact issue you are describing, while the others ran perfectly. Am posting here in hopes that anyone stuck on this issue can find this as a potential fix.
I have all 6 of them running off a 5870 Eyefinity 6 2GB card (6 mini-DP outputs) via Accell Active DVI-Displayport adapters. I spent 8+ hours troubleshooting the darned issue thinking it was my adapters, swapping out and amongst each other every displayport adapter, DVI cable & playing with the video card ports. Even upgraded (some) of the firmware for the active adapters. After much deductive reasoning I concluded that the monitor EDID data being returned by the 3 monitors and insistently read by Win7 was the culprit. (Through various versions of ATI Catalyst/drivers, the best that could be forced were weird resolutions like 1400x900. I installed/uninstalled ATI catalyst versions a disturbingly unhealthy amount of times)
Having searched the web for these models, it is a somewhat present/pervasive issue it seems; many people simply return them to Samsung who supposedly give them a new monitor or swap out the motherboard of the monitor. BTW, the EDID data can be damaged by yanking the power cord off the back with the monitor on and/or the DVI cable, with the monitor on - I believe these monitors are for some reason more susceptible to this than others, and, I think that is what damaged mine, as they were working fine in their previous home.
Fixing it is rather specific and must be done right, otherwise you could brick your monitor(s).
The fix is pulling the EDID from a
properly working 2343BWX monitor using Phoenix EDID Designer 1.3 from the registry of that computer. (should you need this, I'm subscribed to the thread and may be able to help). Then, since it would be proper to change the serial and manufacture data for your specific (but not yet working) monitor, that would be done with Viewsonic EDID 3.1,3 editor, which will help you read the hex of the good EDID data you pulled, and segregate it to allow easier/better editing; I did the actual editting of the DAT file in notepad.exe. Converting the file back and forth into the appropriate *.DAT extension is done with Tomasz Orczyk’s EDID Converter. Ultimate writing of the EDID to the 'bad' monitor is done with EnTech PowerStrip - it must be a registered/paid version, as writing/outputting of the EDID is one of the few features disabled in the trial version of the program. Powerstrip also appears to read the monitor EDID data before and after; as soon as I wrote the EDID to the problematic 2343BWX, it recognized it, confirming the write was successful. Note that newer/fancier video cards won't necessarily work with Powerstrip - in this case, less is better - I used a crusty old GT6600 to do the writing, as, many other even basic yet newish video cards didn't seem to work, with Powerstrip saying it could not read the monitor data.
This latter part - writing the EDID and knowing it is 100% correct, is crucial, otherwise, you stand the chance of bricking your monitor. I'll add here too that Powerstrip seemed to detect that my 2343BWX had corrupt/damaged EDID header information and it offerred to fix it - I did not choose this option, as frankly I don't know what it will write/fix. Most of the details on what needs to be done to fix this is found here:
Fixing EDID on DVI Monitors Showing No Signal When Windows Vista Boots - Komeil Bahmanpour
