Greetings,

Well, if this doesn't beat all! :(

Get this: My current installation of Win7 Pro 64bit is a 'newer version' than what is on my OEM disk. It looks like my only other viable option is to do a clean install.

Per the 'Compatibility Report':

The following issues are preventing Windows from upgrading. Cancel the upgrade, complete each task, and then restart the upgrade to continue.
    * Your current version of Windows is more recent than the version you are trying to upgrade to. Windows cannot complete the upgrade.

I HATE WINDOWS 10!

Unless someone here knows a way around this, such as how to change the version number to something that won't make the upgrade (repair install) puke, I will be doing a clean install. I will do some more research on this as well.

I await any comments or suggestions. :)

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

Ok, I got the errors to stop...

Ha! :D I set BOINC to no new tasks and the cache is dry. :P

I was able to get the Win7 Pro 64bit w/SP1 ISO download the other day and have burned it to disc. Tomorrow, 9/14, I will be doing a clean install of Win7... again.

I will be back running SETI@Home tomorrow, or Tuesday at the latest. :)

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

Please! Someone, shoot Murphy! ;)

If it ain't one thing it's another. I'm trying to install WoW (World of Warcraft) and I keep getting the dreaded BSoD! I have been all over the Internet trying to get this resolved.

• I found that I had an 'unknown device'. Fixed that with an ASUS driver install.
  
• I finally found a program that would decipher the .dmp file. Installed it.
  
• I found that in all cases of BSoD, a file called 'ntoskrnl.exe' was involved. Searched the Internet to find a fix.
  
• The first thing I found was to check memory since the above file has something to do with RAM. Running memtest86 right now...
  
• I have property taxes due this month, I don't need to have to spend money on new RAM. Although, I do plan to get new RAM...
  

Turns out that trying to install WoW found a problem needing attention. :)

And no. This was not the problem I was having before the clean install. Those problems are now fixed. I believe the roll back to Win7 from Win10 was a deliberate act to 'persuade' me to stay with Winblow$ 10 which I REFUSE to do. :)

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

WOOHOO! (Hey! Don't celebrate just yet, Murphy is still on the loose...)

It seems I may have found the BSoD problem. Panda AV was causing something to go tramping all over memory it wasn't supposed to. I made one settings change, per information found on the Internet, and my WoW download/install has been going for over 30 minutes now. Before I couldn't get to 5 minutes before getting the BSoD.

I went from one end of the Internet to the other trying to figure this out. I used Memtest86 several times, I used DlgDiag on my system HDD, and I even found out that Win7 has its very own RAM diagnostics tool called, none other than, Windows Memory Diagnostics. None of these revealed any problems with the hardware. I set up Driver Verifier which gave no more info I could use. Which reminds me, I need to restore my PC to my self-made restore point to turn off DV. I ran SFC and it found nothing wrong. NOTHING!

Once WoW is done, I will install BOINC and see what happens then... :)

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

25 minutes to install ONE .NET Framework update??? WTF!?!?!?

Why the frack do these .NET Framework updates take so long to install? It's fracking pathetic! At this rate, support for Win7 will have expired by the time I'm done installing these updates.

I have absolutely nothing running on that PC. Nothing! I'm typing this on my laptop.

I'm seeing weird stuff going on that I haven't seen before on that PC. The second hand on my widget clock will stop moving for anywhere from 5 to 10 seconds. It'll do that for a while then it will run normal for about 10 to 15 seconds. Then back to sporadic movement, then regular, etc., etc. Weird!

