latest hd3000 drivers not WDDM1.3 for Windows 8.1 - DX10 assessment 0 in WEI

[idata]

I have a notebook pc with Intel i7-2670QM processor which is equipped with HD3000 graphics. The WEI score in windows 8.1 64 bit shows:

0

meaning the tests for DX10 are skipped completely by winsat.

I have the latest hd3000 drivers for windows 8.1 and, by looking at dxdiag, turns out that the drivers is WDDM1.2 and not WDDM1.3 as required by Windows 8.1.

So I must conclude these drivers are not using the DX10 functionality under Windows 8.1 64.

Intel drivers are:

Intel(R) HD Graphics 3000

Report Date: 2/3/2015

Report Time[hh:mm:ss]: 16:44:59

Driver Version: 9.17.10.3517

Operating System: Microsoft Windows 8.1 Pro(6.3.9600)

Default Language: Italian (Italy)

DirectX* Version: 11.0

Physical Memory: 3915 MB

Processor: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz

Processor Speed: 2195 MHz

Vendor ID: 8086

Device ID: 0116

Device Revision: 09

[Kevin_M_Intel]

Hello chriz74x,

You are correct. HD 3000 graphics driver supports up to WDDM1.2 on Windows 8.1.

Please check the Driver release notes here:

http://downloadmirror.intel.com/23764/eng/releasenotes_gfx_3517_64.pdf http://downloadmirror.intel.com/23764/eng/releasenotes_gfx_3517_64.pdf

You can also refer to the Driver ReadMe File here:

http://downloadmirror.intel.com/23764/eng/Installation_Readme_64.txt http://downloadmirror.intel.com/23764/eng/Installation_Readme_64.txt

Kevin M

[idata]

Yes I got that. The question is, does dx10 work at all on windows 8.1 with hd3000 ?

[ROBERT_U_Intel]

@ chriz74x

HD3000 Graphics supports up to DirectX version 10.1, (Good reference here http://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units# Second_generation List of Intel graphics processing units - Wikipedia, the free encyclopedia )

I am currently research why you are seeing the WinSAT and DXDiag results regarding Windows 8.1.

Thanks

Robert

[idata]

This is the output of "winsat d3d -dx10" command in elevated command prompt, sorry it's in Italian but it's obvious that all the dx10 tests are skipped:

C:\Windows\system32>winsat d3d -dx10

Strumento di valutazione sistema Windows

> In esecuzione: Enumerazione delle funzionalità ''

> Tempo di esecuzione 00:00:00.00

> In esecuzione: Valutazione Direct3D WinSAT '-dx10 -aname Batch -time 5 -fbc 1

0 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -

objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)'

> Tempo di esecuzione 00:00:00.00

> In esecuzione: Valutazione Direct3D WinSAT '-dx10 -aname Alpha -time 5 -fbc 1

0 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -

objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)'

> Tempo di esecuzione 00:00:00.00

> In esecuzione: Valutazione Direct3D WinSAT '-dx10 -aname Tex -time 5 -fbc 10

-disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -o

bjs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta

3'

> Tempo di esecuzione 00:00:00.00

> In esecuzione: Valutazione Direct3D WinSAT '-dx10 -aname ALU -time 5 -fbc 10

-disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -o

bjs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta

3'

> Tempo di esecuzione 00:00:00.00

> In esecuzione: Valutazione Direct3D WinSAT '-dx10 -aname GeomF4 -time 7 -fbc

10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 150;200;241 -batchcn

