Overclock.net banner
1 - 2 of 2 Posts

·
Registered
Joined
·
8 Posts
Discussion Starter · #1 ·
Current setup:
Windows 7
6870 MSI, Twin Fozzier II, RMAed to Twin Frozzier III
ASUS Motherboard M4A88TD EVO
Phenom 955

Issue:
Everything was working great the past two years, I have two monitors, a DVI and a VGA. I have the VGA hooked up to the top port, using a DVI adapter, the DVI has always been plugged into the bottom port.

I work from home and plugged my DVI monitor to my docking station so I could dual display my work laptop.

After I was done I went back to my desktop I plugged it back and rebooted. I am not sure what happened but the PC will no longer display anything with both monitors plugged in anymore.

Here is what I know,

*when I have both the monitors plugged in the PC will boot, IE I hear the Windows load chime
*Same thing happens if I have only the DVI monitor plugged in the bottom port
*When I have the vga plugged in the top port only everything works

The DVI monitor works, I have verified this, also when I have it plugged in the bottom port I am getting a signal sent to it, as the screen will switch from no signal received more to a blank screen as soon as I power up the desktop. Also after the PC boots I can unplug the cord from the cards bottom slot and plug it into the top one and the Windows screen looks fine.

I RMAed the first one thinking the bottom port went out, the new is doing the same thing. I also updated my BIOS to the lastest version and this did not do anything to resolve the issue.

Any help or suggestions would be much appreciated
smile.gif


Cheers
…Hide content ?
 

·
Registered
Joined
·
8 Posts
Discussion Starter · #2 ·
After messing around with it for awhile, I booted then plugged the secondary monitor in. No blue screen but no luck. After powering up the secondary monitor I noticed it was in Analog mode. I run this to my PC in a DVI port. I unplugged the Analog cable from the monitor and it worked. Kinda DERP for me to not notice that but after the problems the other one gave me I was thinking it was some type of BIOS issue.
 
1 - 2 of 2 Posts
Top