The fun thing is, I can't open the memory dump file with my 64bit Windows debugger program. I need to load the 32bit Windows debugger program. This tells me one thing immediately, before anything else, and that's that whatever caused it happens in 32bit memory.

Since all parts of BOINC are 64bit, it won't run in 32bit memory. So your problem is not with BOINC. As I already explained earlier, BOINC Manager was just the process loaded into memory when something else decided to crash. That something else is explained in the crash dump:

before the analyze command, just as we've loaded the dump file into the debugger, we'll see a lot of information already:

Loading Dump File [P:\Mump\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
Machine Name:
Kernel base = 0xfffff803`8f01a000 PsLoadedModuleList = 0xfffff803`8f2e6b00
Debug session time: Fri May 10 01:06:07.786 2013 (UTC + 2:00)
System Uptime: 1 days 7:26:01.357
Loading Kernel Symbols
...............................................................
.............................................................Page 11d1e7 not present in the dump file. Type ".hh dbgerr004" for details
...
.........................Page 1da2a9 not present in the dump file. Type ".hh dbgerr004" for details
..
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd7018).  Type ".hh dbgerr001" for details
Loading unloaded module list
........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41792, fffff683fcf828b0, 800000000000, 0}

Page 4043d0 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+371c3 )

System Uptime: 1 days 7:26:01.357 is interesting as it shows it's not a driver problem, since drivers normally crash upon Windows start-up, not after running for more than a day.

The other line of interest is Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+371c3 ), as it shows the module in which the crash happened: Your Windows Kernel crashed. ntkrnlmp means as much as NT Kernel Multi-Processor.
If you don't see any driver stopped responding errors, anything now crashing is normally hardware related, CPU, motherboard, memory related or Power Supply.

I'd start with checking:
- Memory: Rigorous checks, not just one or two runs with memtest86+, but at least a 24 hour continuous run-through. Remember that the crash happened after 31 hours!
- Power Supply: Are all cables connected correctly? No breaks or bends? No weird smells from connectors or PSU itself? No bulging capacitors in the PSU? Is the PSU powerful enough?
- CPU: Dust Check! Thermal compound applied correctly? Are all fans spinning? What kind of temperatures do we reach?
- Motherboard: Check for cracks, breaks, bends, a screw tightened without an insulator between it and the motherboard, bulging capacitors, dust, weird smells, fluids.

Apropos, I managed to 7zip-compress the dump file to 154MB. Don't be afraid to use compression on files before uploading them. :)

I never said that the use of the 32bit or 64bit Windows debugger was related to the crashes. Only said that the actual memory.dmp file is 32bit and cannot be opened by 64bit Windbg, it would throw an error alike Could not match file signature, invalid file format. Could not open dump file, Win32 error 0n87. The parameter is incorrect."
I solved that by installing 32bit Windbg from the Windows 8 SDK. Now both Windbg versions open the file.


As your log showed, system uptime was 31 hours and 26 minutes before the BSOD happened. If you still have it, you can check from the other memory dump of the earlier BSOD how long your system was up then.


Not too sure. I just ran [url]http://www.extreme.outervision.com/PSUEngine[/url] with the most basic of setup options, and already come out on 440W. That's with really basic fans (2x 80mm), 1 HDD, 1 DVD, not adding in any cooling for the CPU/GPU. Perhaps you'd like to add in what is actually in your system and do a new calculation.


Driver crashes can be checked in Windows Event Viewer.
Most all other crashes as well.

Do know that BOINC Manager is nothing more than a graphical user interface that allows you to easily control the underlying client (BOINC). Neither BOINC nor BOINC Manager do anything strenuous on your system, BOINC is a management program, allowing you to easily help out projects with whatever science applications they want to add to your system. Can there be crashes in BOINC Manager? Sure, but then the module name is BOINC Manager, not the process name. Chasing after the process name is a wild goose chase, it's not the culprit.

But you don't have to believe me. There's this easy-to-use resource out there, that I also used when writing my earlier answers to you. It's called a search engine. Just use any of your favorite search engines and fill in "memory management (1a)" (without quotes). Then check out a lot of the information bubbling up.

Hello Daniel Andersson @ amdforum.se,
I expect you are right. We were really hoping that BOINC 7.0.64/65 were reasonably bulletproof, but you seem to have found a weakness.

sigh . .
Lawrence

I experienced another crash/BSOD last night:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880061260b5, Address of the instruction which caused the bugcheck
Arg3: fffff8800bf2efd0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

Page 404879 not present in the dump file. Type ".hh dbgerr004" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruktionen p 0x%08lx refererade till minnet p 0x%08lx. Det gick inte att utf ra en minnes tg rd. F ljande fel returnerades: The memory could not be %s.

