topic Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test in Graphics

Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

idata — Tue, 12 Jan 2016 00:20:38 GMT

I have a problem with winsat test in windows 8.1 (x64). It skips d3d dx10 test. I also get this error message in winsat.log "Driver is not WDDM 1.1 or WDDM 1.2; aborting DX10 assessment" . Here are my log files. Please I hope that you can find a solution.

Hardware info: (msinfo32.exe)

Windows 8.1 Pro 6.3.9600

Hardware Abstraction Layer Version = "6.3.9600.17196"

Intel HD graphics 3000

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

Installed Drivers igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumd32,igd10umd32,igd10umd32

Driver Version 9.17.10.4229

INF File oem46.inf (iSNBM0 section)

Resolution 1600 x 900 x 50 hertz

Memory Address 0xA0000000-0xA03FFFFF

Memory Address 0x90000000-0x9FFFFFFF

I/O Port 0x00005000-0x0000503F

IRQ Channel IRQ 4294967292

I/O Port 0x000003B0-0x000003BB

I/O Port 0x000003C0-0x000003DF

Memory Address 0xA0000-0xBFFFF

Driver c:\windows\system32\drivers\igdkmd64.sys (9.17.10.4229, 5.13 MB (5,384,176 bytes), 01/06/2015 22:00)

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

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...

Re: Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

Amy_C_Intel — Wed, 13 Jan 2016 15:04:04 GMT

Hello, palmiris:

We have not received cases like the one that you mentioned. However; I found this forum in Microsoft site http://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/windows-81-pro-winsat-problems/0d8f8ac2-f361-44f6-bea1-748fe9363f9e?db=5&auth=1 Windows 8.1 Pro - WinSat Problems - Microsoft Community maybe could be helpful.

Regards,

Amy.

Re: Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

idata — Wed, 13 Jan 2016 15:26:01 GMT

Hello,

Did you test to verify if same problem exists with all intel HD 3000 graphics and windows 8.1 x64 systems.????? if you don't test how do you know it is not a graphics card driver related problem with windows 8.1 which is Intel's responsibility to provide a fix.?????

I did not have any issues with windows 8.0.

Please report findings.

Your answer does not enclose any relevant evidence if this problem is replicated or not and if yes why and how in order to fix.

Thanks.

Re: Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

Amy_C_Intel — Thu, 14 Jan 2016 17:35:33 GMT

I ran some tests based on your description but the error did not occurred.

Bear in mind that WinSAT is a module of Microsoft this is not related with the Intel® HD Graphics driver, this will help to match the computer hardware performance with the performance requirements of software.

I would recommend contacting Microsoft in order to address this matter https://support.microsoft.com/en-us/contactus?wa=wsignin1.0 Contact Us.

Regards,

Amy.

Re: Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

idata — Thu, 14 Jan 2016 18:21:58 GMT

Dear Amy,

Hello,

Thanks for the reply and performing a winsat test. I do appreciate this response.

However

1. It would have helped if you posted the winsat.log and latest Formal.Assessment (Recent).WinSAT.xml so that I can compare. In case you still have it please can I have them for private use (comparison purpose)??

2 I have run a clean boot but without the microsoft services selected. I will select all of them again just to test if a microsoft service is causing this issue.

I will keep you posted if any changes occur, which I doubt. I have all latest bios- chipset driver and all other hardware drivers are the newest and all recognised. I am at a dead end. I am thinking of downgrading as a last option..

Regards

Panayiotis

Re: Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

idata — Thu, 14 Jan 2016 21:30:09 GMT

Amy,

I have uninstalled antivirus I have disabled all start-up programs, I have disabled all services including those of Microsoft except power service which is needed and winsat d3d -dx10 still skips the test.

Clean boot does not work either. So it is not a service or a program interference I reckon.

Any suggestions????

