GSOD when plug in USB device using FTDI drivers

When I plug in a device via USB the WIN10 OS immediately generates stopcode error: NOMORE_IRP_STACK_LOCATIONS (green screen) and machine reboots or freezes.

WIN10 Pro x64, OS Insider build 19631, release 200514_1410. Driver installations of course don't appear in the device manager Ports or USB Controller lines because they are never installed.

The device is designed to use FTDI drivers only. Other USB connected devices that work with Microsoft drivers install and operate correctly.

Any suggestions on how to resolve this problem?

Submit feedback: Microsoft Insiders feeback hub

See posting instructions.

Posting Instructions: BSOD - Posting Instructions

As zbook states - submit feedback to Insider Hub. It's the only way that this'll be fixed if it's an Insider build issue.

We can work on fixing Insider builds - but they may not be fixable in that particular build.
If that's the case, then I'd suggest downgrading to an earlier build where it worked - then waiting for the next build or two before updating again (keep disk images to make it easier to revert).

Thank you for the replies.

As requested, attached is the V2 Log Collector zipped file for my machine.

Dean

It is essential to keep Insider builds updated. Be sure to visit Windows Update daily.
What USB device is this? Manufacturer's name and model number will be helpful.

No memory dumps in the uploaded reports.

BIOS/UEFI version 2101 dates from 2014:
- visit the Asus support website for your motherboard and see if there's a more recent version available. If there is, please install it.
- check with Asus to ensure that they support Windows 10 on this motherboard
- as long as you're at the support site - update your chipset drivers and any other drivers/utilities that are available.

WER entries only go back to 22 May.
Are you using a disk cleaning utility? If so, please stop using it while we're troubleshooting.

Please force another crash and check C:\Windows\Minidump for any generated reports (file name will start with the current date). If you can, note the error name/number on the GSOD and let us know what it is.

Also check C:\Windows for MEMORY.DMP. It'll be very large. If there isn't anything in the Minidump folder, then Zip MEMORY.DMP up and upload it to a free file-hosting site (I prefer OneDrive or Google Drive) and post a link here for us to download it.

Update BIOS - CROSSHAIR V FORMULA-Z Driver & Tools | Motherboards | ASUS Global

Uninstall: Driver Easy 5.6.14
Uninstall any drivers installed using this software.

The logs displayed that the OS was installed on 5/22.
There were abnormal shutdowns seen in the log files.
BSOD were not seen in the collected files.

For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive


Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread


Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Thank you all for your inputs they were very helpful for me to focus on potential solutions. Here is the solution that I found.

Solution:
In “Control Panel/Programs and Features/Uninstall or change a program”, the program “ASMedia USB3.0 eXtensible Host Controller” program was removed. Not sure why it was there.

Now, desired operation results as follows, upon plugging the target device into a USB3.0 port:
a. In “Device Manager/Universal Serial Bus controllers”: the “FTDI USB Serial Converter A” and “FTDI USB Serial Converter B” install correctly.
b. In “Ports (COM & LPT)”: the “FTDI USB Serial Port (COM3)” and “FTDI USB Serial Port (COM4)” install correctly.

There is no longer a "NOMORE_IRP_STACK_LOCATIONS" GSOD when I plug in the target device and the device works as it should.

Dean

The V2 logs were no longer present to view files.
The asmedia drivers appear to be the misbehaving drivers.

Thank you for the follow up.

You're welcome.