Blue Screen of Death, or BSOD

New members questions

Posts: 75
Joined: Mon Oct 31, 2016 12:33 pm
PostPosted: Sun Nov 13, 2016 7:19 am
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
Last edited by robmwpropane on Sun Nov 13, 2016 8:28 am, edited 1 time in total.
Image

Posts: 75
Joined: Mon Oct 31, 2016 12:33 pm
PostPosted: Sun Nov 13, 2016 7:56 am
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....
Image

Posts: 12288
Joined: Fri Mar 18, 2011 6:47 pm
PostPosted: Sun Nov 13, 2016 10:58 am
Humm.
Never heard of this.
Try downloading and installing the latest driver from the manufacturer.
http://www.ftdichip.com/Drivers/CDM/CDM21224_Setup.zip
Roberto.

Posts: 75
Joined: Mon Oct 31, 2016 12:33 pm
PostPosted: Sun Nov 13, 2016 11:16 am
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...
Image

Posts: 75
Joined: Mon Oct 31, 2016 12:33 pm
PostPosted: Sun Nov 13, 2016 1:24 pm
Anybody? Man I'm stumped. I've spent all day doing everything I can find:(
Image

Posts: 75
Joined: Mon Oct 31, 2016 12:33 pm
PostPosted: Sun Nov 13, 2016 7:21 pm
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...
Image

Posts: 12288
Joined: Fri Mar 18, 2011 6:47 pm
PostPosted: Sun Nov 13, 2016 7:50 pm
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.
Roberto.

Posts: 75
Joined: Mon Oct 31, 2016 12:33 pm
PostPosted: Sun Nov 13, 2016 8:27 pm
rimai wrote: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
Image

Posts: 12288
Joined: Fri Mar 18, 2011 6:47 pm
PostPosted: Sun Nov 13, 2016 9:01 pm
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?
Roberto.

Posts: 75
Joined: Mon Oct 31, 2016 12:33 pm
PostPosted: Mon Nov 14, 2016 3:47 am
rimai wrote: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......
Image
Next

Return to For New Members

Who is online

Users browsing this forum: No registered users and 1 guest

cron