Member Avatar for rectifryer

I have a low end HP 6005 cpu that will not display more than 720p with my dell 30" 1600p monitor. The drivers are current and I am using a dual link cable. If I swap to a smaller 1080p monitor, the cpu swaps to 1080p automatically. What is the issue here?

  • 2 Contributors
  • 2 Replies
  • 82 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by rectifryer

Dani AI

Generated

Following the exchange between and , the behavior described points to a negotiation or bandwidth problem between the graphics output and the high-resolution display rather than a simple driver setting. The checklist below gives targeted, practical tests and fixes that have resolved the same symptom on older business-class systems.

  • Confirm the graphics device and per-output maximums. On Windows this can be checked in Device Manager or with a tool such as dxdiag/GPU-Z; compare the device specs to the monitor's native mode.
  • Isolate the link: swap the cable/adapter and try a different output (or a known-good discrete GPU) to tell whether the port or the monitor is refusing the native mode. Passive adapters and some single-link cables can look correct but limit bandwidth.
  • Force a mode via the GPU control panel (NVIDIA/AMD/Intel) or Windows Advanced Adapter Modes. Create a custom resolution at the monitor's native pixel clock and 60 Hz; if it is rejected, the problem is almost always EDID or output bandwidth.
  • Read the monitor EDID and reset the monitor OSD; some older panels need an explicit input reset or firmware update to accept the high-res handshake. EDID tools can reveal what modes the system actually sees.
  • If the system consistently refuses the monitor but drives lower-resolution displays fine, the practical remedy is a graphics output known to support the panel (a discrete card with the required DVI dual-link or DisplayPort) or replacing the interface chain (proper dual-link cable/active adapter or native DisplayPort).

Most often the root cause is an output/adapter limitation or a failed EDID handshake rather than an OS driver bug. Replacing the graphics interface with one that explicitly lists the monitor's native resolution is the most reliable long-term fix.

Recommended Answers

All 2 Replies

Member Avatar for rubberman

What OS are you running? Windows of some sort I presume?

Member Avatar for rectifryer

Yes, windows 7 ultimate.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.