kopaka

Originally posted by Galaky: Quote: Ok, I downloaded Memtest86+...and it had frozen at 1:03:58 into it... I'd say you found your problem--or at the very least, a problem! Your system should never lock up running a memory test, especially not after only an hour. Did it report any errors before it froze? You could try swapping the two sticks of RAM to see if that helps, or even try running with just 512 MBs to help further isolate the problem. No matter how you slice it, though: bad memory = dysfunctional system. -k

Originally posted by daz0r: Quote: I also noticed that the OSD version was 1.11 instead of 1.0 on the old-and-busted monitor. v1.11? Curious. What was the Manufacture Date (as reported by the Options/Asset ID in EzTune)? For the record, both my original monitor and my replacement (now just two days old) have OSD v1.1. -k

Originally posted by tried everything: Quote: I have just noticed that the ATI Catalyst Control Center has an option under the "Digital Panel Properties / HDTV Support".... "Add 1080i standard format to the Displays manager" Gateway's FPD2185W supports the 1080i or the 720p (not the 1080p). Can someone try one of these settings with the DVI-D connection and let me know if it works? Also wondering if this would work using the Component Y Pb Pr connections. I have an ATi 850XT connected to my FPD2185W (via DVI and VGA) and setting the HDTV options in the Catalyst driver (v6.1) did squat. I was unable to test the component inputs, but I seriously doubt it would make any difference. Like others have reported, the monitor was working fine for about 10 days and then the DVI suddenly stopped functioning, for no apparent reason. It's curious that I've only read similar reports from owners of ATi cards. Does nVidia not suffer from this? I called Gateway tech support, who had no information on the problem, but indicated that a new firmware for the monitor was in the works. Whether that was true, and whether it would fix the problem remains to be seen. At a minimum, 'corrupt' EDID info in the monitor is clearly related to this problem. Even PowerStrip, which is capable of pulling the EDID data directly from the monitor, was unable to acquire it. For this reason, I think that the EDID may, in fact, be intact, and that it is the DDC link that's actually failing. Regardless of which (corrupt EDID or bad DDC link), the same end result manifests itself. As there seems to be no 'software' fix, I'll exchange the monitor and see how long the new one holds up. If that one busts the same, I'll not try a third. -k