Jump-start your project by learning from devs who
write Windows drivers and file systems every day.
Take an OSR seminar!

Upcoming OSR Seminars:
WDM Lab, Seattle, WA 16 August 2010
WDF Lab, Santa Clara, CA 27 September 2010
Debug Lab, Portland, OR 18 October 2010
Windows Internals & Software Drivers Lab, Santa Clara, CA 15 November 2010


Go Back   OSR Online Lists > ntdev
link KMDF install error code 37
Welcome, Guest
You must login to post to this list
  Message 1 of 10  
04 Jun 07 18:52
John Kraft
xxxxxx@uaudio.com
Join Date: 08 May 2007
Posts To This List: 11
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) <no error text>. 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 --
  Message 2 of 10  
04 Jun 07 19:20
ntdev member 8437
xxxxxx@windows.microsoft.com
Join Date:
Posts To This List: 1404
RE: KMDF install error code 37
0xc0000005 probably isn't "trying to run fre on a chk system". It's STATUS_ACCESS_VIOLATION which isn't a good thing. Are the machines affected limited to a particular language? Are they all non-english? (just a shot in the dark) -p From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of John Kraft Sent: Monday, June 04, 2007 3:52 PM To: Windows System Software Devs Interest List 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=E9ration r?ussie. WdfCoInstaller: [03/28/2007 00:01.11.203] Update process returned error code :status(C0000005) <no error text>. 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 --
  Message 3 of 10  
04 Jun 07 19:58
John Kraft
xxxxxx@uaudio.com
Join Date: 08 May 2007
Posts To This List: 11
RE: KMDF install error code 37
So far, all of the reports we've gotten have been from users with non-English system configurations. We've had reports from both France and the Netherlands, so it isn't specific to a single language. Also, we have many users from both countries who have had no problems. We tried installing French Windows XP configuration, but we weren't able to reproduce it under those conditions either. So it may be that a non-English system is required but not sufficient to induce the problem. -John > From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Peter Wieland > Sent: Monday, June 04, 2007 4:20 PM > To: Windows System Software Devs Interest List > Subject: RE: [ntdev] KMDF install error code 37 > Are the machines affected limited to a particular language? > Are they all non-english? (just a shot in the dark)
  Message 4 of 10  
04 Jun 07 20:41
ntdev member 8437
xxxxxx@windows.microsoft.com
Join Date:
Posts To This List: 1404
RE: KMDF install error code 37
Is it possible that they're running as a non-admin? (another guess) -----Original Message----- From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of John Kraft Sent: Monday, June 04, 2007 4:58 PM To: Windows System Software Devs Interest List Subject: RE: [ntdev] KMDF install error code 37 So far, all of the reports we've gotten have been from users with non-English system configurations. We've had reports from both France and the Netherlands, so it isn't specific to a single language. Also, we have many users from both countries who have had no problems. We tried installing French Windows XP configuration, but we weren't able to reproduce it under those conditions either. So it may be that a non-English system is required but not sufficient to induce the problem. -John > From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Peter Wieland > Sent: Monday, June 04, 2007 4:20 PM > To: Windows System Software Devs Interest List > Subject: RE: [ntdev] KMDF install error code 37 > Are the machines affected limited to a particular language? > Are they all non-english? (just a shot in the dark) --- 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
  Message 5 of 10  
04 Jun 07 21:05
ntdev member 31002
xxxxxx@microsoft.com
Join Date:
Posts To This List: 539
RE: KMDF install error code 37
John- We will be attempting to reproduce this problem here [I'm starting on it now], but since you are having trouble, we probably will, as well. Let us know if anything further comes up. I can't be certain until I truly know, but this smells enough like a bug to me that I intend to take it VERY seriously. If possible I'd like to work this between us through email rather than the NTDEV list- I'll send you a message with my address in the event you can't find mine.
  Message 6 of 10  
04 Jun 07 22:07
Kumar Rajeev
xxxxxx@microsoft.com
Join Date: 16 May 2001
Posts To This List: 19
Re: KMDF install error code 37
%windir%\wdf01005inst.log may have more information on the error. -kumar "Bob Kjelgaard" <xxxxx@microsoft.com> wrote in message news:91224@ntdev... John- We will be attempting to reproduce this problem here [I'm starting on it now], but since you are having trouble, we probably will, as well. Let us know if anything further comes up. I can't be certain until I truly know, but this smells enough like a bug to me that I intend to take it VERY seriously. If possible I'd like to work this between us through email rather than the NTDEV list- I'll send you a message with my address in the event you can't find mine.
  Message 7 of 10  
05 Jun 07 03:09
PaoloC
xxxxxx@tin.it
Join Date:
Posts To This List: 72
Re: 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 Kraft To: Windows System Software Devs Interest List 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) <no error text>. 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 --
  Message 8 of 10  
05 Jun 07 03:29
ntdev member 8437
xxxxxx@windows.microsoft.com
Join Date:
Posts To This List: 1404
RE: 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 Kraft<mailto:xxxxx@uaudio.com> To: Windows System Software Devs Interest List<mailto:xxxxx@lists.osr.com> 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=E9ration r?ussie. WdfCoInstaller: [03/28/2007 00:01.11.203] Update process returned error code :status(C0000005) <no error text>. 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 --
  Message 9 of 10  
05 Jun 07 10:55
ntdev member 31002
xxxxxx@microsoft.com
Join Date:
Posts To This List: 539
RE: KMDF install error code 37
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 Kraft<mailto:xxxxx@uaudio.com> To: Windows System Software Devs Interest List<mailto:xxxxx@lists.osr.com> 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=E9ration r?ussie. WdfCoInstaller: [03/28/2007 00:01.11.203] Update process returned error code :status(C0000005) <no error text>. 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 --
  Message 10 of 10  
05 Jun 07 11:52
ntdev member 31002
xxxxxx@microsoft.com
Join Date:
Posts To This List: 539
RE: KMDF install error code 37
OT, but embarrassing... >> WE already know some things to at least try. << Seriously, the "E" being uppercase was a typo...
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntdev list to be able to post.

All times are GMT -5. The time now is 13:50.

Contact Us - Osr Online Homepage - Top

Copyright ©2005, OSR Open Systems Resourcs, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license