Actually, I have 2 32-bit Windows XP machines connected with a serial cable.
Windbg is attached and running so that I can analyze the bug check right
away. Here's the output from boot time to bug check time:
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
DBGHELP: Symbol Search Path:
\\tsclient\n\packetsphere\c5\driver\c5bus\objfre_wxp_x86\i386;SRV*\\bed-d-edjo\Symbols*http://msdl.microsoft.com/download/symbols;\\bed-d-edjo\perforce\ejoo_dev_interface\packetsphere\c5\driver\c5bus\objchk_wxp_x86\i386
Symbol search path is:
\\tsclient\n\packetsphere\c5\driver\c5bus\objfre_wxp_x86\i386;SRV*\\bed-d-edjo\Symbols*http://msdl.microsoft.com/download/symbols;\\bed-d-edjo\perforce\ejoo_dev_interface\packetsphere\c5\driver\c5bus\objchk_wxp_x86\i386
Executable search path is:
\\tsclient\h\packetsphere\c5\driver\c5bus\objchk_wxp_x86\i386
DBGHELP: SharedUserData - virtual symbol module
DBGHELP:
\\tsclient\n\packetsphere\c5\driver\c5bus\objfre_wxp_x86\i386\ntkrpamp.pdb -
file not found
DBGHELP:
\\tsclient\n\packetsphere\c5\driver\c5bus\objfre_wxp_x86\i386\symbols\exe\ntkrpamp.pdb - file not found
DBGHELP:
\\tsclient\n\packetsphere\c5\driver\c5bus\objfre_wxp_x86\i386\exe\ntkrpamp.pdb - file not found
SYMSRV:
\\bed-d-edjo\Symbols\ntkrpamp.pdb\430480FAAC4F4A45980B99443EDC145E1\ntkrpamp.pdb not found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.pdb/430480FAAC4F4A45980B99443EDC145E1/ntkrpamp.pdb not found
DBGHELP:
\\bed-d-edjo\perforce\ejoo_dev_interface\packetsphere\c5\driver\c5bus\objchk_wxp_x86\i386\ntkrpamp.pdb - file not found
DBGHELP:
\\bed-d-edjo\perforce\ejoo_dev_interface\packetsphere\c5\driver\c5bus\objchk_wxp_x86\i386\symbols\exe\ntkrpamp.pdb - file not found
DBGHELP:
\\bed-d-edjo\perforce\ejoo_dev_interface\packetsphere\c5\driver\c5bus\objchk_wxp_x86\i386\exe\ntkrpamp.pdb - file not found
DBGHELP: ntkrpamp.pdb - file not found
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntkrpamp.exe -
DBGHELP: nt - export symbols
Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
System Uptime: not available
DBGHELP: Symbol Search Path:
\\tsclient\n\packetsphere\c5\driver\c5bus\objfre_wxp_x86\i386;SRV*\\bed-d-edjo\symbols*http://msdl.microsoft.com/download/symbols
KD: Accessing
'\\tsclient\n\packetsphere\c5\driver\c5bus\objfre_wxp_x86\i386\C5eBus.sys'
(\SystemRoot\system32\DRIVERS\C5eBus.sys)
File size 37K..............
MmLoadSystemImage: Pulled \SystemRoot\system32\DRIVERS\C5eBus.sys from kd
*******************************************************************************
*
* This is the string you add to your checkin description
* Driver Verifier: Enabled for C5eBus.sys on Build 2600 E2mHBpcqq9nP3bXHN1FXQD
*
*******************************************************************************
MAC addresses 0x0005e0002080 - 0x0005e0002087RTP HD built on Nov 3 2006 at
19:08:38
TBS: version - sepdrv.sys=Dec 16 2005 10:45:24
SXS: BasepCreateActCtx()
NtOpenFile(\??\C:\??\C:\WINDOWS\system32\winlogon.exe) failed
ERROR: DavReadRegistryValues/RegQueryValueExW(4). WStatus = 127
ERROR: DavReadRegistryValues/RegQueryValueExW(5). WStatus = 127
ERROR: DavReadRegistryValues/RegQueryValueExW(6). WStatus = 127
0 - KeepSCMHappyOnStart
17 - KeepSCMHappyOnStart
34 - TellSCMGoodToGo
SavRoam: initializing communications
SavRoam: initializing COM
SavRoam: starting Transman
SavRoam: loading certs from: C:\Program Files\Symantec AntiVirus\
SavRoam: loading ScsComms
SavRoam: communication initialization SUCCEEDED!
SXS: BasepCreateActCtx()
NtOpenFile(\??\C:\??\C:\WINDOWS\system32\winlogon.exe) failed
watchdog!WdUpdateRecoveryState: Recovery enabled.
SXS: BasepCreateActCtx()
NtOpenFile(\??\C:\??\C:\WINDOWS\system32\winlogon.exe) failed
SXS: BasepCreateActCtx()
NtOpenFile(\??\C:\??\C:\WINDOWS\system32\winlogon.exe) failed
*** Fatal System Error: 0x000000c4
(0x00000060,0x00000000,0x007F82C4,0x00000003)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.
A fatal system error has occurred.
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
DBGHELP:
\\tsclient\n\packetsphere\c5\driver\c5bus\objfre_wxp_x86\i386\ntkrpamp.pdb -
file not found
DBGHELP:
\\tsclient\n\packetsphere\c5\driver\c5bus\objfre_wxp_x86\i386\symbols\exe\ntkrpamp.pdb - file not found
DBGHELP:
\\tsclient\n\packetsphere\c5\driver\c5bus\objfre_wxp_x86\i386\exe\ntkrpamp.pdb - file not found
SYMSRV:
\\bed-d-edjo\symbols\ntkrpamp.pdb\430480FAAC4F4A45980B99443EDC145E1\ntkrpamp.pdb not found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.pdb/430480FAAC4F4A45980B99443EDC145E1/ntkrpamp.pdb not found
DBGHELP: ntkrpamp.pdb - file not found
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntkrpamp.exe -
DBGHELP: nt - export symbols
Loading Kernel Symbols
..............................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {60, 0, 7f82c4, 3}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
DBGHELP:
\\tsclient\n\packetsphere\c5\driver\c5bus\objfre_wxp_x86\i386\mssmbios.pdb -
file not found
DBGHELP:
\\tsclient\n\packetsphere\c5\driver\c5bus\objfre_wxp_x86\i386\symbols\sys\mssmbios.pdb - file not found
DBGHELP:
\\tsclient\n\packetsphere\c5\driver\c5bus\objfre_wxp_x86\i386\sys\mssmbios.pdb - file not found
SYMSRV:
\\bed-d-edjo\symbols\mssmbios.pdb\CEAE494998B24A458588AE7866D1B9421\mssmbios.pdb not found
SYMSRV:
http://msdl.microsoft.com/download/symbols/mssmbios.pdb/CEAE494998B24A458588AE7866D1B9421/mssmbios.pdb not found
DBGHELP: mssmbios.pdb - file not found
*** ERROR: Module load completed but symbols could not be loaded for
mssmbios.sys
DBGHELP: mssmbios - no symbols loaded
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\Dbgv.sys\4124D0031d60\Dbgv.sys not found
SYMSRV:
http://msdl.microsoft.com/download/symbols/Dbgv.sys/4124D0031d60/Dbgv.sys not
found
Followup: MachineOwner
---------
nt!DbgBreakPointWithStatus+0x4:
8052a5d8 cc int 3
1: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA
will
be among the most commonly seen crashes.
Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error codes.
Typically the code is 0x1001 (deadlock detected) and you can
issue a '!deadlock' KD command to get more information.
Arguments:
Arg1: 00000060, A driver has forgotten to free its pool allocations prior to
unloading.
Arg2: 00000000, paged bytes
Arg3: 007f82c4, nonpaged bytes,
Arg4: 00000003, total # of (paged+nonpaged) allocations that weren't freed.
To get the name of the driver at fault, type
dp ViBadDriver l1; dS @$p
Then type !verifier 3 drivername.sys for info on the allocations
that were leaked that caused the bugcheck.
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\ntkrpamp.exe\42250A1E20b000\ntkrpamp.exe not
found
SYMSRV:
http://msdl.microsoft.com/download/symbols/ntkrpamp.exe/42250A1E20b000/ntkrpamp.exe not found
SYMSRV: \\bed-d-edjo\symbols\Dbgv.sys\4124D0031d60\Dbgv.sys not found
SYMSRV:
http://msdl.microsoft.com/download/symbols/Dbgv.sys/4124D0031d60/Dbgv.sys not
found
MODULE_NAME: nt
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1e
BUGCHECK_STR: 0xc4_60
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 804f96e8 to 8052a5d8
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
bad0b7c4 804f96e8 00000003 00000000 8aefcf08 nt!DbgBreakPointWithStatus+0x4
bad0bba4 804f9c37 000000c4 00000060 00000000
nt!KeRegisterBugCheckReasonCallback+0x77c
bad0bbc4 806579f0 000000c4 00000060 00000000 nt!KeBugCheckEx+0x1b
bad0bbec 805ac7c8 8add1618 8ae13920 8ae13948 nt!RtlCompressBuffer+0x4b86
bad0bc18 80582323 8add1618 8ae13930 8ae13910 nt!MmResetDriverPaging+0x147e
bad0bc2c 805b9e25 8ae13948 00000000 8ae13930 nt!NtWriteFile+0x66b7
bad0bc48 805257b8 8ae13948 00000000 00000000 nt!NtFreeVirtualMemory+0x84e7
bad0bc68 805b9e25 8addfb30 00000000 8addfb18 nt!ObfDereferenceObject+0x4c
bad0bc84 805257b8 8addfb30 00000000 8055a100 nt!NtFreeVirtualMemory+0x84e7
bad0bcb8 8059919d 8ae703b0 e31141d8 00000000 nt!ObfDereferenceObject+0x4c
bad0bd3c 805993de bad0bd00 806e4974 e30f6008 nt!IoReportResourceUsage+0xf847
bad0bd58 80599537 bad0bd78 89409b20 8056375c nt!IoReportResourceUsage+0xfa88
bad0bd7c 80537757 89409b20 00000000 8aeab8b8 nt!IoReportResourceUsage+0xfbe1
bad0bdac 805ce794 89409b20 00000000 00000000 nt!ExQueueWorkItem+0x1a3
bad0bddc 805450ce 80537668 00000001 00000000
nt!PsRemoveCreateThreadNotifyRoutine+0x214
00000000 00000000 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x72e
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_NAME: MachineOwner
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Post by Jeffrey Tan[MSFT]Hi,
Based on my understanding, you are debugging a bug check kernel dump file.
Can you tell me what version of Windows the dump is taking from, 32-bit or
64-bit?
Is this symbol loading problem specific with your windbg machine? Have you
tried to use other machines with windbg to debug the dump? Can the symols
be found on other machines?
Additionally, it would be helpful if you can provide the symbol loading
noisy output. This will be helpful for us to analysis.
I will wait for your further information. Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights