Ref: https://i.imgur.com/xExUG1Y.jpg

It has been years since I tested this (rating had been 7.3 but decided
to re-run the rating. For unknown reasons, it reports some sort of
interference (and suggests a driver.) However, Device Manager shows no
driver issues See link above.

Could test no longer work due the Win7 de-support or might there be
another issue at work here?

--
Sailfish
CDC Covid19 Trends: https://www.facebook.com/groups/624208354841034
Rare Mozilla Stuff: http://tinyurl.com/z86x3sg

On 3/6/2022 1:42 AM, Sailfish wrote:
> Ref: https://i.imgur.com/xExUG1Y.jpg
>
> It has been years since I tested this (rating had been 7.3 but decided to re-run the rating. For unknown reasons, it reports some sort of interference (and suggests a driver.) However, Device Manager shows no driver issues See link above.
>
> Could test no longer work due the Win7 de-support or might there be another issue at work here?
>

There's an example here of running it from command line.
This may give you some comments regarding missing resources
or permission errors to create XML files.

https://www.eightforums.com/threads/windows-experience-index-update-or-refresh-wei-score-in-windows-8.4513/

Administrator Command Prompt

Winsat formal -restart clean​

If your video driver is "Microsoft Basic Display Adapter" or "VESA Driver",
that sort of thing, instead of "NVidia 450.77", then that's not going
to work, and the evaluation might stop during video eval. Check Device Manager
(devmgmt.msc) and make sure you have drivers.

The Windows 7 version of that above page, is here. The Windows 8 was
the first one to show up in a Google search.

https://www.sevenforums.com/tutorials/263-windows-experience-index-update-refresh-score.html

WSAT may have been discontinued after W8 or so.

Culturally, there is at least one country, where the people just love WSAT and love
to post "how much higher than 7.9 they got" :-) I'm always willing to admit
my machines here are middle of the road, and leave it at that.

When I was younger, I received a bowling trophy for "Best Attendance",
which gives you some idea what an intense competitor I am :-)

Paul

