I swapped out two power supplies and two motherboard trying to find why about one out of 3 tasks were failing before I noticed the "84" parameter star file was empty. lt had 983 kilo bytes of empty space! I only started looking at the param files when I found that Einstein had no problem on either motherboard.

I even copied over the separation app from another system thinking mine may be corrupted.

This occurred on two different motherboards that I was building.

100 out of 300 errored out
https://milkyway.cs.rpi.edu/milkyway/results.php?hostid=906970
32 out of 132 errored out
https://milkyway.cs.rpi.edu/milkyway/results.php?hostid=906925

6 out of 18,000 were the only errors as the"84" file on this system had data unlike the above two
https://milkyway.cs.rpi.edu/milkyway/results.php?hostid=890877

I have no idea how this occurred but it seems to be the project app should have noticed the param fiile was empty and done something. I see errors all the time in various project results. Gpugrid is famous for saying to "ignore the memory leak warnings"

Found another empty file. Wrote a batch file to compare two Milkyway system data files.

C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>run_them.bat

C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>call runc parameters-80-4s-bg-set2.txt

C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>fc /b parameters-80-4s-bg-set2.txt ..\parameters-80-4s-bg-set2.txt
Comparing files parameters-80-4s-bg-set2.txt and ..\PARAMETERS-80-4S-BG-SET2.TXT
FC: no differences encountered


C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>call runc parameters-81-4s-bg-set2.txt

C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>fc /b parameters-81-4s-bg-set2.txt ..\parameters-81-4s-bg-set2.txt
Comparing files parameters-81-4s-bg-set2.txt and ..\PARAMETERS-81-4S-BG-SET2.TXT
FC: no differences encountered


C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>call runc parameters-82-4s-bg-set2.txt

C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>fc /b parameters-82-4s-bg-set2.txt ..\parameters-82-4s-bg-set2.txt
Comparing files parameters-82-4s-bg-set2.txt and ..\PARAMETERS-82-4S-BG-SET2.TXT
FC: no differences encountered


C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>call runc parameters-83-4s-bg-set2.txt

C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>fc /b parameters-83-4s-bg-set2.txt ..\parameters-83-4s-bg-set2.txt
Comparing files parameters-83-4s-bg-set2.txt and ..\PARAMETERS-83-4S-BG-SET2.TXT
FC: no differences encountered


C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>call runc parameters-84-4s-fixgap-bg-set2.txt

C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>fc /b parameters-84-4s-fixgap-bg-set2.txt ..\parameters-84-4s-fixgap-bg-set2.txt
Comparing files parameters-84-4s-fixgap-bg-set2.txt and ..\PARAMETERS-84-4S-FIXGAP-BG-SET2.TXT
FC: no differences encountered


C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>call runc parameters-84-4s-fixgap-bg-set3.txt

C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>fc /b parameters-84-4s-fixgap-bg-set3.txt ..\parameters-84-4s-fixgap-bg-set3.txt
Comparing files parameters-84-4s-fixgap-bg-set3.txt and ..\PARAMETERS-84-4S-FIXGAP-BG-SET3.TXT
FC: no differences encountered


C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>call runc parameters-84-4s-fixgap.txt

C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\bu>fc /b parameters-84-4s-fixgap.txt ..\parameters-84-4s-fixgap.txt
Comparing files parameters-84-4s-fixgap.txt and ..\PARAMETERS-84-4S-FIXGAP.TXT
00000000: 6E 00
00000001: 75 00
00000002: 6D 00
00000003: 62 00
00000004: 65 00

Well that is worrying. Hopefully it's a weird edge case thing and not common...

Well that is worrying. Hopefully it's a weird edge case thing and not common...

I looked at the hard drive on my swapped out system and there was no problem with any parameter files. It was just this one system that had a problem. Since this file is never re-written it must have been corrupted during the initial setup and fresh install of win10: "Put in win7, OEM activate, upgraded immediately to 10, go find all missing drivers to make it work"