Hello,
I am newbie in Driver World. I am trying to develop volume filter driver. Its just a pass through driver and I wrote INF file which installs this driver. The problem is that after installation the system prompts to restart the box. When I restart it shows BSOD. I tried to debug through WinDbg but unable to get failure cause. WinDbg did output the following things, but I am unable to understand. Could you please help me out? What might be the cause of failure?
Thnaks in advance.
PassThrough -
NTSTATUS
VolumeFilterDispatchPassThrough (IN PDEVICE_OBJECT pDeviceObject, IN PIRP pIrp) {
PDEVICE_EXTENSION pDeviceExtension = (PDEVICE_EXTENSION)pDeviceObject->DeviceExtension;
DbgPrint (“VolumeFilterDispatch: In PassThrough!”);
KdBreakPoint();
IoSkipCurrentIrpStackLocation (pIrp);
return IoCallDriver (pDeviceExtension->pLowerDeviceObject, pIrp);
}
WinDbg -
kd> g
IoCreateDevice: Success!! [pFilterDeviceObject:813b3558]IoAttachDeviceToDeviceStack: Success!!
*** Fatal System Error: 0x0000007b
(0xF9E62640,0xC000000E,0x00000000,0x00000000)
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
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
Loading Kernel Symbols
…
Loading unloaded module list
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7B, {f9e62640, c000000e, 0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : ntoskrnl.exe ( nt!KeDeregisterBugCheckCallback+52d )
Followup: MachineOwner
nt!DbgBreakPointWithStatus+0x4:
8050d064 cc int 3
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INACCESSIBLE_BOOT_DEVICE (7b)
During the initialization of the I/O system, it is possible that the driver
for the boot device failed to initialize the device that the system is
attempting to boot from, or it is possible for the file system that is
supposed to read that device to either fail its initialization or to simply
not recognize the data on the boot device as a file system structure that
it recognizes.
Arguments:
Arg1: f9e62640, Pointer to the device object or Unicode string of ARC name
Arg2: c000000e
Arg3: 00000000
Arg4: 00000000
Debugging Details:
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7B
LAST_CONTROL_TRANSFER: from 80522dea to 8050d064
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f9e6210c 80522dea 00000003 80087000 e1285b20 nt!DbgBreakPointWithStatus+0x4
f9e624d4 804fc1bb 0000007b f9e62640 c000000e nt!KeDeregisterBugCheckCallback+0x52d
f9e624f4 806879a6 0000007b f9e62640 c000000e nt!KeBugCheckEx+0x19
f9e62654 80673e52 80087000 80087000 00000000 nt!KeSetProfileIrql+0x12bd
f9e626a4 8067f996 80087000 f9e627ec 00034000 nt!IoReportHalResourceUsage+0x2a98
f9e627d0 80088228 80683c64 80088228 00000010 nt!KeFindConfigurationNextEntry+0xb73f
80683c70 4f425245 00004553 00640041 00700061 0x80088228
56504958 00000000 00000000 00000000 00000000 0x4f425245