- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have discussed this topic with Fred in chat already, proposing me to update the BIOS driver, which however was not successfull:
My problem is:
I have built an new PC including Intel I5 3570K processor on motherboard Asus P8Z77-M PRO. I have a monitor Iiyama Prolite E485S 19'' native resolution 1280x1024, 60 Hz connected to it. Before that monitor was connected to a PC running Win XP 32 bit on DVI-D interface no problem.
Ever since the first boot on the Win 8 PC, the DVI-D loses the signal on the DVI-D Interface right after BIOS bootscreen upon boot of the Windows OS. Before, i.e. BIOS setup, is working on DVI just fine.
The following has been tried, so far:
1. Reinstalling Intel 4000 HD driver, switching to another version Intel 4000 HD driver proposed by ASUS: After removing the Intel driver, the DVI interface works on native resolution. Upon reboot, the signal is lost again.
2. Testing Linux on the PC, installed on dual boot: DVI interface works fine!!
3. Updating the ASUS BIOS to the newest version - no effect.
4. Reinstalling the Intel chipset driver - no effect.
5. Removing the monitor from the device manager - no effect.
6. Uninstalling the Intel graphics driver 4000 HD using the Programs and features section in order to completely remove leftovers - same result as 1 above.
This issue seems similar to that relating to Windows 7:
I have read
http://www.sevenforums.com/tutorials/7947-force-dvi-hdmi-resolutions-refresh-rates.html Force DVI/HDMI resolutions and refresh rates - Windows 7 Forums
Which suggests to override an EDID such that the information received by the system from a monitor are disregarded and override preferences are used instead. Could this solve the problem? Would this require also a DVI-D cable with removed DDC Pin 7 and/ or DDC hotplug detect pin 16?
I have registered my E-mail and got a case number from Fred. Unfortunately I did neither receive the chat transcript, nor an E-mail regarding that case, Could I get that information forwarde via PM?
Thanks, Joerg
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
got the same problem since months... and i am so fuckin pissed about it...
Intel, come on!!! do something...!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sounds like it could be a DRM/HDCP issue?
I can also confirm I don't get anything like this running my HD 4000 in Linux.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I apologize for you not neither receiving the chat transcript, nor an E-mail regarding that case.
Our software support and engineering group is working on having the DVI-D loses the signal issue fixed on the next driver version. We cannot provide an estimated time for this to happen, but your feedback for sure is important and will be forwarded to higher levels of support.
Looking forward to assisting you further
Regards,
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have a client with the same issue.
Computer System:
MS Windows 8 64-bit (Fully updated)
Intel DB75EN Motherboard (BIOS & Drivers up to date)
Intel Core i5-3470 3.2Ghz
Kingston 8GB DDR3-1600 Memory
Seagate ST31000524AS Hybrid Drive
BENQ G2320HDBL Monitors
MS Wireless 800 Keyboard & Mouse
DMI-D Cables for Primary Monitor & VGA Cable for Secondary Monitor
Dual Monitor mode: Extended
The problem comes if the user logs out, screensave requires password or if sleep mode is initiated. The priomary DVI port turns off on the motherboard and takes a reboot to reinitiate the DVI port. Same occurs monitors and/or cables are replaced.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there any type of adapter being used between the DVI port in the motherboard and the display?
What is the driver version being used?
Please post the dxdiag report generated in that system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can confirm that the a standard DVI-D cable is being used between the motherboard and monitor and no other equipment is involved of any kind. I can reproduce the issue through logging out of a user and then turning the monitor off and then when it subsequently turns back on the screen is no longer seen by the computer.
Windows 8 64-bit confirms that the Intel HD driver is version 9.18.10.3165 and the Intel support website confirms this is the latest version. The BenQ driver which appears to be the built in version for windows, and reported as provided by BenQ reports to be version 1.0.0.0 dated 28/07/2011; however no newer version appears to exist via the BenQ support website.
DXDiag Report (When all is working as it should):
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
DXDiag after system fails to see the Digital Monitor. Please note between the two reports there is no hardware change nor has the computer been rebooted, but rather a standard user logout and both monitors being turned off and then back on again.
------------------
System Information
------------------
Time of this report: 7/24/2013, 09:03:59
Machine name: HBAPC-PASTOR
Operating System: Windows 8 64-bit (6.2, Build 9200) (9200.win8_gdr.130531-1504)
Language: English (Regional Setting: English)
System Manufacturer: INTEL_
System Model: DB75EN__
BIOS: ENB7510H.86A.0045.2013.0307.1509
Processor: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz (4 CPUs), ~3.2GHz
Memory: 8192MB RAM
Available OS Memory: 7628MB RAM
Page File: 1427MB used, 7351MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.02.9200.16384 64bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Input Tab: No problems found.
--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
---------------
Display Devices
---------------
Card name: Intel(R) HD Graphics
Manufacturer: Intel Corporation
Chip type: Intel(R) HD Graphics Family
DAC type: Internal
Device Type: Full Device
Device Key: Enum\PCI\VEN_8086&DEV_0152&SUBSYS_20418086&REV_09
Display Memory: 1792 MB
Dedicated Memory: 480 MB
Shared Memory: 1312 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: BenQ G2320HDBL (Analog)
Monitor Model: G2320HDBL
Monitor Id: BNQ78B2
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HD15
Driver Name: igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igdumdim32,igd10iumd32,igd10iumd32
Driver File Version: 9.18.0010.3165 (English)
Driver Version: 9.18.10.3165
DDI Version: 11
Feature Levels: 11.0,10.1,10.0,9.3,9.2,9.1
Driver Model: WDDM 1.2
Graphics Preemption: DMA
Compute Preemption: Thread group
Driver Attributes: Final Retail
Driver Date/Size: 5/7/2013 17:22:46, 8632320 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B78E66-4212-11CF-6BEF-4B00B4C2C435}
Vendor ID: 0x8086
Device ID: 0x0152
SubSys ID: 0x20418086
Revision ID: 0x0009
Driver Strong Name: oem33.inf:5f63e534c477ad23:iIVBD_w8:9.18.10.3165:pci\ven_8086&dev_0152
Rank Of Driver: 00E02001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C
DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT
Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{B...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can confirm that since posting the DXDiag I realised that BIOS 46 was released and have duly updated the BIOS to the latest version (dated 4th July 2013, however not uploaded until after the 8th July 2013 and therefore had not been installed)
It would obviously be immensely useful for you to know I have also noted that the issue also occurs outside of Windows and exists at the initial BIOS boot sequence. I have noted that at times the monitor states it does not have any signal when initially booted and one has to turn off the computer, turn off the monitors and then turn the monitors back on and boot the computer for the initial BIOS splash screen to appear on both monitors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Updated confirmation of new BIOS being in place:
------------------
System Information
------------------
Time of this report: 7/24/2013, 09:23:44
Machine name: HBAPC-PASTOR
Operating System: Windows 8 64-bit (6.2, Build 9200) (9200.win8_gdr.130531-1504)
Language: English (Regional Setting: English)
System Manufacturer: INTEL_
System Model: DB75EN__
BIOS: ENB7510H.86A.0046.2013.0704.1354
Processor: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz (4 CPUs), ~3.2GHz
Memory: 8192MB RAM
Available OS Memory: 7116MB RAM
Page File: 1583MB used, 6619MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.02.9200.16384 64bit Unicode
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In playing around I've also confirmed that the problem can be recreated if the monitor connected to the HDMI port is turned off. After approx 5 seconds the monitor on the VGA port flashes and is given primary display. When the monitor is turned back on it no longer has any signal and the computer also does not recognise any connection on the DVI port.
This seems to be either a BIOS issue, and thus needing a programming update, or a chip based problem on the motherboard requiring a motherboard replacement.
Your thoughts on this greatly welcomed. We do not have other motherboards of this type in stock to test. That said given the numbers of other users seemingly facing this issue it would seem that the issue is most likely BIOS related as the issue can be easily resolved. That said although the solution is easy it is incredibly annoying to have to reboot your computer every time the monitor is turned off manually or the PC places the monitor into sleep mode etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I agreed with you on the belief that the issue could be either hardware (being a defective motherboard) or a BIOS issue.
One thing I would like to check is, how many monitors are connected to this computer and actively being used? If more than one, have you tried using just a single video display in any of these interfaces (HDMI/DVI)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had problems logging in and so have been delayed in getting back to you. I can confirm that there are two monitors both the same make and model. They are permanently and directly connected to the motherboard with the correct cables for the interfaces being used (e.g. VGA to VGA and DVI-D to DVI-D).
I will try operating just one of the monitors at a time and get back to you.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page