t C(50);C(200);C(300) -objs C(12);C(26);C(45) -noalpha -geomf4shader -texpobj C(

0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1'

> Tempo di esecuzione 00:00:00.00

> In esecuzione: Valutazione Direct3D WinSAT '-dx10 -aname GeomV8 -time 7 -fbc

10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75;100;120 -batchcnt

C(25);C(100);C(150) -objs C(8);C(17);C(29) -noalpha -geomv8shader -texpobj C(0)

-rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1'

> Tempo di esecuzione 00:00:00.00

> In esecuzione: Valutazione Direct3D WinSAT '-dx10 -aname CBuffer -time 5 -fbc

10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75 -batchcnt C(25)

-objs C(8) -rendertotex 6 -rtdelta 3 -texpobj C(1) -cbuffershader -cbufa 2 -cbuf

f 5 -cbufp 6'

> Tempo di esecuzione 00:00:00.00

> Prestazioni Direct3D Batch 0.00 F/s

> Prestazioni Direct3D Alpha Blend 0.00 F/s

> Prestazioni Direct3D ALU 0.00 F/s

> Prestazioni Direct3D Texture Load 0.00 F/s

> Prestazioni Direct3D Geometry 0.00 F/s

> Prestazioni Direct3D Geometry 0.00 F/s

> Prestazione Direct3D Constant Buffer 0.00 F/s

> Tempo di esecuzione totale 00:00:00.45

[idata]

also, this strings appear on winsat.log

WDDM 1.1 or WDDM 1.2; aborting DX10 assessment

So what is happening here is winsat checks if the driver is WDDM 1.3 and since it's not aborts the test.

The question remains: does Windows 8.1 uses directx10 at all without a WDDM 1.3 driver?

[idata]

sorry, this is the exact string in the winsat.log

d3d\graphicsop.cpp:0217: Driver is not WDDM 1.1 or WDDM 1.2; aborting DX10 assessment.

So, driver is not 1.1 nor 1.2 ??

[ROBERT_U_Intel]

@Chriz74x,

The HD3000 Graphics driver supports WDDM 1.2 See this for additional information. http://www.intel.com/support/graphics/sb/CS-033838.htm?wapkw=windows+8+faq Graphics Drivers — Microsoft Windows 8* and Windows 8.1* Support FAQ

I would also recommend testing with the latest driver for HD3000 here: https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=24696&lang=eng&ProdId=3319 Intel® Download Center

Thanks

Robert

[idata]

I have same problem. Specs: Intel 3000 HD, gen 2 intel i5Vpro, windows 8.1 pro x64.

My first thought is that windows 8.1 is missing certain directX 10.1 files and the WEI test cannot run.

Do you intel have any solution for this???

Thanks

Here is part of my winsat.log.

205015 (6972) - d3d\graphicsop.cpp:0217: Driver is not WDDM 1.1 or WDDM 1.2; aborting DX10 assessment.

205015 (6972) - exe\main.cpp:1852: > Run Assessment d3d -dx10 -aname Alpha -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs C(26) -rendertotex 6 -rtdelta 3 -texpobj C(1)

205015 (6972) - d3d\graphicsop.cpp:0195: GraphicsOp::AssessmentThread Launched with priority 0

205015 (6972) - d3d\graphicsop.cpp:0217: Driver is not WDDM 1.1 or WDDM 1.2; aborting DX10 assessment.

205015 (6972) - exe\main.cpp:1852: > Run Assessment d3d -dx10 -aname Tex -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3

205015 (6972) - d3d\graphicsop.cpp:0195: GraphicsOp::AssessmentThread Launched with priority 0

205015 (6972) - d3d\graphicsop.cpp:0217: Driver is not WDDM 1.1 or WDDM 1.2; aborting DX10 assessment.

205015 (6972) - exe\main.cpp:1852: > Run Assessment d3d -dx10 -aname ALU -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs C(20) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3

205015 (6972) - d3d\graphicsop.cpp:0195: GraphicsOp::AssessmentThread Launched with priority 0

205015 (6972) - d3d\graphicsop.cpp:0217: Driver is not WDDM 1.1 or WDDM 1.2; aborting DX10 assessment.

205015 (6972) - exe\main.cpp:1852: > Run Assessment d3d -dx10 -aname GeomF4 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 150;200;241 -batchcnt C(50);C(200);C(300) -objs C(12);C(26);C(45) -noalpha -geomf4shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1

205015 (6972) - d3d\graphicsop.cpp:0195: GraphicsOp::AssessmentThread Launched with priority 0

205015 (6972) - d3d\graphicsop.cpp:0217: Driver is not WDDM 1.1 or WDDM 1.2; aborting DX10 assessment.

205015 (6972) - exe\main.cpp:1852: > Run Assessment d3d -dx10 -aname GeomV8 -time 7 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75;100;120 -batchcnt C(25);C(100);C(150) -objs C(8);C(17);C(29) -noalpha -geomv8shader -texpobj C(0) -rendertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1

205015 (6972) - d3d\graphicsop.cpp:0195: GraphicsOp::AssessmentThread Launched with priority 0

205015 (6972) - d3d\graphicsop.cpp:0217: Driver is not WDDM 1.1 or WDDM 1.2; aborting DX10 assessment.

205015 (6972) - exe\main.cpp:1852: > Run Assessment d3d -dx10 -aname CBuffer -time 5 -fbc 10 -disp off -animate 10 -width 1280 -height 1024 -totalobj 75 -batchcnt C(25) -objs C(8) -rendertotex 6 -rtdelta 3 -texpobj C(1) -cbuffershader -cbufa 2 -cbuff 5 -cbufp 6

205015 (6972) - d3d\graphicsop.cpp:0195: GraphicsOp::AssessmentThread Launched with priority 0

205015 (6972) - d3d\graphicsop.cpp:0217: Driver is not WDDM 1.1 or WDDM 1.2; aborting DX10 assessment.

[idata]

Intel why have you not produced a wddm 1.3 driver in order to properly support intel hd 3000 in windows 8.1??? A 2 year driver support does seem very short for a reputable company. Intel please produce a wddm 1.3 driver to properly support windows 8.1.

[Anonymous]

Hi palmiris,

The second generation processors have a hardware limitation, they meet WDDM 1.2. The 4 gen and latest are prepare for WWDM 2.0

Regards,

Mike C

[idata]

Thanks for your reply.

What exactly is the limitation???? All specs are the same except the following (see table). All intel hardware starting from intel hd 4000 have been upgraded to wddm 1.3 and 2.0 except intel hd 3000.

Here are the hardware differences.

direct X pipelines OpenGL Shader model Open CL Performance Improvement

intel hd 4000 11 16 4 5 1.2 about 40% over intel hd 3000 (due to better spec hardware support)

intel hd 3000 10.1 12 3.1 4.1 -

I have a windows 8.1 with intel i5 vPro 2nd gen, intel hd 3000, and intel centrino ultimate N-6300. The passmark performance for both windows 8.0 and 8.1 are: 1811 and 1752 respectively. The difference is in the 2d (or desktop performance) score only. (search baseline by using "lenovo T420 B87 4236" and the 2 tests will appear)

Widi is working great under windows 8.1 with intel Widi 3.5.41.0 driver only (not able to make windows 10 widi work though). Maybe a different miracast hardware would be able to work under newer widi drivers but I will not be able to test this. I am happy though with my solution which was made under trial and error. For this reason I don't have a problem per se. Everything works fine under windows 8.1, which is a surprise as it is wddm 1.2 (even widi with the proper driver).

I still dont understand the limitation for not providing a wddm 1.3 driver. Does intel hd 3000 need an update (through bios) in order to support a wddm 1.3 driver???? Where is exactly the limitation???

I need a bit of info as your reply will help me take future decisions regarding my future laptop purchases.

Windows 8.1 and windows 10 are tested to be both hardware upgrade compatible so was the intel widi hardware engine check but still without wddm 1.3 and 2.0 driver support to my suprise.

I need a bit more convincing arguments by intel who has not taken the driver update forward though I would have thought if there is a will there is always a way especially if you want to keep your customers happy.

I am happy that windows 8.1 works so I will have microsoft support for another 5 years, compared to windows 7 which will soon end however I will not say the same for the integrated graphics firmware upgrade option. This can only be done through bios, and intel is not so interested in firmware upgrading its hardware nor are the computer manufacturers.

Integrated graphics should be firmware upgraded easily without the need of bios update. Though most customers aim is to save power on laptops through integrated graphics, intel should find a way to software update their integrated graphic without the need of bios update. Then you will have a competitive advantage but not until then.

Regards

[Anonymous]

Hi palmiris,

The graphics features are embedded in the processor, some features require software and hardware updates. For example 3rd gen processors support WDDM 1.3 and they support Windows® 10 but they will have limitations. The graphics driver is provided with Windows® 10 updates.

Windows® 10 comes with Windows Display Driver Model 2.0 and only 4th gen and newer versions are fully compatible. The chart below contains the supported operating systems by graphics generation.

http://www.intel.com/support/graphics/sb/CS-034343.htm?wapkw=cs-034343 Graphics Drivers — Supported Operating Systems

Regards,

Mike C

[idata]

hello,

I am interested in Intel HD 3000 and windows 8.1 full integration, meaning wddm 1.3 compliance. I am expecting that Intel produces a wddm 1.3 driver for Intel HD 3000. If it cannot be done feel free to explain why, but as I said if there is a will there was s always a way. please reconsider.

thanks.

[Anonymous]

Hi palmiris,

I understood your request; however, there is a hardware limitation on second generation processors, the option to include WDDM 1.3 is not possible. Processor are sealed and firmware is secret.

Regards,

Mike C

[idata]

thanks for the info. Usually hardware are upgradable using special software tools within windows. Are you implying that Intel has made a processor with an integrated display driver that it's display firmware cannot be updated???

Firmware that are usually updated:

hardisk

BIOS

CD/DVD

graphics cards

Is Intel display (gpu) firmware not updatetable within dos or windows????

I am trying to understand the Intel cpu integrated graphics.

Can I send you my laptop for a display firmware update?????? just kidding. but it does make sense that if a hardware cannot be updated it is not worth in the long run. Has Intel not found a way to update the firmware or produce a wddm 1.3 compatible driver??

By the way. I read the following article.

Intel prepping HD 4000 firmware update for April, will boost performance by 10 percent. OpenCL 1.2 support will be added. Windows users, Intel's http://macnn.com/rd/282222==%20http://www.intel.com/p/en_US/support/detect update utility can check for and install firmware updates for its componentary. here is the link.http://www.macnn.com/articles/13/03/31/intel.prepping.hd.4000.firmware.update.for.april.will.boost.performance.10.percent/ MacNN Mobile : Latest HeadlinesIs it suppose to be firmware or driver update??? is the article wrong????

Regards

here is the article

Intel says that it is http://macnn.com/rd/282223==http://ultrabooknews.com/2013/03/29/latest-intel-hd-4000-driver/ preparing an update for the integrated HD 4000 GPU found in its third-generation mobile http://macnn.com/rd/282224==http://www.electronista.com/articles/11/10/20/intel.ivy.bridge.ships.en.masse/ 'Ivy Bridge' Core processors, reports Ultrabook News. The firmware update will fix bugs while also boosting performance by up to 10 percent while simultaneously improving battery life. The update, which is scheduled to arrive in April, will be welcome performance boost for ultrabook owners and others who depend on Intel's integrated graphics for their systems.

Intel's reps, speaking at the Game Developers Conference, said that the update (v. 15.31) is tailored for its next-generation http://macnn.com/rd/282221==http://www.electronista.com/articles/13/03/28/intel.gives.developers.new.tools.to.boost.gpu.performance.in.haswell/ 'Haswell' chips due in the second quarter, but it is being made available now for 'Ivy Bridge' users. The new drivers also add support for OpenCL 1.2, which should further supplement the graphics capabilities of its integrated HD 4000 GPUs. The integrated GPU in the forthcoming Haswell processor will double the graphics performance of the HD 4000.

For Windows users, Intel's http://macnn.com/rd/282222==%20http://www.intel.com/p/en_US/support/detect update utility can check for and install firmware updates for its componentary.

[idata]

1. I have upgraded my Vbios to 2170. I have intel HD 3000 and QM67 chipset. Bios has sandy bridge and Ivy bridge microcode which means it supports all socket G2 2nd gen and these 3rd gen processors: i5-3610me and i7-3610qe. However these two cpus (3rd gen) are not widi enabled. Therefore they are useless to me.

Do you think I can use other 3rd gen processors with QM67 chipset as an upgrade to my system??? My bios also supports up to 1866 Mhz memory modules which will speed intel HD 3000 considerably. I am expecting a 15-20% direct 2D/3D gain after my memory upgrade next week).