If winsat cannot run the test is it because the driver is missing a feature which is not enabled in order to run the winsat d3d -dx10 test?? ???? It is something wrong with windows 8.1 which is wddm 1.3 but intel hd 3000 driver is legacy under windows 8.1 since it is using a wddm 1.2 driver as intel failed to develop the driver to fully support windows 8.1???? It is never late to create a wddm 1.3 driver to fully support windows 8.1 and correct issues caused with incompatibilities. Most features are working including widi. You just have to copy intel hd 4000 graphics card driver (except the direct X features) and create the intel hd 3000 wddm 1.3 driver.

If you have an intel hd 3000 driver under production / beta I am willing to test.

Regards

Panayiotis

Request

Please bring this request for further developing intel hd 3000 in order to fully support windows 8.1 or windows 10 or both (wddm 1.3 and or wddm 2.0) to the attention of the management.

Re: Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

Amy_C_Intel — Fri, 15 Jan 2016 17:05:33 GMT

I have tested this behavior on Windows® 8.1 and Intel® HD Graphics 3000 including the latest drivers and the issue did not occurred.

The latest driver available for this graphics controller is 4229, at the moment we do not have information that Intel will be developing more drivers for Intel® HD Graphics 3000 for Windows 8.1. In regard to Windows 10, this graphics controller does not support this operating system, note the picture below;

With Windows® 10 and Intel® HD Graphics 3000 there are no plans no develop new driver, however you should be able to find driver through Windows Updates.

Let me try to test this one more time but this time guide me in how to reproduce this; please include all the steps that you are following to run this test, feel free to add all details you want.

Regards,

Amy.

Re: Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

idata — Fri, 15 Jan 2016 20:17:30 GMT

Dear Amy,

in windows 8.1 x64 there is no WEI benchmark app. It was removed. However you can run the same test on command mode (cmd.exe) as administrator.

in command mode write

winsat d3d

(winsat d3d -dx10)

the dx9 tests run fine

the dx10 tests are skipped since they don't display a value other than 0.

winsat.log and Formal.Assessment (Recent).WinSAT.xml are found in windows/perormance directory

Also when reading winsat.log you will observe the following"Driver is not WDDM 1.1 or WDDM 1.2; aborting DX10 assessment , next to d3d dx10 test. (check my winsat log)

From winsat.log

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

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

396265 (6816) - exe\processresults.cpp:1547: No D3D10 Subscore. Using D3D9 subscore for final D3D score.

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

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

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

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

Why PNPID = ROOT\Basic Display??????????????????????????????????????

there is no call for PNPID from DX10 call why?????????????

Please test as above.

Do you think the problem is in this registry where basic display is set?????? or any other setting which is installed wrongly by the driver??? Here are the registry current display settings: Do you think it is easy to have a look? Something with device 0 is not correct igfx is calling it intel hd 3000 whereas it is also a basic display registry too. Thanks

[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\VIDEO]

"\\Device\\Video0"="\\Registry\\Machine\\System\\CurrentControlSet\\Control\\Video\\{0AA4DC11-7E28-4708-8B59-2C1D6B3D6C6D}\\0000"

"MaxObjectNumber"=dword:00000002

"ObjectNumberList"=hex:00,00,00,00,01,00,00,00,02,00,00,00

"\\Device\\Video1"="\\Registry\\Machine\\System\\CurrentControlSet\\Control\\Video\\{0AA4DC11-7E28-4708-8B59-2C1D6B3D6C6D}\\0001"

"\\Device\\Video2"="\\REGISTRY\\MACHINE\\SYSTEM\\ControlSet001\\Services\\BasicDisplay"

"\\Device\\Disc"="\\REGISTRY\\Machine\\System\\CurrentControlSet\\Services\\TSDDD\\Device0"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BasicDisplay]

"ImagePath"=hex(2):5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\

74,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,72,\

00,69,00,76,00,65,00,72,00,73,00,5c,00,42,00,61,00,73,00,69,00,63,00,44,00,\

69,00,73,00,70,00,6c,00,61,00,79,00,2e,00,73,00,79,00,73,00,00,00

"Type"=dword:00000001

"Start"=dword:00000001

"ErrorControl"=dword:00000000

"Group"="Video"

"Tag"=dword:00000004

