I was analizyng a memory dump from a blue window crash and I realized that BOINC was related (probably caused) to the crash.
I'm pasting below the result of the analisis. It was a 0x50 stop caused to win32k.sys, probably by boinc. I was in front of the PC at the moment, and I had just changed the BOINC config to reduce the percentage of the processor use. Suddenly I checked the Tasks window and realized that 2 tasks indicated that the calc failed. And these were the facts I saw right before the PC crashed.
Can anybody help me whith this? I think this may help us to detect a bug in BOINC, otherwise it may help us identifying something I did wrong. There goes the crash dump analisis:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112311-18064-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Symbols
Executable search path is: C:\Windows\System32
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03465000 PsLoadedModuleList = 0xfffff800`036a2e70
Debug session time: Wed Nov 23 19:33:23.671 2011 (GMT-2)
System Uptime: 2 days 12:17:29.185
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff9010000000e, 0, fffff960000e9705, 5}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -

Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!EngRestoreFloatingPointState+2ac5 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff9010000000e, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960000e9705, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000370d0e0
fffff9010000000e

FAULTING_IP:
win32k!EngRestoreFloatingPointState+2ac5
fffff960`000e9705 f6400f40 test byte ptr [rax+0Fh],40h

MM_INTERNAL_CODE: 5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: boincmgr.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88009191eb0 -- (.trap 0xfffff88009191eb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900ffffffff rbx=0000000000000000 rcx=fffff900c00077d8
rdx=fffff900c0213788 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960000e9705 rsp=fffff88009192040 rbp=fffff900c076a101
r8=0000000000000000 r9=0000000000000cfb r10=0000000056010001
r11=fffff88009192098 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
win32k!EngRestoreFloatingPointState+0x2ac5:
fffff960`000e9705 f6400f40 test byte ptr [rax+0Fh],40h ds:fffff901`0000000e=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800035547a1 to fffff800034d55c0

STACK_TEXT:
fffff880`09191d48 fffff800`035547a1 : 00000000`00000050 fffff901`0000000e 00000000`00000000 fffff880`09191eb0 : nt!KeBugCheckEx
fffff880`09191d50 fffff800`034d36ae : 00000000`00000000 fffff900`c23b2010 000007ff`fffde300 fffff960`000f5499 : nt! ?? ::FNODOBFM::`string'+0x40d4b
fffff880`09191eb0 fffff960`000e9705 : 00000000`0000119c 00000000`00000000 fffff900`c076a101 fffffa80`0813f180 : nt!KiPageFault+0x16e
fffff880`09192040 fffff960`002344eb : fffff900`c0756100 fffff900`c076a100 fffff900`c0854f70 fffff800`03423b7f : win32k!EngRestoreFloatingPointState+0x2ac5
fffff880`091920a0 fffff960`000efd9e : 000007ff`fffde7d8 fffff960`00000001 00000000`00000010 00000000`00000000 : win32k!XLATEOBJ_cGetPalette+0xe83b
fffff880`091920e0 fffff960`00075fc5 : fffff900`c0854f70 00000000`00000001 fffff960`00000000 00000000`0012f1b0 : win32k!EngRestoreFloatingPointState+0x915e
fffff880`09192170 fffff960`0010e2c4 : 00000000`00000000 fffff880`09192320 fffff960`0010e238 00000000`0012f1b0 : win32k!EngBitBlt+0x10965
fffff880`091921d0 fffff800`034d4813 : fffffa80`043bdb60 00000000`00000000 00000000`00000001 00000000`0012fc48 : win32k!W32pArgumentTable+0x95a8
fffff880`091922a0 00000000`778fb3aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0012f188 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778fb3aa


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!EngRestoreFloatingPointState+2ac5
fffff960`000e9705 f6400f40 test byte ptr [rax+0Fh],40h

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32k!EngRestoreFloatingPointState+2ac5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e83ef5b

FAILURE_BUCKET_ID: X64_0x50_win32k!EngRestoreFloatingPointState+2ac5

BUCKET_ID: X64_0x50_win32k!EngRestoreFloatingPointState+2ac5

Followup: MachineOwner
---------

The crash happened in win32k.sys, not in boincmgr.exe, which was just an innocent bystander when your system went haywire.

STOP 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA means as much as "Drivers are using improper memory addresses." It also says so in the dump: "DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT" and "Could not read faulting driver name".

That it happened after you changed something in BOINC, through BOINC Manager does not mean BOINC or BM is at fault. More that the cause lies elsewhere. Think of memory, CPU, hard drive. When BOINC runs work it'll put all those under quite some load. Any fault, any instability will come to light this way.

Try running Prime95 (32bit and 64bit version available) and Memtest86+ to test the CPU and memory with other programs. Prime95 is comparable to BOINC, in that it will put big stress on the CPU and memory. If that causes a same BSOD, it's your memory or CPU. Memtest86+ will stress test the memory.

See this Prime95 tutorial and Memtest86+ tutorial for more help.

---