2. The other problem I have is D3D under windows 8.1 and intel hd 3000. The following tests get a zero in windows 8.1 WEI score (winsat prepop in dos) :

Direct3D batch performance =0

Direct3D alpha blend performance =0

Direct3D ALU performance =0

Direct3D Texture Load performance =0

Direct3D Geometry performance =0

Direct3D Constant Buffer performance =0

The result is a windows 8.1 D3D low score (D3D=5) compared to windows 8.0 D3D score of 6.3.

[Windows Powershell command "Get-WmiObject -Class Win32_WinSAT"]

CPU Score 7.3

D3DScore 5

DisKScore 7.95

Graphics Score: 5.9

Memory Score: 7.5

Can you please help with the D3D low score in windows 8.1???? Can you improve the Wddm 1.2 driver to improve D3D performance in windows 8.1????? Same problem with command winsat d3d -dx10.

Thanks

[Anonymous]

Hi palmiris,

Laptops are embedded systems and they usually don't provide with the option to upgrade the system. The laptop manufacturer can tell you if 3rd gen processors are supported by the BIOS of your laptop.

Regards,

Mike C

[idata]

Thanks for the reply. I guess QM67 chipset is the blame which only supports i5-3610me and i7-3610qe third gen cpus but these cpus have the widi disabled so they are useless to me. So I guess I have to upgrade with second gen i7 which have 1600 mhz support in order to speed up GPU (I will pass on the higher bus support. More power needed - 45watt vs 35watt. I will have to get the manufacturer recommended upgrade which is i7 2640m though clocked at 1333 mhz).