"Owners"=hex(7):64,00,69,00,73,00,70,00,6c,00,61,00,79,00,2e,00,69,00,6e,00,66,\

00,00,00,62,00,61,00,73,00,69,00,63,00,64,00,69,00,73,00,70,00,6c,00,61,00,\

79,00,2e,00,69,00,6e,00,66,00,00,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BasicDisplay\Device0]

"Device Description"="Microsoft Basic Display Adapter"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BasicDisplay\Video]

"Service"="BasicDisplay"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BasicDisplay\Enum]

"0"="ROOT\\BasicDisplay\\0000"

"Count"=dword:00000001

"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BasicDisplay\VolatileSettings]

"{5b45201d-f2f2-4f3b-85bb-30ff1f953599}"=hex:5c,00,3f,00,3f,00,5c,00,52,00,4f,\

00,4f,00,54,00,23,00,42,00,61,00,73,00,69,00,63,00,44,00,69,00,73,00,70,00,\

6c,00,61,00,79,00,23,00,30,00,30,00,30,00,30,00,23,00,7b,00,35,00,62,00,34,\

00,35,00,32,00,30,00,31,00,64,00,2d,00,66,00,32,00,66,00,32,00,2d,00,34,00,\

66,00,33,00,62,00,2d,00,38,00,35,00,62,00,62,00,2d,00,33,00,30,00,66,00,66,\

00,31,00,66,00,39,00,35,00,33,00,35,00,39,00,39,00,7d,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BasicRender]

"ImagePath"=hex(2):5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\

74,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,72,\

00,69,00,76,00,65,00,72,00,73,00,5c,00,42,00,61,00,73,00,69,00,63,00,52,00,\

65,00,6e,00,64,00,65,00,72,00,2e,00,73,00,79,00,73,00,00,00

"Type"=dword:00000001

"Start"=dword:00000001

"ErrorControl"=dword:00000000

"Group"="Video"

"Tag"=dword:00000003

"Owners"=hex(7):62,00,61,00,73,00,69,00,63,00,72,00,65,00,6e,00,64,00,65,00,72,\

00,2e,00,69,...

Re: Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

Amy_C_Intel — Mon, 18 Jan 2016 16:36:37 GMT

Thank you for the information.

Please include dxdiag report, in the "Run" window, type "dxdiag" and click OK. A "DirectX Diagnostic Tool" window should pop up. In the window that has now appeared choose "Save all information" After you've saved the file, please attach here.

I would also like to know, what is the purpose of running this test? What are you trying to get from it?

Regards,

Re: Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

idata — Mon, 18 Jan 2016 19:06:22 GMT

Hello Amy,

I am testing intel hd 3000 (2nd gen i5-2520m) in windows 8.1 to see if it a good upgrade option from windows 8.0 (previous I had windows 7.0). So my tests are to see if:

1. graphics related performance of intel hd 3000 in windows 8.1 is similar to windows 8.0

2. All graphics related performance tests are run successfully

3. there are no driver issues with compatibility mode as windows 8.1 is wddm 1.3 and intel hd 3000 driver is 1.2

4. widi is working as good as windows 8.0

For the moment I have two problems:

1. 2D graphics (desktop) performance test is lower in Windows 8.1 than windows 8.0 (20%) (also tested with passmark performance test)

2 Winsat test skips run d3d -dx10 test

DxDiag.txt file as requested.

Thanks

Panayiotis

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

System Information

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

Time of this report: 1/18/2016, 21:14:48

Machine name: T420_4236_B87

Operating System: Windows 8.1 Pro 64-bit (6.3, Build 9600) (9600.winblue_ltsb.151230-0600)

Language: English (Regional Setting: English)

System Manufacturer: LENOVO

System Model: 4236B87

BIOS: Default System BIOS

Processor: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz (4 CPUs), ~2.5GHz

Memory: 8192MB RAM

Available OS Memory: 8012MB RAM

Page File: 2335MB used, 6955MB available

Windows Dir: C:\WINDOWS

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: 96 DPI (100 percent)

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