Oh well, back to update installs... :(

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

I truly wished that someone would have found Murphy... :(

I install BOINC this morning. Went just dandy.

I shut it down and began more .NET FW update installing. The installation did not go as well as I hoped it would. Ran WAY too long again.

I did a disk cleanup and decided to install Smart Defrag and run it. Man was that drive fragmented. I noticed that the defrag was picking something up from 3 installs ago. .oO(Why does it see that?) I wondered. Bad feeling set in. This install of Win7 is hosed. After the defrag was done, I rebooted. BSoD!!!

I am doing a clean install from my original OEM disk. I don't think that ISO I got from Micro$oft was any good, despite running SFC on it. DONE

Installing drivers now...

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

I now have 'MY' PC running the way I want it and running what I want. So, here is a list of what I have done with a couple questions or so:

• Installed Windows 7 Pro 64bit from my original OEM disk. DONE
  
• Installed all drivers. DONE
  
• Downloaded and manually installed SP1. DONE
  
• Installed most of my programs I use all the time including BOINC 7.4.42 (x64). DONE
  
• Installed security updates up to, but not including, May of this year. DONE (see question(s) below)
  
• Installed security updates for M$ .NET FW 4. DONE (see question(s) below)
  

Except for all the updates I have hidden, and have to continually re-hide, can any updates be trusted from May to present?

I do not have M$ .NET FW 3.5.1 installed on 'MY' PC. Do I need to get the updates for it? I figure that if something should come up and start screaming at me for that version, I can take care of it then.

As for the original topic, I do believe that it may have been resolved by doing the above list of tasks. Time will tell. I have to wait for a huge amount of 'error' WUs to be resolved in my account, most of which are the abandoned ones when my PC got BSoD'd on boot up a few days ago.

Any answers to the above questions or other comments would be greatly appreciated. :)

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

It's been 10 days since my last post here. The MD5 errors are still happening.

I check my stats here several times a day. These errors did not occur prior to my upgrading to Window$ 10. My new MB and CPU were installed in this PC prior to Window$ 10.

As stated in my first post here, I did not see these MD5 errors until after I did the roll back to Win7.

Since, I have downloaded the Win7 Pro 64bit w/SP1 ISO from Micro$oft and burned it to DVD. I did the clean install from that DVD and that was an utterly complete nightmare. I then did a clean install of Win7 Pro 64bit from my OEM disk. Everything worked just fine. I downloaded the SP1 file and installed it. Everything worked just fine. I updated Win7 with updates up to May of this year. Everything is working just fine. Everything, of course, but these damned MD5 errors. :(

I have done HDD diagnostics and RAM diagnostics. No problems there. :)

I now have Linux Mint on my system drive for dual boot. It works just fine. But then, I have not had a problem with Linux in the past. :)

The only 2 things, between me and SETI, that I have not checked are my cable modem and wireless router (this PC is on LAN, not wireless). To be honest, I haven't a clue how to check them.

PLEASE! If anyone has any other ideas other than the ones already mentioned here by others that I have dealt with I need to know. I want to put an end to these errors. If I cannot, I will have no other choice but to sever ties with SETI@Home and BOINC. 16.5 years for me to dedicate to a single project, whether distributed computing or not, is a lot of time to throw away. :(

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I Googled "testing internet connection stability" and got lots of results that look good.

---

I'm no expert on MD5 but as has been pointed out very early on, if BOINC says 'MD5' error it means that the MD5 checksum of the file as received by BOINC did not match the MD5 checksum of this file as supplied by the project.

IOW the file you got is different from the file that was sent out.

So, something is interfering with the files you get. might be AV might be something else, might just be something writing something into the header of the file - you need to figure out what might be tampering with the files, or if anything else might be resulting in receiving corrupted files.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

Greetings,

@Brent: Thanks for that! :) Didn't think about 'stability'. Ran a Pingtest.net and got a 'B' rating. I've done Speedtest.net not long ago and our speed is very good. :)

@William: Yeah, I know about MD5 and what it is for. I ran a MD5 test on Linux Mint the other day when I downloaded it and it passed. This I understand. Thanks anyway. :)

The other half here finally woke up and I had her log into her SETI account. Guest what? She's getting the MD5 errors as well. Sooooo... I'm thinking that I will go out and un-power and restart my modem and router. They have been running continuously for quite some time now. Perhaps I should get into the habit of restarting them once a month. ;)

I'll be back with the results of this. May take a few hours. Or might even fix the problem. Either way, I'll post the results. :)

