Windows 7 BSODs

[geokilla]

For some odd reason, after installing Windows 7 in my rig I've been getting BSODs every once in a while. Sometimes this will cause me to lose my current WU and make it start all over again. I can't determine whether it's the Windows SMP or the NVIDIA GPU/Drivers that's causing the BSODs, but I am OCCT stable for over 6 hours. I've tried running Linpack, but I can't finish the test because my CPU gets up to 80C. I see no point in using Linpack anyways...

Code: Select all

[23:16:21] Completed 265000 out of 500000 steps  (53 percent)
[23:28:41] Writing local files
[23:28:41] Completed 270000 out of 500000 steps  (54 percent)
[23:41:17] Writing local files
[23:41:17] Completed 275000 out of 500000 steps  (55 percent)


--- Opening Log file [July 11 04:45:44 UTC] 


# Windows SMP Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.24R3

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Folding@Home\CPU
Executable: C:\Folding@Home\CPU\[email protected]
Arguments: -smp -verbosity 9 

[04:45:44] - Ask before connecting: No
[04:45:44] - User name: geokilla (Team 38296)
[04:45:44] - User ID: 2D7F8F3D2B43B143
[04:45:44] - Machine ID: 1
[04:45:44] 
[04:45:44] Loaded queue successfully.
[04:45:44] 
[04:45:44] + Processing work unit
[04:45:44] Work type a1 not eligible for variable processors
[04:45:44] Core required: FahCore_a1.exe
[04:45:44] Core found.
[04:45:44] Using generic mpiexec calls
[04:45:44] - Autosending finished units... [July 11 04:45:44 UTC]
[04:45:44] Trying to send all finished work units
[04:45:44] + No unsent completed units remaining.
[04:45:44] - Autosend completed
[04:45:44] Working on queue slot 02 [July 11 04:45:44 UTC]
[04:45:44] + Working ...
[04:45:44] - Calling 'mpiexec -np 4 -channel auto -host 127.0.0.1 FahCore_a1.exe -dir work/ -suffix 02 -checkpoint 15 -verbose -lifeline 3708 -version 624'

[04:45:45] 
[04:45:45] *------------------------------*
[04:45:45] Folding@Home Gromacs SMP Core
[04:45:45] Version 1.74 (March 10, 2007)
[04:45:45] 
[04:45:45] Preparing to commence simulation
[04:45:45] - Ensuring status. Please wait.
[04:46:02] - Looking at optimizations...
[04:46:02] - Working with standard loops on this execution.
[04:46:02] Examination of work files indicates 8 consecutive improper terminations of core.
[04:46:06] - Expanded 2451870 -> 12890333 (decompressed 525.7 percent)
[04:46:07] - Checksums don't match (work/wudata_02.arc)
[04:46:07] - Failed to delete work/wudata_02.arc
[04:46:07] No C.P. to delete.
[04:46:08] work/wudata_02.xvg
[04:46:08] Warning:  check for stray files
[04:46:08] - Starting from initial work packet
[04:46:08] 
[04:46:08] Project: 2653 (Run 13, Clone 155, Gen
[04:46:08] ProjecEntering M.D.
[04:46:08] 3, Clone 155, Gen 128)
[04:46:08] 
[04:46:08] Entering M.D.
[04:46:08] roject: 2653 (Run 13, ClEntering M.D.
[04:46:08] 28)
[04:46:08] 
[04:46:08] Entering M.D.
[04:46:14] t
[04:46:15] Protein: Protein in POPWrWriting local files
[04:46:16] Extra SSE boost OK.
[04:46:22] Writing local files
[04:46:22] Completed 0 out of 500000 steps  (0 percent)
[05:00:47] Writing local files
[05:00:47] Completed 5000 out of 500000 steps  (1 percent)
[05:14:50] Writing local files
[05:14:50] Completed 10000 out of 500000 steps  (2 percent)

[7im]

Intel Burn In tool? StressCPU v2 (based on code used by Fah, so always a good relative stress test).

If you can't pass StressCPU, fah is not going to run.

[geokilla]

Intel Burn In tool? StressCPU v2 (based on code used by Fah, so always a good relative stress test).

If you can't pass StressCPU, fah is not going to run.

Ran the test overnight and it passed fine. I re-checked my vcore settings and it went down to 1.4Vcore instead of the 1.43ish Vcore that I had set when it passed OCCT. I must've pressed the wrong button when I was in the BIOS. I have yet to get anymore BSODs.

[DaleF]

If your CPU is getting too hot when you're running certain benchmarks (such as Linpack) that says that you probably don't have adequate cooling (or are overclocking too high for the cooling that you do have). Personally, it sounds like that is the case to me. F@H is typically pretty good at pushing hardware hard, and if you have a heat problem, it'll likely cause it to manifest itself.
Back off the OC/upgrade your cooling and see if it happens still?