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

[idata]

winsat d3d -dx10 (part of formal.assessment (initial).winsat.xml)

DXVersion="9">240.17999

DXVersion="9">236.21001

DXVersion="9">79.38000

DXVersion="9">72.56000

DXVersion="10">0.00000

DXVersion="10">0.00000

DXVersion="10">0.00000

DXVersion="10">0.00000

DXVersion="10">0.00000

DXVersion="10">0.00000

DXVersion="10">0.00000

Here is the result of runing winsat d3d -dx10 commad (or winsat prepop or winsat formal)

Here is the winsat.log

49316765 (1072) - exe\logging.cpp:0841: --- START 2016\1\6 18:38:46 ---

49316765 (1072) - exe\main.cpp:4511: WinSAT registry node is created or present

49316765 (1072) - exe\main.cpp:4542: Command Line = winsat d3d -dx10

49316765 (1072) - exe\main.cpp:4314: INFO: The axe results path environment variable is not set. Assuming we aren't running under AXE.

49316765 (1072) - exe\main.cpp:4649: INFO: Winsat is not running in AXE mode.

49316765 (1072) - exe\processwinsaterror.cpp:0146: ERROR: tried to read resource strings, unknown exception occured

49316781 (1072) - exe\main.cpp:2615: > DWM Running.

49316781 (1072) - exe\main.cpp:2622: > turning off DWM.

49316781 (1072) - exe\syspowertools.cpp:0983: > Read the active power scheme as '8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'

49316781 (1072) - exe\main.cpp:2923: > power policy saved.

49316828 (1072) - exe\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'

49316828 (1072) - exe\main.cpp:2944: > power policy set to maximum.

49317093 (1072) - exe\main.cpp:0867: > WinSAT info: Version=V6.3 Build-9600.17415

49317109 (1072) - exe\main.cpp:1007: > IsOfficial=TRUE IsFormal=FALSE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE

49317109 (1072) - exe\main.cpp:4125: > Power 'execution' request successfully set.

49317109 (1072) - exe\main.cpp:1852: > Run Assessment features

49317109 (1072) - common\winsatutilities.cpp:1060: PNPID from DX9 call = PCI\VEN_8086&DEV_0126&SUBSYS_21CE17AA&REV_09

49317109 (1072) - common\winsatutilities.cpp:1126: Index [0]: PNPID = PCI\VEN_8086&DEV_0126&SUBSYS_21CE17AA&REV_09

49317109 (1072) - common\winsatutilities.cpp:1150: Matching device PnPID is PCI\VEN_8086&DEV_0126&SUBSYS_21CE17AA&REV_09

49317109 (1072) - common\winsatutilities.cpp:1126: Index [1]: PNPID = ROOT\BasicDisplay

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

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

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

49317109 (1072) - 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)

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

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

49317109 (1072) - 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

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

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

49317109 (1072) - 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

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

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

49317125 (1072) - 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

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

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

49317125 (1072) - 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

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

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

49317125 (1072) - 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

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

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

49317125 (1072) - exe\main.cpp:4164: > Power request 'execution' successfully cleared.

49317140 (1072) - exe\processwinsaterror.cpp:0319: Writing exit code, cant msg and why msg to registry

49317203 (1072) - exe\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'

49317203 (1072) - exe\main.cpp:2985: > Power state restored.

49317203 (1072) - exe\main.cpp:3003: > Not necessary to reenable EMD cache.

49317203 (1072) - exe\main.cpp:5204: > exit value = 0.

Please verify and profuce a fix. (Windows 7.0 & 8..0 x64 had no problems with d3d dx10 tests).

<...

[Cesar_B_Intel]

Hello palmiris,

Thanks for sharing the information about part of the formal.assessment (initial).winsat.xml.

We continuously strive to improve the quality of our products to better serve our users and appreciate feedback on any issues you discover and suggestions for future driver releases.

Please refer to http://www.intel.com/content/www/us/en/support/graphics-drivers/000005526.html Supported Operating Systems for Graphics Drivers and https://downloadmirror.intel.com/24970/eng/ReleaseNotes_GFX_15.28.24.4229.pdf https://downloadmirror.intel.com/24970/eng/ReleaseNotes_GFX_15.28.24.4229.pdf

Regards,

Caesar B_Intel.

[idata]

Hello,

Thanks for the reply. Looking forward for an Intel HD 3000 driver fix for windows 8.1 x64 regarding winsat d3d -dx10 test which is skipped.

Notes

1. For the history I do have latest Intel HD 3000 driver installed (15.28.24.4229)

2. Ref. your diagram I think openCL 1.1 is supported (but not 1.2). probably not the Microsoft certified driver which has only necessary windows support.

3. directcompute (i think 4.1) was able to run with dxcpl command wrap (passmark performance test 4 exe files). so it must be supported too indirectly. It should somehow be automated to run under directx 11.2 without the wrap command.

from msinfo32 --- Display

PNP Device ID PCI\VEN_8086&DEV_0126&SUBSYS_21CE17AA&REV_09\3&21436425&0&10

[Cesar_B_Intel]

Hello palmiris,

Thanks for sharing this information.

Please allow me more time to provide you with more information about this particular issue.

Regards,

Caesar B_Intel.

[idata]

Thanks for working on this issue.

[idata]

Hi Caesar,

Is there any news about Intel HD Graphics 3000 driver and winsat d3d -dx10 test which is skipped in windows 8.1 x64?

Kind regards,

Panayiotis

[Cesar_B_Intel]

