Bus upper filter driver

I am installing a bus upper filter driver on PCI bus.
but i am getting the blue screen before my filter driver is even get called
Can anybody tell me why
Ashish

*** Fatal System Error: 0x0000007b

(0xF402384C,0xC0000034,0x00000000,0x00000000)

Following is the stack at time of crash
f4023344 8042bef7 nt!RtlpBreakWithStatusInstruction
f4023374 8042c2bb nt!KiBugCheckDebugBreak+0x31
f4023700 80551a53 nt!KeBugCheckEx+0x390
f4023864 805510bf nt!IopMarkBootPartition+0xbd
f40238b8 8054fc8c nt!IopInitializeBootDrivers+0x43f
f4023a58 8054ea6c nt!IoInitSystem+0x5ef
f4023da8 80454faf nt!Phase1Initialization+0x71b
f4023ddc 80468ec2 nt!PspSystemThreadStartup+0x69
00000000 00000000 nt!KiThreadStartup+0x16

Probably get a better repsonse in the ntdev list but…

Bug check 7B means that after PnP comples the initial enumeration of the
system, the boot disk is not accessible as a real NT device; the first
parameter to the bug check is either a device object or a PUNICODE_STRING
(with the name of a device; from the address I’d say this is the case here)
and the second is an NT Status code. You will probably find the UNICODE
string is something like “\Arcname\multi(0)disk(0)rdisk(0)partition(3)” -
i.e. is the arcname for the boot disk as defined in the boot.ini file.

If I had to guess, I’d say that if you truly are sure that your driver
didn’t get called, PnP either thinks the installation of the driver is not
complete at boot time or that your driver is not one that it has to load at
boot time and so has punted on completing the startup of the parent bridge
and therefore on enumerating the bus to find the adapter which the boot disk
is connected to…

I suspect you will also find that your driver is being loaded and
DriverEntry is called but AddDevice either is not being called or is called
and returns an error.

/simgr

-----Original Message-----
From: xxxxx@Itronix.com [mailto:xxxxx@Itronix.com]
Sent: Monday, May 06, 2002 6:47 PM
To: Kernel Debugging Interest List
Subject: [windbg] Bus upper filter driver

I am installing a bus upper filter driver on PCI bus.
but i am getting the blue screen before my filter driver is even get called
Can anybody tell me why
Ashish

*** Fatal System Error: 0x0000007b

(0xF402384C,0xC0000034,0x00000000,0x00000000)

Following is the stack at time of crash
f4023344 8042bef7 nt!RtlpBreakWithStatusInstruction
f4023374 8042c2bb nt!KiBugCheckDebugBreak+0x31
f4023700 80551a53 nt!KeBugCheckEx+0x390
f4023864 805510bf nt!IopMarkBootPartition+0xbd
f40238b8 8054fc8c nt!IopInitializeBootDrivers+0x43f
f4023a58 8054ea6c nt!IoInitSystem+0x5ef
f4023da8 80454faf nt!Phase1Initialization+0x71b
f4023ddc 80468ec2 nt!PspSystemThreadStartup+0x69
00000000 00000000 nt!KiThreadStartup+0x16


You are currently subscribed to windbg as: xxxxx@stratus.com
To unsubscribe send a blank email to %%email.unsub%%

Hello Simon,
My filter driver’s file name was not in 8.3 format and Start key has to be
0 as even you mentioned. After doing both of it my driver is working now.
Regards
Ashish

-----Original Message-----
From: Graham, Simon [mailto:xxxxx@stratus.com]
Sent: Thursday, May 09, 2002 9:43 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Bus upper filter driver

Probably get a better repsonse in the ntdev list but…

Bug check 7B means that after PnP comples the initial enumeration of the
system, the boot disk is not accessible as a real NT device; the first
parameter to the bug check is either a device object or a PUNICODE_STRING
(with the name of a device; from the address I’d say this is the case here)
and the second is an NT Status code. You will probably find the UNICODE
string is something like “\Arcname\multi(0)disk(0)rdisk(0)partition(3)” -
i.e. is the arcname for the boot disk as defined in the boot.ini file.

If I had to guess, I’d say that if you truly are sure that your driver
didn’t get called, PnP either thinks the installation of the driver is not
complete at boot time or that your driver is not one that it has to load at
boot time and so has punted on completing the startup of the parent bridge
and therefore on enumerating the bus to find the adapter which the boot disk
is connected to…

I suspect you will also find that your driver is being loaded and
DriverEntry is called but AddDevice either is not being called or is called
and returns an error.

/simgr

-----Original Message-----
From: xxxxx@Itronix.com [mailto:xxxxx@Itronix.com]
Sent: Monday, May 06, 2002 6:47 PM
To: Kernel Debugging Interest List
Subject: [windbg] Bus upper filter driver

I am installing a bus upper filter driver on PCI bus.
but i am getting the blue screen before my filter driver is even get called
Can anybody tell me why
Ashish

*** Fatal System Error: 0x0000007b

(0xF402384C,0xC0000034,0x00000000,0x00000000)

Following is the stack at time of crash
f4023344 8042bef7 nt!RtlpBreakWithStatusInstruction
f4023374 8042c2bb nt!KiBugCheckDebugBreak+0x31
f4023700 80551a53 nt!KeBugCheckEx+0x390
f4023864 805510bf nt!IopMarkBootPartition+0xbd
f40238b8 8054fc8c nt!IopInitializeBootDrivers+0x43f
f4023a58 8054ea6c nt!IoInitSystem+0x5ef
f4023da8 80454faf nt!Phase1Initialization+0x71b
f4023ddc 80468ec2 nt!PspSystemThreadStartup+0x69
00000000 00000000 nt!KiThreadStartup+0x16


You are currently subscribed to windbg as: xxxxx@stratus.com To
unsubscribe send a blank email to %%email.unsub%%


You are currently subscribed to windbg as: xxxxx@itronix.com To unsubscribe
send a blank email to %%email.unsub%%