• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 32 subscribers
  • Views 797 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TUSB3410 driver causing Blue Screen on win7

Bahram Moinvaziri
Prodigy 70 points
Other Parts Discussed in Thread: TUSB3410

Hi,
Sometimes, the USB driver unloads and when attempting to disable/enable device from Device Manager, it causes the computer to blue screen and reboot. Other times, when the host computer restarts, it says that one of the USB devices attached to this computer has malfunctioned and Windows does not recognized it. Under USB Root Hub (3 ports), the Generic USB Hub sub device which has a exclamation icon is called "Unknown Device". Disabling and re-enabling this does not fix the problem and causes blue screen of death to appear. The driver is working intermittently. I am currently writing this post from that computer and this is exactly when the problem has occurred, i need to reboot and try to see if disabling the COM port at the BIOS will affect the behavior.
Thank  you,
Bahram 

  • 0
    TI__Genius 11255 points

    Hello Braham,

    Could you please provide us more detail about your failure? It’ll help us to try to reproduce this problem at our end.

    What Operating system are you using?
    What driver version are you using?
    The blue screen occurs simply disabling-enabling the TUSB3410 instance from the device manager? Or it’s occurring meanwhile you are using other software/application?
    Are you able to reproduce this behavior on a clean system?
    Could you please provide us the reproduction steps (step by step) in order to try to reproduce it at our end?

    Regards,
    Roberto.

  • 0 in reply to Roberto Diaz
    Prodigy 70 points

    Update 10/25/2013: After further testing, i would disconnect the USB hub and then plug-in the TUSB3410 end of the cable into the PC and the driver would fail load. So, it appears that the USB hub had nothing to do with the failure to load.

    Hi Roberto,
    OS is Windows 7 Professional SP1, Running on a Dell Optiplex 900 Intel-i5-2500 CPU @3.3GHZ, with 8GB of RAM.
    I have two different version numbers, the zip file which i have says  USB Drivers V6.5.9017.0 but after the driver is loaded, the properties for the entry under the "Ports (COM & LPT)" under Device Manager says it is Driver Version 6.7.2.0.
    Here is how i can reproduce this:

    1. Install the TUSB3410 driver
    2. Use a terminal emulator program and connect to the port which the TUSB3410 is sitting on. 
    3. Try to perform a write and then while the write is happening, disconnect the cable from device. 
      1. In order to create this effect every time, I use the terminal emulator we wrote. This is because we can control the application. So I can stop the debug session before calling WriteFile and then disconnect the USB cable and then allow the program execution to continue. Since the cable is disconnected, the driver no longer exists and program execution will fail with error code 22. At this point, our emulator program will call ::CancelIoEx, this function causes our program not to crash.
    4. Plug back the USB cable, the program is able to reconnect to the same port and communicate. But sometimes the driver fails to load. 
    5. If the USB cable is plugged back in, the driver does not load, repeated enable/disable, cable insertion, extraction will cause the OS to reboot and hence the blue screen.

    As a side note, in my computer i had a USB Hub, which had 4 USB connections, at each USB port on this hub, there was a Memory stick or Thumb drive. At one time, inserting and extracting the TUSB3410 into/out of the PC would not cause it to load - device manager showing error code 44 (i think this is the number) every time, meaning the driver has failed to load.  I finally removed the USB Hub and after which the plug-in of the TUSB3410 into the USB of PC made it work (by the way, I have never tried plugging the TUSB3410 into the Hub). 

    Best Regards,
    Bahram 

  • 0 in reply to Bahram Moinvaziri
    TI__Genius 11255 points

    Hello Braham, 

                    Sorry for the delay on this, we are trying to reproduce, on the meanwhile we are wondering if you are able to reproduce this problem on a clean system?

                     We’ll let you know as soon as we have any update on this.

     

                    Regards,

                    Roberto.

  • 0 in reply to Roberto Diaz
    Prodigy 70 points

    Hi Roberto,

    What do you call a clean system?

    Thanks,

    Bahram

  • 0 in reply to Bahram Moinvaziri
    TI__Genius 11255 points

    Hello Bahram,

     

                    What I mean is that if you are able to reproduce the problem on a Fresh installation of Windows, that’s to avoid that there is nothing else that affects the TUSB3410 behavior?  

     

    Also I’m wondering if the problem can be replicate in other system than the one that you are using for your testing?

     

    Regards,

    Roberto.

  • 0 in reply to Roberto Diaz
    Prodigy 70 points

    Yes, the problem actually happened on another system first in our manufacturing. Then it was reported to us by our customers and then i was able to reproduce it.

  • 0 in reply to Bahram Moinvaziri
    TI__Genius 11255 points

    Hello Baham,

                     Unfortunately we were not able to reproduce the problem at our end, we have tried using the HyperTerm software with the TUSB3410EVM, during the transmission we disconnect/connect several times the TUSB3410 from the PC and the hardware instance always appears  on the Device Manager and still working without problem.

                     We are wondering if this problem only happens using your software, could you please provide us your software and the instructions (step by step ) to use it?

     

                    Regards,

                    Roberto.