Blue Screen of Death, or BSOD

[robmwpropane]

I got a minute to start playing around with things.

When I connect the usb-ttl to load the drivers, I get the blue screen of death, or (BSOD for anyone searching at a later date)

I've tried uninstalling, reinstalling 3 times. After plugging it back in (5 seconds or so), BSOD.

Any ideas?

Edit: I attached a link for the dump of the BSOD error (not allowed to upload .dmp?);

https://www.dropbox.com/s/dvbwqb0r53pk4 ... 1.dmp?dl=0

[robmwpropane]

Now I've moved to my wife's laptop for a temporary fix.

I had an issue with things at first. When installing the RA software it told me COM 3, when it was really at COM 4 (I had to look in device manager). Once this was changed, everything worked great.

I don't want to use my wife's PC, but I did want to verify the cable and RA worked. So now I'm stuck trying to figure why the driver issue on my PC?

PC is Windows 7 Ultimate SP1, 64 bit, AMD 8350 8 core, 16GB ram....

[rimai]

Humm.
Never heard of this.
Try downloading and installing the latest driver from the manufacturer.
http://www.ftdichip.com/Drivers/CDM/CDM21224_Setup.zip

[robmwpropane]

I did that. They will not install, and if I do it manually I get another BSOD...

I get an "install failed" for both Bus/D2XX Driver and VCP Driver

This is what I find when opening USB Serial Port Properties for this device;

"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"

The BSOD error that I get is;

NO_MORE_ISP_STACK_LOCATIONS
error0x00000035

I'm getting nowhere fast, lol...

[robmwpropane]

Anybody? Man I'm stumped. I've spent all day doing everything I can find:(

[robmwpropane]

Well I downloaded "BlueScreenView" which shows me what's causing the bsod.

I have traced it back to a driver "AiChargerPlus.sys" which says caused by address "AiChargerPlus.sys+5f7", and the crash address is "ntoskrnl.exe+6f440"

I feel like I'm making headway. I've found and deleted the driver, but it still shows up, so I didn't do something right, although the AiChargerPlus no longer shows up in my processes either.

Man, if any of you gurus out there have any insight, I sure would appreciate it. It's not like I'm not searching / trying my hardest...

[rimai]

I've never seen this before.
I don't think that driver has anything to do with the FTDI cable though.
It is definitely something on that computer, since you already confirmed working on the other one.
On my machine, it shows these files on the Driver file details:
c:\windows\system32\drivers\ftser2k.sys
c:\windows\system32\drivers\serenum.sys
c:\windows\system32\ftcserco.dll
c:\windows\system32\ftserui2.sll
Maybe this will help.

[robmwpropane]

I've never seen this before.
I don't think that driver has anything to do with the FTDI cable though.
It is definitely something on that computer, since you already confirmed working on the other one.
On my machine, it shows these files on the Driver file details:
c:\windows\system32\drivers\ftser2k.sys
c:\windows\system32\drivers\serenum.sys
c:\windows\system32\ftcserco.dll
c:\windows\system32\ftserui2.sll
Maybe this will help.

I appreciate the feedback. Are you saying you think I'm looking into the wrong thing? I figured the aichargerplus driver might be freaking out when the FTDI is plugged in. Although it's only supposed to effect USB 3.0, and I only have been using USB 2.0 slots with the FTDI to avoid any problems.

aicharger is for quick charging compatible devices over USB 3.0

[rimai]

No, I'm saying the same thing you are. That aichargerplus shouldn't affect the FTDI driver. They are not related to each other, I think.
Do you get blue screen regardless of which port you connect the cable?
Does it go into bsod right after you plug it in?

[robmwpropane]

No, I'm saying the same thing you are. That aichargerplus shouldn't affect the FTDI driver. They are not related to each other, I think.
Do you get blue screen regardless of which port you connect the cable?
Does it go into bsod right after you plug it in?

Yesterday I was only trying usb 2.0, this morning (because of what you said) I tried usb 3.0 port...and it worked!! Except....it will only works once. The first time I plug it in, the computer recognizes something being plugged in. At this time I can flash the RA, everything works well. Then if I disconnect, my device manager freezes. The PC stays active, I can still do things, but I can not get it to read anything.

All ports will still power devices, just no read / write.

Man, so close, but so far......

[bencollinz]

No, I'm saying the same thing you are. That aichargerplus shouldn't affect the FTDI driver. They are not related to each other, I think.
Do you get blue screen regardless of which port you connect the cable?
Does it go into bsod right after you plug it in?

Yesterday I was only trying usb 2.0, this morning (because of what you said) I tried usb 3.0 port...and it worked!! Except....it will only works once. The first time I plug it in, the computer recognizes something being plugged in. At this time I can flash the RA, everything works well. Then if I disconnect, my device manager freezes. The PC stays active, I can still do things, but I can not get it to read anything.

All ports will still power devices, just no read / write.

Man, so close, but so far......

Create a new user account. Reboot. Login to said new account and try again.
Also, try going into bios and disable 3.0 USB ports (so they act like 2.0).

[robmwpropane]

On my machine, it shows these files on the Driver file details:
c:\windows\system32\drivers\ftser2k.sys
c:\windows\system32\drivers\serenum.sys
c:\windows\system32\ftcserco.dll
c:\windows\system32\ftserui2.sll
Maybe this will help.

These are the same listed on my machine, but under "general" it says "No drivers are installed for this device.", Then if I click on "driver" it says
Driver Provider: FTDI
Driver Date: 9/28/16
Driver Version: 2.12.24.0
Digital Signer: Microsoft Windows Hardware Compatibility Publisher

Device Description is USB Serial Port

Create a new user account. Reboot. Login to said new account and try again.
Also, try going into bios and disable 3.0 USB ports (so they act like 2.0).

Tried to make a new account, same difference. I still need to disable 3.0 in the bios, but honestly, I don't know why that would be effecting the driver... but I'll try it....

[robmwpropane]

Create a new user account. Reboot. Login to said new account and try again.
Also, try going into bios and disable 3.0 USB ports (so they act like 2.0).

Tried the above, no go....thanks for the suggestion though.


Soooooo...just to go into a little rant to follow up with this thread. I still have not been able to get my PC to accept the usb-ttl cable without throwing a fit, bsod, etc. BUT......


I will say I'm super impressed with Roberto. When I pm'ed him about the issue and invited him to take a look, he spent the better part of 2 hours trying to trouble shoot my problem. He could of just shrugged his shoulders, but I watched as he tried everything under the sun to get it to work. At the end of it, he wasn't able to figure out what the issue is, but I'm 100% sure it doesn't have to do with the RA or the usb-ttl cable. It's something specific to my PC. At some point he knew it had nothing to do with his hardware, and STILL proceeded to try and help. I know it's a business, and I know time is money, but I am super grateful that he tried to get this up and running when technically he didn't have to, and didn't ask for anything in return. So while I do wish we could of gotten it to work, man do I appreciate the help. I feel like people who may not know what kind of guy you are, should know. That says a lot about someone, so again, THANK YOU!


I'm going to stick at trying to figure it out, but for now the work around is just to use another computer. I'll update this thread if I ever figure out what it is.

[bencollinz]

The next step would be to reimage the PC. But that's never fun unless you're a tech.

[robmwpropane]

The next step would be to reimage the PC. But that's never fun unless you're a tech.

I'm not a tech, but I've done it. Not fun. Everything else about the PC is great. For the hassle of it all, I'll just get the Bluetooth attachment and be done with it.

[Mirror176]

Don't know if you ever figured things out but other things to try is updating the ai charger plus driver/software or remove it while connecting/installing the ai ftdi driver. You may or may not be able to reinstall after. Even if you had to play a driver dance to choose between fast charge vs RA FTDI driver use it may help make progress beyond the thought of 'it doesn't work'. Contacting the manufacturer of that driver/software may help too if an update didn't resolve it already. There may be a way to 'blacklist' the FTDI connection from being handled through it (manufacturer would know) or a way to disable the fast charge capability through a normal user interface or 'maybe' possible by disabling through something like systernals autoruns (won't vouch for this as it may break things bad depending on their code).