On Sat, 05 Mar 2022 22:42:53 -0800, Sailfish wrote:
> Ref: https://i.imgur.com/xExUG1Y.jpg
>
> It has been years since I tested this (rating had been 7.3 but decided
> to re-run the rating. For unknown reasons, it reports some sort of
> interference (and suggests a driver.) However, Device Manager shows no
> driver issues See link above.
>
> Could test no longer work due the Win7 de-support or might there be
> another issue at work here?

It has nothing to do with software end of support. That's for sure.

Try checking the event log.

On 3/6/2022 2:47 AM, Paul wrote:
> On 3/6/2022 1:42 AM, Sailfish wrote:
>> Ref: https://i.imgur.com/xExUG1Y.jpg
>>
>> It has been years since I tested this (rating had been 7.3 but decided to re-run the rating. For unknown reasons, it reports some sort of interference (and suggests a driver.) However, Device Manager shows no driver issues See link above.
>>
>> Could test no longer work due the Win7 de-support or might there be another issue at work here?
>>
>

Wikipedia says it runs even on Windows 11, from the command line.

It looks more than a bit broken on Windows 11.

winsat formal

> CPU LZW Compression 909.98 MB/s
> CPU AES256 Encryption 12144.57 MB/s
> CPU Vista Compression 2434.42 MB/s
> CPU SHA1 Hash 6467.20 MB/s
> Uniproc CPU LZW Compression 107.05 MB/s
> Uniproc CPU AES256 Encryption 1037.34 MB/s
> Uniproc CPU Vista Compression 294.62 MB/s
> Uniproc CPU SHA1 Hash 794.23 MB/s
> Memory Performance 41490.26 MB/s
> Direct3D Batch Performance 42.00 F/s
> Direct3D Alpha Blend Performance 42.00 F/s
> Direct3D ALU Performance 42.00 F/s
> Direct3D Texture Load Performance 42.00 F/s
> Direct3D Batch Performance 42.00 F/s
> Direct3D Alpha Blend Performance 42.00 F/s
> Direct3D ALU Performance 42.00 F/s
> Direct3D Texture Load Performance 42.00 F/s
> Direct3D Geometry Performance 42.00 F/s
> Direct3D Geometry Performance 42.00 F/s
> Direct3D Constant Buffer Performance 42.00 F/s
> Video Memory Throughput 17650.40 MB/s
> Dshow Video Encode Time 0.00000 s
> Dshow Video Decode Time 0.00000 s
> Media Foundation Decode Time 0.00000 s
> Disk Sequential 64.0 Read 145.68 MB/s 7.1
> Disk Random 16.0 Read 1.44 MB/s 3.9
> Total Run Time 00:00:11.78

The results suggest the test suite may be looking for DirectX 9e support
or something, rather than DirectX 11 or DirectX 12. Because the "42"
number is anomalous.

OK, maybe that's not it, because DXDIAG says this.

Driver File Version: 30.00.13023.4001 (English)
Driver Version: 30.0.13023.4001
DDI Version: 12
Feature Levels: 12_1, 12_0, 11_1, 11_0, 10_1, 10_0, 9_3, 9_2, 9_1
Driver Model: WDDM 3.0

You can run "dxdiag" and save to text, the output, for copy/pasting.

At least the video decode, should be done under DXVA2.

The hard drive above, is a WD Black 7200 RPM 1TB (boot drive).

Paul

Paul graced us with on 3/6/2022 12:18 AM:
> On 3/6/2022 2:47 AM, Paul wrote:
>> On 3/6/2022 1:42 AM, Sailfish wrote:
>>> Ref: https://i.imgur.com/xExUG1Y.jpg
>>>
>>> It has been years since I tested this (rating had been 7.3 but
>>> decided to re-run the rating. For unknown reasons, it reports some
>>> sort of interference (and suggests a driver.) However, Device Manager
>>> shows no driver issues See link above.
>>>
>>> Could test no longer work due the Win7 de-support or might there be
>>> another issue at work here?
>>>
>>
<snip />
Below are the results from my run, which appears to complete
successfully. The Windows test always seems to konk out during the final
"Primary hard drive: Disk data transfer rate" test phase.

C:\Users\Dad>Winsat formal -restart clean
Windows System Assessment Tool
> Running the Formal Assessment
> Running: Feature Enumeration ''
> Run Time 00:00:00.00
> Running: WinSAT Direct3D Assessment '-aname DWM -time 10 -fbc 10
-disp off -no
rmalw 12 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915)
-rendertot
ex 6 -rtdelta 3 -nolock'
> Assessing Desktop Graphics Performance
> Run Time 00:00:11.31
> Running: WinSAT Direct3D Assessment '-aname Batch -time 5 -fbc 10
-disp off -a
nimate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(10) -objs
C(26) -re
ndertotex 6 -rtdelta 3 -texpobj C(1)'
> Assessing DirectX Batch Performance
> Run Time 00:00:05.66
> Running: WinSAT Direct3D Assessment '-aname Alpha -time 5 -fbc 10
-disp off -a
nimate 10 -width 1280 -height 1024 -totalobj 300 -batchcnt C(75) -objs
C(26) -re
ndertotex 6 -rtdelta 3 -texpobj C(1)'
> Assessing DirectX Alpha blend Performance
> Run Time 00:00:05.66
> Running: WinSAT Direct3D Assessment '-aname Tex -time 5 -fbc 10 -disp
off -ani
mate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs
C(20) -noa
lpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3'
> Assessing DirectX Texture load Performance
> Run Time 00:00:05.85
> Running: WinSAT Direct3D Assessment '-aname ALU -time 5 -fbc 10 -disp
off -ani
mate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125) -objs
C(20) -noa
lpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3'
> Assessing DirectX ALU Performance
> Run Time 00:00:05.90
> Running: WinSAT Direct3D Assessment '-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)'
> Assessing DirectX Batch Performance
> Run Time 00:00:05.65
> Running: WinSAT Direct3D Assessment '-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)'
> Assessing DirectX Alpha blend Performance
> Run Time 00:00:05.66
> Running: WinSAT Direct3D Assessment '-dx10 -aname Tex -time 5 -fbc
10 -disp o
ff -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125)
-objs C(2
0) -noalpha -texshader -totaltex 10 -texpobj C(4) -rendertotex 6 -rtdelta 3'
> Assessing DirectX Texture load Performance
> Run Time 00:00:05.69
> Running: WinSAT Direct3D Assessment '-dx10 -aname ALU -time 5 -fbc
10 -disp o
ff -animate 10 -width 1280 -height 1024 -totalobj 500 -batchcnt C(125)
-objs C(2
0) -noalpha -alushader -totaltex 10 -texpobj C(1) -rendertotex 6 -rtdelta 3'
> Assessing DirectX ALU Performance
> Run Time 00:00:05.69
> Running: WinSAT Direct3D Assessment '-dx10 -aname GeomF4 -time 7
-fbc 10 -dis
p 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) -ren
dertotex 6 -rtdelta 3 -tierframes 60 -tiertime 1'
> Assessing DirectX Geometry Performance
> Run Time 00:00:07.89
> Running: WinSAT Direct3D Assessment '-dx10 -aname GeomV8 -time 7
-fbc 10 -dis
p 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) -rende
rtotex 6 -rtdelta 3 -tierframes 60 -tiertime 1'
> Assessing DirectX Geometry Performance
> Run Time 00:00:07.63
> Running: WinSAT Direct3D Assessment '-dx10 -aname CBuffer -time 5
-fbc 10 -di
sp 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 -cb
ufp 6'
> Assessing DirectX Constant Buffer Performance
> Run Time 00:00:05.52
> Running: Media Foundation Playback Assessment '-input
C:\Windows\Performance\W
inSAT\winsat.wmv -nopmp'
> Run Time 00:00:00.86
> Running: Extended Media Assessment '-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 -ov
errideframetype int2fps'
> Run Time 00:00:05.59
> Running: Extended Media Assessment '-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
-overrideframet
ype prog'
> Run Time 00:00:05.49
> Running: Extended Media Assessment '-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
-override
frametype int2fps'
> Run Time 00:00:05.57
> Running: Extended Media Assessment '-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
-override
frametype prog'
> Run Time 00:00:05.54
> Running: Extended Media Assessment '-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
-overrideframe
type prog'
> Run Time 00:00:05.52
> Running: Extended Media Assessment '-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
-overrideframety
pe int2fps'
> Run Time 00:00:05.49
> Running: Media Decode/Encode Assessment '-input
C:\Windows\Performance\WinSAT\
winsatencode.wmv -encode C:\Windows\Performance\WinSAT\winsat.prx'
> Run Time 00:00:01.83
> MOOBE Run Time 00:01:58.42
> Running: CPU Assessment '-encryption -up'
> Run Time 00:00:03.06
> Running: CPU Assessment '-compression -up'
> Run Time 00:00:10.12
> Running: CPU Assessment '-encryption2 -up'
> Run Time 00:00:03.04
> Running: CPU Assessment '-compression2 -up'
> Run Time 00:00:10.05
> Running: CPU Assessment '-encryption'
> Run Time 00:00:10.20
> Running: CPU Assessment '-compression'
> Run Time 00:00:10.17
> Running: CPU Assessment '-encryption2'
> Run Time 00:00:10.16
> Running: CPU Assessment '-compression2'
> Run Time 00:00:10.15
> Running: System memory performance assessment ''
> Run Time 00:00:05.16
> Running: Storage Assessment '-seq -read -n 3'
> Run Time 00:00:04.98
> Running: Storage Assessment '-ran -read -n 3'
> Run Time 00:00:00.38
> Running: Storage Assessment '-scen 2009 -drive C:'
The disk assessment test cannot run accurately because of interference
from anot
her component, such as a driver.
> Run Time 00:00:52.18
> CPU LZW Compression 754.34 MB/s
> CPU AES256 Encryption 383.16 MB/s
> CPU Vista Compression 1945.95 MB/s
> CPU SHA1 Hash 2696.66 MB/s
> Uniproc CPU LZW Compression 141.55 MB/s
> Uniproc CPU AES256 Encryption 102.88 MB/s
> Uniproc CPU Vista Compression 368.07 MB/s
> Uniproc CPU SHA1 Hash 584.99 MB/s
> Memory Performance 28912.80 MB/s
> Direct3D Batch Performance 3983.17 F/s
> Direct3D Alpha Blend Performance 3938.59 F/s
> Direct3D ALU Performance 1844.58 F/s
> Direct3D Texture Load Performance 2022.73 F/s
> Direct3D Batch Performance 4333.32 F/s
> Direct3D Alpha Blend Performance 4359.97 F/s
> Direct3D ALU Performance 2017.88 F/s
> Direct3D Texture Load Performance 2244.26 F/s
> Direct3D Geometry Performance 4455.65 F/s
> Direct3D Geometry Performance 7903.39 F/s
> Direct3D Constant Buffer Performance 3599.32 F/s
> Video Memory Throughput 99197.70 MB/s
> Dshow Video Encode Time 0.84180 s
> Media Foundation Decode Time 0.39150 s
> Disk Sequential 64.0 Read 280.47 MB/s 7.6
> Disk Random 16.0 Read 88.64 MB/s 7.1
> Total Run Time 00:04:08.15

