I have installed BOINC on windows XP, with admin rights and when it starts I get a BSOD. Below is the Core Dump debug info from the BSOD.

I was just wondering if anyone has any ideas on this issue.

Loading Dump File [C:\WINDOWS\Minidump\Mini021512-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is: 
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Feb 15 13:29:59.454 2012 (UTC - 6:00)
System Uptime: 0 days 0:13:54.636
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, e4a31ac0, e4a31ba0, c1c0241}

Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
Probably caused by : win32k.sys ( win32k!HeavyFreePool+b2 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: e4a31ac0, The pool entry we were looking for within the page.
Arg3: e4a31ba0, The next pool entry.
Arg4: 0c1c0241, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  e4a31ac0 

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  boinc.exe

LAST_CONTROL_TRANSFER:  from 8054b583 to 804f9f43

STACK_TEXT:  
9403cbf8 8054b583 00000019 00000020 e4a31ac0 nt!_woutput+0x414
9403cc48 bf802a50 e4a31ac8 00000000 9403cd3c nt!ExFreePoolWithTag+0x4bd
9403cc58 bf8b617a e4a31ac8 9403cd64 0012bcc4 win32k!HeavyFreePool+0xb2
9403cd3c 8054167c 1401039c 00000000 00000000 win32k!IFIOBJR::IFIOBJR+0x82
9403cd64 7c90e514 badb0d00 0012bca4 00000000 nt!RtlIpv4StringToAddressExW+0xfd
WARNING: Frame IP not in any known module. Following frames may be wrong.
9403cd78 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!HeavyFreePool+b2
bf802a50 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  win32k!HeavyFreePool+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4eccf442

FAILURE_BUCKET_ID:  0x19_20_win32k!HeavyFreePool+b2

BUCKET_ID:  0x19_20_win32k!HeavyFreePool+b2

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

0: kd> lmvm win32k
start    end        module name
bf800000 bf9c6000   win32k   M (pdb symbols)          c:\windows\symbols\sys\win32k.pdb
    Loaded symbol image file: win32k.sys
    Image path: win32k.sys
    Image name: win32k.sys
    Timestamp:        Wed Nov 23 07:25:22 2011 (4ECCF442)
    CheckSum:         001D1AC0
    ImageSize:        001C6000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Which version of BOINC? Check that in Advanced view->Help->About BOINC Manager.
What if you tell BOINC not to start up when Windows starts up? (Assuming 6.12.x) Advanced view->Tools->Options->Uncheck "Run Manager at login?".
What kind of computer is it? CPU, RAM, videocard(s), etc.

Since "BAD_POOL_HEADER" problems are normally related to bad drivers, what driver did you update last prior to installing BOINC? Or have you (n)ever updated drivers?

---

It is a work computer. I had them install the latest BOINC install package from the website. The problem also occurs if I have it not start automaticaly and then manually start it.
I know that they have recencly updated my ATI video drivers, however, I am not aware of any other drivers that they have updated.
I am hoping that they will install BOINC on a same model workstation that I use, however, with the company using CORE loads I'm not sure if the problem will be reproducible or not on other computer workstations with the same model as mine.

I have an HP EliteBook 8740w, however the company I work for has removed Windows 7 and put Windows XP on it using a standard core load image. So who knows what is actually causing the issue. I have the feeling this workstation was tweaked from the manufacturer to run with windows 7.


I"m no tech guru, but from part of the dump I'm thinking it may actually be a haredware issue or a some low level driver issue since it mentions RtlIpv4StringToAddressExW+0xfd

9403cbf8 8054b583 00000019 00000020 e4a31ac0 nt!_woutput+0x414
9403cc48 bf802a50 e4a31ac8 00000000 9403cd3c nt!ExFreePoolWithTag+0x4bd
9403cc58 bf8b617a e4a31ac8 9403cd64 0012bcc4 win32k!HeavyFreePool+0xb2
9403cd3c 8054167c 1401039c 00000000 00000000 win32k!IFIOBJR::IFIOBJR+0x82
9403cd64 7c90e514 badb0d00 0012bca4 00000000 nt!RtlIpv4StringToAddressExW+0xfd
WARNING: Frame IP not in any known module. Following frames may be wrong.

RtlIpv4StringToAddressExW+0xfd

That's a network card issue. Realtek IPV4.
Ask your tech support if they updated the network card drivers, or additionally the motherboard chipset drivers.

---

Thank you for your input. I'll forward this on to the tech support team.

Tech support updated all of the drivers and cleaned up my pc.

What finally did the trick was to completely disable Video Acceleration on my display properties. I use dual monitors so I had to do it on both screens. Even though the drivers are all up to date.