Just checked one of the older machines. At first start, I got a screen with "Couldn't read WinSAT values, repair" (or similar). Clicked Repair, Xiret asked to reboot. Clicking the Reboot button did absolutely nothing. Rebooted manually. Second start was without any warning. Clicked "Rate" and it hangs forever at "Getting System Info" (or similar wording). Most of the times I tried ,no WinSAT process was running. Sometimes an idle WinSAT process existed that could not be terminated, not even from TM with Admin rights. No WinSAT log at all. Do you use any advanced code that requires the SSE2 instruction set? This Pentium III doesn't have it. Edit: Running WinSAT formal -v did go right through. As the WinSAT.log from that attempt contains errors, I'm posting it for shiggles. Maybe it's useful for hardening the tool further. Note: The resulting scores cannot be read by Xiret at the next start... Spoiler Code: 13608888 (3968) - winsat\logging.cpp:0815: --- START 2016\8\3 06:11:39 AM --- 13608898 (3968) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\winsat.EXE" formal -v 13608968 (3968) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured 13609198 (3968) - winsat\main.cpp:4474: > IsFormal=TRUE IsMoobe=FALSE. 13609249 (3968) - winsat\main.cpp:4585: Watch dog system enabled 13609249 (3968) - winsat\main.cpp:4600: Main watch dog timer set to 600.0 seconds 13611542 (3968) - winsat\main.cpp:2505: > DWM not running. 13611622 (3968) - winsat\main.cpp:2470: > EMD service will be restored on exit. 13613485 (3968) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e' 13613485 (3968) - winsat\main.cpp:2793: > power policy saved. 13614246 (3968) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c' 13614246 (3968) - winsat\main.cpp:2814: > power policy set to maximum. 13615718 (3968) - d3d\dx9misc.cpp:1030: HRESULT = 8876086a 13615768 (3968) - d3d\dx9misc.cpp:1030: Error: Unable to create the D3D device 13615768 (3968) - d3d\dx9misc.cpp:1030: Error: Unable to check the capabilities of the video card because a d3d device could not be created 13615808 (3968) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance 13615808 (3968) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE 13615808 (3968) - winsat\main.cpp:1775: > Run Assessment features 13618993 (3968) - 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 13621005 (3968) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment. 13623038 (3968) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0 13623048 (3968) - winsat\main.cpp:2037: > DWM Assessment results processing SUCCESS 13623048 (3968) - 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) 13625101 (3968) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment. 13627224 (3968) - 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) 13629247 (3968) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment. 13631220 (3968) - 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 13633173 (3968) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment. 13635186 (3968) - 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 13637129 (3968) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment. 13639202 (3968) - 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) 13639422 (3968) - 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) 13639622 (3968) - 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 13639863 (3968) - 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 13640093 (3968) - 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 13640293 (3968) - 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 13640483 (3968) - 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 13640684 (3968) - winsat\main.cpp:1775: > Run Assessment mfmedia -input C:\Windows\Performance\WinSAT\winsat.wmv -nopmp 13687101 (3968) - 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 13687111 (3968) - winsat\main.cpp:1793: > Not D3D9 or better - skipping assessment. 13687531 (3968) - 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 13687541 (3968) - winsat\main.cpp:1793: > Not D3D9 or better - skipping assessment. 13687741 (3968) - 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 13687741 (3968) - winsat\main.cpp:1793: > Not D3D9 or better - skipping assessment. 13687932 (3968) - 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 13687942 (3968) - winsat\main.cpp:1793: > Not D3D9 or better - skipping assessment. 13688192 (3968) - 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 13688202 (3968) - winsat\main.cpp:1793: > Not D3D9 or better - skipping assessment. 13688412 (3968) - 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 13688412 (3968) - winsat\main.cpp:1793: > Not D3D9 or better - skipping assessment. 13688603 (3968) - winsat\main.cpp:1775: > Run Assessment media -input C:\Windows\Performance\WinSAT\winsatencode.wmv -encode C:\Windows\Performance\WinSAT\winsat.prx 13790830 (3968) - winsat\main.cpp:1775: > Run Assessment moobego 13790890 (3968) - winsat\main.cpp:1775: > Run Assessment cpu -encryption -up 13801655 (3968) - winsat\main.cpp:1775: > Run Assessment cpu -compression -up 13812100 (3968) - winsat\main.cpp:1775: > Run Assessment cpu -encryption2 -up 13822495 (3968) - winsat\main.cpp:1775: > Run Assessment cpu -compression2 -up 13832910 (3968) - winsat\main.cpp:1775: > Run Assessment cpu -encryption 13843225 (3968) - winsat\main.cpp:1775: > Run Assessment cpu -compression 13853700 (3968) - winsat\main.cpp:1775: > Run Assessment cpu -encryption2 13864135 (3968) - winsat\main.cpp:1775: > Run Assessment cpu -compression2 13874530 (3968) - winsat\main.cpp:1775: > Run Assessment mem 13877324 (3968) - winsat\main.cpp:1775: > Run Assessment disk -seq -read -n 0 13895781 (3968) - winsat\main.cpp:1775: > Run Assessment disk -ran -read -n 0 13913466 (3968) - winsat\main.cpp:1775: > Run Assessment disk -scen 2009 -drive C: 14016434 (3968) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0 14016434 (3968) - winsat\processresults.cpp:0962: > Wrote cpu expression compression score to the registry 40 14016444 (3968) - winsat\processresults.cpp:1004: Total physical mem available to the OS : 511 MB (536,403,968 bytes) 14016444 (3968) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DX9 capability 14016444 (3968) - winsat\processresults.cpp:1405: No DX9 capability - limiting D3D Score to 1.0 14016444 (3968) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 530 14016474 (3968) - winsat\processresults.cpp:1498: > Wrote random read disk score to the registry 1136 14016484 (3968) - winsat\processresults.cpp:4371: The Disk Responsiveness Metric is being capped 14016664 (3968) - winsat\main.cpp:0948: > IsOfficial=TRUE IsFormal=TRUE IsMoobe=FALSE RanOverTs=FALSE RanOnbatteries=FALSE 14019278 (3968) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0 14020500 (3968) - winsat\processresults.cpp:0962: > Wrote cpu expression compression score to the registry 40 14020500 (3968) - winsat\processresults.cpp:1004: Total physical mem available to the OS : 511 MB (536,403,968 bytes) 14020500 (3968) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DX9 capability 14020500 (3968) - winsat\processresults.cpp:1405: No DX9 capability - limiting D3D Score to 1.0 14020510 (3968) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 530 14020510 (3968) - winsat\processresults.cpp:1498: > Wrote random read disk score to the registry 1136 14020520 (3968) - winsat\processresults.cpp:4371: The Disk Responsiveness Metric is being capped 14021842 (3968) - common\winsatutilities.cpp:1336: Enabling the WinSAT Task 14022453 (3968) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e' 14022493 (3968) - winsat\main.cpp:2855: > Power state restored. 14022493 (3968) - winsat\main.cpp:2870: > Successfully reenabled EMD. 14022683 (3968) - winsat\main.cpp:2896: > Composition restarted 14022833 (3968) - winsat\watchdog.cpp:0311: Watch dog system shutdown 14022853 (3968) - winsat\main.cpp:4909: > exit value = 0.
Will test ASAP. Actually I did use the WinAero tool before the rise of Xiret... I'm pretty sure the reboot command would have worked. It's just the button gave no response at all. Maybe .NET issue. Edit: Both the WinAero and Chris P.C. tool worked without issues. And now?
Unfortunately, that's the only error I get. The WinSAT.log does not exist at that time, so that's expected. After that, it hangs forever at "Gathering System Information". Could it be that we simply run out of memory here? The system in question does only have 512MiB physical RAM.
Xiret clears old logs automatically and WinSAT must be slow on these machines as its not created in a timely fashion (this is why it hangs for you), but that's my fault for not seeing it. The log reader will stop the thread and close WinSAT if an error occurs, so now I'll look towards better developing the code.
Would it also fix the issue with not being able to read previous (just created by WinAero tool) scores?
See this is odd, that should be no issue at all. May have to send another version to see what the issue is.
A beta version of Xiret will be released in the next few days (v1.4.1) which includes a long list of changes which will be posted later this evening. Also, due to my server being restructured people may encounter issues while downloading or updating, this issue will be temporary.
Here is the changelog for version 1.4.1 (May change before release) Code: 1. New XML parsing method added 2. Fixed a bug in path formatting 3. Memory management system removed 4. Added an auto repair option for corrupted scores 5. WinSAT execution method changed 6. Application multiple instance messagebox removed 7. Messagebox changes to follow the UI 8. Core enhancements 9. UI and Control enhancements 10. Addressed a missing directory issue The change #1 has had a higher percentage of reading scores with malformed XML tags. @Tiger-1: Thanks for your patience @ItielMaN: Appreciate it dude, let me know if you find anything when I send it over, will be soon. I've had to work on updates on little time.
Update delayed as another UI restructure is happening. I'd rather go though everything while planned out. The application is also working on three machines where WinSAT would refuse to complete before. Also, ItielMan... Spartan Toolkit has hit 7MB in size, you know that means something to test is coming, enough said