Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

TraceView etl log analysis

SumitSumit Member Posts: 10

Hi,

I am new to the USB driver development/analysis, I have extracted the etl logs and below are the TraceView logs

00000152 vmusb 4 772 0 0 02\07\2019-06:49:46:231 Set instance ID: 858508856766, unique: 1
00000153 vmusb 4 772 0 0 02\07\2019-06:49:46:231 Set text description, language: 0x409, device: XYZ_Android, location: Port_#0001.Hub_#0025
00000154 vmusb 4 772 0 0 02\07\2019-06:49:46:231 Registered IO internal control preprocessor for manual rejection, PlugNo: 5
00000155 vmusb 4 772 0 0 02\07\2019-06:49:46:231 WdfDeviceAddQueryInterface succeed, status: 0x0
00000156 vmusb 4 772 0 0 02\07\2019-06:49:46:231 Using a power managed queue, PlugNo: 5
00000157 vmusb 4 772 0 0 02\07\2019-06:49:46:231 Unknown( 24): GUID=51526c19-3dac-91c5-c442-f657fec1726a (No Format Information found).
00000158 vmusb 4 772 0 0 02\07\2019-06:49:46:231 Unsupported interface type (passing onto framework), GUID: b8e992ec-a797-4dc4-884684d041707446, version: 1

To my understanding it looks like, windows driver (from system process ID 4) is giving the call to my driver, however it seems like the interface is not implemented in our driver.

Could someone please provide more info on this.
Any help would be much appreciable.

Thanks,
Sumit

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
Developing Minifilters 29 July 2019 OSR Seminar Space
Writing WDF Drivers 23 Sept 2019 OSR Seminar Space
Kernel Debugging 21 Oct 2019 OSR Seminar Space
Internals & Software Drivers 18 Nov 2019 Dulles, VA