BSOD when using serial to usb adapter

[tehdigester]

Hi,

So this computer has been having this problem for a while.
The computer has some equipment connected via a usb to serial converter and it just sits there always plugged in having no problems. However when we go and open up the software which actually tries to pull data from the device, bam, bsod (not all the times, but most of them).

Searching on the internet suggests the usb to serial adapter was a bit dodgy (made by ATEN), so I bought a better (more expensive) version from a different company(keyspan usa-19hs). Yet we still have the problem.

Hopefully someone can lend a hand as to what the problem is now.
I've used DM Log Collector and attached the results.

Thanks again seven forums!

(Im 90% sure its the adapter, but i might be wrong! Something else could be causing the bsods!)

 

[Thedoctor44]

Yeah, the cause it due to the USA19H2kp.SYS driver.

I need a bit more information though.

Upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instructions here. http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html.

 

[tehdigester]

Yeah, the cause it due to the USA19H2kp.SYS driver.

I need a bit more information though.

Upload your MSINFO32.nfo file.

Thanks Thedoctor44!

Here's the requested msinfo.nfo file!

 

[tehdigester]

Anyone have any idea?

 

[Thedoctor44]

hmm, the file seems corrupt. could you upload it again?

Your driver is out of date by 7 years. It needs updating.

[COLOR="Red"]Probably caused by : USA19H2kp.SYS[/COLOR]

b05df000 b05e4e80   USA19H2kp T (no symbols)           
    Loaded symbol image file: USA19H2kp.SYS
    Image path: \SystemRoot\system32\DRIVERS\USA19H2kp.SYS
    Image name: USA19H2kp.SYS
    Timestamp:        [COLOR="red"]Wed May 30 00:32:56 2007[/COLOR] (465CB828)
    CheckSum:         000136EB
    ImageSize:        00005E80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[tehdigester]

hmm, the file seems corrupt.

Huh, gimmie 1sec i'll re-upload it.

Edit: done!

 

[Thedoctor44]

hmm, it's still corrupt.

 

[tehdigester]

hmm, it's still corrupt.

Mmm, i assumed it was a problem with the upload/compression. I guess the nfo was corrupt, i'll generate another one.

Btw, im using the latest drivers dated from 2013 :/

Edit: attached it! Hopefully its not corrupt!!

 

[Thedoctor44]

It's still corrupt or incompatible...

 

[tehdigester]

I think something might be wrong on your end, even my mac can open it!

 

[Thedoctor44]

I've had to open the .nfo file in notepad. It's only yours that it fails to open normally. Anyway, Do you have a keyspan USB serial adapter?

 

[tehdigester]

Anyway, Doy uo have a keyspan USB serial adapter?

Yep, thats the one i'm using!

 

[Thedoctor44]

The driver for it appears to be causing issues, in fact some BSODs itself.

Create a system restore point to prevent further issues. You can follow these instructions if you don't know how to create one.

http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

After the restore point is created you can then update the driver, the only site I've really been able to find is this one. So that's why I wanted you to create a restore point. Update the driver here. Click on the support tab, then the driver for Windows.

USA-49WG | Tripp Lite

 

[tehdigester]

Wouldn't it make more sense to install the drivers for the actual device that i'm using?
USA-19HS | Tripp Lite

Or are you saying these drivers are causing problems and a driver from a different product might work?

Congrats on becoming a power user btw
Been watching your post count exponentially increase!

 

[Thedoctor44]

Yes the driver for your adapter is causing problems, you should update it from the link after you've created a system restore.

Thanks a lot

 

[TheITN00B]

Did this resolve your issue? I believe we're having almost the exact same issue with the exact same adapter at my work. I did update the drivers yesterday with the newest version of the USA-19H drivers, if it doesn't I"m going to use the drivers recommended by Thedoctor44.