Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\lwcomputing.com\Minidumps\analyzed\207.216.97.156-20110605220607-Mini060511-02.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv*F:\lwcomputing.com\Minidumps\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Unable to load image ntoskrnl.exe, Win32 error 0n2 Loading symbols for 804d7000 ntoskrnl.exe -> ntoskrnl.exe *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe ModLoad: 804d7000 806e5000 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: Sun Jun 5 21:42:04.687 2011 (UTC - 4:00) System Uptime: 0 days 0:03:57.798 Unable to load image ntoskrnl.exe, Win32 error 0n2 Loading symbols for 804d7000 ntoskrnl.exe -> ntoskrnl.exe *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe ModLoad: 804d7000 806e5000 ntoskrnl.exe Loading Kernel Symbols .ModLoad: 806e5000 80705d00 halmacpi.dll .ModLoad: ba5a8000 ba5a9b80 kdcom.dll .ModLoad: ba4b8000 ba4bb000 BOOTVID.dll .ModLoad: b9f79000 b9fa6d80 ACPI.sys .ModLoad: ba5aa000 ba5ab100 WMILIB.SYS .ModLoad: b9f68000 b9f78a80 pci.sys .ModLoad: ba0a8000 ba0b1180 isapnp.sys .ModLoad: ba5ac000 ba5ad580 intelide.sys .ModLoad: ba328000 ba32e180 PCIIDEX.SYS .ModLoad: ba0b8000 ba0c2580 MountMgr.sys .ModLoad: b9f49000 b9f67880 ftdisk.sys .ModLoad: ba5ae000 ba5af700 dmload.sys .ModLoad: b9f23000 b9f48700 dmio.sys .ModLoad: ba330000 ba334d00 PartMgr.sys .ModLoad: ba0c8000 ba0d4c80 VolSnap.sys .ModLoad: b9f0b000 b9f22900 atapi.sys .ModLoad: ba4bc000 ba4be280 viostor.sys .ModLoad: b9ef3000 b9f0a880 SCSIPORT.SYS .ModLoad: ba0d8000 ba0e0e00 disk.sys .ModLoad: ba0e8000 ba0f4180 CLASSPNP.SYS .ModLoad: b9ed3000 b9ef2b00 fltMgr.sys .ModLoad: b9ec1000 b9ed2f00 sr.sys .ModLoad: b9eaa000 b9ec0b00 KSecDD.sys .ModLoad: b9e1d000 b9ea9600 Ntfs.sys .ModLoad: b9df0000 b9e1c980 NDIS.sys .ModLoad: b9dd6000 b9defb80 Mup.sys .ModLoad: ba118000 ba124d00 i8042prt.sys .ModLoad: ba388000 ba38e000 kbdclass.sys .ModLoad: ba390000 ba395a00 mouclass.sys Image at ba398000 had size 0 .ModLoad: ba398000 ba399000 fdc.sys .ModLoad: ba3a0000 ba3a5080 usbuhci.sys .ModLoad: b9b00000 b9b23200 USBPORT.SYS .ModLoad: ba5d4000 ba5d5a00 qxl.sys .ModLoad: b9aec000 b9afff00 VIDEOPRT.SYS .ModLoad: ba128000 ba135e00 netkvm.sys .ModLoad: ba138000 ba141100 ES1370MP.sys .ModLoad: b9ac8000 b9aeba80 portcls.sys .ModLoad: ba148000 ba156b00 drmk.sys .ModLoad: b9aa5000 b9ac7700 ks.sys .ModLoad: ba158000 ba160980 vioser.sys .ModLoad: ba168000 ba176000 WDFLDR.SYS .ModLoad: b9a34000 b9aa5000 wdf01000.sys .ModLoad: ba178000 ba180c00 processr.sys .ModLoad: ba7d4000 ba7d4c00 audstub.sys .ModLoad: ba188000 ba194880 rasl2tp.sys .ModLoad: ba574000 ba576780 ndistapi.sys .ModLoad: b9a1d000 b9a33580 ndiswan.sys .ModLoad: ba198000 ba1a2200 raspppoe.sys .ModLoad: ba1a8000 ba1b3d00 raspptp.sys .ModLoad: ba3a8000 ba3aca80 TDI.SYS .ModLoad: b9a0c000 b9a1ce00 psched.sys .ModLoad: ba1b8000 ba1c0900 msgpc.sys .ModLoad: ba3b0000 ba3b4580 ptilink.sys .ModLoad: ba3c8000 ba3cc080 raspti.sys .ModLoad: b992e000 b995de80 rdpdr.sys .ModLoad: ba1d8000 ba1e1f00 termdd.sys .ModLoad: ba5de000 ba5df100 swenum.sys .ModLoad: b8fa0000 b8ffdf00 update.sys .ModLoad: b9d9e000 b9da1c80 mssmbios.sys .ModLoad: ba268000 ba277c00 serial.sys .ModLoad: b9d9a000 b9d9dd80 serenum.sys .ModLoad: b9656000 b9660000 NDProxy.SYS . ModLoad: b9646000 b9654880 usbhub.sys .ModLoad: ba640000 ba641280 USBD.SYS .ModLoad: b4521000 b4523980 gameenum.sys .ModLoad: ba5e6000 ba5e7f00 Fs_Rec.SYS .ModLoad: b3419000 b3419b80 Null.SYS .ModLoad: ba5e8000 ba5e9080 Beep.SYS .ModLoad: b3c3e000 b3c43200 vga.sys .ModLoad: ba5ea000 ba5eb080 mnmdd.SYS .ModLoad: ba5ec000 ba5ed080 RDPCDD.sys .ModLoad: b3c36000 b3c3aa80 Msfs.SYS .ModLoad: b3c2e000 b3c35880 Npfs.SYS .ModLoad: b4519000 b451b280 rasacd.sys .ModLoad: ae2f5000 ae307600 ipsec.sys .ModLoad: ae29c000 ae2f4480 tcpip.sys .ModLoad: ae274000 ae29bc00 netbt.sys .ModLoad: ae24e000 ae273500 ipnat.sys .ModLoad: ae22c000 ae24dd00 afd.sys .ModLoad: b3c82000 b3c8a780 netbios.sys .ModLoad: b3c72000 b3c7a700 wanarp.sys .ModLoad: ae201000 ae22be80 rdbss.sys .ModLoad: ae191000 ae200500 mrxsmb.sys .ModLoad: b33a0000 b33aae00 Fips.SYS .ModLoad: b32c8000 b32ca880 hidusb.sys .ModLoad: b3370000 b3379000 HIDCLASS.SYS .ModLoad: b3c26000 b3c2c180 HIDPARSE.SYS .ModLoad: b32c4000 b32c6f80 mouhid.sys .ModLoad: b32c0000 b32c3780 dump_scsiport.sys .ModLoad: b32bc000 b32be280 dump_viostor.sys .ModLoad: bf800000 bf9c5980 win32k.sys .ModLoad: b32a8000 b32aa900 Dxapi.sys .ModLoad: b3c1e000 b3c22500 watchdog.sys .ModLoad: bf000000 bf011600 dxg.sys .ModLoad: b24bb000 b24bbd00 dxgthk.sys .ModLoad: bf012000 bf02ba00 qxldd.dll .ModLoad: b96d2000 b96d5900 ndisuio.sys .ModLoad: aa104000 aa118480 wdmaud.sys .ModLoad: b7b59000 b7b67d80 sysaudio.sys .ModLoad: ba60e000 ba60f880 splitter.sys .ModLoad: aa0e1000 aa103d00 aec.sys .ModLoad: b738f000 b739cd00 swmidi.sys .ModLoad: b737f000 b738be80 DMusic.sys .ModLoad: aa0b6000 aa0e0180 kmixer.sys .ModLoad: ba73c000 ba73cb80 drmkaud.sys .ModLoad: a9f41000 a9f6d180 mrxdav.sys .ModLoad: a9ec1000 a9f18600 srv.sys .ModLoad: a9d40000 a9d80e00 HTTP.sys Loading User Symbols Loading unloaded module list ....... Loaded dbghelp extension DLL Loaded ext extension DLL Loaded exts extension DLL Loaded kext extension DLL Loaded kdexts extension DLL Loading symbols for 806e5000 halmacpi.dll -> halmacpi.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000000A, {13c, 2, 1, 806e7a16} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* Loading symbols for bf800000 win32k.sys -> win32k.sys *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Loading symbols for bf012000 qxldd.dll -> qxldd.dll *** WARNING: Unable to verify timestamp for qxldd.dll *** ERROR: Module load completed but symbols could not be loaded for qxldd.dll ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* Probably caused by : qxldd.dll ( qxldd+6ff7 ) Followup: MachineOwner --------- 1: kd> .symfix 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000013c, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 806e7a16, address which referenced memory Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: qxldd FAULTING_MODULE: 804d7000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4ca37851 WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd 0000013c CURRENT_IRQL: 2 FAULTING_IP: hal!KeAcquireInStackQueuedSpinLock+26 806e7a16 8711 xchg edx,dword ptr [ecx] CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xA LAST_CONTROL_TRANSFER: from 00000000 to 806e7a16 SYMBOL_ON_RAW_STACK: 1 STACK_ADDR_RAW_STACK_SYMBOL: ffffffffb7f48638 STACK_COMMAND: dds B7F48638-0x20 ; kb STACK_TEXT: b7f48618 b7f48630 b7f4861c bf801978 win32k+0x1978 b7f48620 00000108 b7f48624 00000001 b7f48628 e1538750 b7f4862c bf806216 win32k+0x6216 b7f48630 b7f48648 b7f48634 bf018ff7 qxldd+0x6ff7 b7f48638 00000108 b7f4863c e1538750 b7f48640 e153883b b7f48644 fdf70280 b7f48648 b7f48664 b7f4864c bf0190b7 qxldd+0x70b7 b7f48650 00000000 b7f48654 00000045 b7f48658 00000001 b7f4865c e1538750 b7f48660 e153883b b7f48664 b7f48684 b7f48668 bf0248d0 qxldd+0x128d0 b7f4866c e1538750 b7f48670 00000001 b7f48674 fdf70280 b7f48678 00000000 b7f4867c e12bd898 b7f48680 0000ffff b7f48684 b7f48698 b7f48688 bf013e0c qxldd+0x1e0c b7f4868c e1538750 b7f48690 fdf70280 b7f48694 00000002 FOLLOWUP_IP: qxldd+6ff7 bf018ff7 ?? ??? SYMBOL_NAME: qxldd+6ff7 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: qxldd.dll BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- 1: kd> q quit: Unloading exts extension DLL Unloading kext extension DLL Unloading kdexts extension DLL Unloading dbghelp extension DLL Unloading ext extension DLL