Driver Load Failure c0000365 (STATUS_FAILED_DRIVER_ENTRY)

NTDEV
1

Does anyone know under what conditions would the PipCallDriverAddDevice fail with STATUS_FAILED_DRIVER_ENTRY. I get the following on load:

KD: Accessing ‘\server\Work\xxx\windows-port\rebuild\src\kernel\output\chk_wnet_x86\i386\xxx.sys’ (\SystemRoot\System32\Drivers\xxx.sys)
File size 235K…
MmLoadSystemImage: Pulled \SystemRoot\System32\Drivers\xxx.sys from kd
PipCallDriverAddDevice: Ignoring driver load failure (status = c0000365) until user-mode PnPMgr comes online

Because I have a map file, I get the over and over a number of times in WinDbg…

Any clues would be appreciated…

Thanks,
Tom

2

This menas DriverEntry returned !NT_SUCCESS, the actual error value is not displayed. Put a bp in your DriverEntry and see why you are returning failure.

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@comcast.net
Sent: Friday, April 25, 2008 3:42 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Driver Load Failure c0000365 (STATUS_FAILED_DRIVER_ENTRY)

Does anyone know under what conditions would the PipCallDriverAddDevice fail with STATUS_FAILED_DRIVER_ENTRY. I get the following on load:

KD: Accessing ‘\server\Work\xxx\windows-port\rebuild\src\kernel\output\chk_wnet_x86\i386\xxx.sys’ (\SystemRoot\System32\Drivers\xxx.sys)
File size 235K…
MmLoadSystemImage: Pulled \SystemRoot\System32\Drivers\xxx.sys from kd
PipCallDriverAddDevice: Ignoring driver load failure (status = c0000365) until user-mode PnPMgr comes online

Because I have a map file, I get the over and over a number of times in WinDbg…

Any clues would be appreciated…

Thanks,
Tom

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

3

Thanks Doron,
Actually, my DriverEntry was never called. I had a BP on it and it never hit. Actually turned out, the problem was difference between building for KMDF 1.7 and having KMDF 1.5 on the system…

Thanks,
Tom

4

In case something like this ever happens again, you can put a bp on !FxDriverEntry to see if the framework provided entry point is invoked. FxDriverEntry will call DriverEntry after it has bound your driver to the framework runtime.

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@comcast.net
Sent: Tuesday, April 29, 2008 1:17 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Driver Load Failure c0000365 (STATUS_FAILED_DRIVER_ENTRY)

Thanks Doron,
Actually, my DriverEntry was never called. I had a BP on it and it never hit. Actually turned out, the problem was difference between building for KMDF 1.7 and having KMDF 1.5 on the system…

Thanks,
Tom

—
NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer