Quantcast
Channel: Intel Communities: Message List
Viewing all articles
Browse latest Browse all 20046

Re: Windows 8/8.1 Intel HD 4000 Laptop Graphics Driver Problem!!!

$
0
0

kevin_intel wrote:

 

The OEM images that the computers have preinstall are configured by the Computer Manufacture to work smoothly with the hardware of the computer so installing a retail version may be affecting the operating or performance.

 

As mentioned before, the VBIOS is pulled by the Graphics and Media control panel from the BIOS itself so my recommendation is to update the BIOS to latest.

Hey Kevin!

 

     Sorry for taking so long to reply... From my own research I have to agree with you that OEM installations have a specific configuration targeted for each laptop/PC model... More so when dealing with Win8/8.1, compared to Win7... And Asus does have a reputation for how they sometimes make it so difficult for USERS to "Clean" install a different OS other than the OEM installation... Although I do have to say that it shouldn't cause these issues when "Generic" Drivers are concerned... I mean it's a fresh and pristine OS environment with a "Clean" Win8.1 install... I would think that it should make things EVEN EASIER for installing Intel® drivers...

     Now, about the Graphics & Media Control Panel... It does pick up the vBIOS... BUT ONLY if I boot Win8.1 WITH "LAUNCH CSM - ENABLED"  (Non-UEFI Boot) set in BIOS... ONLY then does the vBIOS load and gets picked up... What I'm getting at is: When booting WITH UEFI... The Intel® EFI GOP driver is used instead of the vBIOS... Correct... The issue is the GOP Driver IS NOT BEING PICKED UP... As you can see in the image I previously posted... It depicts the GOP Version DOES get picked up by the Gfx Control Panel... And on my system I only get vBIOS Version "0.0" My argument is that MY Gfx panel IS NOT picking up the GOP driver!!! And only shows vBIOS 0.0 when it shouldn't even say vBIOS... It should say GOP Version... I have already updated to the latest vBIOS & EFI GOP driver... I also just "Clean" installed the latest HD 4000 driver v3496... With no change to the whole issue I've been describing here...


Viewing all articles
Browse latest Browse all 20046

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>