Minitaur loses USB ocasionally. Only restarting it fixes

The Moog Forum Taurus, Minitaur & Sirin
1

Essentially what I’m having happen is that on rare occasions while working in Machine 2.1.1 64bit Standalone with my Minitaur (firmware version 2.1.0) connected by USB my DAW will suddenly stop playing and will not continue to play if attempted. If I unplug the power from the Minitaur and plug it back in it responds again. If I just unplug and plug back in the USB it doesn’t fix the issue and Windows pops up an “unrecognized USB device” error. If I restart Maschine, or rather, attempt, it simply doesn’t launch until I ‘reboot’ the Minitaur. I’m not running the editor while this happens.

More details:
Windows 8 64bit all up to date.
All of my midi-USB devices are running through a USB 3.0 hub to a USB 3.0 port

2

Hi there,

Andy Hughes from the Moog Service Lab here.

I will report this to our engineers for review, but as a general rule we suggest not running our devices through hubs for best results.

Please test this issue without the hub and please let me know if it persists.

You can reach me at andy@moogmusic.com


Thanks,
Andy Hughes
Service Department Manager
Moog Music, Inc.

3

Alright. I’ve since had this same issue occur with the minitaur directly connected to the motherboard (also different port). Below is from my event logs. I was not running the editor/plugin at the time. I never use it in my DAW so I’ve since removed it from Maschine’s plugin index. I will update if I get the same issue after removing it from the index.

Log Name: Application
Source: Windows Error Reporting
Date: 2014-08-13 00:01:33
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: mh-nuc
Description:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Maschine 2.exe
P2: 2.1.1.1332
P3: 534eada3
P4: dd45
P5: 134217729
P6:
P7:
P8:
P9:
P10:

Attached files:

These files may be available here:
C:\Users****\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_Maschine 2.exe_ea256ef285d1df83633f68f8bf61d43899e1df2_2abcc36a_5533564c

Analysis symbol:
Rechecking for solution: 0
Report Id: a6f2c503-22b7-11e4-8265-c03fd5630ed4
Report Status: 2048
Hashed bucket:
Event Xml:



1001
4
0
0x80000000000000

7677
Application
mh-nuc





0
AppHangB1
Not available
0
Maschine 2.exe
2.1.1.1332
534eada3
dd45
134217729












C:\Users****\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_Maschine 2.exe_ea256ef285d1df83633f68f8bf61d43899e1df2_2abcc36a_5533564c ###no minitaur.dll’s show as loaded


0
a6f2c503-22b7-11e4-8265-c03fd5630ed4
2048



Log Name: Application
Source: Windows Error Reporting
Date: 2014-08-13 00:01:50
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: mh-nuc
Description:
Fault bucket , type 0
Event Name: AppTermFailureEvent
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Temp\WER7D8B.tmpatk.kdmp
C:\Windows\Temp\WER7D8C.tmp.appcompat.txt
C:\Windows\Temp\WER7DAC.tmp.xml
C:\Windows\Temp\WER7E1A.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_00000000_cab_59877e37\memory.hdmp
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_00000000_cab_59877e37\triagedump.dmp
WERGenerationLog.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_00000000_cab_59877e37

Analysis symbol:
Rechecking for solution: 0
Report Id: ae80c931-22b7-11e4-8265-c03fd5630ed4
Report Status: 131076
Hashed bucket:
Event Xml:



1001
4
0
0x80000000000000

7678
Application
mh-nuc





0
AppTermFailureEvent
Not available
0





















C:\Windows\Temp\WER7D8B.tmpatk.kdmp
C:\Windows\Temp\WER7D8C.tmp.appcompat.txt
C:\Windows\Temp\WER7DAC.tmp.xml
C:\Windows\Temp\WER7E1A.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_00000000_cab_59877e37\memory.hdmp
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_00000000_cab_59877e37\triagedump.dmp
WERGenerationLog.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_00000000_cab_59877e37


0
ae80c931-22b7-11e4-8265-c03fd5630ed4
131076



Log Name: Application
Source: Application Hang
Date: 2014-08-13 00:02:43
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: mh-nuc
Description:
The program Maschine 2.exe version 2.1.1.1332 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 180
Start Time: 01cfb6b6a87cfdd9
Termination Time: 60000
Application Path: C:\Program Files\Native Instruments\Maschine 2\Maschine 2.exe
Report Id: a6f2c503-22b7-11e4-8265-c03fd5630ed4
Faulting package full name:
Faulting package-relative application ID:

Event Xml:



1002
2
101
0x80000000000000

7679
Application
****



Maschine 2.exe
2.1.1.1332
180
01cfb6b6a87cfdd9
60000
C:\Program Files\Native Instruments\Maschine 2\Maschine 2.exe
a6f2c503-22b7-11e4-8265-c03fd5630ed4




430072006F00730073002D0074006800720065006100640000000000

Log Name: Application
Source: SideBySide
Date: 2014-08-13 00:02:56
Event ID: 33
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: mh-nuc
Description:
Activation context generation failed for "C:\Users*\SkyDrive\Data\VstPlugins\Minitaur_Editor_3.0.0_WIN\Editor\Plugin Editor\Minitaur Editor(x86).dll". Dependent Assembly Microsoft.VC90.DebugCRT,processorArchitecture=“x86”,publicKeyToken=“1fc8b3b9a1e18e3b”,type=“win32”,version=“9.0.21022.8” could not be found. Please use sxstrace.exe for detailed diagnosis.
Event Xml:



33
2
0
0x80000000000000

7680
Application
mh-nuc



Microsoft.VC90.DebugCRT,processorArchitecture=“x86”,publicKeyToken=“1fc8b3b9a1e18e3b”,type=“win32”,version=“9.0.21022.8”


















C:\Users*\SkyDrive\Data\VstPlugins\Minitaur_Editor_3.0.0_WIN\Editor\Plugin Editor\Minitaur Editor(x86).dll