Click here for important information about Computing.net.
When i play battlefield 2 it crashes after a few
minutes of play, black screen and reboot. The
systemdump says "pnkbstrk.sys" is the
badguy. Anyone got any idea what to do.
Punkbuster is a requirement if you want to
play on most of the servers.Minidump as follows!
Microsoft (R) Windows Debugger Version
6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights
reserved.
Loading Dump File
[C:\WINDOWS\Minidump\Mini030810-01.dmp]
Mini Kernel Dump File: Only registers and
stack trace are availableSymbol 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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer
SingleUserTS
Machine Name:
Kernel base = 0x804d7000
PsLoadedModuleList = 0x8055d720
Debug session time: Mon Mar 8 12:19:38.498
2010 (UTC + 1:00)
System Uptime: 0 days 0:22:37.208
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
...............
ERROR: FindPlugIns 80070015
******************************************************
*************************
*
*
* Bugcheck Analysis
*
*
*
******************************************************
*************************Use !analyze -v to get detailed debugging
information.BugCheck 1000008E, {c0000005, 804f4d12,
97a3aa4a, 0}*** WARNING: Unable to verify timestamp for
hal.dll
Unable to load image PnkBstrK.sys, Win32
error 0n2
*** WARNING: Unable to verify timestamp for
PnkBstrK.sys
*** ERROR: Module load completed but
symbols could not be loaded for PnkBstrK.sys
Probably caused by : PnkBstrK.sys (
PnkBstrK+df5f )Followup: MachineOwner
---------
The rest of the minidump... ERROR: FindPlugIns 80070015
*******************************************************************************
* *
* Bugcheck Analysis
*
* *
***********************************************************************
********KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
(1000008e)
This is a very common bugcheck. Usually the exception
address pinpoints
the driver/function that caused the problem. Always note this
address
as well as the link date of the driver/image that contains this
address.
Some common problems are exception code 0x80000003.
This means a hard
coded breakpoint or assertion was hit, but this system was
booted
/NODEBUG. This is not supposed to happen as developers
should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and
the
system is booted /DEBUG. This will let us see why this
breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804f4d12, The address that the exception occurred at
Arg3: 97a3aa4a, Trap Frame
Arg4: 00000000Debugging 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:
nt!CcSetValidData+1e
804f4d12 894804 mov dword ptr [eax+4],ecxTRAP_FRAME: 97a3aa4a -- (.trap 0xffffffff97a3aa4a)
ErrCode = 00000002
eax=00000000 ebx=86f72728 ecx=00000281 edx=00000000
esi=00000000 edi=00000000
eip=804f4d12 esp=97a3aabe ebp=97a3ab06 iopl=0 nv
up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010246
nt!CcSetValidData+0x1e:
804f4d12 894804 mov dword ptr [eax+4],ecx
ds:0023:00000004=????????
Resetting default scopeCUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: PnkBstrB.exe
UNALIGNED_STACK_POINTER: 97a3aabe
LAST_CONTROL_TRANSFER: from 804ff853 to 804f4d12
STACK_TEXT:
97a3ab06 804ff853 86f72768 97a3ab52 97a3ab46
nt!CcSetValidData+0x1e
97a3ab56 806e6ef2 00000000 00000000 97a3ab6e
nt!CcPerformReadAhead+0x16d
97a3ab6e 978b5f5f badb0d00 978b380c 0d00978b
hal!HalBuildMdlFromScatterGatherList+0xde
WARNING: Stack unwind information not available. Following
frames may be wrong.
97a3ac18 978ab051 8714b6d8 86772000 97a3ac3c
PnkBstrK+0xdf5f
97a3ac40 804ef19f 8714b6d8 877900e0 806e6410
PnkBstrK+0x3051
97a3ac64 805807f7 8714b6d8 877900e0 8706a1a0
nt!MiFlushSectionInternal+0x256
97a3ad00 80579274 0000026c 00000000 00000000
nt!NtSetInformationThread+0x125
97a3ad34 8054163c 0000026c 00000000 00000000
nt!SepOpenTokenOfThread+0x87
97a3ad64 7c90e514 badb0d00 008efe3c 99448d98
nt!RtlIpv4StringToAddressExW+0xbd
97a3ad78 00000000 00000000 00000000 00000000
0x7c90e514
STACK_COMMAND: kbFOLLOWUP_IP:
PnkBstrK+df5f
978b5f5f ?? ???SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: PnkBstrK+df5f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: PnkBstrK
IMAGE_NAME: PnkBstrK.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b1d7a06
FAILURE_BUCKET_ID: 0x8E_PnkBstrK+df5f
BUCKET_ID: 0x8E_PnkBstrK+df5f
Followup: MachineOwner
---------0: kd> lmvm PnkBstrK
start end module name
978a8000 978cc000 PnkBstrK T (no symbols)
Loaded symbol image file: PnkBstrK.sys
Image path: PnkBstrK.sys
Image name: PnkBstrK.sys
Timestamp: Mon Dec 07 22:56:22 2009 (4B1D7A06)
CheckSum: 00025505
ImageSize: 00024000
Translations: 0000.04b0 0000.04e4 0409.04b0
0409.04e4
Ad Choices