FM9 USB Firmware V 1.02 Release

So here is what I did. Clicked on Windows Error Reporting and then ordered the list by clicking on the Time heading:

1710427497001.png

Looked for something relating to the DAW I was using, which had crashed and caused the FM9 USB to stop working (as I said earlier other things had also caused the crash, just happened to be Studio One on this occasion). This led me to:

1710427625110.png

I contacted their support and they said that Jamstix (a drum VST3 plugin) was crashing an Nvidia Ray Tracing driver, and their advice was to update the Nvidia drivers as a first option. I got lucky because that fixed the problem with the USB driver. Digging a bit deeper it turned out that the PCI Express Root Port shared by the USB 3.10 AMD extensible host controller and Nvidia graphics card had become unresponsive and that was caused by the Nvidia driver.

It gets complicated, but more often than not, updating drivers for things is a good place to start. Obviously make sure you are running latest Windows 11 23H2 (look under "About Your PC" from Start menu), especially if you are seeing ntdll.dll errors.

I'd be happy to look at the NFO file if you like.
 
So I went a while without using the FM9 as an interface just due to life/convenience of having an interface that doesn't drop audio, but I decided to give it a whirl tonight having recently installed the latest firmware. Sure enough, loaded up the next Beato interview in queue on Youtube (Vai and Satch!) and I reliably lost audio around the 10:50 mark. This was 2:21 am my time, on 4/25/2024. I'm not seeing any errors in the NFO dump from msinfo, but hopefully I'm just missing something important!

I can't upload it due to size/file type, but here's a link to it for further analysis: https://benbouchard.s3.amazonaws.com/FM9Crash.nfo
 
So the relevant entry is the one I've posted at the bottom (there is another preceding it that confirms it is FM9-Edit).

What the log also confirms is that it is a driver conflict (which we guessed anyway), because it is faulting in ntdll.dll.

It's probably a red herring but a few minutes later Windows Update tried to check for updates (possibly triggered by the failing driver), and that also failed, and it's not the first time Windows Update has failed, looking at the logs. You should probably try to sort that out anyway, just to be sure it isn't a part of the problem.

That said, the very first steps you need to take are to update the driver for your GTX1070 graphics card, and possibly your BIOS as well. You can find the relevant vendor pages here:

https://www.nvidia.com/en-us/geforce/drivers/results/221876/

https://www.asus.com/motherboards-c...helpdesk_bios?model2Name=TUF-GAMING-X570-PLUS

The Nvidia driver is dated March 05 2024, the BIOS is even more recent at 04/04/2024.

Proceed with caution. Back things up first!

If you use Bitlocker on your hard drive MAKE SURE YOU HAVE BACKED UP THE KEY!

If you aren't confident about doing the BIOS, leave it, it may be unnecessary, although personally I always like to keep mine up to date because of the fact that updating it has fixed issues for me in the past (admittedly on one occasion it also introduced an annoying bug so YMMV).

Once you've done the updates, try to get Windows Update to check for updates and make sure it works and everything is up to date and Windows Update is happy.

Then try again with the FM9, and report back :)

I also suggest that you check the drivers for the other hardware just as a matter of course, but if it's all getting too much that can wait until you've tried these first steps.

4/26/2023 2:07 AM Windows Error Reporting Fault bucket 1972135161285957847, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FM9-Edit.exe
P2: 1.1.8.0
P3: 643029fd
P4: ntdll.dll
P5: 10.0.22621.1485
P6: b7f0154a
P7: c0000005
P8: 0000000000033aba
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.43bae763-d95d-4cf1-9373-26ced6d6eef7.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6d49079f-a2dd-4c18-b88b-e70e986358dd.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7073402b-4093-49a1-9bfd-725ab5c74d6f.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f58ac8ba-941a-43c8-9b2f-76eb82b6eef6.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a240cc2b-e662-4f0d-8034-3a9c236c4920.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FM9-Edit.exe_87ee9b60bd2a13f274a9d0cfa2b7c66fdeb7c7f3_fa3b33fb_8eccddd7-85fe-4de3-a461-d56cd7851450

Analysis symbol: 
Rechecking for solution: 0
Report Id: 7dafe4e0-2913-4718-9744-973c7b7cd3b1
Report Status: 268435456
Hashed bucket: 737c15bad0100d90cb5e6e7af981d8d7
Cab Guid: 0
 
Appreciate the thorough assistance on this! BIOS and GPU updated, hopefully can give this another go in a few days. I think one thing I'll be sure to try is triggering it with Axe Edit open, and then closing Axe Edit and trying to duplicate if does still occur, just to rule that out.

In regard to the Windows update errors, that's kind of a strange one. My system is fully up to date, regularly successfully auto updates, and in all other facets of update the checks work fine and don't show any errors. My build is matching the latest here: https://learn.microsoft.com/en-us/w...lease-information#windows-11-current-versions, and if I check the update logs there was a successful defender update just this morning 🤷‍♂️
 
You must log in or register to reply here.
Back
Top Bottom