FAULTING_IP:
atikmpag+480b5
fffff880`061260b5 488b9190000000 mov rdx,qword ptr [rcx+90h]

CONTEXT: fffff8800bf2efd0 -- (.cxr 0xfffff8800bf2efd0)
rax=fffff8a0166676d0 rbx=00000001000003c0 rcx=00000000003c0000
rdx=0000000000000030 rsi=fffffa8010620010 rdi=fffffa800e30e100
rip=fffff880061260b5 rsp=fffff8800bf2f9d0 rbp=fffff8800bf2f9d0
r8=000000000221c035 r9=00000000003c0000 r10=0000000000000801
r11=fffff8800bf30380 r12=00000000c0005f00 r13=fffff8a017a3b300
r14=fffffa800e30e180 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
atikmpag+0x480b5:
fffff880`061260b5 488b9190000000 mov rdx,qword ptr [rcx+90h] ds:002b:00000000`003c0090=????????????????
Resetting default scope

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8800611e7de to fffff880061260b5

STACK_TEXT:
fffff880`0bf2f9d0 fffff880`0611e7de : 00000000`00000000 fffff880`0bf2fa00 fffffa80`10620010 fffff880`0bf30460 : atikmpag+0x480b5
fffff880`0bf2f9e0 fffff880`062fa0ab : fffffa80`0e30e180 fffffa80`0e30e180 00000000`0000001c 00000001`00000005 : atikmpag+0x407de
fffff880`0bf2fa10 fffff880`06312d10 : fffff880`0bf2fa80 fffff880`0630945a 00000000`00000000 fffff880`0bf2fa80 : atikmdag+0x9e0ab
fffff880`0bf2fa50 fffff880`0630bbab : 00000000`00000000 fffff880`062fa0b3 fffffa80`0cc25048 fffffa80`0e2e4900 : atikmdag+0xb6d10
fffff880`0bf2fa80 fffff880`06311cb5 : fffffa80`10620010 fffff880`0bf2fc00 00000000`00000001 00000000`00025bce : atikmdag+0xafbab
fffff880`0bf2fad0 fffff880`060ea6ab : fffffa80`0e30e1a0 fffff880`00000000 fffff8a0`00000000 00000000`00001ff0 : atikmdag+0xb5cb5
fffff880`0bf2fb90 fffff880`0589e24d : fffffa80`0e2e4900 fffff880`0bf30170 fffff880`0bf30400 fffff8a0`17ad7d00 : atikmpag+0xc6ab
fffff880`0bf2fe70 fffff880`058dd419 : fffff880`0bf30170 fffff880`0bf30731 fffff8a0`17a3b330 fffff880`0bf306e0 : dxgkrnl!ADAPTER_RENDER::DdiOpenAllocation+0x7d
fffff880`0bf2fec0 fffff880`058dc761 : fffff8a0`00125000 fffff880`0bf306e0 fffff880`0bf30420 fffff8a0`17ad7d00 : dxgkrnl!DXGDEVICE::OpenAllocations+0x259
fffff880`0bf2ff80 fffff880`058b4690 : 00000000`00000799 fffff880`0bf30731 00000000`00000000 00000000`00000701 : dxgkrnl!DXGDEVICE::CreateAllocation+0xdb1
fffff880`0bf30650 fffff880`058b3f1b : fffff8a0`00000238 fffff8a0`020556a0 fffff8a0`178116c0 00000000`00000000 : dxgkrnl!DXGDEVICE::OpenResource<_D3DKMT_OPENRESOURCEFROMNTHANDLE>+0x330
fffff880`0bf30770 fffff880`058b3b67 : fffffa80`12e0d080 00000000`00000301 fffff8a0`00000001 fffff8a0`17811600 : dxgkrnl!OpenResourceFromGlobalHandleOrNtObject<_D3DKMT_OPENRESOURCEFROMNTHANDLE>+0x36b
fffff880`0bf30950 fffff802`4dcd4453 : 0000004c`cf63de90 00000000`00000020 0000004c`cf63e2f0 00000000`00000001 : dxgkrnl!DxgkOpenResourceFromNtHandle+0x193
fffff880`0bf30a80 000007fd`c624233a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000004c`cf63de38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fd`c624233a


FOLLOWUP_IP:
atikmpag+480b5
fffff880`061260b5 488b9190000000 mov rdx,qword ptr [rcx+90h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmpag+480b5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5154e9d9

STACK_COMMAND: .cxr 0xfffff8800bf2efd0 ; kb

FAILURE_BUCKET_ID: 0x3B_atikmpag+480b5

BUCKET_ID: 0x3B_atikmpag+480b5

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

7: kd> lmvm atikmpag
start end module name
fffff880`060de000 fffff880`06172000 atikmpag (no symbols)
Loaded symbol image file: atikmpag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
Image name: atikmpag.sys
Timestamp: Fri Mar 29 02:09:45 2013 (5154E9D9)
CheckSum: 00091A60
ImageSize: 00094000
File version: 8.14.1.6304
Product version: 8.14.1.6304
File flags: 8 (Mask 3F) Private
File OS: 40004 NT Win32
File type: 3.4 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Advanced Micro Devices, Inc.
ProductName: AMD driver
InternalName: atikmpag.sys
OriginalFilename: atikmpag.sys
ProductVersion: 8.14.01.6304
FileVersion: 8.14.01.6304
FileDescription: AMD multi-vendor Miniport Driver
LegalCopyright: Copyright (C) 2007 Advanced Micro Devices, Inc.


Download link to MEMORY.DMP is here: http://tbf.me/a/BZqjDv

Timestamp: Fri Mar 29 02:09:45 2013 (5154E9D9)

??????