WDK Kit 6000 for Windows Vista

TheMSsForum.com: The Microsoft Software Forum

The MSS Forum ‹ Drivers
- Archive
  - Biz
  - MCSE
  - CRM
  - Drivers
  - Framework
  - ADO
  - ASP
  - Compact
  - Forms
  - Dotnet
  - C#
  - VB
  - FontpageGen
  - Excel
  - WorkSheet
  - Exchange
  - Setup
  - Fox
  - Fontpage
  - ASP
  - IIS
  - Entourage
  - Money
  - Messanger
  - PocketPC
  - Powerpoint
  - Project
  - Publisher
  - Excel
  - VB
  - Security
  - Portal
  - Services
  - SQLServerDev
  - SVCS
  - SQLServer
  - VB
  - VC
  - MFC
  - ExcelGen

- Previous
  - 1
    - File system Driver: File Properties window problem. hello, I am developing a file system driver right now. I am successfully able to create file and directory. There is a problem after that. After creating the file when i right click on file my driver hangs, The request IRP_MN_QUERY_DIRECTORY comes repeatedly. I dont know how and why it is coming continuously? please help me to solve this problem, if you didn't understand my question completely then please ask me, thanks in advance, regards, Hitesh Tag: WDK Kit 6000 for Windows Vista Tag: 95365
  - 2
    - accessing physical memory mapped to a pci board I would like to view physical memory that is mapped to a pci board. (I am writing a driver for the board for a real-time OS and I would like to see what data is in the board's registers after a successful startup in Windows to help recreate that in the other OS.) I tried using a tool called WinIO to try to create a virtual address to that physical memory. It works for both read and write of some addresses, like 0x9FFF0. However, the resource the board uses is address at 0xE8100000 which I cannot pick up with the tool. I have confirmed that address in windows device manager and in the BAR0 entry in the table that the PCI board registers with windows. Is there some protection in Windows that I must circumvent to view that memory? I am running XP SP2. The board's driver is installed and the board is functioning properly in windows while I am trying to read the memory. I have 1 GB of physical RAM and a swap file of 1.5 GB. (the memory address that PCI board is at appears to be about 3.8 GB offset (0xE8100000)... I'm not sure why it is able to have an address that is beyond the sum of the physical and swap memory.) I appreciate any thoughts you have. Thanks, John Tag: WDK Kit 6000 for Windows Vista Tag: 95364
  - 3
    - [WIA] Minidriver (UMDF/WDM), usbscan (32/64 bit) and certification Hello, In order to use a scanner on Windows XP/2003/Vista, we can't use an UMDF driver, can we? So, we have to start from the scanner minidriver sample "wiascanr", which is a WDM driver. Is it ok for Vista? In the WIA architecture, we have to make a minidriver (user mode) but we need an USB driver (kernel mode) for instance... Is "usbscan.sys" always correct? And for a x64-based version of Vista? Finally, in order to have a "Microsoft certification", are "wiascanr" and "usbscan" usable? Thank you very much!! Tag: WDK Kit 6000 for Windows Vista Tag: 95362
  - 4
    - How to write a virtual com port driver on XP or later? I would write a virtual com port driver on XP or later. Is there any sample code for this? or What should be the start point to study com port driver? Best Regards Jack Huang Tag: WDK Kit 6000 for Windows Vista Tag: 95359
  - 5
    - Developing a device driver for a WiFi device Hi... I need to interface a WiFi device that defines its own protocols with a Windows PC. I've done some Googling and a found a set of Windows WiFi APIs that I think I can use. Do I need to build a device driver? ( The device will never interact directly with the kernel ) And what would be best IDE to use? Thanks in advance... Tag: WDK Kit 6000 for Windows Vista Tag: 95358
  - 6
    - Job opportunities Hi everyone, My employer has opened or is about to open several positions. Four of them require skills and proficiency in Windows driver writing, especially in Network and Storage drivers. Thus there are great chances that the potential candidates are readers of this newsgroup (and a few other ones. I am cross-posting). I know this group is not made for that purpose and I apologize in advance to those of you who are not interested (sorry for the cross postings too, but the skills we are searching are quite hard to find, I want to maximize our chances to find the right future colleagues). Two positions are opened in Paris, France and two will be opened in the USA (east coast) very soon. In each location there is one Senior Engineer position and one Developer-Engineer position. Contact me in private (jobs at windowsdiskless dot com) for more details (this is a forwarded e-mail address and I will receive the e-mails sent to this address). This is a real opportunity, not a fake! Thanks in advance -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ Tag: WDK Kit 6000 for Windows Vista Tag: 95355
  - 7
    - optimazation options on free build environment by default Hi all. I have a question about free build environment on WDK(version 6000). On x86 Free Build Environment, MSC_OPTIMIZATION defaults to /0xs. I understand that /Oxs implies the use of the Frame Pointer Omission (/Oy) option. but /Oy- is appointed in compile. This cause is so that it is written as the following in "i386mk.inc" . DBGFLAGS=$(DBGFLAGS) /Oy- CFLAGS=$(386_FLAGS) $(NT386FLAGS) $(STDFLAGS) $(DBGFLAGS) $(PERFFLAGS) $(USER_C_FLAGS) Why will /Oy- be set ? Will there be any important meaning in setting /Oy- ? Tag: WDK Kit 6000 for Windows Vista Tag: 95350
  - 8
    - windows ce 5.0 intermediate driver hi all, i'm new to windows ce... And i'm using windows ce 5.0 platform builder.... could any body tell me,how to install the intermediate driver using windows ce 5.0 platform builder? thanQ all Tag: WDK Kit 6000 for Windows Vista Tag: 95349
  - 9
    - WDF DMA use Hi. I'm designing a device driver that interacts with a master PCI DSP. I have read the documentation regarding the DMA abstraction and have some questions. The way that the DMA will work is packet-based mode, and packets will be 4KByte. Packets will be allocated by a user mode process, and an MDL will be built to describe this packet. Although the packet size is equal to a page size (32 bit OS) it might be fragment to several locations on the physical memory. A scatter\gather list will hold the description of physical address per fragment. The questions are: 1. What is the size of the smallest fragment? Will it be a byte? 1a. Can I assume what will be the number of fregamnts for 4096 bytes packet (reminder - it was allocates in a user mode application)? 2. Can I set the number of fragments and size? 3. If I set the trasfer length to be 4096 bytes and my packet size is 4096 bytes will a transaction contain one transfer? 4. If the DSP interrupts when a trasfer is completed, however it interrupts in other occasions, can the driver tell the difference? Can I write some logic in the DPC (ISR of course cannot tell the difference) in order to destingwish between two "reasons" of DSP interrupt? 5. Will a 4096 bytes Thank you in advanced for your help! Tag: WDK Kit 6000 for Windows Vista Tag: 95333
  - 10
    - How to progamatically do a USB "soft eject" like explorer Windows explorer allows for a soft eject feature for USB drives that I would like to recreate in my program. This is useful for USB drives where a compact flash is inserted and removed but the USB drive remains connected to the PC. Does anyone know what functions are involved to accomplish this? I have seen code which accomplishes the hard eject (removing the entire USB device) but not the soft eject which only flushes the cache. Thanks Tag: WDK Kit 6000 for Windows Vista Tag: 95324
  - 11
    - Re: No UINumber being assigned to PCI attached MPS devices in Vista Eliyas, The UINumber is correctly reported on XP. The same computer, BIOS and adapters cards are used in both instances but with different boot drives. The system uses PCI and PCI-X buses. Should there be a difference between XP and Vista? Seems like a bug... We use the UINumber to show the physical position of Adapter cards in systems we ship out. The user can then distinguish between multiple Adapter cards installed in the same system, configure the cards, attach cables, etc.. Needless to say, we will continue to ship our product with XP until we can get everything working properly and with the same performance. Thanks for your response, Todd Lange On May 29, 8:15 pm, "Eliyas Yakub [MSFT]" <eliy...@online.microsoft.com> wrote: > What are you trying to do with theUINumber? > > According to PCI folks, starting Vista, this information is reported if the > ACPI firmware includes the UI information. > > Windows Vista populates the value forUINumberin the DEVICE_CAPABILITIES > structure using one of the two methods based on the device types > > For PCI Express devices, a UI number is obtained by reading the Physical > Slot Number value in the Slot Capabilities register. This is only when the > PCI root bus implements an _OSC method and the firmware hands control for > express features to the operating system using this method. > > For non-express devices, the PCI driver populates the UI number value from > the parent. > It is perfectly legit for the BIOS/firmware to provide UI number info (using > _SUN method for instance). In this case, the value from this method > over-writes the value populated by the PCI bus driver. > > -Eliyas > > <toddlan...@yahoo.com> wrote in message > > news:1180470255.199597.299690@m36g2000hse.googlegroups.com... > > > On May 25, 12:13 pm, "Del Fredricks" > > <del.fredri...@ms.discussions.com> wrote: > >> I have an MPS driver which relied upon theUINumberto identify which > >> attached device was being addressed. Past OS's apparently assigned this > >> attribute the PCI slot location of the MPS board. However, it appears as > >> though Vista no longer performs this assignment. Is the a different > >> mechanism that can be used which works in 2000, Server 2003, and XP? > > > Hi Del, > > > I've run across the same problem in Vista. We have an application > > that scans the PCI bus and gets device id and physical slot number > > (UINumber). I have tried three different methods of getting the > >UINumber, but each method has failed. > > > I have tried the following: > > > 1) Calling IoGetDeviceProperty() with DevicePropertyUINumber as a > > parameter. This fails with error code 0xC0000034 > > (STATUS_OBJECT_NAME_NOT_FOUND). > > > 2) Using IRP IRP_MN_QUERY_CAPABILITIES. This returns -1 in the > >UINumberitem of the DEVICE_CAPABILITIES structure. > > > 3) Calling SetupDiGetDeviceRegistryProperty() with SPDRP_UI_NUMBER (I > > also tried SPDRP_UI_NUMBER_DESC_FORMAT) as an input parameter. This > > function returns FALSE with LastError set to (ERROR_INVALID_DATA). > > > There is no mention that this is not supported in Vista in the > > documentation. It appears to be a Vista bug. > > > If you find out another method of getting this information, please let > > me know. > > > Thanks, > > > Todd Lange Tag: WDK Kit 6000 for Windows Vista Tag: 95323
  - 12
    - Question regarding COM ports I'm trying to use a call to: l = ComDBGetCurrentPortUsage( HComDB, bufBits, 256, CDB_REPORT_BITS, pMaxPortsReported ); to determine if a USB serial port device is plugged in. Before plugging in the device, the device manager reports that I have 2 COM ports and 2 printer ports. After plugging in the device it reports 3 COM ports and 2 printer ports. However, before plugging in the device, a call to ComDBGetCurrentPortUsage fills in the bit array with 05 00 00... and after the call it still returns 05 00 00... (for COM 1 and COM 3) How can I determine if the USB COM device has been plugged in and if it has, what number has been assigned to it? It returns these values even if I powered up with the device unplugged. The call to ComDBGetCurrentPortUsage is in a dll written in 'C++'. The call to the dll is from a routine written in Visual Basic. Thanks for your help -- Regards, Dean Tag: WDK Kit 6000 for Windows Vista Tag: 95315
  - 13
    - WdfUsbTargetDeviceSendControlTransferSynchronously from TimerExpired function causes access violation I'm currently writing a KMDF based driver that will upon insertion of a USB device, download firmware to it and then reset the USB bus causing re-enumeration. I'm not entirely clear on the best way to implement this, my current plan is as follows: * From EvtPrepareHardware, I start a timer which causes TimerExpired to be called * In TimerExpired, I do a USB control transfer to check device state, upload a block of data and then set another timer. I thought this should be working, but I'm running into an access violation somewhere in the USB stack, and I'm not sure how to debug this further. When I call this function from EvtPrepareHardware itself, everything works fine, but calling it from TimerExpired causes the access violation. The call stack at that moment is as follows: (using KMDF 1.5) nt!DbgBreakPoint Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+0x186 mydriver!WdfUsbTargetDeviceSendControlTransferSynchronously+0x29 mydriver!TimerExpired Now I have two questions: 1. Should I be using this design or would you suggest a different way? (the protocol requires me to sleep every now and then, and since you can't just use Sleep() I decided to go for the design as described). 2. What could be causing the access violation? Is it not allowed to call USB stack functions from TimerExpired? My TimerExpired function looks something like this: VOID TimerExpired(IN WDFTIMER Timer) { NTSTATUS status; WDFDEVICE Device; PDEVICE_CONTEXT pDeviceContext; WDF_USB_CONTROL_SETUP_PACKET thePacket; BYTE buf[16]; DWORD len, nbytes; WDF_MEMORY_DESCRIPTOR memoryDescriptor; Device = WdfTimerGetParentObject(Timer); pDeviceContext = GetDeviceContext(Device); WDF_USB_CONTROL_SETUP_PACKET_INIT_CLASS( &thePacket, BmRequestDeviceToHost, BmRequestToInterface, 0x05, 0, 0 ); pDeviceContext = GetDeviceContext(Device); WDF_MEMORY_DESCRIPTOR_INIT_BUFFER(&memoryDescriptor, (PVOID) buf, *len); status = WdfUsbTargetDeviceSendControlTransferSynchronously( pDeviceContext- >WdfUsbTargetDevice, WDF_NO_HANDLE, // Optional WDFREQUEST NULL, // PWDF_REQUEST_SEND_OPTIONS &thePacket, &memoryDescriptor, // MemoryDescriptor &nbytes); // BytesTransferred } Tag: WDK Kit 6000 for Windows Vista Tag: 95314
  - 14
    - [problem in installing the KMDF sample driver in windows XP] I am having a problem installing the KMDF sample driver in windows XP operating system. i am using the WinDDK/6001/ windows XP x86 checked build environment for building the driver sys file. it will create the automatic inf file . this inf file has Coinstaller.Section which is specifies the WdfCoinstaller01007.dll file. WDK provides this file in WDK/redist directory . i copied .inf file .sys file and WdfCoinstaller010007.dll file in one directory . using the control panel add new hardware i have installed the driver. but this is not installed the driver properly. it has given this error message: "The specified resource type cannot be found in the image file". if any body have idea to solve this error give suggestion: thanks is advance. sulibsp Tag: WDK Kit 6000 for Windows Vista Tag: 95313
  - 15
    - Can we use cpp to write WDM driver ? Hi I found that some WDM audio driver source use cpp files , so can DDK use all C++ class and library ? Can we use other languages (like VB C# Java) to develop Microsoft drivers ? Thank you Tag: WDK Kit 6000 for Windows Vista Tag: 95311
  - 16
    - [KMDF] General question: test of a 64 bit driver Is it really impossible to install uncertified driver on a 64 bit Vista ? If yes, how to test the driver ? ^^ Thank you! Tag: WDK Kit 6000 for Windows Vista Tag: 95306
  - 17
    - KMDF driver for XP Hello All, I am using Windows XP SP1. I have downloaded the WDK 6001 with KMDF version 1.7. when I tried to load the sample driver "echo" or "toaster", the following error message is generated "The specified resource name cannot be found in the image file" Release notes says that, the sample drivers provided with KMDF 1.7 can run on Windows Server 2003 / Vista. Even a simple driver with DriverEntry with only KdPrint() on KMDF with CoInstaller of 1.7, same error message is coming. Please let me know how to solve this problem. Also, whether can I use this WDK / KMDF version for XP driver development? -Kans. Tag: WDK Kit 6000 for Windows Vista Tag: 95305
  - 18
    - How to get the packet of KS_TVTUNER_CHANGE_INFO in Analog tuner Dr Hello: I am studying analog tuner driver. I start from DDK Sample "anlgtuner". In graphedt, it can play. When i want to change the channel, it stops work with error code "Incorrect function 0x80070001". It seems that the function to receive KS_TVTUNER_CHANGE_INFO is missed in driver from DDK doc: when the tuner switches from one channel to another, A minidriver must propagate a tuning packet from its tuner filter, through the crossbar filter, and then into the analog video input pin on its capture filter. This packet is only available in user mode until it reaches the capture filter. The minidriver receives this tuning packet as a KS_TVTUNER_CHANGE_INFO structure on the analog video input pin of the minidriverâ??s capture filter. I add AVStrMiniPinProcess callback routine in KSPIN_DISPATCH of the video input pin of the capture filter. But this routine was never hit and error still occured. So how to get the packet of KS_TVTUNER_CHANGE_INFO in Analog tuner Driver? Could somebody point me out? Thanks Max Tag: WDK Kit 6000 for Windows Vista Tag: 95304
  - 19
    - code optimization hurt my driver Once built with the default optimization in free build, my driver cannot ackledge the interrupt flags (writing back to clear). Once I added /Od and /Oi, the driver works fine again. Anyone has suggestion where should I check for such kind of problem ? Thanks -Gary Tag: WDK Kit 6000 for Windows Vista Tag: 95291
  - 20
    - avstream sample freezes system hello, i'm already wrote about this problem with no reply. building avssamp example and using it with some client app freeze xp and vista (this app is works well with real cameras). i can't find a way to figure out what is the problem with, because bsod is not happening, just mouse cursor is freezes and system is stall :( no error logs found on reboot. -Andrey Tag: WDK Kit 6000 for Windows Vista Tag: 95288
  - 21
    - make USB hub easily identifiable Some quick background: We are making a set of USB medical data collection devices. Most commonly, they will be packaged together and permanently connected to a USB hub in the same case, however they will also be available as independent devices. I need to know whether a unified device is connected or a bunch of individual modules, among other things the user should be informed if one of the devices fails in the unified collection. The hub chip uses an EEPROM that specifies the VID, PID, and device number. How can I use the standard USB hub driver for our device but tag it in a way I can detect while enumerating devices (using e.g. SetupDiCreateDeviceInfoList, SetupDiGetDeviceInterfaceDetail)? It would be best if I can control the name of the device which appears in Device Manager after the driver loads, but as long as I can distinguish our hub+devices group from a device attached to a standard hub it will be fine. Should I put in a different VID/PID pair (we can get numbers assigned) and write an INF that loads the Microsoft driver? Where would I find an example of that? Or would it be better to leave the VID and PID alone and change the device number? Any advice would be appreciated. Tag: WDK Kit 6000 for Windows Vista Tag: 95268
  - 22
    - IOCTL_USB_USER_REQUEST Hi, I wish to use IOCTL_USB_USER_REQUEST to access the raw usb device from my application. Could somebody throw some light on IOCTL_USB_USER_REQUEST.On which Windows OS it is officially supported? what are the prerequisites to use them ? My target OS range from windows 2000 to vista. Docs mention that "This request is not enabled unless the root hub is disabled." what exactly does that mean? Thanks Subodh Tag: WDK Kit 6000 for Windows Vista Tag: 95255
  - 23
    - USB CDC driver Hi All, I am developing USB CDC driver for windows CE. I am using following functions for registry manupulations. RegisterClientSettings UnRegisterClientSettings OpenClientRegistryKey RegisterClientDriverID So using those functions I can access the registry. I need to get the string path of the handle returned by OpenClientRegistryKey function. This is because I need to pass it to ActivateDevice function. So 1. How can I get string registry path from handle of the registry ? 2. I call UnRegisterClientSettings function inside USBDeviceAttach function. But it fail is there any reason ? Please help me. Sira Buwa. Tag: WDK Kit 6000 for Windows Vista Tag: 95249
  - 24
    - USB CDC driver Hi All, I am developing USB CDC driver for windows CE. I am using following functions for registry manupulations. RegisterClientSettings UnRegisterClientSettings OpenClientRegistryKey RegisterClientDriverID So using those functions I can access the registry. I need to get the string path of the handle returned by OpenClientRegistryKey function. This is because I need to pass it to ActivateDevice function. So 1. How can I get string registry path from handle of the registry ? 2. I call UnRegisterClientSettings function inside USBDeviceAttach function. But it fail is there any reason ? Please help me. Sira Buwa. Tag: WDK Kit 6000 for Windows Vista Tag: 95248
  - 25
    - WdfDeviceCreateDeviceInterface Again Hello All, I have posted a query regarding failure of WdfDeviceCreateDeviceInterface() in my driver with error code 0xC0000010. As suggested i have logged the message using !wdflogdump but im not able to trace the reason for the failure from the log. Can anyone look at the log and let me know if im missing anything. As i told earlier the same driver works fine for Windows XP but fails for Vista. Here is the framework log. Please look at the line number 49 below where the failure occured Thank You. Regards, Tim Trace format prefix is: %7!u!: %!FUNC! - TMF file used for formatting IFR log is: D:\WINDDK\6000\tools\tracing \i386\wdf01005.tmf Log at 82e59000 Gather log: Please wait, this may take a moment (reading 4032 bytes). % read so far ... 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 110, 120, 130, 140, 150, 160, 170, 180, 190, 100 There are 201 log entries --- start of log --- 3: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering PnP State WdfDevStatePnpInitStarting from WdfDevStatePnpInit 4: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering PnP State WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting 5: FxIoTarget::SubmitLocked - ignoring WDFIOTARGET 74C037B0 state, sending WDFREQUEST 847F7698, state 1 6: FxIoTarget::SubmitLocked - ignoring WDFIOTARGET 58BEA148 state, sending WDFREQUEST 847F7600, state 1 7: FxIoTarget::SubmitLocked - ignoring WDFIOTARGET 5D2B9798 state, sending WDFREQUEST 847F7628, state 1 8: FxIoTarget::SubmitLocked - ignoring WDFIOTARGET 7C806178 state, sending WDFREQUEST 847F7678, state 1 9: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpInit from WdfDevStatePnpObjectCreated 10: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering power policy state WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated 11: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7D03AFE8 ! devobj 0x8370DAC0 entering power idle state FxIdleStarted from FxIdleStopped 12: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerStartingCheckDeviceType from WdfDevStatePowerObjectCreated 13: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerD0Starting from WdfDevStatePowerStartingCheckDeviceType 14: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerD0StartingConnectInterrupt from WdfDevStatePowerD0Starting 15: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerD0StartingDmaEnable from WdfDevStatePowerD0StartingConnectInterrupt 16: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerD0StartingStartSelfManagedIo from WdfDevStatePowerD0StartingDmaEnable 17: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7D03AFE8 ! devobj 0x8370DAC0 entering power idle state FxIdleStartedPowerUp from FxIdleStarted 18: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7D03AFE8 ! devobj 0x8370DAC0 entering power idle state FxIdleDisabled from FxIdleStartedPowerUp 19: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerDecideD0State from WdfDevStatePowerD0StartingStartSelfManagedIo 20: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerD0 from WdfDevStatePowerDecideD0State 21: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering power policy state WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarting 22: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering power policy state WdfDevStatePwrPolStartingDecideS0Wake from WdfDevStatePwrPolStartingSucceeded 23: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering power policy state WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake 24: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7D03AFE8 ! devobj 0x8370DAC0 entering power idle state FxIdleDisabled from FxIdleDisabled 25: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering PnP State WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable 26: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering PnP State WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces 27: FxChildList::ProcessBusRelations - PDO created successfully, WDFDEVICE 58BEB288 !devobj A2DABA50 28: imp_WdfRegistryQueryString - WDFKEY 74D85E88, QueryPartial failed, 0xc0000034(STATUS_OBJECT_NAME_NOT_FOUND) 29: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpInit from WdfDevStatePnpObjectCreated 30: FxPkgPnp::Dispatch - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60, IRP_MJ_PNP, 0x00000000(IRP_MN_START_DEVICE) IRP 0xA2DF3810 31: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpInitStarting from WdfDevStatePnpInit 32: FxPkgPnp::Dispatch - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50, IRP_MJ_PNP, 0x00000000(IRP_MN_START_DEVICE) IRP 0xA2DF3810 33: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpInitStarting from WdfDevStatePnpInit 34: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting 35: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated 36: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerStartingCheckDeviceType from WdfDevStatePowerObjectCreated 37: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerStartingChild from WdfDevStatePowerStartingCheckDeviceType 38: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerD0Starting from WdfDevStatePowerStartingChild 39: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerD0StartingConnectInterrupt from WdfDevStatePowerD0Starting 40: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerD0StartingDmaEnable from WdfDevStatePowerD0StartingConnectInterrupt 41: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerD0StartingStartSelfManagedIo from WdfDevStatePowerD0StartingDmaEnable 42: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerDecideD0State from WdfDevStatePowerD0StartingStartSelfManagedIo 43: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerD0BusWakeOwner from WdfDevStatePowerDecideD0State 44: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStarted from WdfDevStatePwrPolStarting 45: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarted 46: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable 47: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces 48: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting 49: FxPkgPnp::PnpPrepareHardware - EvtDevicePrepareHardware failed 0xc0000010(STATUS_INVALID_DEVICE_REQUEST) 50: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpFailedOwnHardware from WdfDevStatePnpHardwareAvailable 51: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpFailed from WdfDevStatePnpFailedOwnHardware 52: FxIoQueue::QueuePurge - All WDFQUEUE 0x5D232390 requests cancelled 53: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x5D232390 54: FxIoQueue::QueuePurge - All WDFQUEUE 0x5D20A4D0 requests cancelled 55: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x5D20A4D0 56: FxIoQueue::QueuePurge - All WDFQUEUE 0x7D0381E8 requests cancelled 57: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7D0381E8 58: FxIoQueue::QueuePurge - All WDFQUEUE 0x7C9151E8 requests cancelled 59: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7C9151E8 60: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD7E778 requests cancelled 61: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD7E778 62: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpFailedWaitForRemove from WdfDevStatePnpFailed 63: FxPkgPnp::Dispatch - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60, IRP_MJ_PNP, 0x00000002(IRP_MN_REMOVE_DEVICE) IRP 0xA2DF3810 64: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpRemoved from WdfDevStatePnpFailedWaitForRemove 65: FxChildList::NotifyDeviceRemove - WDFCHILDLIST 5D310478: removing children 66: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpFdoRemoved from WdfDevStatePnpRemoved 67: FxIoQueue::QueuePurge - All WDFQUEUE 0x7D189C10 requests cancelled 68: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7D189C10 69: FxIoQueue::Dispose - Purging WDFQUEUE 0x7D189C10 synchronously 70: FxIoQueue::QueuePurge - All WDFQUEUE 0x7D189C10 requests cancelled 71: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7D189C10 72: FxIoQueue::Dispose - Purging WDFQUEUE 0x5D232390 synchronously 73: FxIoQueue::QueuePurge - All WDFQUEUE 0x5D232390 requests cancelled 74: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x5D232390 75: FxIoQueue::Dispose - Purging WDFQUEUE 0x5D20A4D0 synchronously 76: FxIoQueue::QueuePurge - All WDFQUEUE 0x5D20A4D0 requests cancelled 77: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x5D20A4D0 78: FxIoQueue::Dispose - Purging WDFQUEUE 0x7D0381E8 synchronously 79: FxIoQueue::QueuePurge - All WDFQUEUE 0x7D0381E8 requests cancelled 80: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7D0381E8 81: FxIoQueue::Dispose - Purging WDFQUEUE 0x7C9151E8 synchronously 82: FxIoQueue::QueuePurge - All WDFQUEUE 0x7C9151E8 requests cancelled 83: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7C9151E8 84: FxIoQueue::Dispose - Purging WDFQUEUE 0x7CD7E778 synchronously 85: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD7E778 requests cancelled 86: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD7E778 87: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpFinal from WdfDevStatePnpFdoRemoved 88: FxPkgPnp::_PnpRemoveDevice - WDFDEVICE 74D3D4D8, !devobj A2DD8B60 waiting for remove event to finish processing 89: FxPkgPnp::Dispatch - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50, IRP_MJ_PNP, 0x00000002(IRP_MN_REMOVE_DEVICE) IRP 0xA2DF3810 90: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpStartedRemoving from WdfDevStatePnpStarted 91: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStopping from WdfDevStatePwrPolStartingSucceeded 92: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerGotoD3Stopped from WdfDevStatePowerD0BusWakeOwner 93: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerStopped from WdfDevStatePowerGotoD3Stopped 94: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStoppingWaitingForImplicitPowerDown from WdfDevStatePwrPolStopping 95: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStoppingSendStatus from WdfDevStatePwrPolStoppingWaitingForImplicitPowerDown 96: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStopped from WdfDevStatePwrPolStoppingSendStatus 97: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpRemovingDisableInterfaces from WdfDevStatePnpStartedRemoving 98: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpRemoved from WdfDevStatePnpRemovingDisableInterfaces 99: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpCheckForDevicePresence from WdfDevStatePnpRemoved 100: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpRemovedPdoWait from WdfDevStatePnpCheckForDevicePresence 101: FxPkgPnp::_PnpRemoveDevice - WDFDEVICE 58BEB288, !devobj A2DABA50 waiting for remove event to finish processing 102: FxDevice::Destroy - Deleting !devobj A2DD8B60, WDFDEVICE 74D3D4D8, attached to !devobj A2DABA50 2: FxPkgPnp::Dispatch - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0, IRP_MJ_PNP, 0x00000000(IRP_MN_START_DEVICE) IRP 0xA2DCDC48 3: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering PnP State WdfDevStatePnpInitStarting from WdfDevStatePnpInit 4: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering PnP State WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting 5: FxIoTarget::SubmitLocked - ignoring WDFIOTARGET 74C037B0 state, sending WDFREQUEST 847F7698, state 1 6: FxIoTarget::SubmitLocked - ignoring WDFIOTARGET 58BEA148 state, sending WDFREQUEST 847F7600, state 1 7: FxIoTarget::SubmitLocked - ignoring WDFIOTARGET 5D2B9798 state, sending WDFREQUEST 847F7628, state 1 8: FxIoTarget::SubmitLocked - ignoring WDFIOTARGET 7C806178 state, sending WDFREQUEST 847F7678, state 1 9: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpInit from WdfDevStatePnpObjectCreated 10: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering power policy state WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated 11: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7D03AFE8 ! devobj 0x8370DAC0 entering power idle state FxIdleStarted from FxIdleStopped 12: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerStartingCheckDeviceType from WdfDevStatePowerObjectCreated 13: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerD0Starting from WdfDevStatePowerStartingCheckDeviceType 14: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerD0StartingConnectInterrupt from WdfDevStatePowerD0Starting 15: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerD0StartingDmaEnable from WdfDevStatePowerD0StartingConnectInterrupt 16: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerD0StartingStartSelfManagedIo from WdfDevStatePowerD0StartingDmaEnable 17: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7D03AFE8 ! devobj 0x8370DAC0 entering power idle state FxIdleStartedPowerUp from FxIdleStarted 18: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7D03AFE8 ! devobj 0x8370DAC0 entering power idle state FxIdleDisabled from FxIdleStartedPowerUp 19: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerDecideD0State from WdfDevStatePowerD0StartingStartSelfManagedIo 20: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering Power State WdfDevStatePowerD0 from WdfDevStatePowerDecideD0State 21: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering power policy state WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarting 22: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering power policy state WdfDevStatePwrPolStartingDecideS0Wake from WdfDevStatePwrPolStartingSucceeded 23: FxPkgPnp::PowerPolicyEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering power policy state WdfDevStatePwrPolStarted from WdfDevStatePwrPolStartingDecideS0Wake 24: FxPowerIdleMachine::ProcessEventLocked - WDFDEVICE 0x7D03AFE8 ! devobj 0x8370DAC0 entering power idle state FxIdleDisabled from FxIdleDisabled 25: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering PnP State WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable 26: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x7D03AFE8 !devobj 0x8370DAC0 entering PnP State WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces 27: FxChildList::ProcessBusRelations - PDO created successfully, WDFDEVICE 58BEB288 !devobj A2DABA50 28: imp_WdfRegistryQueryString - WDFKEY 74D85E88, QueryPartial failed, 0xc0000034(STATUS_OBJECT_NAME_NOT_FOUND) 29: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpInit from WdfDevStatePnpObjectCreated 30: FxPkgPnp::Dispatch - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60, IRP_MJ_PNP, 0x00000000(IRP_MN_START_DEVICE) IRP 0xA2DF3810 31: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpInitStarting from WdfDevStatePnpInit 32: FxPkgPnp::Dispatch - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50, IRP_MJ_PNP, 0x00000000(IRP_MN_START_DEVICE) IRP 0xA2DF3810 33: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpInitStarting from WdfDevStatePnpInit 34: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting 35: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStarting from WdfDevStatePwrPolObjectCreated 36: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerStartingCheckDeviceType from WdfDevStatePowerObjectCreated 37: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerStartingChild from WdfDevStatePowerStartingCheckDeviceType 38: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerD0Starting from WdfDevStatePowerStartingChild 39: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerD0StartingConnectInterrupt from WdfDevStatePowerD0Starting 40: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerD0StartingDmaEnable from WdfDevStatePowerD0StartingConnectInterrupt 41: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerD0StartingStartSelfManagedIo from WdfDevStatePowerD0StartingDmaEnable 42: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerDecideD0State from WdfDevStatePowerD0StartingStartSelfManagedIo 43: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerD0BusWakeOwner from WdfDevStatePowerDecideD0State 44: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStarted from WdfDevStatePwrPolStarting 45: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStartingSucceeded from WdfDevStatePwrPolStarted 46: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpEnableInterfaces from WdfDevStatePnpHardwareAvailable 47: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpStarted from WdfDevStatePnpEnableInterfaces 48: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpHardwareAvailable from WdfDevStatePnpInitStarting 49: FxPkgPnp::PnpPrepareHardware - EvtDevicePrepareHardware failed 0xc0000010(STATUS_INVALID_DEVICE_REQUEST) 50: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpFailedOwnHardware from WdfDevStatePnpHardwareAvailable 51: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpFailed from WdfDevStatePnpFailedOwnHardware 52: FxIoQueue::QueuePurge - All WDFQUEUE 0x5D232390 requests cancelled 53: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x5D232390 54: FxIoQueue::QueuePurge - All WDFQUEUE 0x5D20A4D0 requests cancelled 55: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x5D20A4D0 56: FxIoQueue::QueuePurge - All WDFQUEUE 0x7D0381E8 requests cancelled 57: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7D0381E8 58: FxIoQueue::QueuePurge - All WDFQUEUE 0x7C9151E8 requests cancelled 59: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7C9151E8 60: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD7E778 requests cancelled 61: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD7E778 62: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpFailedWaitForRemove from WdfDevStatePnpFailed 63: FxPkgPnp::Dispatch - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60, IRP_MJ_PNP, 0x00000002(IRP_MN_REMOVE_DEVICE) IRP 0xA2DF3810 64: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpRemoved from WdfDevStatePnpFailedWaitForRemove 65: FxChildList::NotifyDeviceRemove - WDFCHILDLIST 5D310478: removing children 66: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpFdoRemoved from WdfDevStatePnpRemoved 67: FxIoQueue::QueuePurge - All WDFQUEUE 0x7D189C10 requests cancelled 68: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7D189C10 69: FxIoQueue::Dispose - Purging WDFQUEUE 0x7D189C10 synchronously 70: FxIoQueue::QueuePurge - All WDFQUEUE 0x7D189C10 requests cancelled 71: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7D189C10 72: FxIoQueue::Dispose - Purging WDFQUEUE 0x5D232390 synchronously 73: FxIoQueue::QueuePurge - All WDFQUEUE 0x5D232390 requests cancelled 74: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x5D232390 75: FxIoQueue::Dispose - Purging WDFQUEUE 0x5D20A4D0 synchronously 76: FxIoQueue::QueuePurge - All WDFQUEUE 0x5D20A4D0 requests cancelled 77: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x5D20A4D0 78: FxIoQueue::Dispose - Purging WDFQUEUE 0x7D0381E8 synchronously 79: FxIoQueue::QueuePurge - All WDFQUEUE 0x7D0381E8 requests cancelled 80: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7D0381E8 81: FxIoQueue::Dispose - Purging WDFQUEUE 0x7C9151E8 synchronously 82: FxIoQueue::QueuePurge - All WDFQUEUE 0x7C9151E8 requests cancelled 83: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7C9151E8 84: FxIoQueue::Dispose - Purging WDFQUEUE 0x7CD7E778 synchronously 85: FxIoQueue::QueuePurge - All WDFQUEUE 0x7CD7E778 requests cancelled 86: FxIoQueue::QueuePurge - All driver cancellable requests cancelled in WDFQUEUE 0x7CD7E778 87: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x74D3D4D8 !devobj 0xA2DD8B60 entering PnP State WdfDevStatePnpFinal from WdfDevStatePnpFdoRemoved 88: FxPkgPnp::_PnpRemoveDevice - WDFDEVICE 74D3D4D8, !devobj A2DD8B60 waiting for remove event to finish processing 89: FxPkgPnp::Dispatch - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50, IRP_MJ_PNP, 0x00000002(IRP_MN_REMOVE_DEVICE) IRP 0xA2DF3810 90: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpStartedRemoving from WdfDevStatePnpStarted 91: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStopping from WdfDevStatePwrPolStartingSucceeded 92: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerGotoD3Stopped from WdfDevStatePowerD0BusWakeOwner 93: FxPkgPnp::PowerEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering Power State WdfDevStatePowerStopped from WdfDevStatePowerGotoD3Stopped 94: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStoppingWaitingForImplicitPowerDown from WdfDevStatePwrPolStopping 95: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStoppingSendStatus from WdfDevStatePwrPolStoppingWaitingForImplicitPowerDown 96: FxPkgPnp::NotPowerPolicyOwnerEnterNewState - WDFDEVICE 0x58BEB288 ! devobj 0xA2DABA50 entering not power policy owner state WdfDevStatePwrPolStopped from WdfDevStatePwrPolStoppingSendStatus 97: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpRemovingDisableInterfaces from WdfDevStatePnpStartedRemoving 98: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpRemoved from WdfDevStatePnpRemovingDisableInterfaces 99: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpCheckForDevicePresence from WdfDevStatePnpRemoved 100: FxPkgPnp::PnpEnterNewState - WDFDEVICE 0x58BEB288 !devobj 0xA2DABA50 entering PnP State WdfDevStatePnpRemovedPdoWait from WdfDevStatePnpCheckForDevicePresence 101: FxPkgPnp::_PnpRemoveDevice - WDFDEVICE 58BEB288, !devobj A2DABA50 waiting for remove event to finish processing 102: FxDevice::Destroy - Deleting !devobj A2DD8B60, WDFDEVICE 74D3D4D8, attached to !devobj A2DABA50 ---- end of log ---- Tag: WDK Kit 6000 for Windows Vista Tag: 95247
- Next
  - 1
    - ndis 5.0 intermediate driver hi all, i'm working on ndis 5.0 intermediate driver. Please tell me is there any way to originate the packets from intermediate driver,not from the upper protocol driver.If it is there, what is process to allocate packets and send it lower drivers? thanQ all. Tag: WDK Kit 6000 for Windows Vista Tag: 95243
  - 2
    - Accessing the routing table from a protocol driver in kernel mode Is there a way to access the tcp/ip routing table from a kernel mode protocol driver? If not, is the only way to get the routing table data down to my protocol driver via IOCTLs from an app in user mode? Regards, Jess Howe Tag: WDK Kit 6000 for Windows Vista Tag: 95241
  - 3
    - IOCTL handling in vista hi all! I am writing sample wdf driver for learning purpose . my user mode applicaton is not at all getting data through IOCTl's . can any one analyse the code and tell me the error ! my driver code is NTSTATUS DriverEntry( IN PDRIVER_OBJECT DriverObject, IN PUNICODE_STRING RegistryPath ) { NTSTATUS NtStatus = STATUS_SUCCESS; WDF_DRIVER_CONFIG WdfConfig; WDFDRIVER hDriver; PWDFDEVICE_INIT pInit = NULL; KdPrint(("LoopBack Driver Sample - Driver Framework Edition.\n")); KdPrint(("Built %s %s\n", __DATE__, __TIME__)); WDF_DRIVER_CONFIG_INIT ( &WdfConfig, WDF_NO_EVENT_CALLBACK ); WdfConfig.DriverInitFlags |= WdfDriverInitNonPnpDriver; WdfConfig.EvtDriverUnload = LbkEvtDriverUnload; NtStatus = WdfDriverCreate( DriverObject, RegistryPath, WDF_NO_OBJECT_ATTRIBUTES, &WdfConfig, &hDriver ); if( !NT_SUCCESS( NtStatus )) { KdPrint( ("WdfDriverCreate failed with status 0x%x\n", NtStatus)); } pInit = WdfControlDeviceInitAllocate( hDriver, //SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_R_RES_R &SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_RW_RES_R ); if (pInit == NULL) { NtStatus = STATUS_INSUFFICIENT_RESOURCES; return NtStatus; } NtStatus = LbkEvtDeviceAdd(hDriver, pInit); KdPrint(("LoopBack Driver : OUT with Status %x",NtStatus)); return NtStatus; } NTSTATUS LbkEvtDeviceAdd( IN WDFDRIVER Driver, IN PWDFDEVICE_INIT DeviceInit ) { NTSTATUS NtStatus = STATUS_SUCCESS; PFDO_DATA fdoData; WDF_IO_QUEUE_CONFIG queueConfig; WDF_OBJECT_ATTRIBUTES fdoAttributes; WDFDEVICE hDevice; WDFQUEUE queue; DECLARE_CONST_UNICODE_STRING( ntDeviceName, L"\\Device\\devLBK" ); DECLARE_CONST_UNICODE_STRING( symbolicLinkName, L"\\DosDevices\\symLBK" ); PAGED_CODE(); KdPrint(("LbkEvtDeviceAdd : IN")); WdfDeviceInitSetExclusive( DeviceInit, TRUE ); WdfDeviceInitSetIoType( DeviceInit, WdfDeviceIoBuffered ); WDF_OBJECT_ATTRIBUTES_INIT_CONTEXT_TYPE( &fdoAttributes, FDO_DATA ); NtStatus = WdfDeviceInitAssignName( DeviceInit, &ntDeviceName ); if( ! NT_SUCCESS( NtStatus ) ) { KdPrint(("WdfDeviceInitAssignName failed %!STATUS!",NtStatus)); return NtStatus; } NtStatus = WdfDeviceCreate( &DeviceInit, &fdoAttributes, &hDevice ); if( !NT_SUCCESS( NtStatus )) { KdPrint(("LbkEvtDeviceAdd : WdfDeviceCreate failed with status code 0x%x\n",NtStatus)); return NtStatus; } NtStatus = WdfDeviceCreateSymbolicLink( hDevice, &symbolicLinkName ); if( ! NT_SUCCESS( NtStatus )) { KdPrint(("WdfDeviceCreateSymbolicLink failed %!STATUS!", NtStatus)); return NtStatus; } fdoData = LbkFdoGetData( hDevice ); WDF_IO_QUEUE_CONFIG_INIT_DEFAULT_QUEUE(&queueConfig, WdfIoQueueDispatchSequential); queueConfig.EvtIoRead = LbkEvtIoRead; queueConfig.EvtIoWrite = LbkEvtIoWrite; queueConfig.EvtIoDeviceControl = LbkEvtIoDeviceControl; NtStatus = WdfIoQueueCreate( hDevice, &queueConfig, WDF_NO_OBJECT_ATTRIBUTES, &queue ); if( ! NT_SUCCESS( NtStatus )) { KdPrint( ("LbkEvtDeviceAdd : WdfIoQueueCreate failed 0x%x\n", NtStatus)); return NtStatus; } WdfControlFinishInitializing( hDevice ); fdoData->WdfDriver = Driver; fdoData->WdfDevice = hDevice; fdoData->DeviceBufferPtr = NULL; fdoData->DeviceBufferSize = 0; fdoData->DeviceSize = 0; fdoData->DeviceBufferPtr = ExAllocatePoolWithTag( PagedPool, xferSize ,'1234'); fdoData->DeviceSize = xferSize; KdPrint(("LbkEvtDeviceAdd : OUT")); return NtStatus; } VOID LbkEvtIoDeviceControl( IN WDFQUEUE Queue, IN WDFREQUEST Request, IN size_t OutputBufferLength, IN size_t InputBufferLength, IN ULONG IoControlCode ) { NTSTATUS NtStatus = STATUS_SUCCESS; PFDO_DATA fdoData; PVOID UserBuffer; size_t xfer; KdPrint(("LbkEvtIoDeviceControl : IN")); KdPrint(("LbkEvtIoDeviceControl : OutputBufferLength %d",OutputBufferLength)); KdPrint(("LbkEvtIoDeviceControl : InputBufferLength %d",InputBufferLength)); PAGED_CODE(); fdoData = LbkFdoGetData( WdfIoQueueGetDevice( Queue )); switch( IoControlCode ) { case IOCTL_CUR_SIZE : KdPrint(("LbkEvtIoDeviceControl : IOCTL_CUR_SIZE")); NtStatus = WdfRequestRetrieveOutputBuffer( Request, 0, &UserBuffer, &xfer ); if( ! NT_SUCCESS( NtStatus )) { NtStatus = STATUS_INSUFFICIENT_RESOURCES; break; } KdPrint((" fdoData->DeviceBufferSize %d ,%d",fdoData->DeviceBufferSize,xfer)); RtlCopyMemory( UserBuffer, &fdoData->DeviceBufferSize , OutputBufferLength ); KdPrint((" userbuffer = %d",*((PLONG)UserBuffer))); //WdfRequestSetInformation( Request, OutputBufferLength ); break; case IOCTL_MAX_SIZE : KdPrint(("LbkEvtIoDeviceControl : IOCTL_MAX_SIZE")); NtStatus = WdfRequestRetrieveOutputBuffer( Request, 0, &UserBuffer, &xfer ); if( ! NT_SUCCESS( NtStatus )) { NtStatus = STATUS_INSUFFICIENT_RESOURCES; break; } KdPrint((" fdoData->DeviceSize %d ,%d",fdoData->DeviceSize,xfer)); RtlCopyMemory( UserBuffer, &fdoData->DeviceSize , OutputBufferLength ); KdPrint((" userbuffer = %d",*((PLONG)UserBuffer))); break; default: NtStatus = STATUS_INVALID_DEVICE_REQUEST; } WdfRequestCompleteWithInformation( Request, NtStatus, (ULONG_PTR) 0 ); KdPrint(("LbkEvtIoDeviceControl : OUT")); } and application code is int main() { HANDLE hDevice; BOOL status; hDevice = CreateFile( "\\\\.\\symLBK", GENERIC_READ | GENERIC_WRITE, 0, NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL ); if( hDevice == INVALID_HANDLE_VALUE ) { printf("Failed to obtain file handle to device: " "%s with Win32 error code: %d\n","LODRV1", GetLastError() ); return 1; } printf("Succeeded in obtaining handle to loopback device.\n"); printf("Attempting write to device with 16 characters...\n"); char outBuffer[50]; for( DWORD i=0; i< sizeof( outBuffer ); i++ ) outBuffer[i] = ( char ) i; DWORD outCount = 16; DWORD bW; status = WriteFile( hDevice, outBuffer, outCount, &bW, NULL ); if( !status ) { printf("Failed on call to WriteFile - error: %d\n", GetLastError() ); } if( outCount == bW ) { printf("Succeeded in writing %d bytes\n", outCount); } else { printf("Failed to write the correct number of bytes.\n""Attempted to write %d bytes, but WriteFile reported %d bytes.\n",outCount, bW ); return 3; } printf("Attempting DeviceIoControl request...\n"); getchar(); ULONG size =0,data =0; LPDWORD byte = &data; BOOL bSuccess; bSuccess = DeviceIoControl( hDevice, IOCTL_CUR_SIZE, NULL, 0, &size, sizeof( ULONG ), byte, NULL ); if( !bSuccess ) { printf("Failed on call to WriteFile - error: %d\n", GetLastError() ); } printf("Current Data Device Size Is %d \n",size ); printf("data Size Is %u \n",data); bSuccess = DeviceIoControl( hDevice, IOCTL_MAX_SIZE, NULL, 0, &size, sizeof(ULONG), byte, NULL ); printf("Total Device Size Is %u \n",size ); printf("data size %u \n",data); getchar(); status = CloseHandle( hDevice ); if( ! status ) { printf("Failed on call to CloseHandle - error: %d\n",GetLastError() ); return 6; } } Tag: WDK Kit 6000 for Windows Vista Tag: 95237
  - 4
    - Authenticode driver signing on Windows 2003 Hi, I 'm using the signtool in Win2003 R2 DDK to sign a network driver for Win2003 with authenticode using a valid VerigSign class 3 certificate. The sys file and CAT file have been embedded a vaild signature in "Trusted root Certification Authory" and "Trusted Published" store. When I install the driver, it show a "unsigned driver" warning, and appear as "Not digital signed" in Device Manager. Is there any additional requirement for the certificate or driver to use authenticode driver signing on Windows 2003? Thanks Tag: WDK Kit 6000 for Windows Vista Tag: 95234
  - 5
    - Restricting driver access acroos sessions Hi, I have a server running on Windows server 2003, to which various clients connect through RDP. When a USB device is plugged in to a client, it appears on the server as well. Now, I would like to restrict the access of the device by other clients. How could I do this? Thanks, Tag: WDK Kit 6000 for Windows Vista Tag: 95230
  - 6
    - Common buffer allocation for DMA in WDF 1.1 I have updated a WDM function driver to WDF,the DMA function(Our device act as bus master) was added into.The whole project works well but there is a problem that I have no idea about.When start my device in the device manager,if the DMA common buffer is too big for system (system can not find a big enough continus physics memory),the WdfCommonBufferCreate failed,then the OS crash with a blue screen.The followwing is my codes: WDF_DMA_ENABLER_CONFIG dmaConfig; WDF_DMA_ENABLER_CONFIG_INIT( &dmaConfig, WdfDmaProfilePacket ,//Profile was WdfDmaProfilePacket DevExt->MaximumTransferLength ); TraceEvents(TRACE_LEVEL_INFORMATION, DBG_PNP, " - The DMA Profile is WdfDmaProfilePacket ");//Profile was WdfDmaProfileScatterGather64Duplex status = WdfDmaEnablerCreate( DevExt->Device, &dmaConfig, WDF_NO_OBJECT_ATTRIBUTES, &DevExt->DmaEnabler ); if (!NT_SUCCESS (status)) { #if DBG KdPrint(("ADX: WdfDmaEnablerCreate failed with status %x\n",status)); #endif return status; } #if DBG KdPrint(("ADX: WdfDmaEnablerCreate finished with status %x\n",status)); #endif } // // Allocate common buffer for DMA // // NOTE: This common buffer will not be cached. // Perhaps in some future revision, cached option could // be used. This would have faster access, but requires // flushing before starting the DMA in PLxStartWriteDma. //First we read the buffer size from registry:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Adx16xx\Parameters\ADX,Key:DMABufferSize status = WdfDriverOpenParametersRegistryKey( WdfGetDriver(), STANDARD_RIGHTS_ALL, WDF_NO_OBJECT_ATTRIBUTES, &hKey ); status = WdfRegistryOpenKey( hKey, &keyName, KEY_READ, WDF_NO_OBJECT_ATTRIBUTES, &subkey1 ); status = WdfRegistryQueryValue( subkey1, &valueName, sizeof(ULONG), &(DevExt->dx.DMABufferSize), NULL, NULL ); WdfRegistryClose(hKey); WdfRegistryClose(subkey1); if (!NT_SUCCESS(status)) DevExt->dx.DMABufferSize=0x200000;//default buffer size is 2M #if DBG KdPrint(("ADX: evExt->WriteCommonBufferSize:%x\n",DevExt->dx.DMABufferSize)); #endif // DevExt->WriteCommonBufferSize =DevExt->dx.DMABufferSize;//sizeof(DMA_TRANSFER_ELEMENT) * DevExt->WriteTransferElements; status = WdfCommonBufferCreate( DevExt->DmaEnabler, DevExt->WriteCommonBufferSize, WDF_NO_OBJECT_ATTRIBUTES, &DevExt->WriteCommonBuffer ); if (!NT_SUCCESS(status)) { #if DBG KdPrint(("ADX: WdfCommonBufferCreate failed with status %x\n",status)); #endif return status; } I track into my codes,found that the code run to WdfCommonBufferCreate.My problem is ,if failed , the WdfCommonBufferCreate should return an error status code ,then the driver loading will failed with the status code,but not give me a blue screen. Can any one give me suggestions?Is the bug fixed in the version 1.5 KMDF? Tag: WDK Kit 6000 for Windows Vista Tag: 95227
  - 7
    - COM port naming Hi, I am working on a WDF serial port driver wherein I create a virtual serial COM port and I need to have the COM port number of my choice always whenever I load the driver. For this I had created a device map and written that value using RtlWriteRegistryValue(). By doing this I am able to get the COM port number of my choice in the Hyper Terminal, but the device manager is showing the COM port number which windows has assigned. Now I want the COM port number of my choice to be reflected even in the Device Manager. Can anyone of you please help me in resolving issue? Thanks in advance. Regards, Vijay Kumar K Tag: WDK Kit 6000 for Windows Vista Tag: 95226
  - 8
    - SMARTCARD_EXTENSION & OsData Hi, The SMARTCARD_EXTENSION structure has a member OsData->DeviceObject. What purpose does DeviceObject server here? Why woul'd smclib need the drivers DeviceObject. -- Vijairaj Tag: WDK Kit 6000 for Windows Vista Tag: 95223
  - 9
    - PsSetLoadImageNotification changed ? In my driver I make a call to PsSetLoadImageNotification () and get a callback as expected. One of the params in the callback is the ProcessId. I'm saving the processId to note when a particular (say, my) user mode component is loaded so that when I see Ioctl's I can assure myself that I know who I'm talking to. In XP this worked fine, the same code in Vista does not: Once the user mode program is running , I dump out the process using !process 0 0 in windbg which indicates that the ProcessId that I got in my callback is that of the Parent CID not the guy I'm loading Of course, when I do PsGetCurrentProcessId() in my DeviceControl routine, I get the process's Id, and I never recognize my particular user mode component. Any ideas, beyond of course going back to an XP box and making sure that the behavior I think I saw is really happening there? -- Gak - Finecats Tag: WDK Kit 6000 for Windows Vista Tag: 95222
  - 10
    - INF file processing API functions Hi, I am trying to understand why is there a need for INF file processing functions when, for example, we can use standard C/C++ File IO functions. I have a few questions. What is advantage of using INF file processing API such as SetupOpenInfFile? And what is proper method of chain of actions needed to properly read a Hardware ID of a device from INF file if you are searching through a whole directory full of INF files? Suppose, device belongs to NET class and we want to match a network adapter Hardware ID to the one present in some INF file. My guess is we can eliminate any INF file that does not belong to NET class. Need some guidance on how to properly do this. More details can be provided if need be. Thanks Tag: WDK Kit 6000 for Windows Vista Tag: 95220
  - 11
    - DeviceIoControl blocks even in Overlapped I/O mode? How is this possible? Could someone please clarify the term "Overlapped I/O" (or "Pending I/ O")? I thought that if I implement and use it properly, DeviceIoControl() would never wait/block, leaving it instead to a WaitForMultipleObjects() or WaitForSingleObject() down the line. However, in a recent buggy driver implementation of mine I managed to make DeviceIoControl() block in a write operation... How is this possible? I thought that the "no wait intelligence" (in overlapped mode) is built into the DeviceIoControl() code and not dependent upon the device driver implementation. Have I misunderstood? What am I missing? Thanks, Don Tag: WDK Kit 6000 for Windows Vista Tag: 95217
  - 12
    - Analyze Crash Dump Hello All, I have a USB-Serial driver developed for Windows XP. I open the handle to virtual COM and close the handle for it. Then i uninstall the COM device. The entire code runs properly for uninstall and finally after ReleaseHardware() i get the below bug check. I do not see any statement in my driver from the bug check. How can i know which module in my driver caused the bug check. Can some one provide me some information or any useful links to know the root cause of the bug? Your suggestions are appreciable. Thank You. uba ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: ffffffe0, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: aa16f45b, address which referenced memory Debugging Details: ------------------ *** No owner thread found for resource 80551160 *** No owner thread found for resource 80551160 *** No owner thread found for resource 80551160 WRITE_ADDRESS: ffffffe0 CURRENT_IRQL: 2 FAULTING_IP: Wdf01000!FxIrpQueue::RemoveNextIrpFromQueue+12 aa16f45b 8716 xchg edx,dword ptr [esi] DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: f8940948 -- (.trap 0xfffffffff8940948) ErrCode = 00000002 eax=ffffffa8 ebx=00000000 ecx=82aec8b4 edx=00000000 esi=ffffffe0 edi=aa1a2f30 eip=aa16f45b esp=f89409bc ebp=f89409c0 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246 Wdf01000!FxIrpQueue::RemoveNextIrpFromQueue+0x12: aa16f45b 8716 xchg edx,dword ptr [esi] ds: 0023:ffffffe0=???????? Resetting default scope LOCK_ADDRESS: 805511e0 -- (!locks 805511e0) Resource @ nt!IopDeviceTreeLock (0x805511e0) Shared 1 owning threads Threads: 82bc8b30-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x805511e0 Thread Count : 1 Thread address: 0x82bc8b30 Thread wait : 0x57194 LAST_CONTROL_TRANSFER: from 804f780d to 80526da8 STACK_TEXT: f89404fc 804f780d 00000003 f8940858 00000000 nt! RtlpBreakWithStatusInstruction f8940548 804f83fa 00000003 ffffffe0 aa16f45b nt!KiBugCheckDebugBreak +0x19 f8940928 8053f853 0000000a ffffffe0 00000002 nt!KeBugCheck2+0x574 f8940928 aa16f45b 0000000a ffffffe0 00000002 nt!KiTrap0E+0x233 f89409c0 aa16f5c9 00000000 f89409e4 f89409dc Wdf01000! FxIrpQueue::RemoveNextIrpFromQueue+0x12 f89409d0 aa165a58 f89409e4 f89409fc aa17d287 Wdf01000! FxIrpQueue::GetNextRequest+0xf f89409dc aa17d287 82aec8b4 82aeca14 82aec840 Wdf01000! FxRequest::GetNextRequest+0x11 f89409fc aa17d6bd 00000001 00000001 00000000 Wdf01000! FxIoQueue::QueuePurge+0x3b1 f8940a1c aa17f6bf 00000002 00000008 82aecb70 Wdf01000! FxIoQueue::StopProcessingForPower+0x30 f8940a3c aa18b603 00000002 82aecb70 f8940a60 Wdf01000! FxPkgIo::StopProcessingForPower+0x88 f8940a4c aa18b6fe 00000001 82aecb70 00000117 Wdf01000! FxPkgPnp::PnpCleanupForRemove+0x37 f8940a60 aa18b245 82aecb70 aa1a4260 82aecb70 Wdf01000! FxPkgPnp::PnpEventRemovingDisableInterfaces+0xb4 f8940a88 aa18bfa0 00000117 82aecc10 82aecb70 Wdf01000! FxPkgPnp::PnpEnterNewState+0x15c f8940ab0 aa18c2aa f8940ac8 00000000 82aecb70 Wdf01000! FxPkgPnp::PnpProcessEventInner+0x1f5 f8940ad4 aa184ecc 00000200 82aecb70 aa1a3790 Wdf01000! FxPkgPnp::PnpProcessEvent+0x1c8 f8940afc aa1840d6 82aecb70 f8940b1c 00000000 Wdf01000! FxPkgPnp::_PnpRemoveDevice+0x69 f8940b20 aa16dd9a 82afde70 f8940b48 aa16df9f Wdf01000! FxPkgPnp::Dispatch+0x26e f8940b2c aa16df9f 82aeca60 82afde70 00000000 Wdf01000! FxDevice::Dispatch+0x7f f8940b48 804eddf9 82aeca60 82afde70 00000000 Wdf01000! FxDevice::DispatchWithLock+0x5d f8940b58 aa40e42d 82afdf70 82aeba88 82afde70 nt!IopfCallDriver+0x31 f8940b80 aa40e9fd 82aeba88 82afde70 82afdf4c serenum!Serenum_FDO_PnP +0x1ab f8940b9c 804eddf9 82aeba88 82afde70 f8940c28 serenum!Serenum_PnP+0x3b f8940bac 80586d67 825a5ae8 825a5ae8 00000002 nt!IopfCallDriver+0x31 f8940bd8 80586e8b 82aeba88 f8940c04 00000000 nt!IopSynchronousCall +0xb7 f8940c2c 804f5b48 825a5ae8 00000002 00000000 nt!IopRemoveDevice+0x93 f8940c54 8058899c e2aa1e30 00000015 e2acb288 nt! IopRemoveLockedDeviceNode+0x160 f8940c6c 80588a03 8228f3c0 00000002 e2acb288 nt! IopDeleteLockedDeviceNode+0x34 f8940ca0 8058e673 825a5ae8 02acb288 00000002 nt! IopDeleteLockedDeviceNodes+0x3f f8940d34 8058e936 f8940d70 806d0778 e2b06898 nt! PiProcessQueryRemoveAndEject+0x76b f8940d50 8058ea8f f8940d70 825654b0 8055a1fc nt! PiProcessTargetDeviceEvent+0x2a f8940d74 80533dd0 825654b0 00000000 82bc8b30 nt!PiWalkDeviceList+0xfd f8940dac 805c4a28 825654b0 00000000 00000000 nt!ExpWorkerThread+0x100 f8940ddc 80540fa2 80533cd0 00000001 00000000 nt!PspSystemThreadStartup +0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: Wdf01000!FxIrpQueue::RemoveNextIrpFromQueue+12 aa16f45b 8716 xchg edx,dword ptr [esi] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: Wdf01000!FxIrpQueue::RemoveNextIrpFromQueue+12 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Wdf01000 IMAGE_NAME: Wdf01000.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4549b23a FAILURE_BUCKET_ID: 0xD1_W_Wdf01000!FxIrpQueue::RemoveNextIrpFromQueue +12 BUCKET_ID: 0xD1_W_Wdf01000!FxIrpQueue::RemoveNextIrpFromQueue+12 Followup: MachineOwner --------- Tag: WDK Kit 6000 for Windows Vista Tag: 95214
  - 13
    - How to develop UVC webcam driver on win2k Dear all, As our customer request driver of UVC webcam for the early Windows OSes, I need to develop a driver for UVC webcam on Win2K. But I have some questions just as below: 1 Can MS USBCAMD minidriver or AVStream achitecture support UVC webcam driver development? I means if the UVC request/command can be sent to Webcam successfully, or some special trick is need to get/set request thru interface. 2 Is there any special request for the webcam hardware? in other words, besides UVC HW logic, another no-UVC HW interface for custom driver? 3 What is right sample code to kick off UVC webcam driver? Any idea is appraciated. Thanks in advance! Tag: WDK Kit 6000 for Windows Vista Tag: 95206
  - 14
    - InputBufferLength , OutputBufferLength Quiestion I'm mking a USB filter driver, when I recive a IRP_MJ_DEVICE_CONTROL i check DbgPrint("Len (I) %d ",irpStack- >Parameters.DeviceIoControl.InputBufferLength); DbgPrint("Len (O) %d ",irpStack- >Parameters.DeviceIoControl.OutputBufferLength); But InputBufferLength and OutputBufferLength aas always the same value, why ? How can I check if a IRP packet is going DOWN to the stack or is going UP? Because it seems to catch only DOWN IRP packets. Best regards Tag: WDK Kit 6000 for Windows Vista Tag: 95205
  - 15
    - KeWaitForSingleObject() can only reach 0.01sec timeout I am using the KeWaitForSingleObject() to do delay in my kernel mode driver like following: LARGE_INTEGER nWaitTime; nWaitTime = RtlConvertLongToLargeInteger(-1000 * 10);// I need 0.001sec KeSetTimer(&fdoData->kTimer, nWaitTime, NULL); KeWaitForSingleObject(&fdoData->kTimer, Executive, KernelMode, FALSE, NULL); But when I use DbgView to catch the actual delay, I found that it can only reach 0.01second at most and cannot satisfy my requirement, 0.001sec. Any comment is appreaciated. Tag: WDK Kit 6000 for Windows Vista Tag: 95200
  - 16
    - USB Phone driver question Hi I've got some USB phone sample from vendor, it will be installed by Windows XP after I plugged in USB port , and I saw it use the system usbaudio.sys . I need to create some ks filter properties and events as a vendor's own USB phone driver . Is it possible we base this driver on Windows system audio driver ? I've researched that a custom audio driver can use portcls driver ( collection of port drivers) and adapter driver ( collection of miniport drivers ) . Should I use usbaudio.sys as adapter driver ? If this way ok how can I make its portcls driver ? I did not find sample code like portcls.sys from DDK . Tag: WDK Kit 6000 for Windows Vista Tag: 95198
  - 17
    - Virtual Audio Device Hi When do we need to implement a virtual audio driver, why we just use specific audio class driver , is there some good sample code included in DDK ? Thank you . Tag: WDK Kit 6000 for Windows Vista Tag: 95197
  - 18
    - Conversion to 64 bit... Hi, Is there should be any limitation using a 32 bit compiled printer driver, on a windows xp 64 bit? Also, is there should be any limitation limitation (or that a code change is required) using 32 bit user mode application that runs on xp 64 bit, and communicates with a 64 bit compiled driver ? (Besides exchanging pointers from kernel to user mode and back) Thanks! Tag: WDK Kit 6000 for Windows Vista Tag: 95191
  - 19
    - Conversion to 64 bit... Hi, Is there should be any limitation using a 32 bit compiled printer driver, on a windows xp 64 bit? Also, is there should be any limitation limitation (or that a code change is required) using 32 bit user mode application that runs on xp 64 bit, and communicates with a 64 bit compiled driver ? (Besides exchanging pointers from kernel to user mode and back) Thanks! Tag: WDK Kit 6000 for Windows Vista Tag: 95190
  - 20
    - Failed to load driver on Vista I have an application that works with two particular drivers, one is loaded on boot and second is loaded when my application is working. I use the first driver to load and unload the second driver using ZwLoad/ UnloadDriver. Everything works fine on Win2K and XP but I encounter some problems in Vista. Sometimes I get error 0xC0000034 upon ZwLoadDriver of my second driver. I looked for my drivers and devices in the system, but monitors such as DeviceTree or WinObj do not show any of them. On the other hand, from a full memory dump I can see my second driver loaded. >From some reasons that I can't explain, I see that when I run my application "as administrator" and immediately close the application everything suddenly get back to track. When I run my application as administrator I even do not attemp to load the driver. Of course, after computer restart the application starts to work fine as well. It is important to mention that both drivers are properly signed. Any help is very appreciated. Tag: WDK Kit 6000 for Windows Vista Tag: 95189
  - 21
    - LNK2019 Error with Win Server 2003 Checked x64 I've written a driver and have successfully built it using WinXP Checked Build. When I compile the same project with the Windows Server 2003 Checked x64 tools, I get "LNK2019 - unresolved external symbol <blah blah> referenced in DriverEntry". I'm linking in .lib files, declaring them as "external" in the driver code. As I said, the same code and files compile perfectly with the WinXP Checked Build compiler. I'm getting the LNK2019 unresolved errors with the Windows Server 2003 Checked x64 Build compiler. Any help and insight would be appreciated. Thanks Tag: WDK Kit 6000 for Windows Vista Tag: 95186
  - 22
    - Re: USB camera driver speed limited in vista system? We send a bulk request using 1600*1200(1920000) bytes size to host driver. Is this size wrong? Thank you very much! Abei no, it does not. waht size reads are you sending to the bulk endpoint? -- Please do not send e-mail directly to this alias. this alias is for newsgroup purposes only. This posting is provided "AS IS" with no warranties, and confers no rights. "abei" <aboutwho_1@163.com> wrote in message news:umQNx%23tnHHA.2452@TK2MSFTNGP02.phx.gbl... > We have a 2M pixels USB camera to be used in new vista system. We have > developped a new driver for vista and it works well, but now we have found > a problem about this driver. Our camera can output about 10fps > (1600*1200 ) stream when it works in Windows XP system. But our camera can > only output about 5fps(1600 * 1200) stream when it works in vista. > Does anyone have meet this problem? Does Vista have a speed limited to USB > bulk pipe? > > thank very much! > > abei > Tag: WDK Kit 6000 for Windows Vista Tag: 95184
  - 23
    - RNDIS interface stops sending traffic after REMOTE_NDIS_RESET_MSG Hi Guys, Could somebody tell me why RNDIS interface stops transmitting eth packets after sending a REMOTE_NDIS_RESET_MSG? Is there any command to know about the reason of this soft reset? Also, which command we can use from RNDIS device side to tell the host to restart the RNDIS initialisation process again? Or Is there any msg from device side that it can be the initiator? Thanks a lot for any help.. Regards, Joji Tag: WDK Kit 6000 for Windows Vista Tag: 95173
  - 24
    - Using QueryPerformanceCounter in NDIS miniport driver I want to use QueryPerformanceCounter() to get the system's time. But, when I use it in the DriverEntry(), it will cause the driver crash. So, I'm asking whether I could use this function in the miniport driver??? Or, I use it wrongly. Please help me! Thanks! Tag: WDK Kit 6000 for Windows Vista Tag: 95171
  - 25
    - AVStream PresentationTime The DDK docs say, for IKsReferenceClock::GetTime, "Do not call this method when obtaining a timestamp for the PresentationTime member of KSSTREAM_HEADER. Instead, call IKsReferenceClock::GetCorrelatedTime in this situation." However, every one of the samples uses GetTime, and none use GetCorrelatedTime. Any insight? Or does it just not matter very much? Cheers, --mkj Michael K. Jones Stone Hill Comsulting http://www.stonehill.com Tag: WDK Kit 6000 for Windows Vista Tag: 95169

Hello All,
please tell me where i will get the WDK 6000 kit for building the KMDF
driver for Windows Vista.

thanks

Re: WDK Kit 6000 for Windows Vista by Don

Don
Thu May 31 10:47:10 CDT 2007

See http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx

--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

<sulibsp@gmail.com> wrote in message
news:1180626000.481039.274940@q69g2000hsb.googlegroups.com...
> Hello All,
> please tell me where i will get the WDK 6000 kit for building the KMDF
> driver for Windows Vista.
>
> thanks
>

Top