Device Status Code 37 (DriverEntry failure) spiteful problem.
in [Device Drivers]
|
Prev: KeQueryInterruptTime() issue
Next: NDIS Mux sample
From: SergeV on 25 Dec 2007 04:42 Hello. I just downloaded and installed drivers for SiLabs USB converter. Seamless and quiet installation ended up with Code 37 error in the DevMgr. (therefore I guess the driver is MS certified) DDK recommend in this case driver upgrade. But I have the latest available (and not too young: dated 15.10.2007) Many unistall/install/plug/unplugs did not help. Same result. I think DriverEntry error in not concerned with hardware. Moreover I know the device is OK and working (under Linux). I beleive that status=37 (CM_PROB_FAILED_DRIVER_ENTRY) is not that error code the DriverEntry normally return, huh? However I failed to find any traces of a sane and descriptive error code .... :-( Any suggestions? Thanks! Please treat this post as general question: what to do in these cases beyond what DDK suggest. I do not think this is a (pure) SiLabs problem or they soon will give me an upgrade. I hope I can do something myself (but yet don't know what :-) Fresh Setupapi.log file the last install created : <--code-- (setupapi.log) --> #I022 Found "USB\VID_10C4&PID_EA60" in D:\WINDOWS\inf\oem56.inf; Device: "Silic> #I063 Selected driver installs from section [silabser.Dev] in "d:\windows\inf\o> #I320 Class GUID of device remains: {4D36E978-E325-11CE-BFC1-08002BE10318}. #I058 Selected best compatible driver. #I124 Doing copy-only install of "USB\VID_10C4&PID_EA60\0001". #I056 Coinstallers registered. #-011 Installing section [silabser.Dev.NT.Interfaces] from "d:\windows\inf\oem5> #I054 Interfaces installed. #I123 Doing full install of "USB\VID_10C4&PID_EA60\0001". #I163 Device not started: Device has problem: 0x25: CM_PROB_FAILED_DRIVER_ENTRY. #I121 Device install of "USB\VID_10C4&PID_EA60\0001" finished successfully. <---/code--->
From: Volodymyr Shcherbyna on 26 Dec 2007 08:53 I would contact software vendor support for more details. Also, you can debug this driver using WinDbg (or SoftIce). Just put breakpoint to ZwLoadDriver and look how things go. This would not fix the problem, but you will have an idea why it fails. -- Volodymyr NG tips: http://msmvps.com/blogs/v_scherbina/pages/microsoft-newsgroups-tips.aspx "SergeV" <s_no_spam_v(a)a_ca.de_m.org> wrote in message news:%234Fe8ptRIHA.1188(a)TK2MSFTNGP04.phx.gbl... > Hello. > > I just downloaded and installed drivers for SiLabs USB converter. > Seamless and quiet installation ended up with Code 37 error in the DevMgr. > (therefore I guess the driver is MS certified) > DDK recommend in this case driver upgrade. But I have the latest available > (and not too young: dated 15.10.2007) > Many unistall/install/plug/unplugs did not help. Same result. > > I think DriverEntry error in not concerned with hardware. Moreover I know > the device is OK and working (under Linux). > I beleive that status=37 (CM_PROB_FAILED_DRIVER_ENTRY) is not that error > code the DriverEntry normally return, huh? > However I failed to find any traces of a sane and descriptive error code > ... :-( > > Any suggestions? > Thanks! > > Please treat this post as general question: what to do in these cases > beyond what DDK suggest. > I do not think this is a (pure) SiLabs problem or they soon will give me > an upgrade. > I hope I can do something myself (but yet don't know what :-) > > Fresh Setupapi.log file the last install created : > <--code-- (setupapi.log) --> > #I022 Found "USB\VID_10C4&PID_EA60" in D:\WINDOWS\inf\oem56.inf; Device: > "Silic> > #I063 Selected driver installs from section [silabser.Dev] in > "d:\windows\inf\o> > #I320 Class GUID of device remains: > {4D36E978-E325-11CE-BFC1-08002BE10318}. > #I058 Selected best compatible driver. > #I124 Doing copy-only install of "USB\VID_10C4&PID_EA60\0001". > #I056 Coinstallers registered. > #-011 Installing section [silabser.Dev.NT.Interfaces] from > "d:\windows\inf\oem5> > #I054 Interfaces installed. > #I123 Doing full install of "USB\VID_10C4&PID_EA60\0001". > #I163 Device not started: Device has problem: 0x25: > CM_PROB_FAILED_DRIVER_ENTRY. > #I121 Device install of "USB\VID_10C4&PID_EA60\0001" finished > successfully. > <---/code---> >
From: SergeV on 27 Dec 2007 02:12 "Volodymyr Shcherbyna" wrote : >I would contact software vendor support for more details. Sure I did it first. But... X-mas, probably. > Also, you can debug this driver using WinDbg (or SoftIce). Just put > breakpoint to ZwLoadDriver and look how things go. You mean Windows checked build ? Thank you, Volodymir. I'll try.
From: Volodymyr Shcherbyna on 27 Dec 2007 17:07 >> Also, you can debug this driver using WinDbg (or SoftIce). Just put >> breakpoint to ZwLoadDriver and look how things go. > > You mean Windows checked build ? No. I mean debugging faulting driver DriverEntry routine. P.S. I also hope that you do not verify (using verifier.exe) the driver, because in some cases it may fail to load due to failures in memory allocations. -- Volodymyr NG tips: http://msmvps.com/blogs/v_scherbina/pages/microsoft-newsgroups-tips.aspx "SergeV" <s_no_spam_v(a)a_ca.de_m.org> wrote in message news:u73SrfFSIHA.4272(a)TK2MSFTNGP06.phx.gbl... > > "Volodymyr Shcherbyna" wrote : >>I would contact software vendor support for more details. > > Sure I did it first. But... X-mas, probably. > > >> Also, you can debug this driver using WinDbg (or SoftIce). Just put >> breakpoint to ZwLoadDriver and look how things go. > > You mean Windows checked build ? > > > Thank you, Volodymir. I'll try. >
From: Tim Roberts on 28 Dec 2007 23:02
"Volodymyr Shcherbyna" <v_scherbina(a)online.mvps.org> wrote: > >P.S. I also hope that you do not verify (using verifier.exe) the driver, >because in some cases it may fail to load due to failures in memory >allocations. Only if you enable pool allocation failures, which you should not do except during an intentional test. I run with verifier enabled on my drivers 100% of the time. -- Tim Roberts, timr(a)probo.com Providenza & Boekelheide, Inc. |