Definitely seeing some new issues since the update:
1) Infrequent BSODs causing full reboot
2) Seems to take much longer to process jobs
3) AstroPulse jobs freeze, if you hit Suspend them Resume job will resume normally, but at some point the job will error out and report back as aborted.
Systems affected are Intel P4s 1.8/1.9g running WinXP

Definitely seeing some new issues since the update:
1) Infrequent BSODs causing full reboot
2) Seems to take much longer to process jobs
3) AstroPulse jobs freeze, if you hit Suspend them Resume job will resume normally, but at some point the job will error out and report back as aborted.
Systems affected are Intel P4s 1.8/1.9g running WinXP

I'm not seeing this on any of my machines (A Win XP pro x64, Intel Q9550, on a Win XP Pro x32 Pentium 4 3 GHz machine, a Win 7 AMD C50 laptop nor on a Win 7 AMD Athlon2 215...) no BSODs, no data as to length of job (the Q9550 was changed quite recently, the Athlon2 215 just recently went 27/7... and I was running optimized apps on the other two) and I've had no problems with AP jobs.

According to Eric at the link, V7 jobs should be taking longer, there's more processing going on.... Hello, from Albany, CA!...

For me it is not so much that AP jobs freeze but some tend to start normally, get around half way through, run incredibly slowly but eventually speed up again and finish normally.
I know there is experimentation with various types of AP units now so maybe this is what I am seeing. I have definitely had some jobs go through within the hour and a quarter predicted while some take over five times that.

I run 2 machines (Win 7 pro 64 bit). Both have GPU's that SAH can use. One got version 7 GPU work but the jobs errored saying the GPU was non-existant.
The other got jobs that ran for hours but never progressed. The GPU Meter indicated that the GPU was not doing any work. I aborted all of the GPU work so I now wait with baited breath for new GPU work!!

I run 2 machines (Win 7 pro 64 bit). Both have GPU's that SAH can use. One got version 7 GPU work but the jobs errored saying the GPU was non-existant.
The other got jobs that ran for hours but never progressed. The GPU Meter indicated that the GPU was not doing any work. I aborted all of the GPU work so I now wait with baited breath for new GPU work!!

If you have not already done so, take a look at some of the v7 problem threads inb the Number Crunching Forum. If you don't see something that looks like your problems, open a new thread there.Donald
Infernal Optimist / Submariner, retired

I concur with the reports of dramatic slowdowns of work units processed. I have gone from an average of 12.7K per day to about 9.6K per day with no hardware or software changes except the new SAH software. This is on a Windows 8 box running a I5 2320 @ 3Ghz with 16 gigs of ram. This box's sole purpose is to run SAH, so I am a bit at a loss to the performance change. I have run several benchmarks to recheck the numbers and all return within 1% of the baseline when the machine was built.

Have, for the first time in the 5 years since I built this computer, been getting BSODs fairly frequently since the upgrade to Ver. 7. Running Vista Home Premium on an ASUS mobo, with an AMD Phenom quad core running at 2.95 GHz (very slightly overclocked). It would take much more than this to make me call it quits. I've been with Seti@Home off and on since pretty much day one. As long as I have a computer, which is always, and an internet connection, not always a possiblity, I will crunch your data. Should any more info concerning my system or the exact conditions preceding the BSODs be useful plesde feel free to contact me at me registered email address.
Got your back...
John

I concur with the reports of dramatic slowdowns of work units processed. I have gone from an average of 12.7K per day to about 9.6K per day with no hardware or software changes except the new SAH software. This is on a Windows 8 box running a I5 2320 @ 3Ghz with 16 gigs of ram. This box's sole purpose is to run SAH, so I am a bit at a loss to the performance change. I have run several benchmarks to recheck the numbers and all return within 1% of the baseline when the machine was built.

Each unit takes longer to do because more work is being done on it.DavidSitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

Here's whats new with V7 for me. My 3 month old PC started crawling at less than half the speed it operated at before. The screen saver acted like it was stuck in the mud. Froze and crashed twice so sorrowfully, I pulled the plug on crunching. I will continue to check back here to see if anybody comes up with the "fix" but personally... I was kicking butt with the previous version. I cant sacrifice my hard earned build. Nothing Im saying is meant to insult anyone OR their hard work. I am grateful to all that have a hand in allowing me to participate in our goals.
Dennis Smythe

If you bring up the screen saver it will show you the data location info for the work project you are seeing. Write that down and then goto sky-map.org and type it into the search bar
example : 5h 31' 6" , +29 32' 13"
That's the location of my current work unit.

I have 4 PC's running Seti@home: i7 Quad Core Win7-64 at 100% does most of the work. I have over 17 million units credit. When I upgraded all PC's to Ver 7, my user average output began dropping immediately from over 21,000/day to less than 12,000 a day and still dropping. Looks like it will end up about 1/2 my old daily output. Every machine is running slower. Should I go back to the last version before Ver 7?
Wayne