Intel 3000 HD i7 Sandy 64bit and Everquest 2

idata · ‎03-23-2013

Hi,

I am having some issues with the Intel 3000 HD, currently using 9.17.10.2932 driver.

I have had this issue ever since I got this computer a year ago, an Asus K53E, Windows 7 64 bit, Japanese OS.

Not just EQ2, but also many old games that use OpenGL. I'm not sure if the EQ2 issue is an Open GL issue though.

Here is a picture from the Wailing Caves area which illustrates the issue. It happens in other places in the game, but this is an easy to access place.

Generally mist effects and certain particle effects seem to cause it. I have tried many things to try and fix it, setting all settings to lowest possible and also the highest possible settings and many in between. All with the same issue.

DArce · ‎03-25-2013

Have you tried using the video drivers provided from Asus* and the latest BIOS posted there?

http://www.asus.com/Notebooks_Ultrabooks/K53E/# support http://www.asus.com/Notebooks_Ultrabooks/K53E/# support

idata · ‎03-25-2013

I had it as such until recently where I updated the video driver to the latest intel driver to see if it fixed the issue.

The bios is up to date as well.

idata · ‎03-25-2013

Is there any way I could log errors or find out what the program is failiing to call via the driver, or do I have to do it from the offending program itself?

I will have to ask SOE(Sony Online Entertainment) about what I can do to check with their software if there is some sort of video extension init error as well, I guess.

DArce · ‎03-26-2013

Could you please load again our generic driver and provide us the dxdiag report generated in your system?

To get this report, you can go to the start menu and run dxdiag, then click on save this information and copy paste here the contents on the file that you will create.

idata · ‎03-26-2013

------------------

System Information

------------------

Time of this report: 3/27/2013, 07:42:51

Machine name: COMPUTERNAME

Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130104-1431)

Language: Japanese (Regional Setting: Japanese)

System Manufacturer: ASUSTeK Computer Inc.

System Model: K53E

BIOS: BIOS Date: 09/26/11 13:43:38 Ver: 04.06.03

Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 CPUs), ~2.0GHz

Memory: 8192MB RAM

Available OS Memory: 7970MB RAM

Page File: 2265MB used, 13673MB 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.01.7601.17514 32bit Unicode

------------

DxDiag Notes

------------

Display Tab 1: No problems found.

Sound Tab 1: 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 3000

Manufacturer: Intel Corporation

Chip type: Intel(R) HD Graphics Family

DAC type: Internal

Device Key: Enum\PCI\VEN_8086&DEV_0116&SUBSYS_16521043&REV_09

Display Memory: 1760 MB

Dedicated Memory: 192 MB

Shared Memory: 1568 MB

Current Mode: 1366 x 768 (32 bit) (60Hz)

Monitor Name: 汎用 PnP モニター

Monitor Model: unknown

Monitor Id: LGD02DC

Native Mode: 1366 x 768(p) (59.996Hz)

Output Type: Internal

Driver Name: igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumd32,igd10umd32,igd10umd32

Driver File Version: 9.17.0010.2932 (English)

Driver Version: 9.17.10.2932

DDI Version: 10.1

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 12/14/2012 02:42:34, 12615680 bytes

WHQL Logo'd: n/a

WHQL Date Stamp: n/a

Device Identifier: {D7B78E66-4256-11CF-8778-5836B7C2C435}

Vendor ID: 0x8086

Device ID: 0x0116

SubSys ID: 0x16521043

Revision ID: 0x0009

Driver Strong Name: oem49.inf:Intel.Mfg.NTamd64:iSNBM0:9.17.10.2932:pci\ven_8086&dev_0116

