WinSAT Crashing on Direct3D 10 ALU Step

I have a new M11xR2 that I just finished clean installing Windows 7 on following BatBoy's procedure. However, I cannot run the WinSAT without it crashing on the Direct3D 10 ALU assessment step. I am running the latest Nvidia drivers (267.76) and the latest Intel HD Graphics drivers (8.15.10.2321). Anyone know how to fix this?

 

I had the same error with the same driver combo. I ended up going to windows/performance/winsat/datastore and deleting all the previous runs. I also looked at the log file in the winsat folder, which indicated a power scheme setting so I went command center and made sure everything was hi-performance for AC as that is how I have it set. After doing that, no problem running WinSAT:

Here is my log for the error run:

20401467 (12192) - winsat\logging.cpp:0815: --- START 2011\3\27 9:25:19 AM ---
20401467 (12192) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\winsat.exe" formal -cancelevent 4dc7d016-3aaf-4916-92b5-70c85f1b89cf
20401467 (12192) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured
20401483 (12192) - winsat\main.cpp:4474: > IsFormal=TRUE IsMoobe=FALSE.
20401529 (12192) - winsat\main.cpp:4585: Watch dog system enabled
20401529 (12192) - winsat\main.cpp:4600: Main watch dog timer set to 600.0 seconds
20402247 (12192) - winsat\main.cpp:2490: > DWM Running.
20403869 (12192) - winsat\main.cpp:2497: > turning off DWM.
20403885 (12192) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
20403885 (12192) - winsat\main.cpp:2793: > power policy saved.
20403963 (12192) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
20403963 (12192) - winsat\main.cpp:2814: > power policy set to maximum.
20404696 (12192) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance
20404696 (12192) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE
20404696 (12192) - winsat\main.cpp:1775: > Run Assessment features
20405461 (12192) - winsat\main.cpp:1775: > Run Assessment dwm -aname DWM -time 10 -fbc 10 -disp off -normalw 12 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock
20419017 (12192) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 1444080
20419017 (12192) - winsat\main.cpp:2037: > DWM Assessment results processing SUCCESS
20419033 (12192) - winsat\main.cpp:1775: > Run Assessment d3d -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)
20426583 (12192) - winsat\main.cpp:1775: > Run Assessment d3d -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)
20433244 (12192) - winsat\main.cpp:1775: > Run Assessment d3d -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
20440389 (12192) - winsat\main.cpp:1775: > Run Assessment d3d -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
20447456 (12192) - winsat\main.cpp:1775: > 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)

21619367 (10596) - winsat\logging.cpp:0815: --- START 2011\3\27 9:45:37 AM ---
21619367 (10596) - winsat\main.cpp:2861: > no need to restore power state (no saver object).
21619367 (10596) - winsat\main.cpp:2873: > Not necessary to reenable EMD cache.
21619382 (10596) - winsat\main.cpp:4909: > exit value = 4.

 

Thank you. Deleting all of the old WinSAT runs did the trick. However, I'm getting a graphics score of 3.3 now when I was receiving a 3.5 out of the box from Dell. I wonder if the latest Intel driver is crap...

 

So I re-ran the WinSAT and now I get a 3.4...The Intel Graphics score is dynamic for some reason...

 

Ahh... where were guys when we were talking about this in the 267.76 thread? It was also mentioned that with the 267.76 drivers, it won't save the changes when you modify your power plan. It will always set it to "high performance."