Invalid device parameters from device driver

Rachid K. Add a comment. Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer.

Look for critical errors in the system log that occurred in the same time window as the blue screen. To try and isolate the cause, temporally disable power save using control panel, power options.

Some driver issues are related to the various states of system hibernation and the suspending and resumption of power. If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.

Please rate your experience Yes No. If you cannot answer them yourself, then please get the answer from someone who has more knowledge with these issues. What is the difference between Windows 10 and Windows 7 when it comes to the validation of the Configuration Descriptor? Is there a setting in the Registry, which affects how the Configuration Descriptor gets validated? What is not compliant in the Configuration Descriptor as sent by the device? Here is the data again:. On a side note: I tried to search the registry for an entry related to the Configuration Descriptor.

Details required : characters remaining Cancel Submit 9 people found this reply helpful. Meanwhile, I got the device working. It was indeed the Configuration Descriptor. The third byte of the data should have been 0x27 instead of 0x28, shrinking the size of the structure from 40 to 39 bytes. Evidently this was checked when the device is enumerated.

I was able to read it and I found the sequence of the Device Descriptor. I like to stress that I got lucky, and what I did is certainly beyond an average user. It would have been so much easier if there was a setting in the registry for this kind of problem.

After all, before I upgraded the PC from Windows 7 to Windows 10, Microsoft claimed that everything is compatible, so they are obligated to fulfill their promises. It is truly pathetic that I did not get any useful reply from Microsoft. Here is the data as sent by the device: 0x09, 0x02, 0x28, 0x00, 0x01, 0x01, 0x00, 0x60, 0x00, 0x09, 0x04, 0x00, 0x00, 0x03, 0xFF, 0x00, 0x00, 0x00, 0x07, 0x05, 0x82, 0x00, 0x40, 0x00, 0x00, 0x07, 0x05, 0x02, 0x02, 0x40, 0x00, 0x00, 0x07, 0x05, 0x88, 0x01, 0x00, 0x02, 0x01, 0x04 Analyzing this, this describes an interface with 3 endpoints I formatted the data accordingly.

This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :.

Cancel Submit. This can arise due to several reasons, to narrow down the cause, I would like you to provide the information stated below 1.

Have you tried plugging the device to different ports or another Windows 10 device? What is the manufacturer of the device? Is it a USB stick or an external drive?

Have you check the error it displays under Device Manager? Method 1: Device Manager 1. Right click on the Start Menu and click on Device Manager 2. Locate your device and double click to expand the same. How satisfied are you with this reply?