Device manager error code 37

NTDEV
1

I am trying to figure out a specific reason for error code 37 .
Is it a load time error, an issue with the image such as signing or architecture?

  • KMDF specific or not
  • before or after driver entry
  • before or after IRP start device

Many thanks

2

xxxxx@yahoo.com wrote:

I am trying to figure out a specific reason for error code 37 .
Is it a load time error, an issue with the image such as signing or architecture?

As a quick Google would have showed, Code 37 means the driver returned a
failure from DriverEntry. Usually, a signing or architecture problem
would have fired Code 39, but since both of those things are trivial to
check, I presume you have already checked them.

  • KMDF specific or not

Not. However, since most KMDF drivers just return the value from
WdfDriverCreate, the error could have come from KMDF. A debug print
will answer that question.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

3

Take a look at
https://technet.microsoft.com/en-us/library/cc771328(v=ws.10).aspx Remember
web searches are your friend, the page is easily findable by searching for
“Device manager error code”

Don Burn
Windows Driver Consulting
Website: http://www.windrvr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Friday, April 17, 2015 1:11 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Device manager error code 37

I am trying to figure out a specific reason for error code 37 .
Is it a load time error, an issue with the image such as signing or
architecture?

  • KMDF specific or not
  • before or after driver entry
  • before or after IRP start device

Many thanks

NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

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

4

Ok I’ll check the links. But if I understand your response correctly Err 37 means anything other than success from Driver entry. That is as specific as I was hoping.

5

It /could/ be a kmdf config issue. When you build a kmdf driver we hijack DriverEntry and set the entry point to FxDriverEntry which binds to the wdf runtime based on the version of wdf you build with and then calls your DriverEntry. If you don’t have at a minimum the needed version of wdf installed, FxDriverEntry will return failure without calling your DriverEntry.

So, do you reference the wdf co installer in your inf or assume the right wdf version is installed? What os is this happening on? What version of wdf are you building against?

d

Bent from my phone

From: xxxxx@yahoo.commailto:xxxxx
Sent: ?4/?17/?2015 10:29 AM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: RE:[ntdev] Device manager error code 37

Ok I’ll check the links. But if I understand your response correctly Err 37 means anything other than success from Driver entry. That is as specific as I was hoping.

—
NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

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</mailto:xxxxx></mailto:xxxxx>