X64: IPv6 installed/removed, without reboot, then playing BF2 and voila crash.

Hello,

I added IPv6 protocol support to see it in action. Then I removed it again.
Then I kept on computing without a reboot.

Then I play Battlefield 2 and then when the map ended the system crashed:

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


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

Symbol search path is:
SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free
x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.070321-2337
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
Debug session time: Wed Feb 27 16:36:01.406 2008 (GMT+1)
System Uptime: 0 days 14:30:28.339
Loading Kernel Symbols
..............................................................................................................................................
Loading User Symbols
Loading unloaded module list
...................................................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa8004d58230, fffffa8004d58290, 6060403}

Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+45e )

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

1: 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: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8004d58230, The pool entry we were looking for within the page.
Arg3: fffffa8004d58290, The next pool entry.
Arg4: 0000000006060403, (reserved)

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


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: fffffa8004d58230

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800011ab36c to fffff8000102e890

STACK_TEXT:
fffffadf`c909bc28 fffff800`011ab36c : 00000000`00000019 00000000`00000020
fffffa80`04d58230 fffffa80`04d58290 : nt!KeBugCheckEx
fffffadf`c909bc30 fffff800`010e8b85 : fffffadf`fee16bb0 00000000`00000000
fffffadf`fee16bb0 00000000`00000000 : nt!ExFreePoolWithTag+0x45e
fffffadf`c909bcf0 fffff800`0124a972 : 00000000`00000000 fffffadf`cecc6570
00000000`00000080 fffffadf`cecc6570 : nt!MiDereferenceSegmentThread+0x259
fffffadf`c909bd70 fffff800`01020226 : fffffadf`c8c7b180 fffffadf`cecc6570
fffffadf`c8c83680 00000000`00000000 : nt!PspSystemThreadStartup+0x3e
fffffadf`c909bdd0 00000000`00000000 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExFreePoolWithTag+45e
fffff800`011ab36c cc int 3

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 460280f7

SYMBOL_NAME: nt!ExFreePoolWithTag+45e

FAILURE_BUCKET_ID: X64_0x19_20_nt!ExFreePoolWithTag+45e

BUCKET_ID: X64_0x19_20_nt!ExFreePoolWithTag+45e

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

 

This crash might have something to do with punkbuster.

I seemed as if I was playing on a punkbuster free server.

Apperently not.

Somehow when I rebooted punkbuster was secretly installed again and running.

Bye,
Skybuck.

 

Info about this executable:

https://www.microsoft.com.nsatc.net...maintain/featusability/termserv.mspx?mfr=true

(just click continue when it complains about certificates)

"
Microkernel

Notice in Figure 3.2 that many of the modular components of the Terminal
Server operating system are built around a Microkernel. The Microkernel is a
small and very efficient program that handles the core functions of the
operating system.
The Microkernel's primary job is managing the operating system's workload.
As a manager, the Microkernel takes the tasks assigned to it by the
applications and divides the work between the server's microprocessors. In a
multiprocessor system, the efficiency of the Microkernel is critical.
Without an efficient Microkernel, some processors become overburdened while
others remain idle.
The Microkernel actually resides in either ntoskrnl.exe or ntkrnlmp.exe in
the SYSTEM32 directory. The ntkrnlmp.exe file is the multiprocessing version
of ntoskrnl.exe. It is specially written to handle multiprocessor
synchronization.
"