Rank Of Driver: 00E02001

Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C

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

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,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)=(IMC3,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/Ou...

idata · ‎03-26-2013

Sorry about the massive post, couldn't attach the file to the post. I don't have any public file sharing logins either.

DArce · ‎03-27-2013

Could you please confirm if there is also an nVidia Graphics Driver installed in your system?

From what I can see in your system manufacturer's web site, they also provide a driver for that which makes me wonder if your system features switchable graphics. Switchable graphics is an option provided by the computer manufacturer to use and Intel(R) video controller and an alternate third party one. For this to work a special driver is required, so our generic drivers should not be used in that kind of systems.

idata · ‎03-27-2013

No Nvidea on this system. I also checked the hidden devices as well.

All device manufacturers provide a driver from what I know. Asus have device drivers that go into a automatic updater so maybe they have to repackage it for that reason.

idata · ‎03-27-2013

If you could confirm whether or not the issue exists with the driver by playing the game (it is free to play), you can ask someone for a CoV (game teleportation mechanic) to the water area in the wailing caves. I would do it, but I fear that it would be outside your work hours. 10pm-12am (6-8am PDT) +9 GMT. Or 7:30am to 8:00am +9 GMT.

idata · ‎03-27-2013

If you did decide to test it, I would recommend turning the client to streaming otherwise you will download the whole 15GB game.

idata · ‎03-28-2013

I've ascertained that the game is Directx based.

Kevin_M_Intel · ‎03-29-2013

Hello Nzjpnboy,

Please be aware that we provide generic drivers that have not been developed or tested specially for your system. Each motherboard, laptop or Original Equipment Manufacturer can add, remove and change features on the video controllers they implement on their systems. Therefore they provide customized drivers to support such changes. So we always recommend using the latest drivers provided directly by your motherboard or Original Equipment Manufacturer.

You can download our latest driver we have available in our website. We just released a new driver version and you can try it by downloading it from the following link:

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22628&lang=eng&OSVersion=Windows%207%20%2864-bit%29*&DownloadType=%0A%09%09%09%09%09%09%09Drivers%0A%09%09%09%09%09%09

Note that we have information about the features supported in your graphics controller. You can check this information in the following link:

http://www.intel.com/support/graphics/sb/CS-033757.htm http://www.intel.com/support/graphics/sb/CS-033757.htm

I suggest you to update your drivers to the latest ones from the system manufacturer download page and also to update the system with the latest direct software. Another good idea is to contact the game developer to know what the requirements are for this game so you can check if your system meets the minimum requirements.

Thanks.

idata · ‎03-31-2013

Hello Kevin,

The reason why I wanted you guys to test it on your side was to eliminate the possibility that it is a mainboard/OEM driver difference. I was hoping to clarify the issue by having someone with the same video card test it and confirm whether or not it is a problem with the driver/Card itself or whether it is a combination of my driver and mainboard.

I will try the recommendations that you have posted. As I have stated previously, I've had no luck with the OEM driver, that is why I switched to the Intel Driver.

I have already been in contact with the games community to see if there are any other's with the same sort of issue, but it's in the support forums, so I doubt it's getting the amount of attention that I would like it to. I will try talking to the games CS. I doubt I will get much from the OEM, but I will try that channel as well, but I would like to ascertain what the issue actually is first rather than having 3 balls flying at once.

The game runs on Direct X 9, The intel HD 3000 has support for DirectX 10.

I have installed all the DX updates for 9 as well as making sure that 10 was up to date. I can run two instances of the game without issue, the system spec is far above that of the game. I have also refreshed (deleted and redownloaded) the game files too.

I will try the new drivers if they can be used on my Japanese OS system. I will report back on the results.

idata · ‎03-31-2013

I tried the new driver to no effect.

Kevin_M_Intel · ‎04-01-2013

Hello nzjpnboy,

I am sorry to hear the Intel® driver provided did not work in your system.

Note that the driver that we can provide is a generic driver for your system. This is because when the OEM or your computer manufacturer creates the computer will also design and create the customize drivers specifically for the unit. Due to this situation, they are able to modify, or include more changes in their drivers to make it work as they would like.

At this point since you have tested our latest generic driver, I can suggest you testing the previous driver version we have available. You can download this driver version from the following link:

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22375&lang=eng&OSVersion=Windows%207%20%2864-bit%29*&DownloadType=%0A%09%09%09%09%09%09%09Drivers%0A%09%09%09%09%09%09

We have an application called Intel® Processor Diagnostics Tool. You can test the processor components and it will show the result of the test once completed. You can use it by accessing to the following link:

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19792&keyword=Processor+Diagnostics+Tool&lang=eng http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19792&keyword=Processor+Diagnostics+Tool&lang=eng

If after installing the driver we have available issue persists, will be necessary to wait for a newer driver from the system manufacturer since it may contain fixes for the issue with your computer.