DxDiag Version: 6.03.9600.17415 64bit 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 Type: Full Device

Device Key: Enum\PCI\VEN_8086&DEV_0126&SUBSYS_21CE17AA&REV_09

Display Memory: 1760 MB

Dedicated Memory: 128 MB

Shared Memory: 1632 MB

Current Mode: 1600 x 900 (32 bit) (60Hz)

Monitor Name: LCD 1600x900

Monitor Model: unknown

Monitor Id: LEN40A1

Native Mode: 1600 x 900(p) (60.020Hz)

Output Type: Internal

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

Driver File Version: 9.17.0010.4229 (English)

Driver Version: 9.17.10.4229

DDI Version: 10.1

Feature Levels: 10.1,10.0,9.3,9.2,9.1

Driver Model: WDDM 1.2

Graphics Preemption: DMA

Compute Preemption: DMA

Miracast: Not Supported by Graphics driver

Hybrid Graphics GPU: Not Applicable

Power P-states: Not Applicable

Driver Attributes: Final Retail

Driver Date/Size: 5/26/2015 21:00:24, 12694808 bytes

WHQL Logo'd: Yes

WHQL Date Stamp:

Device Identifier: {D7B78E66-4266-11CF-9F64-C401B7C2C435}

Vendor ID: 0x8086

Device ID: 0x0126

SubSys ID: 0x21CE17AA

Revision ID: 0x0009

Driver Strong Name: oem47.inf:5f63e534992ddd9e:iSNBM0:9.17.10.4229:pci\ven_8086&dev_0126

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)=...

Re: Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

idata — Thu, 21 Jan 2016 12:34:31 GMT

Amy I am double posting this at intel web site

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

created by Cesar Badilla in Graphics - /message/366674# 366674 View the full discussion

I think I may have identified a problem.

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

2. I may have installed Mar09 redistribution before 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.

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

Re: Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

idata — Fri, 22 Jan 2016 18:04:13 GMT

Ok I have identified the problem.

This information is missing from dxdiag

BIOS: 83ET76WW (1.46 )

Windows 8.0 which I have just installed has it.

here is the dxdiag from windows 8.0 as a comparison with my previous post.

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

System Information

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

Time of this report: 1/22/2016, 18:47:36

Machine name: T420-4236-B87

Operating System: Windows 8 Pro 64-bit (6.2, Build 9200) (9200.win8_rtm.120725-1247)

Language: Greek (Regional Setting: Greek)

System Manufacturer: LENOVO

System Model: 4236B87

BIOS: 83ET76WW (1.46 )

Processor: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz (4 CPUs), ~2.5GHz

Memory: 8192MB RAM

Available OS Memory: 8012MB RAM

Page File: 2255MB used, 10364MB 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

This makes me believe that an upgrade from windows 7.0 is not the correct way to install windows 8.1. A clean installation is probably the best way otherwise problems arise with direct3D -dx10.

I will not install windows 8.1 as windows 8.0 is probably the best operating system for the intel hd 3000.

I dont think that it is a driver problem.

It is either:

1. an installation upgrade bug. A clean installation is needed (advanced installation by deleting all locations in order for the system to create new installation locations)

2. A bios incompatibility with windows 8.1

Intels driver is working fine.

Sorry for the trouble.

Re: Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

Amy_C_Intel — Mon, 25 Jan 2016 17:44:33 GMT

palmiris, Thank you for your feedback. I am glad to hear that you were able to identified this issue. I am sure that this post will help other users with similar issues.

Regards,

Re: Intel HD 3000 Windows 8.1 (x64) and WINSAT D3D -dx10 test

idata — Mon, 25 Jan 2016 18:12:11 GMT

Here is the WEI score under Windows 8. It rocks.

I recommend for people who update windows 7 to windows 8.1 to do a clean installation. Just to make sure check the winsat d3d -dx10. If this test fails do a clean installation and if this still persists ask for a windows 8.1 bios compatible update.

This thread I assume it is now answered. I agree that many users have this problem. I hope this thread is helpful to them too.

Regards

Panayiotis