JJ graced us with on 3/5/2022 11:51 PM:
> On Sat, 05 Mar 2022 22:42:53 -0800, Sailfish wrote:
>> Ref: https://i.imgur.com/xExUG1Y.jpg
>>
>> It has been years since I tested this (rating had been 7.3 but decided
>> to re-run the rating. For unknown reasons, it reports some sort of
>> interference (and suggests a driver.) However, Device Manager shows no
>> driver issues See link above.
>>
>> Could test no longer work due the Win7 de-support or might there be
>> another issue at work here?
>
> It has nothing to do with software end of support. That's for sure.
>
> Try checking the event log.

Where's that located?

--
Sailfish
CDC Covid19 Trends: https://www.facebook.com/groups/624208354841034
Rare Mozilla Stuff: http://tinyurl.com/z86x3sg

On 3/6/2022 2:37 PM, Sailfish wrote:

> > Run Time 00:00:52.18
> > CPU LZW Compression                          754.34 MB/s
> > CPU AES256 Encryption                        383.16 MB/s
> > CPU Vista Compression                        1945.95 MB/s
> > CPU SHA1 Hash                                2696.66 MB/s
> > Uniproc CPU LZW Compression                  141.55 MB/s
> > Uniproc CPU AES256 Encryption                102.88 MB/s
> > Uniproc CPU Vista Compression                368.07 MB/s
> > Uniproc CPU SHA1 Hash                        584.99 MB/s
> > Memory Performance                           28912.80 MB/s
> > Direct3D Batch Performance                   3983.17 F/s
> > Direct3D Alpha Blend Performance             3938.59 F/s
> > Direct3D ALU Performance                     1844.58 F/s
> > Direct3D Texture Load Performance            2022.73 F/s
> > Direct3D Batch Performance                   4333.32 F/s
> > Direct3D Alpha Blend Performance             4359.97 F/s
> > Direct3D ALU Performance                     2017.88 F/s
> > Direct3D Texture Load Performance            2244.26 F/s
> > Direct3D Geometry Performance                4455.65 F/s
> > Direct3D Geometry Performance                7903.39 F/s
> > Direct3D Constant Buffer Performance         3599.32 F/s
> > Video Memory Throughput                      99197.70 MB/s
> > Dshow Video Encode Time                      0.84180 s
> > Media Foundation Decode Time                 0.39150 s
> > Disk  Sequential 64.0 Read                   280.47 MB/s          7.6
> > Disk  Random 16.0 Read                       88.64 MB/s          7.1
> > Total Run Time 00:04:08.15
>

C:\Windows\Performance\WinSAT\winsat.log

At the end of the log, it claims it is writing the Registry.

44903796 (8860) - exe\processresults.cpp:1739: > Wrote CRS score to the registry 59
44903796 (8860) - exe\processresults.cpp:1760: > Wrote memory score to the registry 92
44903796 (8860) - exe\processresults.cpp:1779: > Wrote cpu score to the registry 92
44903796 (8860) - exe\processresults.cpp:1800: > Wrote DWM score to the registry 81
44903796 (8860) - exe\processresults.cpp:1820: > Wrote D3D score to the registry 99
44903796 (8860) - exe\processresults.cpp:1840: > Wrote disk score to the registry 59

Since this is a machine-wide rating, it would need Administrator.

If the current logged user is a limited user, it might not write out properly.

Paul

Paul graced us with on 3/6/2022 3:41 PM:
> On 3/6/2022 2:37 PM, Sailfish wrote:
>
<snip/>
>
> Since this is a machine-wide rating, it would need Administrator.
>
> If the current logged user is a limited user, it might not write out
> properly.
>
I'm the soul user and my account is Administrator. Below is the contents
of the log file.

I notice that there are some ERROR entries but unsure if those errors
affect the failure of the test nor what they even mean.

Note, I even ran a registry clean before testing it again but it made no
difference.

//
16378435 (3176) - winsat\logging.cpp:0815: --- START 2022\3\6 20:11:52
PM ---
16378435 (3176) - winsat\main.cpp:4301: Command Line =
"C:\Windows\system32\winsat.exe" formal -cancelevent
e3e76eea-f029-4099-9aef-0bca91dfa75c
16378451 (3176) - winsat\processwinsaterror.cpp:0095: ERROR: tried to
read resource strings, unknown exception occured
16378451 (3176) - winsat\main.cpp:4474: > IsFormal=TRUE IsMoobe=FALSE.
16378482 (3176) - winsat\main.cpp:4585: Watch dog system enabled
16378482 (3176) - winsat\main.cpp:4600: Main watch dog timer set to
600.0 seconds
16378950 (3176) - winsat\main.cpp:2490: > DWM Running.
16378950 (3176) - winsat\main.cpp:2501: > leaving DWM on.
16378966 (3176) - winsat\main.cpp:2470: > EMD service will be restored
on exit.
16379730 (3176) - winsat\syspowertools.cpp:0983: > Read the active power
scheme as '8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
16379730 (3176) - winsat\main.cpp:2793: > power policy saved.
16379761 (3176) - winsat\syspowertools.cpp:1015: > Set the active power
scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
16379761 (3176) - winsat\main.cpp:2814: > power policy set to maximum.
16380042 (3176) - winsat\logging.cpp:1763: ERROR: pahse enter/leave
imballance
16380042 (3176) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE
IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE
16380042 (3176) - winsat\main.cpp:1775: > Run Assessment features
16380260 (3176) - winsat\main.cpp:1775: > Run Assessment disk -seq -read
-n 3
16384519 (3176) - winsat\main.cpp:1775: > Run Assessment disk -ran -read
-n 3
16384800 (3176) - winsat\main.cpp:1775: > Run Assessment disk -scen 2009
-drive C:
16436670 (3176) - storage\diskprof.cpp:0283: The disk assessment test
cannot run accurately because of interference from another component,
such as a driver.
16436670 (3176) - winsat\main.cpp:2056: > disk Assessment FAILED due to
an error
16436670 (3176) - winsat\processresults.cpp:1480: > Wrote disk score to
the registry 590
16436670 (3176) - winsat\processresults.cpp:1498: > Wrote random read
disk score to the registry 166574
//
16436686 (3176) - winsat\syspowertools.cpp:1015: > Set the active power
scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
16436686 (3176) - winsat\main.cpp:2855: > Power state restored.
16436686 (3176) - winsat\main.cpp:2870: > Successfully reenabled EMD.
16436686 (3176) - winsat\watchdog.cpp:0311: Watch dog system shutdown
16436686 (3176) - winsat\main.cpp:4909: > exit value = 1.

17108504 (4092) - winsat\logging.cpp:0815: --- START 2022\3\6 20:24:02
PM ---
17108504 (4092) - winsat\main.cpp:2861: > no need to restore power state
(no saver object).
17108504 (4092) - winsat\main.cpp:2873: > Not necessary to reenable EMD
cache.
17108504 (4092) - winsat\main.cpp:4909: > exit value = 4.

17867122 (6308) - winsat\logging.cpp:0815: --- START 2022\3\6 20:36:41
PM ---
17867122 (6308) - winsat\main.cpp:4301: Command Line =
"C:\Windows\system32\winsat.exe" formal -cancelevent
d4a5181b-c7d0-4e46-9ccf-ae9faf1012fa
17867122 (6308) - winsat\processwinsaterror.cpp:0095: ERROR: tried to
read resource strings, unknown exception occured
17867122 (6308) - winsat\main.cpp:4474: > IsFormal=TRUE IsMoobe=FALSE.
17867153 (6308) - winsat\main.cpp:4585: Watch dog system enabled
17867153 (6308) - winsat\main.cpp:4600: Main watch dog timer set to
600.0 seconds
17867621 (6308) - winsat\main.cpp:2490: > DWM Running.
17867621 (6308) - winsat\main.cpp:2501: > leaving DWM on.
17867621 (6308) - winsat\main.cpp:2470: > EMD service will be restored
on exit.
17868401 (6308) - winsat\syspowertools.cpp:0983: > Read the active power
scheme as '8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
17868401 (6308) - winsat\main.cpp:2793: > power policy saved.
17868432 (6308) - winsat\syspowertools.cpp:1015: > Set the active power
scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
17868432 (6308) - winsat\main.cpp:2814: > power policy set to maximum.
17868713 (6308) - winsat\logging.cpp:1763: ERROR: pahse enter/leave
imballance
17868713 (6308) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE
IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE
17868713 (6308) - winsat\main.cpp:1775: > Run Assessment features
17869228 (6308) - winsat\main.cpp:1775: > Run Assessment disk -seq -read
-n 3
17873440 (6308) - winsat\main.cpp:1775: > Run Assessment disk -ran -read
-n 3
17873720 (6308) - winsat\main.cpp:1775: > Run Assessment disk -scen 2009
-drive C:
17925591 (6308) - storage\diskprof.cpp:0283: The disk assessment test
cannot run accurately because of interference from another component,
such as a driver.
17925591 (6308) - winsat\main.cpp:2056: > disk Assessment FAILED due to
an error
17925591 (6308) - winsat\processresults.cpp:1480: > Wrote disk score to
the registry 590
17925591 (6308) - winsat\processresults.cpp:1498: > Wrote random read
disk score to the registry 181739
17925606 (6308) - winsat\syspowertools.cpp:1015: > Set the active power
scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
17925606 (6308) - winsat\main.cpp:2855: > Power state restored.
17925606 (6308) - winsat\main.cpp:2870: > Successfully reenabled EMD.
17925606 (6308) - winsat\watchdog.cpp:0311: Watch dog system shutdown
17925606 (6308) - winsat\main.cpp:4909: > exit value = 1.

--
Sailfish
CDC Covid19 Trends: https://www.facebook.com/groups/624208354841034
Rare Mozilla Stuff: http://tinyurl.com/z86x3sg

On 3/6/2022 11:50 PM, Sailfish wrote:
> Paul graced us with on 3/6/2022 3:41 PM:
>> On 3/6/2022 2:37 PM, Sailfish wrote:
>>
> <snip/>
>>
>> Since this is a machine-wide rating, it would need Administrator.
>>
>> If the current logged user is a limited user, it might not write out properly.
>>
> I'm the soul user and my account is Administrator. Below is the contents of the log file.
>
> I notice that there are some ERROR entries but unsure if those errors affect the failure of the test nor what they even mean.
>
> Note, I even ran a registry clean before testing it again but it made no difference.
>
> //
> 16378435 (3176) - winsat\logging.cpp:0815: --- START 2022\3\6 20:11:52 PM ---
> 16378435 (3176) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\winsat.exe" formal -cancelevent e3e76eea-f029-4099-9aef-0bca91dfa75c
> 16378451 (3176) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured
> 16378451 (3176) - winsat\main.cpp:4474: > IsFormal=TRUE  IsMoobe=FALSE.
> 16378482 (3176) - winsat\main.cpp:4585: Watch dog system enabled

The non-Microsoft participant here, claims the BIOS reportage to the
OS can cause this failure. From the OS, you can read out the DMI
and get things like "motherboard name".

https://answers.microsoft.com/en-us/windows/forum/all/help-rating-problem/0c3e6736-1cd8-4aa2-9219-cc375462aaba

When it does an OOBE (out of box experience) run, it evaluates
all subsystems. Later on, it evaluates fewer of the subsystems.
Like my CPU and memory did not get re-evaluated.

It claims I don't have a WDDM driver, when DXDIAG says "WDDM 1.1".

It claims DWM is not running, when on Win7, dwm.exe is running.

Some of the messages have spelling mistakes.

I suspect (but cannot prove) that it wants a WHQL driver.
If you go to the NVidia site, both non-WHQL and WHQL drivers
are offered. NVidia submits some of the drivers for a
blessing by Microsoft, but not all of them. I haven't checked
whether the drivers staged on the Catalog Server, are WHQL or not,
as usually they are not the same drivers that NVidia is offering
from its own site.

So on the one hand, while it pretends to be "super-careful"
about what it tests, it's also too stupid to turn off the
Search Indexer while the disk benchmark is running.

I think clowns wrote this - possibly a contract job done
by someone outside Microsoft. Sure, they used GUIDs to refer
to power schema, which would be a sign of a Microsoft employee,
but on the other hand, the output would not read like a bad
novel if actual quality Microsoft employees worked on it.

I wish I could help further, but my test didn't finish either
on the new machine, and is just as bad a novel as the results
on the 2015 machine. The new machine, all the frame rates are "42",
and it says right in the results, it could not "something or other"
a D3D device. DXDIAG seems to have no trouble, all boxes ticked
on DXDIAG.

And the winsat.log file, may have had results in the file already,
from the year 2009. My machine, I think I got the P9X79 in the year
2015, so it would be pretty hard for a test to be dated 2009.
I think the 2015 test is the first real test in the log on the
P9X79.

There is a "datastore" folder, and it shows the pattern of either
doing a full test, or doing a subset of all tests.

Paul

Paul graced us with on 3/7/2022 1:52 AM:
> On 3/6/2022 11:50 PM, Sailfish wrote:
>> Paul graced us with on 3/6/2022 3:41 PM:
>>> On 3/6/2022 2:37 PM, Sailfish wrote:
>>>
>> <snip/>
>>>
>>> Since this is a machine-wide rating, it would need Administrator.
>>>
>>> If the current logged user is a limited user, it might not write out
>>> properly.
>>>
>> I'm the soul user and my account is Administrator. Below is the
>> contents of the log file.
>>
>> I notice that there are some ERROR entries but unsure if those errors
>> affect the failure of the test nor what they even mean.
>>
>> Note, I even ran a registry clean before testing it again but it made
>> no difference.
>>
>> //
>> 16378435 (3176) - winsat\logging.cpp:0815: --- START 2022\3\6 20:11:52
>> PM ---
>> 16378435 (3176) - winsat\main.cpp:4301: Command Line =
>> "C:\Windows\system32\winsat.exe" formal -cancelevent
>> e3e76eea-f029-4099-9aef-0bca91dfa75c
>> 16378451 (3176) - winsat\processwinsaterror.cpp:0095: ERROR: tried to
>> read resource strings, unknown exception occured
>> 16378451 (3176) - winsat\main.cpp:4474: > IsFormal=TRUE IsMoobe=FALSE.
>> 16378482 (3176) - winsat\main.cpp:4585: Watch dog system enabled
>
> The non-Microsoft participant here, claims the BIOS reportage to the
> OS can cause this failure. From the OS, you can read out the DMI
> and get things like "motherboard name".
>
> https://answers.microsoft.com/en-us/windows/forum/all/help-rating-problem/0c3e6736-1cd8-4aa2-9219-cc375462aaba
>
>
> When it does an OOBE (out of box experience) run, it evaluates
> all subsystems. Later on, it evaluates fewer of the subsystems.
> Like my CPU and memory did not get re-evaluated.
>
> It claims I don't have a WDDM driver, when DXDIAG says "WDDM 1.1".
>
> It claims DWM is not running, when on Win7, dwm.exe is running.
>
> Some of the messages have spelling mistakes.
>
> I suspect (but cannot prove) that it wants a WHQL driver.
> If you go to the NVidia site, both non-WHQL and WHQL drivers
> are offered. NVidia submits some of the drivers for a
> blessing by Microsoft, but not all of them. I haven't checked
> whether the drivers staged on the Catalog Server, are WHQL or not,
> as usually they are not the same drivers that NVidia is offering
> from its own site.
>
> So on the one hand, while it pretends to be "super-careful"
> about what it tests, it's also too stupid to turn off the
> Search Indexer while the disk benchmark is running.
>
> I think clowns wrote this - possibly a contract job done
> by someone outside Microsoft. Sure, they used GUIDs to refer
> to power schema, which would be a sign of a Microsoft employee,
> but on the other hand, the output would not read like a bad
> novel if actual quality Microsoft employees worked on it.
>
> I wish I could help further, but my test didn't finish either
> on the new machine, and is just as bad a novel as the results
> on the 2015 machine. The new machine, all the frame rates are "42",
> and it says right in the results, it could not "something or other"
> a D3D device. DXDIAG seems to have no trouble, all boxes ticked
> on DXDIAG.
>
The odd thing is that it seems to complete fine when using cmd console
invocation, "Winsat formal -restart clean"? I believe as you suggest, it
may be broken on the Windows side from some update such as a Knowledge
Base patch where they neglected to test the Winsat feature during system
test phase?

> And the winsat.log file, may have had results in the file already,
> from the year 2009. My machine, I think I got the P9X79 in the year
> 2015, so it would be pretty hard for a test to be dated 2009.
> I think the 2015 test is the first real test in the log on the
> P9X79.
>
> There is a "datastore" folder, and it shows the pattern of either
> doing a full test, or doing a subset of all tests.
>
Yeah, I deleted the log file before trying it again to produce the file
I sent you. to remove previous run entries. Interestingly, I mounted a
Reflex C: drive image before I ran the recent tests and there was no
winsat.log file in the folder. Anyway, I restored my system from just
before I ran that test and the old rating now displays.

As always, your willingness to dig deeply to analyze problems is most
appreciated.

--
Sailfish
CDC Covid19 Trends: https://www.facebook.com/groups/624208354841034
Rare Mozilla Stuff: http://tinyurl.com/z86x3sg