Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Pobieranie\Mini021811-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.100216-1514
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Fri Feb 18 09:59:33.462 2011 (GMT+1)
System Uptime: 0 days 12:33:52.761
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {80000004, 806d8945, f62b0d80, 0}
Unable to load image igxpmp32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igxpmp32.sys
*** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys
Unable to load image igxpgd32.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igxpgd32.dll
*** ERROR: Module load completed but symbols could not be loaded for igxpgd32.dll
*** WARNING: Unable to verify timestamp for igxprd32.dll
*** ERROR: Module load completed but symbols could not be loaded for igxprd32.dll
Probably caused by : pci.sys ( pci!PciReadWriteConfigSpace+38 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* 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: 80000004, The exception code that was not handled
Arg2: 806d8945, The address that the exception occurred at
Arg3: f62b0d80, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - Taki interfejs nie jest obs ugiwany.
FAULTING_IP:
hal!WRITE_PORT_ULONG+9
806d8945 c20800 ret 8
TRAP_FRAME: f62b0d80 -- (.trap 0xfffffffff62b0d80)
ErrCode = 00000000
eax=80001090 ebx=00000090 ecx=00000090 edx=00000cf8 esi=806dd210 edi=f62b0e7c
eip=806d8945 esp=f62b0df4 ebp=f62b0e04 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
hal!WRITE_PORT_ULONG+0x9:
806d8945 c20800 ret 8
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: explorer.exe
LAST_CONTROL_TRANSFER: from 806d5e33 to 806d8945
STACK_TEXT:
f62b0df0 806d5e33 00000cf8 80001090 806dd210 hal!WRITE_PORT_ULONG+0x9
f62b0e04 806d5bef 806dd210 f62b0e24 f62b0f50 hal!HalpPCIWriteUlongType1+0x23
f62b0e38 806d6017 f62b0e00 00000002 f62b0f50 hal!HalpPCIConfig+0x4d
f62b0e58 806d6e17 f62b0e7c 00000002 f62b0f50 hal!HalpWritePCIConfig+0x2d
f62b0ee8 f733cae0 00000000 00000000 00000002 hal!HaliPciInterfaceWriteConfig+0x33
f62b0f0c f733cb74 86433be0 00000002 f62b0f50 pci!PciReadWriteConfigSpace+0x38
f62b0f2c f733cfcc 863fc978 f62b0f50 00000090 pci!PciWriteDeviceConfig+0x1e
f62b1054 f733fcbd 863fc978 f62b10dc 00000090 pci!PciExternalWriteDeviceConfig+0x1ac
f62b1078 f733c34d 863fc978 00000000 f62b10dc pci!PciWriteDeviceSpace+0x5d
f62b1098 ed6d5212 863fc978 00000000 f62b10dc pci!PciWriteAgpConfig+0x1d
f62b10b4 ed6f5891 85671358 00000004 00000000 VIDEOPRT!VideoPortSetBusData+0x3a
WARNING: Stack unwind information not available. Following frames may be wrong.
f62b10e8 ed706acd 85671358 000000ea 00000000 igxpmp32+0xd891
f62b1138 ed6d535b 85671358 000000ea 85961000 igxpmp32+0x1eacd
f62b115c ed6e2114 f62b11f4 00000000 856e8be0 VIDEOPRT!pVpGeneralBugcheckHandler+0x61
f62b121c 804ee129 8520d040 857513e8 00000000 VIDEOPRT!pVideoPortDispatch+0x4aa
f62b122c bf8c15e7 00000000 00000000 00000000 nt!IopfCallDriver+0x31
f62b125c bf93d854 8520d040 0023002c 00000000 win32k!GreDeviceIoControl+0x93
f62b1284 bf961b1e 00000000 00000000 f62b12d8 win32k!DrvPrepareForEARecovery+0x26
f62b12a4 bf8a60fc e1baecf0 00000000 e2475e90 win32k!HandleStuckThreadException+0x24
f62b12d8 bf8053e5 e2475e90 00000000 00000000 win32k!WatchdogDrvSynchronizeSurface+0x57
f62b12ec bf8388fc e2475e90 00000000 00000000 win32k!PDEVOBJ::vSync+0x36
f62b1508 bf02af67 e2475e90 e160b008 00000000 win32k!EngCopyBits+0x12a
f62b152c bf02ad1b e2475e90 e1087e90 00000000 igxpgd32+0x6f67
f62b1554 bf02a973 e2475e90 e1087e90 00000000 igxpgd32+0x6d1b
f62b173c bf03f4fd e2475e90 e1087e90 00000000 igxpgd32+0x6973
f62b1764 bf01946f e2475e90 e1087e90 00000000 igxpgd32+0x1b4fd
f62b1820 bf805a38 e2475e90 e1087e90 00000000 igxprd32+0x746f
f62b186c bf809cd0 e2475e90 e1087e90 00000000 win32k!WatchdogDrvCopyBits+0x53
f62b1900 8053d658 e2475e80 e3c72a70 e108bae0 win32k!NtGdiBitBlt+0x51c
f62b1900 7c90e514 e2475e80 e3c72a70 e108bae0 nt!KiFastCallEntry+0xf8
0007f3f8 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
pci!PciReadWriteConfigSpace+38
f733cae0 3b4518 cmp eax,dword ptr [ebp+18h]
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: pci!PciReadWriteConfigSpace+38
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: pci
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 480252bb
FAILURE_BUCKET_ID: 0x8E_pci!PciReadWriteConfigSpace+38
BUCKET_ID: 0x8E_pci!PciReadWriteConfigSpace+38
Followup: MachineOwner
---------Proszę o pomoc w znalezieniu źródła problemu
i jeśli można podać przykład jego rozwiązania Podam jeszcze na jakiej to "maszynie"
Laptop HP 550
Windows XP Professional SP3
Intel Celeron M CPU 530 @ 1.73GHz
1,73GHz, 0,99 GB RAM
Karty graficzne: Mobile Intel 965 Express Chipset Family - (pokazuje mi 2 razy to samo)
