Should I be seeing win2k bugcheck when it tries to load my
driver because of a supporting kernel mode DLL file (i.e.
another .SYS with exports I require) is not available on disk?
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
Yes, you sure should, if it’s a boot driver. The bugcheck code should be:
0x7B - INACCESSIBLE_BOOT_DEVICE. That’s because if the loader can’t resolve
the references, then it thinks your driver can’t succeed, and since it’s
required for booting, it abandons the effort. At least, that’s what
happened when I tried the same thing with my SCSI miniport. But then, I was
*the boot disk*, so if I didn’t work, there really was no recovering.
Phil
-----Original Message-----
From: Rick Bowman [mailto:xxxxx@bustech.com]
Sent: Thursday, January 25, 2001 9:31 AM
To: NT Developers Interest List
Subject: [ntdev] Bugcheck for a missing load module?
Should I be seeing win2k bugcheck when it tries to load my
driver because of a supporting kernel mode DLL file (i.e.
another .SYS with exports I require) is not available on disk?
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
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
I’m a network driver though, PNP, StartType 3?
Rick
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Barila, Phil
Sent: Thursday, January 25, 2001 12:44 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Bugcheck for a missing load module?
Yes, you sure should, if it’s a boot driver. The bugcheck code should be:
0x7B - INACCESSIBLE_BOOT_DEVICE. That’s because if the loader can’t resolve
the references, then it thinks your driver can’t succeed, and since it’s
required for booting, it abandons the effort. At least, that’s what
happened when I tried the same thing with my SCSI miniport. But then, I was
*the boot disk*, so if I didn’t work, there really was no recovering.
Phil
-----Original Message-----
From: Rick Bowman [mailto:xxxxx@bustech.com]
Sent: Thursday, January 25, 2001 9:31 AM
To: NT Developers Interest List
Subject: [ntdev] Bugcheck for a missing load module?
Should I be seeing win2k bugcheck when it tries to load my
driver because of a supporting kernel mode DLL file (i.e.
another .SYS with exports I require) is not available on disk?
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@bustech.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
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
Can’t help you there. Don’t know anything about network drivers.
How could you succeed if you are dependent on a another .sys when it’s not
there? Or are you just wondering how to get it to boot through the failure,
instead of BSOD? I don’t know how to do that either, but I sure hope
someone else knows and will tell us!
Phil
-----Original Message-----
From: Rick Bowman [mailto:xxxxx@bustech.com]
Sent: Thursday, January 25, 2001 10:02 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Bugcheck for a missing load module?
I’m a network driver though, PNP, StartType 3?
Rick
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Barila, Phil
Sent: Thursday, January 25, 2001 12:44 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Bugcheck for a missing load module?
Yes, you sure should, if it’s a boot driver. The bugcheck code should be:
0x7B - INACCESSIBLE_BOOT_DEVICE. That’s because if the loader can’t resolve
the references, then it thinks your driver can’t succeed, and since it’s
required for booting, it abandons the effort. At least, that’s what
happened when I tried the same thing with my SCSI miniport. But then, I was
*the boot disk*, so if I didn’t work, there really was no recovering.
Phil
-----Original Message-----
From: Rick Bowman [mailto:xxxxx@bustech.com]
Sent: Thursday, January 25, 2001 9:31 AM
To: NT Developers Interest List
Subject: [ntdev] Bugcheck for a missing load module?
Should I be seeing win2k bugcheck when it tries to load my
driver because of a supporting kernel mode DLL file (i.e.
another .SYS with exports I require) is not available on disk?
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@bustech.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
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
The PnP manager will load a PnP driver when it decides. Just because you
have Start set to 3 don’t expect it to wait to load when a user logs in.
Given that … any DLL that your driver requires must be in place and
visible when your driver loads. Visible, because some path names are not
available until late in the load process; i.e. don’t expect to load a SCSI
miniport from C:\MyDevices\MyScsi\Version12\myscsidevice.sys.
Gary
-----Original Message-----
From: Rick Bowman [mailto:xxxxx@bustech.com]
Sent: Thursday, January 25, 2001 10:02 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Bugcheck for a missing load
module?
I’m a network driver though, PNP, StartType 3?
Rick
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
I agree with you, but should it bug-check ? NT 4.0 doesn’t bug check.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Gary Little
Sent: Thursday, January 25, 2001 3:50 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Bugcheck for a missing load module?
The PnP manager will load a PnP driver when it decides. Just because you
have Start set to 3 don’t expect it to wait to load when a user logs in.
Given that … any DLL that your driver requires must be in place and
visible when your driver loads. Visible, because some path names are not
available until late in the load process; i.e. don’t expect to load a SCSI
miniport from C:\MyDevices\MyScsi\Version12\myscsidevice.sys.
Gary
-----Original Message-----
From: Rick Bowman [mailto:xxxxx@bustech.com]
Sent: Thursday, January 25, 2001 10:02 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Bugcheck for a missing load
module?
I’m a network driver though, PNP, StartType 3?
Rick
You are currently subscribed to ntdev as: xxxxx@bustech.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
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
To my knowledge and experience, yes it will.
Gary
-----Original Message-----
From: Rick Bowman [mailto:xxxxx@bustech.com]
Sent: Thursday, January 25, 2001 2:19 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Bugcheck for a missing load
module?
I agree with you, but should it bug-check ? NT 4.0 doesn’t
bug check.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Gary
Little
Sent: Thursday, January 25, 2001 3:50 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Bugcheck for a missing load module?
The PnP manager will load a PnP driver when it decides. Just
because you
have Start set to 3 don’t expect it to wait to load when a
user logs in.
Given that … any DLL that your driver requires must be in
place and
visible when your driver loads. Visible, because some path
names are not
available until late in the load process; i.e. don’t expect
to load a SCSI
miniport from
C:\MyDevices\MyScsi\Version12\myscsidevice.sys.
Gary
-----Original Message-----
From: Rick Bowman
[mailto:xxxxx@bustech.com]
Sent: Thursday, January 25, 2001 10:02 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Bugcheck for a
missing load
module?
I’m a network driver though, PNP, StartType
3?
Rick
You are currently subscribed to ntdev as: xxxxx@bustech.com
To unsubscribe send a blank email to
leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as:
xxxxx@delphieng.com
To unsubscribe send a blank email to
leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
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
STOP 0x7B is a specific code to indicate that the boot device (the disk containing
the OS) cannot be found. A common cause for this error is that the SCSI miniport
has not been loaded, or cannot locate its disk devices. It is *not* displayed for
the generic failure to load a boot-start device. IME, this kind of failure
doesn’t cause any problem at all (besides the fact that obviously the device
controlled by the driver is unavailable), but I it depends on the value of
ErrorControl in the registry for the particular device.
Regards,
Paul Bunn, UltraBac.com, 425-644-6000
Microsoft MVP - WindowsNT/2000
http://www.ultrabac.com
-----Original Message-----
From: Barila, Phil [mailto:xxxxx@intel.com]
Sent: Thursday, January 25, 2001 9:44 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Bugcheck for a missing load module?
Yes, you sure should, if it’s a boot driver. The bugcheck code should be:
0x7B - INACCESSIBLE_BOOT_DEVICE. That’s because if the loader can’t resolve
the references, then it thinks your driver can’t succeed, and since it’s
required for booting, it abandons the effort. At least, that’s what
happened when I tried the same thing with my SCSI miniport. But then, I was
*the boot disk*, so if I didn’t work, there really was no recovering.
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
The fact that the original poster was working on a network driver wasn’t
revealed until after I wrote this. However, your reminder of the
ErrorControl entry, as I had completely forgot about it.
Phil
* Philip D. Barila | (503) 264-8386
* Intel Corp. | M/S JF2-53 Office JF2-2-G6
* Storage Architecture and Performance
* Internet Systems Lab
-----Original Message-----
From: Paul Bunn [mailto:xxxxx@UltraBac.com]
Sent: Friday, January 26, 2001 11:04 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Bugcheck for a missing load module?
STOP 0x7B is a specific code to indicate that the boot device (the disk
containing
the OS) cannot be found. A common cause for this error is that the SCSI
miniport
has not been loaded, or cannot locate its disk devices. It is *not*
displayed for
the generic failure to load a boot-start device. IME, this kind of failure
doesn’t cause any problem at all (besides the fact that obviously the device
controlled by the driver is unavailable), but I it depends on the value of
ErrorControl in the registry for the particular device.
Regards,
Paul Bunn, UltraBac.com, 425-644-6000
Microsoft MVP - WindowsNT/2000
http://www.ultrabac.com
-----Original Message-----
From: Barila, Phil [mailto:xxxxx@intel.com]
Sent: Thursday, January 25, 2001 9:44 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Bugcheck for a missing load module?
Yes, you sure should, if it’s a boot driver. The bugcheck code should be:
0x7B - INACCESSIBLE_BOOT_DEVICE. That’s because if the loader can’t resolve
the references, then it thinks your driver can’t succeed, and since it’s
required for booting, it abandons the effort. At least, that’s what
happened when I tried the same thing with my SCSI miniport. But then, I was
*the boot disk*, so if I didn’t work, there really was no recovering.
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
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
Absolutely it should bugcheck. What you describe is that your driver is calling
an export routine – if that routine isn’t present then it’s going to call address
0, and should bugcheck as nicely on NT4 as Win2K.
Regards,
Paul Bunn, UltraBac.com, 425-644-6000
Microsoft MVP - WindowsNT/2000
http://www.ultrabac.com
-----Original Message-----
From: Rick Bowman [mailto:xxxxx@bustech.com]
Sent: Thursday, January 25, 2001 9:31 AM
To: NT Developers Interest List
Subject: [ntdev] Bugcheck for a missing load module?
Should I be seeing win2k bugcheck when it tries to load my
driver because of a supporting kernel mode DLL file (i.e.
another .SYS with exports I require) is not available on disk?
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
It appears the loader on WinNT realizes that a supporting load module is not
available and throws an event, but doesn’t bugcheck. Win2K seems to realize
the same thing although bugchecks with a STOP code of:
0xC000026C STATUS_DRIVER_UNABLE_TO_LOAD
and Error Status of:
0xC0000034 STATUS_OBJECT_NAME_NOT_FOUND
I’m thinking MS implemented this differently in Win2K, or I’ve missed
something in my build, or elsewhere, etc.
The ErrorControl theory sounded like the one, but in both cases (NT & 2K),
it’s set to 0x1 which certainly doesn’t indicate bugcheck in either DDK
(both document ErrorControl the same).
Is there anyone from Microsoft out there that knows how this should behave??
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
> STOP 0x7B is a specific code to indicate that the boot device (the disk
containing
the OS) cannot be found. A common cause for this error is that the SCSI
More exactly - this means - “unable to mount the SystemRoot filesystem
volume”. This surely can be due to disk stack failures.
Max
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