Microsoft (R) Windows Debugger Version 6.10.0003.233 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [G:\AV nowe\Dumpy\Mini091510-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\symbole*http://msdl.microsoft.com/download/symbols Executable search path is: Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt Built by: 2600.xpsp_sp2_gdr.100216-1441 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a6a0 Debug session time: Wed Sep 15 18:48:51.546 2010 (GMT+2) System Uptime: 0 days 0:06:24.140 Loading Kernel Symbols ............................................................... ........................................................... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {84a1b83f, 0, 8057c50c, 0} Could not read faulting driver name Probably caused by : hardware ( NDIS!ndisWorkerThread+4b ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: 84a1b83f, memory referenced. Arg2: 00000000, value 0 = read operation, 1 = write operation. Arg3: 8057c50c, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: 84a1b83f FAULTING_IP: nt!PspCreateThread+69d 8057c50c 8574d307 test dword ptr [ebx+edx*8+7],esi MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x50 TRAP_FRAME: f79c2b9c -- (.trap 0xfffffffff79c2b9c) ErrCode = 00000000 eax=01a66e70 ebx=82fb49c8 ecx=0e5aa7af edx=e034cdce esi=82c85bd0 edi=82c85e18 eip=8057c50c esp=f79c2c10 ebp=f79c2d4c 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!PspCreateThread+0x69d: 8057c50c 8574d307 test dword ptr [ebx+edx*8+7],esi ds:0023:84a1b83f=???????? Resetting default scope MISALIGNED_IP: nt!PspCreateThread+69d 8057c50c 8574d307 test dword ptr [ebx+edx*8+7],esi LAST_CONTROL_TRANSFER: from 80523fb8 to 8053358e STACK_TEXT: f79c2b38 80523fb8 00000050 84a1b83f 00000000 nt!KeBugCheckEx+0x1b f79c2b84 804e172b 00000000 84a1b83f 00000000 nt!MmAccessFault+0x6f5 f79c2b84 8057c50c 00000000 84a1b83f 00000000 nt!KiTrap0E+0xcc f79c2d4c 8057d326 f79c2db4 001f03ff 00000000 nt!PspCreateThread+0x69d f79c2d80 f735abd8 f79c2db4 001f03ff 00000000 nt!PsCreateSystemThread+0x33 f79c2dac 8057d363 00000604 00000000 00000000 NDIS!ndisWorkerThread+0x4b f79c2ddc 804f828a f735ab85 00000000 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: NDIS!ndisWorkerThread+4b f735abd8 85c0 test eax,eax SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: NDIS!ndisWorkerThread+4b FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: IP_MISALIGNED BUCKET_ID: IP_MISALIGNED Followup: MachineOwner ---------