My computer's uptime right now is over 8 days. It's now about 54 hours since I started doing Seti and approaching 10 hours since I let it do Einstein along with the Seti. So far, so good.
I don't really see why you think your video artifact is related to your BOINC problem. I had pretty much the same problem as you, but on entirely different hardware (I have no separate GPU) and without the video artifact. I can understand you being annoyed by it, but I think it's an entirely separate issue.
I suggest you start running Seti -- only -- on your i7 and see if it can handle that. I'm not far enough into my Seti-and-Einstein-together experiment to recommend you follow my lead on that, but if I make it to Monday morning without a crash, I will suggest you try it then.
David
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
My computer's uptime right now is over 8 days. It's now about 54 hours since I started doing Seti and approaching 10 hours since I let it do Einstein along with the Seti. So far, so good.
I don't really see why you think your video artifact is related to your BOINC problem. I had pretty much the same problem as you, but on entirely different hardware (I have no separate GPU) and without the video artifact. I can understand you being annoyed by it, but I think it's an entirely separate issue.
I suggest you start running Seti -- only -- on your i7 and see if it can handle that. I'm not far enough into my Seti-and-Einstein-together experiment to recommend you follow my lead on that, but if I make it to Monday morning without a crash, I will suggest you try it then.
David
Greetings David,
Great going on your problem solving and uptime. My i7's uptime got blasted last night, about 12 hours ago. We've been having really high winds and I believe that the wind somehow caused a brownout ultimately shutting down both my i7 and my Linux PCs. I estimate that the i7 was up for about 57 hours before the brownout. That was without BOINC installed and running.
The artifact I mentioned is not caused by BOINC, it appears when I, or Windoze, installs the nVIDIA graphics driver(s). It's a tiny little approximately 2 by 8 pixel, speck of colored pixels the same colors as the Windoze logo. It appears when, I assume, Windows is doing its hardware checks. If I don't have nVIDIA installed, the artifact does not appear. BOINC has nothing to do with it, especially since I don't have BOINC installed right now.
The reason I believe that the appearance of the artifact, when booting, has any relation to BOINC is because when the artifact is appearing, when booting, that is when I have a problem with BOINC. When there is no appearance of the artifact, I have no problem running BOINC. That is the only relation with BOINC that the artifact has. As I said, the artifact is not caused by BOINC.
I really wish I could get a screen capture of it so that people will know exactly what I am talking about when I mention the artifact.
I have been thinking of installing BOINC, again, to see how it fares since my update of the BIOS software. Maybe let it get a few SETI WUs and see what happens. The last time I did, I was doing some MilkyWay WUs, for testing, and most of them had computation errors after 3 hours of running. I immediately shut BOINC down and uninstalled it.
Without BOINC running, the i7 runs just fine. It's when BOINC is running, whether doing actual work or not, and having nVIDIA installed, that it wreaks havoc with my i7. I firmly believe that if I don't use nVIDIA or I can get it to install without having the artifact appearing, that BOINC and the i7 will do just fine. I installed Linux on the i7 as a dual boot and installed the Linux version of BOINC. It ran without a single problem, even running 2 projects WUs. That alone tells me that there is nothing wrong with the i7. Hmmm... Let me think on this some more...
... The artifact I mentioned is not caused by BOINC, it appears when I, or Windoze, installs the nVIDIA graphics driver(s). It's a tiny little approximately 2 by 8 pixel, speck of colored pixels the same colors as the Windoze logo. It appears when, I assume, Windows is doing its hardware checks. If I don't have nVIDIA installed, the artifact does not appear. BOINC has nothing to do with it, especially since I don't have BOINC installed right now.
The reason I believe that the appearance of the artifact, when booting, has any relation to BOINC is because when the artifact is appearing, when booting, that is when I have a problem with BOINC. When there is no appearance of the artifact, I have no problem running BOINC. That is the only relation with BOINC that the artifact has. As I said, the artifact is not caused by BOINC.
I really wish I could get a screen capture of it so that people will know exactly what I am talking about when I mention the artifact.
I have been thinking of installing BOINC, again, to see how it fares since my update of the BIOS software. Maybe let it get a few SETI WUs and see what happens. The last time I did, I was doing some MilkyWay WUs, for testing, and most of them had computation errors after 3 hours of running. I immediately shut BOINC down and uninstalled it.
Without BOINC running, the i7 runs just fine. It's when BOINC is running, whether doing actual work or not, and having nVIDIA installed, that it wreaks havoc with my i7. I firmly believe that if I don't use nVIDIA or I can get it to install without having the artifact appearing, that BOINC and the i7 will do just fine. I installed Linux on the i7 as a dual boot and installed the Linux version of BOINC. It ran without a single problem, even running 2 projects WUs. That alone tells me that there is nothing wrong with the i7. Hmmm... Let me think on this some more...
Your description looks like graphics memory corruption.
Adding in your surrounding pieces, that could be a Windows driver problem or something that is specific to that hardware and Windows.
However... Why is that not a problem for everyone else using a similar setup to yours?... What is there that is unique for your one example?...
... The artifact I mentioned is not caused by BOINC, it appears when I, or Windoze, installs the nVIDIA graphics driver(s). It's a tiny little approximately 2 by 8 pixel, speck of colored pixels the same colors as the Windoze logo. It appears when, I assume, Windows is doing its hardware checks. If I don't have nVIDIA installed, the artifact does not appear. BOINC has nothing to do with it, especially since I don't have BOINC installed right now.
The reason I believe that the appearance of the artifact, when booting, has any relation to BOINC is because when the artifact is appearing, when booting, that is when I have a problem with BOINC. When there is no appearance of the artifact, I have no problem running BOINC. That is the only relation with BOINC that the artifact has. As I said, the artifact is not caused by BOINC.
I really wish I could get a screen capture of it so that people will know exactly what I am talking about when I mention the artifact.
I have been thinking of installing BOINC, again, to see how it fares since my update of the BIOS software. Maybe let it get a few SETI WUs and see what happens. The last time I did, I was doing some MilkyWay WUs, for testing, and most of them had computation errors after 3 hours of running. I immediately shut BOINC down and uninstalled it.
Without BOINC running, the i7 runs just fine. It's when BOINC is running, whether doing actual work or not, and having nVIDIA installed, that it wreaks havoc with my i7. I firmly believe that if I don't use nVIDIA or I can get it to install without having the artifact appearing, that BOINC and the i7 will do just fine. I installed Linux on the i7 as a dual boot and installed the Linux version of BOINC. It ran without a single problem, even running 2 projects WUs. That alone tells me that there is nothing wrong with the i7. Hmmm... Let me think on this some more...
Your description looks like graphics memory corruption.
After the problem started, when I attached to Einstein, the artifact would show up from then on during boot and at that time I was running a 6 month old Evga nVIDIA card. Ok, like you, I thought it was a problem with the card, so I replaced it with a brand new Galaxy nVIDIA card. Same thing, even after several repair installs and a clean install of WinXP.
So, unless there is an identical problem with these 2 cards of different manufacture and I believe technology, I seem to remember a reference to the new card built on Fermi technology, I believe it highly unlikely that it is a video hardware problem. FurMark reported no problem with the new card after it torture tested the card.
Quote:
Adding in your surrounding pieces, that could be a Windows driver problem or something that is specific to that hardware and Windows.
As I have stated many times, the only time the artifact appears is when I have nVIDIA installed. When I did the clean install of WinXP, I assume a generic Micro$oft video driver was being used. Until I installed the nVIDIA driver, the artifact never once appeared during any boot cycle. Once the nVIDIA driver was installed, BAM! The artifact appeared. And when it makes its appearance, something screws with BOINC.
Quote:
However... Why is that not a problem for everyone else using a similar setup to yours?... What is there that is unique for your one example?...
A 6 year old DVD/CD re-writable drive, that works perfectly? A 6 year old, or so, iOmega Zip drive that I don't have powered or a data cable hooked to? The fact that this MoBo does not come with a floppy drive port? Had to get a USB floppy drive, which I never use, by the way. Floppies are so, 20th century. ;)
Quote:
Something going wrong during the Windows bootup?
Keep searchin',
Martin
Although I haven't looked at it lately, I would look at the event log to see if a clue could be found there. Nothing shows up in the log without the artifact appearance or with it.
I had nVIDIA installed, when running with the 6 month old card, for, well, 6 months and had no problem at all. BOINC did its thing just fine. As soon as I attached to Einstein, BAM! I now cannot run BOINC when nVIDIA is installed. Well, I can, it's just that running them both screws with the i7 somehow, or perhaps Windoze. I have no clue anymore.
As I stated some time ago, here in this thread, the only other test I can think of to do, which may bring a definitive solution, would be to abandon the nVIDIA technology and switch to ATI. But, that will have to wait until I get my tax return or get back to work in about 4 more weeks.
I last rebooted my computer about 5pm on 3 December (that only because at the previous reboot the network adapter failed to initialize). I allowed it to get Seti tasks somewhere around 6pm on 9 Dec. And I allowed it to get Einstein tasks about 2:20pm on 11 Dec. So far, nothing has crashed or frozen. My radio feed is still online. Next, I plan to gradually increase Einstein's resource share back to what it was before, 50. If it keeps working that way, then one of two things fixed it: either increasing the preference setting for "stop work when non-BOINC CPU usage reaches" from 20% to 40%; or I'm right about Seti "regulating" Einstein, perhaps in that the regular switching back and forth between projects causes the Einstein problem to reset every time it stops running to allow Seti to run.
I definitely think you should proceed with your plan to let your i7 do some Seti work. Set your cache very small first so it only downloads a small amount of work it in case it doesn't work. (Of course, Seti's splitters ran out of data to split overnight, and today they'll be going into their regular weekly outage...) If it does work for 2-3 days, then cautiously let it have a bit of Einstein.
Now if only I can remember where that resource share setting is...
David
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
Update:
Now if only I can remember where that resource share setting is...
David
It is on the website under Your Account and then:
Preferences for this project Einstein@Home preferences
Yeah, I found it. But now Seti's out of work again and I'm not going to take Einstein off NNT again until there is a steady supply of Seti so it can keep switching between them.
David
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
Before doing last night's 13 Micro$oft updates, which of course required a re-boot, the i7 ran for 3 days 21 hours without a single problem. This was without BOINC installed and running.
One thing I did notice, and Googled about, was that my Vcore voltage was averaging 0.88 volts. I saw somewhere, on the Internet, where the Vcore voltage parameters are between 0.8x and 1.xx volts. Ok, so the i7 is at the minimum Vcore voltage. Cool.
I decided to install BOINC and attach to SETI. I dropped the CPU core usage back to 50% (4 cores 12.5% usage each) and it is currently running. After the downloads were complete, I set SETI to NNT. BOINC has been running roughly 2 hours now. It completed 4 WUs and is currently trying to upload the fourth. The other 3 have not been reported yet either. I believe the connection to SETI may be down... Well, I just looked and the fourth WU has uploaded. And, all 4 are now reported. Well see how well this is going to work. Vcore voltage is now at 1.12v
The i7 BOINCs much, much faster than the Core 2 Duo does. But then, I would guess that's to be expected, huh? ;)
I have made no further changes to the i7 since I updated the BIOS about a week ago or so. I still get the artifact when the i7 boots. The reason I installed BOINC and went with SETI is that I had no problems running SETI before all this started. I'm thinking that if all goes well running SETI, I will NOT be running Einstein. Ahh, but then, in my previous tests running VP and MW I had the problem. So... I guess we'll see. :)
That's it for now. I'll report back in a few hours with any further developments. :)
Just under 10 hours and I had 18 SETI WUs completed and reported. No adverse affects noticed. I will now get some more WUs and continue this test. Update to follow, when done with the next batch...
Just under 10 hours and I had 18 SETI WUs completed and reported. No adverse affects noticed. I will now get some more WUs and continue this test. Update to follow, when done with the next batch...
Good luck.
After good confidence with the s@h WUs...
Just for a giggle, try a few e@h WUs to see what happens?...
Happy crunchin',
Martin
ps: Hope you're going to write an executive summary after this little epic!
Siran, My computer's
)
Siran,
My computer's uptime right now is over 8 days. It's now about 54 hours since I started doing Seti and approaching 10 hours since I let it do Einstein along with the Seti. So far, so good.
I don't really see why you think your video artifact is related to your BOINC problem. I had pretty much the same problem as you, but on entirely different hardware (I have no separate GPU) and without the video artifact. I can understand you being annoyed by it, but I think it's an entirely separate issue.
I suggest you start running Seti -- only -- on your i7 and see if it can handle that. I'm not far enough into my Seti-and-Einstein-together experiment to recommend you follow my lead on that, but if I make it to Monday morning without a crash, I will suggest you try it then.
David
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
RE: Siran, My computer's
)
Greetings David,
Great going on your problem solving and uptime. My i7's uptime got blasted last night, about 12 hours ago. We've been having really high winds and I believe that the wind somehow caused a brownout ultimately shutting down both my i7 and my Linux PCs. I estimate that the i7 was up for about 57 hours before the brownout. That was without BOINC installed and running.
The artifact I mentioned is not caused by BOINC, it appears when I, or Windoze, installs the nVIDIA graphics driver(s). It's a tiny little approximately 2 by 8 pixel, speck of colored pixels the same colors as the Windoze logo. It appears when, I assume, Windows is doing its hardware checks. If I don't have nVIDIA installed, the artifact does not appear. BOINC has nothing to do with it, especially since I don't have BOINC installed right now.
The reason I believe that the appearance of the artifact, when booting, has any relation to BOINC is because when the artifact is appearing, when booting, that is when I have a problem with BOINC. When there is no appearance of the artifact, I have no problem running BOINC. That is the only relation with BOINC that the artifact has. As I said, the artifact is not caused by BOINC.
I really wish I could get a screen capture of it so that people will know exactly what I am talking about when I mention the artifact.
I have been thinking of installing BOINC, again, to see how it fares since my update of the BIOS software. Maybe let it get a few SETI WUs and see what happens. The last time I did, I was doing some MilkyWay WUs, for testing, and most of them had computation errors after 3 hours of running. I immediately shut BOINC down and uninstalled it.
Without BOINC running, the i7 runs just fine. It's when BOINC is running, whether doing actual work or not, and having nVIDIA installed, that it wreaks havoc with my i7. I firmly believe that if I don't use nVIDIA or I can get it to install without having the artifact appearing, that BOINC and the i7 will do just fine. I installed Linux on the i7 as a dual boot and installed the Linux version of BOINC. It ran without a single problem, even running 2 projects WUs. That alone tells me that there is nothing wrong with the i7. Hmmm... Let me think on this some more...
Gotta get back to my snow shoveling... :(
Keep on BOINCing...! :)
CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187
Siran's website: [ ONLINE! ]
RE: ... The artifact I
)
Your description looks like graphics memory corruption.
Adding in your surrounding pieces, that could be a Windows driver problem or something that is specific to that hardware and Windows.
However... Why is that not a problem for everyone else using a similar setup to yours?... What is there that is unique for your one example?...
Something going wrong during the Windows bootup?
Keep searchin',
Martin
See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)
Greetings
)
Greetings Martin,
After the problem started, when I attached to Einstein, the artifact would show up from then on during boot and at that time I was running a 6 month old Evga nVIDIA card. Ok, like you, I thought it was a problem with the card, so I replaced it with a brand new Galaxy nVIDIA card. Same thing, even after several repair installs and a clean install of WinXP.
So, unless there is an identical problem with these 2 cards of different manufacture and I believe technology, I seem to remember a reference to the new card built on Fermi technology, I believe it highly unlikely that it is a video hardware problem. FurMark reported no problem with the new card after it torture tested the card.
As I have stated many times, the only time the artifact appears is when I have nVIDIA installed. When I did the clean install of WinXP, I assume a generic Micro$oft video driver was being used. Until I installed the nVIDIA driver, the artifact never once appeared during any boot cycle. Once the nVIDIA driver was installed, BAM! The artifact appeared. And when it makes its appearance, something screws with BOINC.
A 6 year old DVD/CD re-writable drive, that works perfectly? A 6 year old, or so, iOmega Zip drive that I don't have powered or a data cable hooked to? The fact that this MoBo does not come with a floppy drive port? Had to get a USB floppy drive, which I never use, by the way. Floppies are so, 20th century. ;)
Although I haven't looked at it lately, I would look at the event log to see if a clue could be found there. Nothing shows up in the log without the artifact appearance or with it.
I had nVIDIA installed, when running with the 6 month old card, for, well, 6 months and had no problem at all. BOINC did its thing just fine. As soon as I attached to Einstein, BAM! I now cannot run BOINC when nVIDIA is installed. Well, I can, it's just that running them both screws with the i7 somehow, or perhaps Windoze. I have no clue anymore.
As I stated some time ago, here in this thread, the only other test I can think of to do, which may bring a definitive solution, would be to abandon the nVIDIA technology and switch to ATI. But, that will have to wait until I get my tax return or get back to work in about 4 more weeks.
Thanks Martin! :)
Keep on BOINCing...! :)
CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187
Siran's website: [ ONLINE! ]
Update: I last rebooted my
)
Update:
I last rebooted my computer about 5pm on 3 December (that only because at the previous reboot the network adapter failed to initialize). I allowed it to get Seti tasks somewhere around 6pm on 9 Dec. And I allowed it to get Einstein tasks about 2:20pm on 11 Dec. So far, nothing has crashed or frozen. My radio feed is still online. Next, I plan to gradually increase Einstein's resource share back to what it was before, 50. If it keeps working that way, then one of two things fixed it: either increasing the preference setting for "stop work when non-BOINC CPU usage reaches" from 20% to 40%; or I'm right about Seti "regulating" Einstein, perhaps in that the regular switching back and forth between projects causes the Einstein problem to reset every time it stops running to allow Seti to run.
I definitely think you should proceed with your plan to let your i7 do some Seti work. Set your cache very small first so it only downloads a small amount of work it in case it doesn't work. (Of course, Seti's splitters ran out of data to split overnight, and today they'll be going into their regular weekly outage...) If it does work for 2-3 days, then cautiously let it have a bit of Einstein.
Now if only I can remember where that resource share setting is...
David
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
RE: Update: Now if only I
)
It is on the website under Your Account and then:
Preferences for this project Einstein@Home preferences
RE: RE: Update: Now if
)
Yeah, I found it. But now Seti's out of work again and I'm not going to take Einstein off NNT again until there is a steady supply of Seti so it can keep switching between them.
David
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
Greetings everyone, ***
)
Greetings everyone,
*** UPDATE ***
Before doing last night's 13 Micro$oft updates, which of course required a re-boot, the i7 ran for 3 days 21 hours without a single problem. This was without BOINC installed and running.
One thing I did notice, and Googled about, was that my Vcore voltage was averaging 0.88 volts. I saw somewhere, on the Internet, where the Vcore voltage parameters are between 0.8x and 1.xx volts. Ok, so the i7 is at the minimum Vcore voltage. Cool.
I decided to install BOINC and attach to SETI. I dropped the CPU core usage back to 50% (4 cores 12.5% usage each) and it is currently running. After the downloads were complete, I set SETI to NNT. BOINC has been running roughly 2 hours now. It completed 4 WUs and is currently trying to upload the fourth. The other 3 have not been reported yet either. I believe the connection to SETI may be down... Well, I just looked and the fourth WU has uploaded. And, all 4 are now reported. Well see how well this is going to work. Vcore voltage is now at 1.12v
The i7 BOINCs much, much faster than the Core 2 Duo does. But then, I would guess that's to be expected, huh? ;)
I have made no further changes to the i7 since I updated the BIOS about a week ago or so. I still get the artifact when the i7 boots. The reason I installed BOINC and went with SETI is that I had no problems running SETI before all this started. I'm thinking that if all goes well running SETI, I will NOT be running Einstein. Ahh, but then, in my previous tests running VP and MW I had the problem. So... I guess we'll see. :)
That's it for now. I'll report back in a few hours with any further developments. :)
Keep on BOINCing...! :)
CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187
Siran's website: [ ONLINE! ]
Greetings everyone, ***
)
Greetings everyone,
*** UPDATE ***
Just under 10 hours and I had 18 SETI WUs completed and reported. No adverse affects noticed. I will now get some more WUs and continue this test. Update to follow, when done with the next batch...
Keep on BOINCing...! :)
CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187
Siran's website: [ ONLINE! ]
RE: Just under 10 hours and
)
Good luck.
After good confidence with the s@h WUs...
Just for a giggle, try a few e@h WUs to see what happens?...
Happy crunchin',
Martin
ps: Hope you're going to write an executive summary after this little epic!
See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)