Hi,
I am getting the following error when I am debugging a SCSI miniport driver using windebugger.
Opened \.\COM1
Microsoft (R) Windows Kernel Debugger Version 4.0.0018.0
Copyright (c) Microsoft Corporation. All rights reserved.
Waiting to reconnect…
Symbol search path is: c:\iscsi\objchk\i386
Loaded dbghelp extension DLL
Loaded ext extension DLL
Loaded kext extension DLL
Loaded kdextx86 extension DLL
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: c:\iscsi\objchk\i386
Executable search path is:
PsLoadedModuleList not initialized yet. Delay kernel load.
Windows 2000 Kernel Version 2195 UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046ccf0
System Uptime: not available
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
ACPI: Length does not match fixed attributes
Break instruction exception - code 80000003 (first chance)
*******************************************************************************
* *
* You are seeing this message because you pressed either *
* CTRL+C (if you run kd.exe) or, *
* CTRL+BREAK (if you run WinDBG), *
* on your debugger machine’s keyboard. *
* *
* THIS IS NOT A BUG OR A SYSTEM CRASH *
* *
* If you did not intend to break into the debugger, press the “g” key, then *
* press the “Enter” key now. This message might immediately reappear. If it *
* does, press “g” and “Enter” again. *
* *
*******************************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
nt!DbgBreakPointWithStatus+4:
80455994 cc int 3
kd> lm
start end module name
80062000 80072460 hal (export symbols)
80400000 805a2340 nt (export symbols)
bfeb2000 bfec71e0 mup (no symbolic information)
bfec8000 bfeefc20 ndis (export symbols)
bfef0000 bff72700 ntfs (export symbols)
bff73000 bff83e40 ksecdd (export symbols)
bff84000 bff98c00 atapi (no symbolic information)
bff99000 bffba620 dmio (no symbolic information)
bffbb000 bffd70c0 ftdisk (no symbolic information)
bffd8000 bffffbc0 acpi (no symbolic information)
f7000000 f700e500 pci (no symbolic information)
f7010000 f701b680 isapnp (no symbolic information)
f7020000 f7028280 classpnp (export symbols)
f7280000 f72854a0 pciidex (export symbols)
f7288000 f728f1e0 mountmgr (no symbolic information)
f7290000 f7297080 disk (no symbolic information)
f7298000 f729ca40 ino_flpy (no symbolic information)
f72a0000 f72a5680 viaagp (no symbolic information)
f7410000 f7412a20 bootvid (export symbols)
f7414000 f7416b80 partmgr (no symbolic information)
f7500000 f7501c00 diskperf (no symbolic information)
f7502000 f7503b80 dmload (no symbolic information)
f75c8000 f75c8f80 wmilib (export symbols)
f75c9000 f75c9b00 pciide (no symbolic information)
Unloaded modules:
kd> bp iscsi!DriverEntry
Bp expression ‘iscsi!DriverEntry’ could not be resolved, adding deferred bp
kd> g
ERROR: Symbol file could not be found. Defaulted to export symbols for VIDEOPRT.SYS -
ERROR: Symbol file could not be found. Defaulted to export symbols for USBD.SYS -
ERROR: Symbol file could not be found. Defaulted to export symbols for KS.SYS -
ERROR: Symbol file could not be found. Defaulted to export symbols for portcls.sys -
ERROR: Symbol file could not be found. Defaulted to export symbols for ndistapi.sys -
ERROR: Symbol file could not be found. Defaulted to export symbols for TDI.SYS -
ERROR: Symbol file could not be found. Defaulted to export symbols for ptilink.sys -
ERROR: Symbol file could not be found. Defaulted to export symbols for SCSIPORT.SYS -
Breakpoint 0 hit
Breakpoint 1 hit
Breakpoint 5 hit
iscsi!DriverEntry:
f74c4280 55 push ebp
kd> p
iscsi!DriverEntry+7:
f74c4287 6a14 push 0x14
kd> p
iscsi!DriverEntry+15:
f74c4295 8d45fc lea eax,[ebp-0x4]
kd> p
iscsi!DriverEntry+1f:
f74c429f 8d45f8 lea eax,[ebp-0x8]
kd> p
iscsi!DriverEntry+25:
f74c42a5 8d450c lea eax,[ebp+0xc]
kd> g
Breakpoint 3 hit
iscsi!iSCSIFindAdapter:
f74c4324 55 push ebp
kd> p
iscsi!iSCSIFindAdapter+4:
f74c4328 bef4010000 mov esi,0x1f4
kd> p
iscsi!iSCSIFindAdapter+12:
f74c4336 56 push esi
kd> t
iscsi!MemAlloc:
f74c690c 55 push ebp
kd> p
iscsi!MemAlloc+3:
f74c690f 6844646b20 push 0x206b6444
kd> p
iscsi!MemAlloc+13:
f74c691f 5d pop ebp
kd> p
iscsi!iSCSIFindAdapter+1d:
f74c4341 a3786e4cf7 mov [iscsi!pcRecv (f74c6e78)],eax
kd> p
iscsi!iSCSIFindAdapter+22:
f74c4346 8b451c mov eax,[ebp+0x1c]
kd> p
iscsi!iSCSIFindAdapter+28:
f74c434c e8831c0000 call iscsi!fiInitialiseSessionVariables (f74c5fd4)
kd> p
Breakpoint 4 hit
iscsi!iSCSIFindAdapter+2d:
f74c4351 e8ba030000 call iscsi!fiInitConfig (f74c4710)
kd> p
iscsi!iSCSIFindAdapter+34:
f74c4358 7445 jz iscsi!iSCSIFindAdapter+0x7b (f74c439f)
kd> p
iscsi!iSCSIFindAdapter+36:
f74c435a e849200000 call iscsi!fiCreateSocket (f74c63a8)
kd> t
Breakpoint 2 hit
iscsi!fiCreateSocket:
f74c63a8 55 push ebp
kd> p
iscsi!fiCreateSocket+9:
f74c63b1 33c0 xor eax,eax
kd> p
iscsi!fiCreateSocket+2f:
f74c63d7 6a08 push 0x8
kd> p
iscsi!fiCreateSocket+39:
f74c63e1 6832624cf7 push 0xf74c6232
kd> p
iscsi!fiCreateSocket+45:
f74c63ed 6a18 push 0x18
kd> p
iscsi!fiCreateSocket+4e:
f74c63f6 33db xor ebx,ebx
kd> p
iscsi!fiCreateSocket+50:
f74c63f8 6a33 push 0x33
kd> p
iscsi!fiCreateSocket+71:
f74c6419 6a0c push 0xc
kd> p
iscsi!fiCreateSocket+78:
f74c6420 be4a624cf7 mov esi,0xf74c624a
kd> p
iscsi!fiCreateSocket+8f:
f74c6437 6a05 push 0x5
kd> p
iscsi!fiCreateSocket+9e:
f74c6446 6a08 push 0x8
kd> p
iscsi!fiCreateSocket+ac:
f74c6454 6a33 push 0x33
kd> p
iscsi!fiCreateSocket+cd:
f74c6475 85c0 test eax,eax
kd> p
iscsi!fiCreateSocket+d1:
f74c6479 685e624cf7 push 0xf74c625e
kd> p
ZwCreateFile Failed
iscsi!fiCreateSocket+dc:
f74c6484 8d45ec lea eax,[ebp-0x14]
kd> iscsi!Status
^ Syntax error in ‘iscsi!Status’
kd> g
Failed to Open the UDP device
Unable to obtain Transport Address File Object
Fatal System Error: 0x0000001e
(0xC0000005,0x8041F2FC,0x00000000,0x00000030)
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.
**********************************************************************
Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {c0000005, 8041f2fc, 0, 30}
Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : ntoskrnl ( nt!DbgBreakPointWithStatus+4 )
Followup: MachineOwner
---------
nt!DbgBreakPointWithStatus+4:
80455994 cc int 3
kd> !analyze -v
Bugcheck Analysis
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8041f2fc, The address that the exception occurred at
Arg3: 00000000, Parameter 0 of the exception
Arg4: 00000030, Parameter 1 of the exception
Debugging Details:
------------------
*****Kernel symbols are WRONG. Please fix symbols to do analysis.
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 1E
LAST_CONTROL_TRANSFER: from 8042c2bb to 80455994
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f741abb0 8042c2bb 00000003 80409688 00000000 nt!DbgBreakPointWithStatus+0x4
f741af3c 80454f55 0000001e c0000005 8041f2fc nt!KeBugCheckEx+0x169
f741bddc 80468ec2 8054e3b8 80087000 00000000 nt!PsSetCreateThreadNotifyRoutine+0x50
00000000 00000000 00000000 00000000 00000000 nt!KiUnexpectedInterrupt+0x180
FOLLOWUP_IP:
nt!DbgBreakPointWithStatus+4
80455994 cc int 3
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!DbgBreakPointWithStatus+4
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl
STACK_COMMAND: kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
kd> g
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Bugcheck Analysis
*
**************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {c0000005, 8041f2fc, 0, 30}
Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : ntoskrnl ( nt!DbgBreakPointWithStatus+4 )
Followup: MachineOwner
---------
nt!DbgBreakPointWithStatus+4:
80455994 cc int 3
please help me in solving this if anone can
regards
sreenivas
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com