Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: new GTX-Titan box fails 'Windows Experience' & has jerky window drags?


14 Apr 2013   #1

Win7 Pro 64
 
 
new GTX-Titan box fails 'Windows Experience' & has jerky window drags?

I've got a new dual Xeon SuperMicro X9DAi box box with 128GB Crucial ECC RAM with a Titan and a Corsair AX1200i.

After installing all the drivers (latest motherboard BIOS, latest nVidia drivers, chipset drivers) & all Microsoft updates, I noticed that dragging any window across the screen was jerky and was leaving trails.

My first testing was on a 2560 x 1440 DELL U2713HM connected thru Display Port.

I've also tried DVI connectors with two other monitors, it acts the same.

Here are the logs from my Windows Experience, which fails with the useful error msg of 'The Windows Experience Index for your system could not be computed. Could not measure system memory performance."

Dragging a window on my 3 year old X8DAE with a GTX-580 is flawless. This box is about 3x faster and the video card is 2 generations later?

1186340 (3160) - winsat\logging.cpp:0815: --- START 2013\4\14 21:42:08 PM ---
1186340 (3160) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\winsat.exe" formal -cancelevent 80aa14d0-d7c1-42af-92d3-492a75bb5624
1186340 (3160) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured
1186340 (3160) - winsat\main.cpp:4474: > IsFormal=TRUE IsMoobe=FALSE.
1186387 (3160) - winsat\main.cpp:4585: Watch dog system enabled
1186387 (3160) - winsat\main.cpp:4600: Main watch dog timer set to 600.0 seconds
1186450 (3160) - winsat\main.cpp:2505: > DWM not running.
1186450 (3160) - winsat\main.cpp:2470: > EMD service will be restored on exit.
1186808 (3160) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
1186808 (3160) - winsat\main.cpp:2793: > power policy saved.
1186824 (3160) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
1186824 (3160) - winsat\main.cpp:2814: > power policy set to maximum.
1187651 (3160) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance
1187666 (3160) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE
1187666 (3160) - winsat\main.cpp:1775: > Run Assessment features
1187791 (3160) - 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
1215949 (3160) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0
1215949 (3160) - winsat\main.cpp:2037: > DWM Assessment results processing SUCCESS
1215949 (3160) - 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)
1223188 (3160) - 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)
1230317 (3160) - 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
1237618 (3160) - 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
1248866 (3160) - 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)
1255574 (3160) - winsat\main.cpp:1775: > 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)
1269723 (3160) - winsat\main.cpp:1775: > 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
1277273 (3160) - winsat\main.cpp:1775: > 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
1283872 (3160) - winsat\main.cpp:1775: > 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
1293747 (3160) - winsat\main.cpp:1775: > 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
1302748 (3160) - winsat\main.cpp:1775: > 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
1309846 (3160) - winsat\main.cpp:1775: > Run Assessment mfmedia -input C:\Windows\Performance\WinSAT\winsat.wmv -nopmp
1312717 (3160) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_1080_5sec_MPEG2_HD_15mbps.mpg -dshow -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 270 -expfrmmax 300 -overrideframetype int2fps
1321422 (3160) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_1080_5sec_VC1_15mbps.wmv -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog
1338769 (3160) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_480i_5sec_6mbps_new.mpg -dshow -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 270 -expfrmmax 300 -overrideframetype int2fps
1347801 (3160) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_480p_5sec_6mbps_new.mpg -dshow -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog
1356413 (3160) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_1080_5sec_10mbps_h264.mp4 -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog
1364837 (3160) - winsat\main.cpp:1775: > Run Assessment mediaex -input C:\Windows\Performance\WinSAT\Clip_480_5sec_6mbps_h264.mp4 -video offscreen -audio mute -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 270 -expfrmmax 300 -overrideframetype int2fps
1373776 (3160) - winsat\main.cpp:1775: > Run Assessment media -input C:\Windows\Performance\WinSAT\winsatencode.wmv -encode C:\Windows\Performance\WinSAT\winsat.prx
1385008 (3160) - winsat\main.cpp:1775: > Run Assessment moobego
1385054 (3160) - winsat\main.cpp:1775: > Run Assessment cpu -encryption -up
1388206 (3160) - winsat\main.cpp:1775: > Run Assessment cpu -compression -up
1398236 (3160) - winsat\main.cpp:1775: > Run Assessment cpu -encryption2 -up
1401310 (3160) - winsat\main.cpp:1775: > Run Assessment cpu -compression2 -up
1411325 (3160) - winsat\main.cpp:1775: > Run Assessment cpu -encryption
1421902 (3160) - winsat\main.cpp:1775: > Run Assessment cpu -compression
1432900 (3160) - winsat\main.cpp:1775: > Run Assessment cpu -encryption2
1445661 (3160) - winsat\main.cpp:1775: > Run Assessment cpu -compression2
1461245 (3160) - winsat\main.cpp:1775: > Run Assessment mem
1461245 (3160) - winsat\main.cpp:1890: ERROR: Could not start assessment.
1461308 (3160) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0
1461308 (3160) - winsat\processresults.cpp:0962: > Wrote cpu expression compression score to the registry 269
1461308 (3160) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DWM performance score
1461308 (3160) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0
1461323 (3160) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
1461323 (3160) - winsat\main.cpp:2855: > Power state restored.
1461323 (3160) - winsat\main.cpp:2870: > Successfully reenabled EMD.
1461339 (3160) - winsat\main.cpp:2896: > Composition restarted
1461339 (3160) - winsat\watchdog.cpp:0311: Watch dog system shutdown
1461339 (3160) - winsat\main.cpp:4909: > exit value = 1.


My System SpecsSystem Spec
.

15 Apr 2013   #2

Windows 7 Ultimate Retail Box (64-bit installed) + Service Pack 1
 
 

I never update a brand new PC until I've tried it out of the box for a day or two, so I have some baseline comparison, performance wise.

Never heard of that hardware, so I am going to surmise that you need to fall back on the video and the chipset drivers and see if those work, based on those winsat messages, that is where I would begin.

Wondering if you need very specific drivers, and not just the normal Nvidia suite when upgrading that new monster card, that would mess ya up for sure if the case.
My System SpecsSystem Spec
15 Apr 2013   #3

Win7 Pro 64
 
 

I resolved the problem of the jerkiness by setting optimal defaults in the SuperMicro BIOS. I guess I'd turned off something I thought I wouldn't need that caused issues. However, the 'Windows Experience' still fails with "Could not measure system memory performance." I have 128GB of Crucial ECC RAM and tested overnight with both MemTest86 and MemTest86+. I would like to get that working, as it's annoying to have it fail out of the box?
My System SpecsSystem Spec
.


15 Apr 2013   #4

Win7 Home Premium 64x
 
 

can you do a winsat mem test instead of the WIE score?

enter command prompt as administrator and type "winsat mem" and it will give you the throughput of your RAM.
My System SpecsSystem Spec
Reply

 new GTX-Titan box fails 'Windows Experience' & has jerky window drags?




Thread Tools



Similar help and support threads for2: new GTX-Titan box fails 'Windows Experience' & has jerky window drags?
Thread Forum
Window 7 Start-Up Repair completes but window fails to boot. General Discussion
RDC window fails to close Network & Sharing
Migrating to a new MOBO, W7 "system out of box experience" fails Installation & Setup
Trouble with experience window rating Hardware & Devices
Windows Experience Index Fails General Discussion
nVidia issues & My not so smooth Window 7 experience. Graphic Cards
Experience Index fails Performance & Maintenance

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:07 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33