Seems to be only seti, not seti beta. Had to boot Home Vista Premium 64 SP1 into safe mode and get rid of the VLAR's as the 2nd BSOD occured when BM 6.5.0 started automatically. This WU seemed to be the one causing the problem as it reported several unknown errors on each "startup" and then finally reported it could not find the file. I assume it could not find the file because I deleted it.

Even after getting rid of all vlars 0.0 .. 0.01 I had another BSOD (my 3rd). GPUGRID and seti beta seem ok. This system has a gfx280 and another with a 9800gfx+ has not BSOD's yet. However, the seti WU's have not worked up high enough to run as that system still has some beta's to crunch.

Did not get any snow, just the BSOD.

EDIT: The 3rd BSOD was also caused by a 0.001 type VLAR. Not sure why my script failed to see it. Script is here:

findstr /M "<true_angle_range>0\.[0-1]" *.* > low_ar.bat

I manually added the phrase "del " before each line in "low_ar.bat" and then ran the text file as a batch. Probably a way to do that automatically one would think.

Followup - Got to work and was able to check the 9800gtx+ and it had the snow problem. A number of the "beta seti" wu's also had the "no room for results" but without a time stamp on the beta and non-beta seti results it is hard to tell which WU from which project caused the problem. It would appear that once an error occured then even the good vlars started failing and the error might have propagated from seti to seti beta once the card had the display fault. There was no BSOD on this system.

Vista Ultra 64 SP1 , 6.5.0, beta:6.07 and seti:6.06, whql:181.20

read here ;)

---