Driver Problems? Questions? Issues?
Put OSR's experience to work for you! Contact us for assistance with:
  • Creating the right design for your requirements
  • Reviewing your existing driver code
  • Analyzing driver reliability/performance issues
  • Custom training mixed with consulting and focused directly on your specific areas of interest/concern.
Check us out. OSR, the Windows driver experts.

Monthly Seminars at OSR Headquarters

East Coast USA
Windows Internals and SW Drivers, Dulles (Sterling) VA, 13 November 2017

Kernel Debugging & Crash Analysis for Windows, Nashua (Amherst) NH, 4 December 2017

Writing WDF Drivers I: Core Concepts, Nashua (Amherst) NH, 8 January 2018

WDF Drivers II: Advanced Implementation Techniques, Nashua (Amherst) NH, 15 January 2018


Go Back   OSR Online Lists > ntdev
Welcome, Guest
You must login to post to this list
  Message 1 of 1  
05 Oct 17 07:45
Balaji vasudevan
xxxxxx@gmail.com
Join Date: 05 Oct 2017
Posts To This List: 5
DriverEntry and DriverUnload.

Hi All, I am working on a WDI model based driver for a SDIO wireless card. While installing the driver, DriverEntry gets called and is soon followed by a DriverUnload. There are no calls to other handlers in between. I checked the call stack at the time of unload and it is as below: 00 ffffe600`3ea6e658 fffff80b`d3ec1499 QcaWdiSdio10x64!DriverUnload 01 ffffe600`3ea6e660 fffff80b`d3ec1406 ndis!ndisMInvokeDriverUnload+0x2d 02 ffffe600`3ea6e690 fffff80b`d2dfb3db ndis!ndisMUnloadEx+0x56 03 ffffe600`3ea6e6d0 fffff802`d57c022f VerifierExt!xdv_DriverUnload_wrapper+0x7b 04 ffffe600`3ea6e700 fffff802`d57c0025 nt!IopUnloadDriver+0x1f3 05 ffffe600`3ea6e830 fffff802`d53235e2 nt!PnpUnloadAttachedDriver+0x9d 06 ffffe600`3ea6e880 fffff802`d5766d1a nt!PnpRemoveLockedDeviceNode+0x22e 07 ffffe600`3ea6e8e0 fffff802`d5766a5a nt!PnpDeleteLockedDeviceNode+0x4e 08 ffffe600`3ea6e920 fffff802`d5765acd nt!PnpDeleteLockedDeviceNodes+0xbe 09 ffffe600`3ea6e990 fffff802`d566d846 nt!PnpProcessQueryRemoveAndEject+0x339 0a ffffe600`3ea6eac0 fffff802`d5677e24 nt!PnpProcessTargetDeviceEvent+0xf2 0b ffffe600`3ea6eaf0 fffff802`d523e158 nt!PnpDeviceEventWorker+0x254 0c ffffe600`3ea6eb80 fffff802`d52dcf77 nt!ExpWorkerThread+0xd8 0d ffffe600`3ea6ec10 fffff802`d5371a06 nt!PspSystemThreadStartup+0x47 0e ffffe600`3ea6ec60 00000000`00000000 nt!KiStartSystemThread+0x1 The card is inserted at this point and sits on a PCIe to SDIO adapter. The target system being used is a 64 bit machine running 15063 build of the OS. I checked the setupapi logs and a snippet of it shows "timed out" message: !!! dvi: Timed out waiting for device post-install to complete. 13:18:59.522 ump: Server install process exited with code 0x000005b4 13:19:00.332 ump: {Plug and Play Service: Device Install exit(000005b4)} !!! ndv: Device install failed for device. !!! ndv: Error 1460: This operation returned because the timeout period expired. ndv: Installing NULL driver. ndv: Marking non-present device 'SD\VID_0271&PID_0701\5&13199BF9&0&0' for reinstall A full log of the process is pasted here: https://pastebin.com/2hcXEFBS I am not sure why PnpProcessQueryRemoveAndEject is being called. A reboot of the device seems to bring up the module just fine. Any guidance or help is welcome. Regards, Balaji.
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 02:16.


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