man I'm a nub...can someone also inform me what I'm doing wrong with my signature to get the folding stats? lol

oh alright here we go:
I have a 650w corsair psu and the Q8400 is actually quad core...but so what you guys are saying is I should be running either the gpu or the smp2...but not at the same time?

Not sure now which driver it was, but a while back I had random driver related BSODs. Sometimes half an hour after I started folding on the gpus, sometimes it took a week. Not sure which driver I used back then, and which one I´m using atm (and is rock stable).
I´ll let you know when I get back home
edit: the one that´s rock solid for me now is 266.58, so you may have a different issue there

nah it's all good...how do you run it with 3 cores??

I guess it could be an overheating situation...
 
alright something else could be goin on...I was just folding only with my GTX 570 and the run of the mill single core processor and boom after a few hrs I come back downstairs to another bsod...so it can't be the SMP...
 
The problem is I never BSOD until I started folding...though I can game for like 10 hrs straight...prime95 and memtest are both solid...
 
One thing I recall is that I had put in two new sticks of ram that weren't being used to get to 6gb of ram...though it's been fine for about a month...
 
idk if this helps but the BSOD said "Driver_IRQL_NOT_LESS_OR_EQUAL" and "ndis.sys - address FFFFF8800147787A"
 
anyway if someone could help me out with some info that would be great...I really want to start folding basically every time I'm not gaming...but this is really off putting :(
 
 

well the thing is it has happened twice now today...even though the past week I've been folding no prob...
 
here's one really big thing I'm noticing...both times it seems to be as it's sending a finished WU??

I have HFM....is that the same?  The reason I'm saying that it's when it's sending is because when I reboot it says that it's sending and a new WU usually starts up after the BSOD reboot...

so this program tracks it all...but will it help my BSOD?

Im such a nub but what is eoc?? Lol

ah ok lol...yeah I tried that tracker program but idk I can't seem to get it to start through that...just seems easier for me to run it without the tracker...
 
I'm going to fold for the night and track it with hfm like i've been doing...I'm not going to run either the cpu or smp though...just gpu for the night to try to eliminate the fact that it could be conflicting when the two run together...
 
I'll let you guys know if it crashes in the morning :P

Sounds like it. Which wu was it?

i'm a new user, and i'm also having BSOD issues, but idk if for the same reasons.
 
i DLd the CPU and GPU client. though i'm running Win7 64bit, the DLer says it's for 32bit x86 OS, the description in the DL says windows vista/7. Figured this was ok.
 
so i tried CPU folding, and i saw the icon in the notification area. just for giggles, i opened multiple cores for folding, 2 to be exact. that wasn't good. BSOD. then i tried just one core, after less than 1/2 hr BSOD. i noticed someone mention we could run folding with a single core, so i'm wondering if i DLed the right clients. 6.23 and 6.41 respectively i believe.
 
i don't even know what SMP2 is when u guys mention it. what doe that fold off of?
 
so i tried the GPU folding as well. i left it overnight as it looked fine for the first 10 min until my comp's display turned off (i'm in high performance mode, so no sleep mode). should i leave the display on all night as well?
 
note, i am OCd. specs are in my MRs.

both CPU and GPU are watercooled ATM. on highest settings games never gets above 50. i already have an idea it's my voltage or ram settings.. TY!

Guinibee

ah ok lol...yeah I tried that tracker program but idk I can't seem to get it to start through that...just seems easier for me to run it without the tracker...

I'm going to fold for the night and track it with hfm like i've been doing...I'm not going to run either the cpu or smp though...just gpu for the night to try to eliminate the fact that it could be conflicting when the two run together...

I'll let you guys know if it crashes in the morning :P

Guinibee, if you want to know what the root cause was, when Windows 7 crashes it creates a Dump file located on your machine.
 
This file is located (typically) at C:\Windows\Minidump\  and has a .dmp extension.  You can open this file with a debug editor of your choice and read out the logs to find the root cause of your crash.
 
Here's a link if you'd like to try it yourself:  http://support.microsoft.com/kb/315263
 
Alternatively, I'm (unfortunately) very familiar with these dumps and have all the tools to read them if you can upload your dmp file here or post somewhere and send me a link.