Keep on BOINCing...! :)

[edit] Good news so far: After restarting the modem and router I ran Pingtest.net again and we went from a 'B' rating to an 'A' rating. Woohoo... :) I will run it again after this just to verify... [/edit]

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

[edit] Good news so far: After restarting the modem and router I ran Pingtest.net again and we went from a 'B' rating to an 'A' rating. Woohoo... :) I will run it again after this just to verify... [/edit]

Arriving late to the discussion and following on, since the net has run out of IPv4 addresses many of the home routers I've run into seem to need periodic reboots.

---

[edit] Good news so far: After restarting the modem and router I ran Pingtest.net again and we went from a 'B' rating to an 'A' rating. Woohoo... :) I will run it again after this just to verify... [/edit]

Arriving late to the discussion and following on, since the net has run out of IPv4 addresses many of the home routers I've run into seem to need periodic reboots.

Greetings Gary,

Last I knew, the Net was running out of IPv4 addresses hence the new IPv6 addresses which would be virtually unlimited. Regardless though, I shall endeavor to remember to reset the router once a month. Thanks for this reminder of IPv4. :)

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

UPDATE: Not so much.

If this don't just beat all! Something has happened at SETI Prime whereby my WUs are uploading just fine, but they are not getting updated. And because of this I'm not getting any new WUs. Which means I cannot tell if my modem/router reset worked to eliminate my current dilemma or not. Maybe the problem will be fixed today. ;)

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

There is a server issue, and Matt posted a little note:

http://setiathome.berkeley.edu/forum_thread.php?id=77990&postid=1730548#1730548

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

There is a server issue, and Matt posted a little note:

http://setiathome.berkeley.edu/forum_thread.php?id=77990&postid=1730548#1730548

That one wouldn't explain the reported error:

8/28/2015 5:13:48 AM | SETI@home | Started download of 01no11af.3884.20599.438086664203.12.139
8/28/2015 5:13:50 AM | SETI@home | Finished download of 01no11af.3884.20599.438086664203.12.139
8/28/2015 5:13:50 AM | SETI@home | [error] MD5 check failed for 01no11af.3884.20599.438086664203.12.139
8/28/2015 5:13:50 AM | SETI@home | [error] expected 0206a1a834822fa5a40ad92e62cf7969, got c230fe3bf5431e59785cb4be7029a195
8/28/2015 5:13:50 AM | SETI@home | [error] Checksum or signature error for 01no11af.3884.20599.438086664203.12.139

(which dates from before the connectivity problems, anyway)

For that, there's no troubleshooting possible except finding the named file and looking to see what's wrong with it.

Greetings,

Due to the routing snafu at Berkeley, I was unable to update 99 WUs or get new ones to run since September 30th. I saw a post here a bit ago that gave a proxy IP address and port to try to get to SETI. I plugged it in a few minutes ago and finally got through.

I reported my finished WUs and downloaded a boat load of new ones. Not a single MD5 error in the lot. This may be a bit too early to tell so I will post another update tomorrow or sooner if the errors creep back into my life. ;)

I hope this dilemma is finally over! Woohoo! :)

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

Well, I'm still getting those dreaded MD5 errors; got 4 just this morning. I guess resetting my modem and router did nothing to resolve this, unless they will need resetting daily which will be a pain in the you-know-what.

Something somewhere is changing the work unit files before or as I get them, and I'm at a loss... :(

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

Ok, I just performed a last ditch effort. I updated from v7.4.42 to v7.6.9. I highly doubt that this will resolve the issue, but it may be worth the try.

Keep on BOINCing...! :)

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Very much doubt that will have any effect as the MD5 error you are seeing is suggestive of the file being corrupted somewhere between the SETI servers and you PC. As this problem does not appear to be affecting many people (you are the only one reporting it) I would be looking at the link between your ISP and your PCs.

In the past this sort of problem was caused when compression was turned on by the ISP, but not correctly recognised by the connected PC. Very frustrating to diagnose exactly where this is happening without full access to the intermediate server and router logs.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?