Windows 10: Winsat formal crashing

Gets to here:

and then get a popup window saying winsat had a problem and will terminate.

Graphics card:

Mobile Intel(R) 965 Express Chipset Family (Microsoft Corporation - WDDM 1.1)
Code: Log Name: Application Source: Application Error Date: 02/05/2017 14:00:55 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: MARYPC-V1TBDQH Description: Faulting application name: WinSAT.exe, version: 10.0.14393.0, time stamp: 0x578999f5 Faulting module name: igdumd64.dll, version: 8.14.10.2697, time stamp: 0x4f6bfd42 Exception code: 0xc0000005 Fault offset: 0x00000000000b221d Faulting process ID: 0x13a8 Faulting application start time: 0x01d2c3441094f559 Faulting application path: C:\Windows\System32\WinSAT.exe Faulting module path: C:\Windows\System32\igdumd64.dll Report ID: 90a3d491-8c37-4ff2-8bd1-5f30189dd73b Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-05-02T13:00:55.847362600Z" /> <EventRecordID>3075</EventRecordID> <Channel>Application</Channel> <Computer>MARYPC-V1TBDQH</Computer> <Security /> </System> <EventData> <Data>WinSAT.exe</Data> <Data>10.0.14393.0</Data> <Data>578999f5</Data> <Data>igdumd64.dll</Data> <Data>8.14.10.2697</Data> <Data>4f6bfd42</Data> <Data>c0000005</Data> <Data>00000000000b221d</Data> <Data>13a8</Data> <Data>01d2c3441094f559</Data> <Data>C:\Windows\System32\WinSAT.exe</Data> <Data>C:\Windows\System32\igdumd64.dll</Data> <Data>90a3d491-8c37-4ff2-8bd1-5f30189dd73b</Data> <Data> </Data> <Data> </Data> </EventData> </Event>[/quote] igdumd64.dll is the Intel Graphics Driver ...

Any updates or fixes?

Dave

:)

 

After upgrading from Windows 7 to 10 unable to defrag.

Hi Anju,

I ran "chkdsk /f" as you suggested and then tried to defrag, however, the disk is still wrongly identified as SSD.

I also reran "winsat formal" with the same result.

Not wishing to be too obtuse, should I have run the whole of:- "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinSAT"

at the command prompt, or just "winsat formal"?

Regards

 

where is windows 10 System Performance Rating ?

Thank you for the information your and Ronnie's reply this will help with future issues.

The computer I am using is a dual boot with Windows 7 Pro and Windows 10 Pro. Using the Windows 7 tool I get different results from running winsat prepop or winsat formal as follows:

W7 prepop formal

Index/WinSPRLevel 3.5 3.6 3.3

Processor/CPUScore 6.8 6.9 7.0

Memory/MemoryScore 7.5 7.2 7.2

Graphics/GraphicsScore 3.5 3.6 3.3

Gaming Graphics/D3DScore 5.4 3.8 9.9

Primary Disk/DiskScore 7.1 5.9 5.9

I am especially interested in the different output form running winsat prepo vs winsat formal. I did a search on the two commands and could not find the information an explanation or cause. And while I am at it is there a reason for not running the commands
in Powershell instead of from a cmd promt?

 

Try downloading and running the (portable) Winaero WEI Tool. It seems to work when Winsat does not. Why? Who knows?: Downloads / Software / Winaero WEI Tool





Good luck,

 

Update: The 3D results looked too high, so I went in and looked at the Winsat 3D results, and it said the 3D tests are no longer run; therefore, the 3D score is bogus on my rig. I am running W10 Insider 16184.

 

Those must be some of most useless benchmarks ever. That's just a front end for what Windows do during installation to very roughly determine some initial user settings, Like performance settings.
Look at this:



Newest processor with 6/12 cores @4.1GHz gives it 8.9 and very basic, low end GPU gets 8.2 and 9.9. Score for SSD is almost same as for a HDD. I was getting almost same score for a dual core Athlon, 512 MB Gpu and HDD.