My boinc manager keeps crashing and causing BSOD after a few seconds of system boot even when I haven't add any projects.
Can anyone help find out what's the problem? Thank you very much!

Here is the BSOD dump file info viewed by Windbg:

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


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

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.17.amd64fre.th2_release.151121-2308
Machine Name:
Kernel base = 0xfffff802`76e90000 PsLoadedModuleList = 0xfffff802`7716ec70
Debug session time: Tue Jan 12 14:24:41.212 2016 (UTC - 5:00)
System Uptime: 0 days 0:00:35.917
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 139, {3, ffffd000e1b87650, ffffd000e1b875a8, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )

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

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

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd000e1b87650, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd000e1b875a8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10586.17.amd64fre.th2_release.151121-2308

SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME: GL552VW

SYSTEM_SKU: ASUS-NotebookSKU

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: GL552VW.216

BIOS_DATE: 11/20/2015

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: GL552VW

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: 3

BUGCHECK_P2: ffffd000e1b87650

BUGCHECK_P3: ffffd000e1b875a8

BUGCHECK_P4: 0

TRAP_FRAME: ffffd000e1b87650 -- (.trap 0xffffd000e1b87650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe000ed488690 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe000ed6f7a88 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80276fe9d82 rsp=ffffd000e1b877e0 rbp=0000000000000001
r8=ffffe000e8aa7338 r9=0000000000000000 r10=7fffe000e8aa7338
r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
nt! ?? ::FNODOBFM::`string'+0x8c82:
fffff802`76fe9d82 cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: ffffd000e1b875a8 -- (.exr 0xffffd000e1b875a8)
ExceptionAddress: fffff80276fe9d82 (nt! ?? ::FNODOBFM::`string'+0x0000000000008c82)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

CPU_COUNT: 8

CPU_MHZ: a20

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 33'00000000 (cache) 33'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT

BUGCHECK_STR: 0x139

PROCESS_NAME: System

CURRENT_IRQL: 2

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000003

ANALYSIS_SESSION_HOST: DESKTOP-951QFR1

ANALYSIS_SESSION_TIME: 01-12-2016 17:10:09.0557

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER: from fffff80276fdd2e9 to fffff80276fd2760

STACK_TEXT:
ffffd000`e1b87328 fffff802`76fdd2e9 : 00000000`00000139 00000000`00000003 ffffd000`e1b87650 ffffd000`e1b875a8 : nt!KeBugCheckEx
ffffd000`e1b87330 fffff802`76fdd610 : 00000000`00000000 00000000`00000008 ffffe000`e8a96088 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffffd000`e1b87470 fffff802`76fdc7f3 : ffffe000`ebb18611 ffffc001`4b600170 ffffd000`e1b87740 ffffc001`00000010 : nt!KiFastFailDispatch+0xd0
ffffd000`e1b87650 fffff802`76fe9d82 : ffffe000`ed37c9a8 fffff802`76ec272f 00000000`00000000 fffff802`76ea5197 : nt!KiRaiseSecurityCheckFailure+0xf3
ffffd000`e1b877e0 fffff802`76ea42c4 : ffffe000`00000000 ffffe000`ed37c900 ffffe000`ed37c900 00000000`ffffffff : nt! ?? ::FNODOBFM::`string'+0x8c82
ffffd000`e1b87810 fffff802`76ea41e2 : 00000000`00000000 00000000`00000001 00000000`00000001 ffffe000`00000002 : nt!CcDeallocateBcb+0x1c
ffffd000`e1b87840 fffff802`76ea3daa : ffffe000`00000001 00000000`0002d000 00000000`000002fd 00000000`00000001 : nt!CcUnpinFileDataEx+0x3c2
ffffd000`e1b878a0 fffff802`76f30180 : 00000000`0002d000 ffffd000`e1b879a9 00000000`00000900 00000000`0002d000 : nt!CcReleaseByteRangeFromWrite+0xaa
ffffd000`e1b878f0 fffff802`76f30686 : ffffe000`e745b8b0 00000000`00000000 00000000`00000001 ffffd000`e1b87a98 : nt!CcFlushCachePriv+0x450
ffffd000`e1b87a00 fffff802`76efab79 : fffff802`77223200 ffffe000`00001000 00000000`00000000 00000000`ae193431 : nt!CcWriteBehindInternal+0x156
ffffd000`e1b87a80 fffff802`76e99125 : 0000008d`bd9bbfff 00000000`00000080 ffffe000`e6279680 ffffe000`e8bff800 : nt!ExpWorkerThread+0xe9
ffffd000`e1b87b10 fffff802`76fd7906 : ffffd000`e65af180 ffffe000`e8bff800 fffff802`76e990e4 00000000`00000000 : nt!PspSystemThreadStartup+0x41
ffffd000`e1b87b60 00000000`00000000 : ffffd000`e1b88000 ffffd000`e1b81000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 8c66561180cc9266a886088d1ad4aeaea6368885

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 34e9acfcca7200aac1294562de7a2b15629e465b

THREAD_SHA1_HASH_MOD: fe34192f63d13620a8987d294372ee74d699cfee

FOLLOWUP_IP:
nt!KiFastFailDispatch+d0
fffff802`76fdd610 c644242000 mov byte ptr [rsp+20h],0

FAULT_INSTR_CODE: 202444c6

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiFastFailDispatch+d0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 565189c8

IMAGE_VERSION: 10.0.10586.17

BUCKET_ID_FUNC_OFFSET: d0

FAILURE_BUCKET_ID: 0x139_3_nt!KiFastFailDispatch

BUCKET_ID: 0x139_3_nt!KiFastFailDispatch

PRIMARY_PROBLEM_CLASS: 0x139_3_nt!KiFastFailDispatch

TARGET_TIME: 2016-01-12T19:24:41.000Z

OSBUILD: 10586

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2015-11-22 04:24:24

BUILDDATESTAMP_STR: 151121-2308

BUILDLAB_STR: th2_release

BUILDOSVER_STR: 10.0.10586.17.amd64fre.th2_release.151121-2308

ANALYSIS_SESSION_ELAPSED_TIME: 199f

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x139_3_nt!kifastfaildispatch

FAILURE_ID_HASH: {36173680-6f08-995f-065a-3d368c996911}

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

---

If you have an Nvidia GPU and you're using the 361.43 driver from Nvidia, downgrade to an earlier driver, like 359.06, and the problem will go away. It's a problem that Windows 10 has with the GPU detection.

---

Yes, just had the same problem on my Windows 8.1 laptop after upgrading to the GeForce 361.43 driver. Downgraded to 359.06, and things work smoothly again.

---

Problem solved. Thank you!

---

Same here - running BOINC (7.6.22 x64) under Windows-10, but the video-card/process (those tasks assigned to GPU) keeps crashing and restarting (never had these issues under earlier versions of Windows). I've already suspended the GPU, but BOINC is still assigning tasks to the GPU (although they all end up in suspended mode). Is there a way to tell BOINC not to assign tasks -at all- to the GPU? The CPU assigned tasks all run fine!

---

Is there a way to tell BOINC not to assign tasks -at all- to the GPU?

Your Account->Seti project preferences->Edit preferences->Uncheck Use {flavor of GPU}->Use Update preferences button at the bottom of the page. The next time BOINC asks for work, it'll get those preferences and immediately stop asking for work for that GPU.

If you run other projects, you have to do this at those projects as well.

But the problem here isn't with BOINC or with Seti, but with the Windows supplied driver. What you need is the driver supplied by the GPU manufacturer, AMD/ATI, Intel or Nvidia. And then, as shown originally in this thread, not always the latest newest version, as older drivers can be more sturdy in this regard.

That you didn't have this problem with earlier versions of Windows is most probably because under those versions you decided which drivers the GPU should run with, whereas Windows 10 demands that it does all the driver updating -unless you turn that off for a handful of weeks. And so Windows 10 puts on unstable drivers, unstable for doing calculations. They may be stable for desktop work. Even WHQL tested drivers don't test whether they're stable doing CUDA or OpenCL calculations, only if they don't crash people's Windows desktops.

---

Ist das Problem gefixt mit dem aktuellsten Treiber 364.72?

Ist das Problem gefixt mit dem aktuellsten Treiber 364.72?

Soweit ich weiß , ist es nicht. Ich schlage vor, 355.82.

---

Zur Info: Ist gefixt! läuft problemlos...