Yes, they are using 1.1. If 1.5 was already installed, then the update would not even have been attempted, as a newer version of 1.x KMDF is already present (which is what the later message about post processing indicates).
This snippet indicates that their first driver invoked the update program to install the KMDF runtime, but that process crashed with an AV caught in some generic exception handler it contains (in some post-install task after the framework installation itself had taken place, or at least at some point where the installation was verifiable)- because of that, the driver install failed.
A second KMDF driver was then installed successfully, since the framework made it the first time around.
The first driver is a bus driver that spawns devices for which the second driver is the FDO, so of course nothing is working since the bus driver failed.
I’m not sure why it’s intermittent and only occurs on certain machines- I’ve been working with the OP and still have no clear patterns to that. WE already know some things to at least try.
Also have quite a few unanswered questions popping up now- trying to get them in coherent order…
Thanks for all the suggestions (from all sources).
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Peter Wieland
Sent: Tuesday, June 05, 2007 12:28 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] KMDF install error code 37
Except that this line:
WdfCoInstaller: [03/28/2007 00:01.17.953] DIF_INSTALLDEVICE: GetLatestInstalledVersion install version major 0x1, minor 0x1 is less then or equal to latest major 0x1, minor 0x1, asking for post processing
Leads me to believe that 1.1 is what’s already installed on the machine.
-p
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Paolo Cazzola
Sent: Tuesday, June 05, 2007 12:08 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] KMDF install error code 37
Just another guess:
Installing KMDF 1.1 on a system with some other WDF 1.5 driver already installed.
WdfCoInstaller: [03/27/2007 23:59.53.718] ReadComponents: WdfSection for Driver Service hypkern using KMDF lib version Major 0x1, minor 0x1
Regards,
PaoloC
----- Original Message -----
From: John Kraftmailto:xxxxx
To: Windows System Software Devs Interest Listmailto:xxxxx
Sent: Tuesday, June 05, 2007 12:51 AM
Subject: [ntdev] KMDF install error code 37
A few of our customers have been reporting problems when trying to install (using a DPInst-based installer) our KMDF device driver. The number of people encountering difficulties is quite small, and we have been unable to reproduce the failure in-house. The failures are occurring on Windows XP machines, and thusfar they seem to be occurring primarily in Europe. The symptom of the failure is that the driver fails to start at boot time. Device Manager indicates that the driver has failed with Code 37.
My reading of the problem is that something in the DriverEntry code path is failing. We asked the customers to try running a version of the driver with some additional debugging messages enabled, and the debugging versions show that the driver is never getting into our DriverEntry() code. I suspect that the KMDF preamble code is failing for some reason.
Setupact.log has the following:
WdfCoInstaller: [03/27/2007 23:59.53.609] DIF_INSTALLDEVICE: Pre-Processing
WdfCoInstaller: [03/27/2007 23:59.53.718] ReadComponents: WdfSection for Driver Service hypkern using KMDF lib version Major 0x1, minor 0x1
WdfCoInstaller: [03/27/2007 23:59.53.875] VerifyMSRoot: exit: error(0) Op?ration r?ussie.
WdfCoInstaller: [03/28/2007 00:01.11.203] Update process returned error code :status(C0000005) . Possible causes are running fre version of coinstaller on checked version of OS and vice versa
WdfCoInstaller: [03/28/2007 00:01.17.875] DIF_INSTALLDEVICE: Pre-Processing
WdfCoInstaller: [03/28/2007 00:01.17.890] ReadComponents: WdfSection for Driver Service hypaudio using KMDF lib version Major 0x1, minor 0x1
WdfCoInstaller: [03/28/2007 00:01.17.953] DIF_INSTALLDEVICE: GetLatestInstalledVersion install version major 0x1, minor 0x1 is less then or equal to latest major 0x1, minor 0x1, asking for post processing
WdfCoInstaller: [03/28/2007 00:01.18.859] DIF_INSTALLDEVICE: Post-Processing
WdfCoInstaller: [03/28/2007 00:03.19.437] DIF_INSTALLDEVICE: Pre-Processing
I’m somewhat alarmed by the error code, but I don’t think that the customers involved are running checked versions of the OS (is there a simple way to tell for sure?).
Setup.api looks pretty normal
Thanks.
-John
—
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx>