Wow...y'all are a testy bunch aren't you.

The answer is still BOINC regardless of the task, since the software is needed to run the task. If I uninstall BOINC the issues cease. I understand that the task adds another element to the mix, but in the end, it all comes back here since the individual science projects don't want to deal with the issue, they simply tell me to come here.

The task that "seems" to be running most of the time (I can't sit and monitor it 24 hours a day) is SETI.

---

[quote]
You would be testy too if you tried to deal with you but you don't... you just come here and make us deal with you.

Excuse me? I've gone out of my way for weeks testing and re-testing trying to find a fix for the problem. First with the SETI folks, and now here.

Why? Because I care about the science. I've been crunching numbers for YEARS, and never, ever has anyone been as rude as you.

You know what, I'm sorry I'm a bit fed up, but after weeks and weeks of this, I'm at my wits end. For you to talk down to me, and be rude, is just unacceptable.

So for you to say "You would be testy too if you tried to deal with you", is rude to a level that I can't believe. I'm literally shaking I am so mad.

If you turn your computer off and leave it off then it doesn't crash and we don't have a problem. So it must be your broken computer. Now you wanna talk sense or you wanna just point figners?

Look, my point was that I had eliminated everything EXCEPT the tasks and BOINC. I've been talking sense, but you know what, I've been told for weeks it was my computer, so if you want to talk pointing fingers, I suggest you look in the mirror.

Because they know the fixer meisters are here. So listen when we tell you.

Ummm...yeah, but all you can manage to do is be rude, and yet I've complied with ever action you've asked me to take. If you look at all that I have done, and all the information I have provided you would see that. However, instead you just want to be rude and nasty.

NOW DAMMIT!!... well... we'll play with you for a while until you're no longer amusing and then one by one we'll just ignore you.

Really? You won't play with my anymore? I mean seriously? All I want to do is contribute to the science. Isn't that supposed to be the point? You know what, if this petty BS is all BOINC is about, then I'll gladly uninstall the app and forget you even exist...but I "wanted" to help.

Oh, and turn off your screensaver or set it to "blank screen" to see if that's causing the crash. No, don't tell us it can't be the screensaver, just do it.

Screensaver has never been used (well not for over a year or more).

Even though I've had to endure the way you talk to me, when all I want to do is fix the issue, I'll try one last thing. I'll do as you suggest and detach from SETI...see what happens.

Hopefully you'll still "want to play with me".

---

OK, everyone got that out of their systems? Thanks, enough. Please be civil.

I have looked a little into the nvlddmkm.sys BSOD and have read plenty of forums with people having this error. It happens on all Nvidia cards that I can see, with all versions of Windows. Different drivers don't make any difference. What does fix it for a lot of people, is to get a new video card. Weirdly enough, exchanging the present video card for a new Nvidia card fixes the problem 100%.

Then there is the thing with the blowing capacitors, we have someone walking around both these and the Seti forums posting all about it. But ok, usually when caps blow, the card doesn't work anymore. So that's scratched off the list. ;-)

So yes, test with which projects you do and don't get the BSOD.
Write down what project science application was running at the time of the BSOD. (if need be at a guess)

---

Ok, after testing for quite a few more days, it appears that only when tasks from SETI are running does the BSOD occur. So, detaching from SETI solves the issue, yet I'd sure like to get back to running tasks from SETI.

Any thoughts?

Thanks!

---

Ok, after testing for quite a few more days, it appears that only when tasks from SETI are running does the BSOD occur. So, detaching from SETI solves the issue, yet I'd sure like to get back to running tasks from SETI.

Any thoughts?

Thanks!

Are those CUDA tasks?

Yes, but I've disabled CUDA (went to SETI preferences, disable all GPU usage).

---

So, all CUDA tasks are finished but the BSODs still occur?

The preferences only prevent new tasks from being downloaded, already present ones still have to be processed (or aborted).

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

Hmm, ok...since I've detached, I will re-attach and get all new tasks. See if it BSODs anymore now.

---