Collatz is BSODing my computer

[Maxwell]

Ok. So, my computer (Silver Hammer), used to run Collatz quite well. After the DNETC scare, I ran DNETC up to 100M, changing none of the setting on my system. Today, I stop DNETC and start Collatz back up. Nothing but a string of BSODs.

This is Win7x64, 2x5970, CCC 10.10, BOINC 6.10.58. Running (now) at stock settings.

I have restarted the machine, reset the project, detached/reattached to Collatz. I uninstalled the driver, ran Driver Sweeper, reinstalled the driver (10.10 has historically been the most stable on my system). I ran chkdsk, and I keep getting the same thing over and over.

Any ideas as to what I can try? I want to go on a Collatz push, but need working cards to do that...

[Fire$torm]

Ok. So, my computer (Silver Hammer), used to run Collatz quite well. After the DNETC scare, I ran DNETC up to 100M, changing none of the setting on my system. Today, I stop DNETC and start Collatz back up. Nothing but a string of BSODs.

This is Win7x64, 2x5970, CCC 10.10, BOINC 6.10.58. Running (now) at stock settings.

I have restarted the machine, reset the project, detached/reattached to Collatz. I uninstalled the driver, ran Driver Sweeper, reinstalled the driver (10.10 has historically been the most stable on my system). I ran chkdsk, and I keep getting the same thing over and over.

Any ideas as to what I can try? I want to go on a Collatz push, but need working cards to do that...

I would try the following:
Detach Collatz and shutdown BM.

Locate your BOINC data\projects folder and make sure the "boinc.thesonntags.com_collatz" folder and the "boinc.thesonntags.com_collatzsymbols" folder have been deleted.

Run CCleaner on the registry for orphaned entries and the HDD for orphaned files.

Run Free Registry DeFrag (will not really help the problem but it will help speed bootup so why not.) DeFrag will request reboot when it is finished, say yes.

Now go to Collatz website and make sure ONLY GPU work is selected. Note: Collatz now has a "Mini Collatz" app. Try the normal app first. Try the mini app if the normal app crap out your system.

Reattach Collatz. (Keeping fingers crossed)

[Crazybob]

I pulled some Collatz today to make up for MW being down and did notice 1 WU ran for 1 hour and 11 minutes.

[Maxwell]

I pulled some Collatz today to make up for MW being down and did notice 1 WU ran for 1 hour and 11 minutes.

Slicker recently upped the size of the Collatz WUs, so that's not surprising. They are now 4x longer than they used to be.

@F$: The only part of that I hadn't tried was running CC cleaner. But I did just follow your directions and got the same "screen goes oddly pixelated, blacks out, BSOD, shut down" sequence.

Crap. Other thoughts? My computer is being naughty right now...

[Fire$torm]

Slicker recently upped the size of the Collatz WUs, so that's not surprising. They are now 4x longer than they used to be.

@F$: The only part of that I hadn't tried was running CC cleaner. But I did just follow your directions and got the same "screen goes oddly pixelated, blacks out, BSOD, shut down" sequence.

Crap. Other thoughts? My computer is being naughty right now...

Not really sure although jokers comment jogged a memory. I think it would be a good Idea to "Re-seat" all your computer parts, cards, plugs and screws. And while your at it try swapping the positions of any components that have twins, video cards, memory stick. One last thing, err two last things. Run an anti-malware utility like Malwarebytes and unplug all USB devices sans mouse and KB.

[Mumps]

And, also, have you tried running only mini-Collatz? That might help identify if the cards simply don't like the longer WU's.

[Maxwell]

So as it turns out, it is not Collatz specifically, but any load on the cards now. I tested Mumps' idea the opposite way - I started to run a DNETC WU on there (which was fine until yesterday), and got the same BSOD problem.

When I get a chance to dig into the computer, I'll reseat every thing. Thanks for the ideas, folks.

[joker]

I am not a computer guru in any manner but I did have a case of the BSOD's awhile back and it ended up being my memory. I just laxed my timings a little and it solved my problems. Good luck.

[Maxwell]

I am not a computer guru in any manner but I did have a case of the BSOD's awhile back and it ended up being my memory. I just laxed my timings a little and it solved my problems. Good luck.

So this is the one thing I haven't tried...

I have done just about everything else suggested in this thread, save for swapping out hardware/trying things in a new system (both of which aren't possible for me).

After running through y'all's suggestions and a crapton of googling the symptoms, I've seen quite a few mentions of it potentially being a RAM issue. I have run Win7's Memtest, and it showed that everything was fine. However, I did find several folks online who noted it really was a RAM problem, even though the RAM passed the Memtest. They solved the issue by doing what joker did - lax the timings.

So how do I do that?

[Harley]

So this is the one thing I haven't tried...

I have done just about everything else suggested in this thread, save for swapping out hardware/trying things in a new system (both of which aren't possible for me).

After running through y'all's suggestions and a crapton of googling the symptoms, I've seen quite a few mentions of it potentially being a RAM issue. I have run Win7's Memtest, and it showed that everything was fine. However, I did find several folks online who noted it really was a RAM problem, even though the RAM passed the Memtest. They solved the issue by doing what joker did - lax the timings.

So how do I do that?

Its done through the MB BIOS setup.