IMPORTANT:

Do you have plans for better windows 8.1 x64 driver for intel hd 3000????. The D3D WEI score (5) is low compared to windows 8.0 D3D WEI score (6.3).

I think that windows 8.1 HD 3000 driver is not competent enough in 3D compared to windows 8.0. Something wrong with wddm 1.2 driver in windows 8.1 or again it could be a directX d3d dll problem. Do you plan to offer a driver update to rectify the low D3D WEI score?

Can you please give us a windows 8.1 gpu x64 driver cure????

Happy Christmas.

[Anonymous]

Hi palmiris,

The processor is still under support and warranty, so Intel might be launching a newer graphics driver in the next months.

Regards,

Mike C

[idata]

Hello Mike C,

I take you responds as a confirmation to the win 8.1 D3D performance issue.

I hope then that Intel will succeed in finding a cure for the D3D performance issue, by utilizing the necessary intel resources for preparing a x64 win 8.1 driver for Intel HD 3000 for better D3D performance, similar to win 8.0/7.0 D3D WEI score (x64).

I agree with the fellow intel HD 3000 users: "So I must conclude these drivers are not using the DX10 functionality under Windows 8.1 64"

Still waiting for intel/Microsoft to find a solution for running a winsat benchmark and fixing the DX10/Intel HD 3000 driver under windows 8.1 x64 bit.

First thing I would check.

1. WinSAT is skipping the DirectX 10 tests because it checks whether the Driver Model version is exactly "1.2". Note that the Windows 8 driver model is 1.2, and the Windows 8.1 driver model is 1.3. So the check should really be whether the windows driver model is >= 1.2.

2. D3D DX10 test is running fine under passmark performance test. However I could not get directcompute to run in passmark perf test with intel hd 3000 (direct compute 4.1 compatible) in windows 8.1. Also directcompute is disabled in GPU-Z, and also disabled in DirectComputeBenchmark_v0_45b.

DirectCompute is supported on DX10 class devices if only drivers support it. Latest intel HD 3000 driver does not support Directcompute in windows 8.1.

It seems that intel never produced a hardware compatible driver under windows 8.1. It only works in compatibility-legacy mode which is very disappointing for the Intel high quality company image. I am really disappointed with intel driver support for intel HD 3000.