Hello palmiris,

I am sorry for the delayed response. I appreciate your patience. However, I do not have any updates yet.

Regards,

Caesar B_Intel.

[idata]

Hello Caesar,

You are my last hope before downgrading windows 8.1 to windows 8.0 which will make my day a mess. I will wait as long as it takes.

Thanks

Panayiotis

[Cesar_B_Intel]

Hello palmiris,

Thank you for your patience. As soon as I have an update I will definitely let you know.

Regards,

Caesar B_Intel.

[idata]

Hello Caesar,

Thanks for letting me know that intel is still investigating this matter.

Regards

Panayiotis

[idata]

I think I may have identified a problem.

1. I have a june 2010 directX installation on my laptop which I cannot uninstall for the moment.

2. I may have installed also Mar09 redistribution before installing the june 2010 directX redistribution

3. I did find the following registry entry

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectX]

"Version"="4.09.00.0904"

"InstalledVersion"=hex:00,00,00,09,00,00,00,00

"MinFeatureLevel"=dword:0000a100 (41216)

"MaxFeatureLevel"=dword:0000a100 (41216)

"SDKVersion"="9.29.1962.0"

The registry maybe forcing directX 9.0

So I think my registry must be corrupt with directX 9.0 even though sfc /scannow does not recognise an error and chkdsk /r does not recognise an error.

Do you know if I can correct the registry in order to use directX 11.2 (so it would also use 10.1)?????? in order to test if possible?

.

..

...

continuation

I have uninstalled all previous directX drivers (by reinstalling and uninstalling since I could not remove it).

Still same problem remains. I have reinstalled intel hd 3000 latest intel driver. Still the problem remains.

Did you manage to recreate the issue by any chance??? Is it a driver problem with windows 8.1 due to compatibility mode driver installation.??? (Windows 8.1 is wddm 1.3 whereas intel hd 3000 driver is wddm 1.2)

Thanks

[Cesar_B_Intel]

Hello palmiris,

You could try registry modifications on your own discretion.

Have you tried chkdsk /f and /X?

I suggest uninstalling DirectX* using http://www.revouninstaller.com/revo_uninstaller_free_download.html Revo Uninstaller* to make sure any "leftovers" are removed, too. Then proceed to install the DirectX* version you want to test.

Regards,

Caesar B_Intel.

*Other names and brands may be claimed as the property of others.

[idata]

Hello,

Thanks for the recommendation.

I have uninstalled previous versions of directX. Winsat d3d -dx10, stills skips the test.

Did Intel manage to reproduce this problem???? The reason for asking is because I will proceed with a clean installation of either windows 8 or windows 8.1 depending on winsat ability to run all tests. I dont want to spend more time on windows 8.1 clean installation and finding out that this problem still remains.

Is it possible to inform me if intel managed to recreate the same winsat problem on windows 8.1 x64 pro with intel hd 3000?? If yes will there be a fix on either intel or MS side depending who has the bug code???

Thanks.

Subsequent post:

Dear Cesar

I have installed Windows 8.0 (not windows 8.1).

I have observed the following:

In DXdiag summary report the bios information in the windows 8.1 is different that the windows 8.0.

So the problem must come from the windows 7 update to windows 8.0 to windows 8.1.

Carrying out a clean installation of windows 8.0 there is no problem.

so it must be an upgrade problem. A clean installation sorts out the problem for windows 8.0.

I will not carry out an update for windows 8.1 however with this method I have concluded that the problem must be either

1. The upgrade process creates problems within windows and a clean installation is needed

2. A bios incompatibility with windows 8.1.

Thus the intel hd 3000 driver problem I encountered in windows 8.1 must not stem from the driver itsleft but must stem from the windows direct update method rather than a clean installation (or maybe a bios incompatibility with the newer operating system).

I will close the case, I opened, after your reply.

Thanks for the assistance.

[DKing4]

I just noticed this as I was lurking around looking for more driver information on my 3630qm I-7.

I can confirm the first part of what you're saying and thank you for the second part!

It makes sense now that the driver came from.....well actually mine came from Toshiba due to the fact they're all kinds of awesome. So I'm getting Miracast and WiDi, albeit with constant disconnects, thus my looking for more info.

Thanks again, that helps a lot!

[idata]

What is the use then if you are getting disconnects?? With windows 8 and 8.1 I do not get any disconnects and I am using an i5-2520m and an i7-2640m with intel hd 3000. Upgrade firmware of miracast hdmi dongle in case you havent. My hdmi dongle has an external antenna for better stronger signal. Also most importsnt point get 1amp 5v ac/dc usb power supply for the hdmi dongle. The usb Tv power supply is in most cases insufficient causing instability and disconnections.

[DKing4]

Thank you SO much!

I don't know if it was updating the firmware or changing to a dedicated power supply but I haven't got a disconnect in about 6 hours and counting.

http://www.highgeekly.com/mobile/Windows/microsoft-band-2-gets-another-small-firmware-update.f/microsoft-issues-small-firmware-update-for-wireless-display-adapter.html Microsoft issues small firmware update for Wireless Display Adapter - Mobile - HighGeekly

[idata]

You are lucky I answered even though you were not referring to me. Glad I could help you sort out your widi problem. I don't think intel would answer you

I had the same problem so I went through the same route to find a fix.

Regards

Panayiotis

[Anonymous]

Hi palmiris,

Thank you for your suggestion.

Regards,

Mike C

[idata]

You are welcome mikec_intel. Glad I have helped..