Caged Anger
09-03-2007, 08:47 PM
its the debugging tools output for the minidump i got the last time UT2004 crashed.
I just reformatted my whole system, so I'm rather irked that a fresh, un-messed-around with install of the game hasn't resolved the issue.
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini090307-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Mon Sep 3 16:09:59.609 2007 (GMT-4)
System Uptime: 0 days 0:05:19.172
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.................................................. .................................................. ............................
Loading User Symbols
Loading unloaded module list
............
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 44, {88376348, d63, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for ks.sys
*** ERROR: Module load completed but symbols could not be loaded for ks.sys
*** WARNING: Unable to verify timestamp for portcls.sys
*** ERROR: Module load completed but symbols could not be loaded for portcls.sys
************************************************** ***********************
*** ***
*** ***
*** 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!_IRP ***
*** ***
************************************************** ***********************
Probably caused by : ks.sys ( ks+4d9d )
Followup: MachineOwner
---------
kd> .symfix
No downstream store given, using C:\Program Files\Debugging Tools for Windows\sym
kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: 88376348, Address of the IRP
Arg2: 00000d63
Arg3: 00000000
Arg4: 00000000
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!_IRP ***
*** ***
************************************************** ***********************
MODULE_NAME: ks
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 41107ef8
IRP_ADDRESS: 88376348
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x44
LAST_CONTROL_TRANSFER: from 804f076f to 804f8aef
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bacc7d38 804f076f 00000044 88376348 00000d63 nt+0x21aef
bacc7d70 b92bed9d 88597ce8 88376494 bacc7d98 nt+0x1976f
bacc7d80 b92be2ef 8835db38 88376348 bacc7da0 ks+0x4d9d
bacc7d98 b92c075c 8835db38 88376348 88375290 ks+0x42ef
bacc7dbc b92c0791 88376348 88376494 00000000 ks+0x675c
bacc7df4 b92bde13 88375290 02c8df98 00000001 ks+0x6791
bacc7e20 b92be188 015befc4 bacc7e00 00000000 ks+0x3e13
bacc7e50 b92bd0ec 0038e764 8835d950 bacc7e88 ks+0x4188
bacc7e60 b92bfc10 8838e764 00000000 8846e008 ks+0x30ec
bacc7e88 b92c1310 01398fb0 88375478 8837563c ks+0x5c10
bacc7eb4 b92be2ef 8835d950 00000103 bacc7ed4 ks+0x7310
bacc7ecc b92be76b 8835d950 8846e008 00000000 ks+0x42ef
bacc7ee8 804f054c 00000000 8846e008 02375478 ks+0x476b
bacc7f18 ae6e6bf2 883958c0 8846e008 00000000 nt+0x1954c
bacc7f2c ae6e068d 88361cac 8846e008 bacc7f48 portcls+0x7bf2
bacc7f40 ae6e01ef 88361cac 8846e008 883958c0 portcls+0x168d
bacc7f5c ae6e2a9f 8846e008 8835aec8 00004000 portcls+0x11ef
bacc7f7c ae6e6a24 883958c0 00000100 bacc7fa8 portcls+0x3a9f
bacc7fb8 ae6e0497 00000c80 89a43978 ffdff000 portcls+0x7a24
bacc7fd0 80540f7d 89a923e8 89a923d8 00000000 portcls+0x1497
bacc7fd4 89a923e8 89a923d8 00000000 00000000 nt+0x69f7d
bacc7fd8 89a923d8 00000000 00000000 00000000 0x89a923e8
bacc7fdc 00000000 00000000 00000000 00000000 0x89a923d8
STACK_COMMAND: kb
FOLLOWUP_IP:
ks+4d9d
b92bed9d ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: ks+4d9d
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ks.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
kd> lmvm ks
start end module name
b92ba000 b92dc680 ks T (no symbols)
Loaded symbol image file: ks.sys
Image path: ks.sys
Image name: ks.sys
Timestamp: Wed Aug 04 02:15:20 2004 (41107EF8)
CheckSum: 0002E05C
ImageSize: 00022680
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
I just reformatted my whole system, so I'm rather irked that a fresh, un-messed-around with install of the game hasn't resolved the issue.
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini090307-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Mon Sep 3 16:09:59.609 2007 (GMT-4)
System Uptime: 0 days 0:05:19.172
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.................................................. .................................................. ............................
Loading User Symbols
Loading unloaded module list
............
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 44, {88376348, d63, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for ks.sys
*** ERROR: Module load completed but symbols could not be loaded for ks.sys
*** WARNING: Unable to verify timestamp for portcls.sys
*** ERROR: Module load completed but symbols could not be loaded for portcls.sys
************************************************** ***********************
*** ***
*** ***
*** 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!_IRP ***
*** ***
************************************************** ***********************
Probably caused by : ks.sys ( ks+4d9d )
Followup: MachineOwner
---------
kd> .symfix
No downstream store given, using C:\Program Files\Debugging Tools for Windows\sym
kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: 88376348, Address of the IRP
Arg2: 00000d63
Arg3: 00000000
Arg4: 00000000
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!_IRP ***
*** ***
************************************************** ***********************
MODULE_NAME: ks
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 41107ef8
IRP_ADDRESS: 88376348
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x44
LAST_CONTROL_TRANSFER: from 804f076f to 804f8aef
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bacc7d38 804f076f 00000044 88376348 00000d63 nt+0x21aef
bacc7d70 b92bed9d 88597ce8 88376494 bacc7d98 nt+0x1976f
bacc7d80 b92be2ef 8835db38 88376348 bacc7da0 ks+0x4d9d
bacc7d98 b92c075c 8835db38 88376348 88375290 ks+0x42ef
bacc7dbc b92c0791 88376348 88376494 00000000 ks+0x675c
bacc7df4 b92bde13 88375290 02c8df98 00000001 ks+0x6791
bacc7e20 b92be188 015befc4 bacc7e00 00000000 ks+0x3e13
bacc7e50 b92bd0ec 0038e764 8835d950 bacc7e88 ks+0x4188
bacc7e60 b92bfc10 8838e764 00000000 8846e008 ks+0x30ec
bacc7e88 b92c1310 01398fb0 88375478 8837563c ks+0x5c10
bacc7eb4 b92be2ef 8835d950 00000103 bacc7ed4 ks+0x7310
bacc7ecc b92be76b 8835d950 8846e008 00000000 ks+0x42ef
bacc7ee8 804f054c 00000000 8846e008 02375478 ks+0x476b
bacc7f18 ae6e6bf2 883958c0 8846e008 00000000 nt+0x1954c
bacc7f2c ae6e068d 88361cac 8846e008 bacc7f48 portcls+0x7bf2
bacc7f40 ae6e01ef 88361cac 8846e008 883958c0 portcls+0x168d
bacc7f5c ae6e2a9f 8846e008 8835aec8 00004000 portcls+0x11ef
bacc7f7c ae6e6a24 883958c0 00000100 bacc7fa8 portcls+0x3a9f
bacc7fb8 ae6e0497 00000c80 89a43978 ffdff000 portcls+0x7a24
bacc7fd0 80540f7d 89a923e8 89a923d8 00000000 portcls+0x1497
bacc7fd4 89a923e8 89a923d8 00000000 00000000 nt+0x69f7d
bacc7fd8 89a923d8 00000000 00000000 00000000 0x89a923e8
bacc7fdc 00000000 00000000 00000000 00000000 0x89a923d8
STACK_COMMAND: kb
FOLLOWUP_IP:
ks+4d9d
b92bed9d ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: ks+4d9d
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ks.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
kd> lmvm ks
start end module name
b92ba000 b92dc680 ks T (no symbols)
Loaded symbol image file: ks.sys
Image path: ks.sys
Image name: ks.sys
Timestamp: Wed Aug 04 02:15:20 2004 (41107EF8)
CheckSum: 0002E05C
ImageSize: 00022680
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0