This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TUSB7340 issue with Access Virus TI2

Other Parts Discussed in Thread: TUSB7340

Hello. I have big problems with my Silverstone EC04 USB3 card (TUSB7340) and music synthesizer Access Virus TI2. When I plug Virus TI2 into USB3 card port I have a BSOD, also Windows 7 goes to BSOD during boot up if Virus TI2 connected to Silverstone EC04. With on-board USB3 Hostchip (ASMedia 104x) my Virus TI2 works fine.

The Support of the Access Music says this "As I mentioned already in my earlier email the BSOD is not just caused by our driver, but also the drivers for this PCI card, so this is definitely something you need to get in touch with the manufacturer, especially if the Virus works fine on an on-board USB port". Drivers for TUSB7340 was taken on this site and up to date, v. 1.16.2.0.

Minidumps of BSOD is here: http://www.sendspace.com/file/7nuv1t

 0005.Minidump.zip

 

Please, help me.

  • Hello Denis,

     

                    We have a test driver that solve a similar behavior using other HD audio devices, could you please provide us a contact e-mail were we can send you this test driver?

     We are planning to add this changes in to our next official driver release meanwhile please test the driver and verify if you problem is solve.

     

    Regards,

    Roberto.             

  • Yes, my email is skydan (at) bk.ru

  • Hi Roberto! When a new driver will be available for me?

  • Hello Denis,

     

                    I already sent you the test driver to your personal e-mail.

     

                    Please note that this drive is only for testing propose those changes will be included on the next official release.

     

    Regards,

    Roberto

  • I installed this driver, but situation is still bad. Win 7 goes to BSOD when I plug in my synthesizer.

    Here are dumps.

    6404.Minidump.zip

  • Hello Denis,

     

                    Taking a look to the attached Memory Dumps it’s pointing that the problem is caused by the VirusUSB.sys driver and not by the TI driver. The warning and errors displayed that make reference to the tihub3.sys driver are only because you have not the driver symbols loaded on your system. (those symbols are only for debug purposes).

     

                    Please take al look to the following memory dump info.

     

     

                    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    Use !analyze -v to get detailed debugging information.

     

    BugCheck D1, {fffffa8055a00018, 2, 0, fffff8800ae2ecb1}

     

    *** WARNING: Unable to verify timestamp for VirusUSB.sys

    *** ERROR: Module load completed but symbols could not be loaded for VirusUSB.sys

    *** WARNING: Unable to verify timestamp for tihub3.sys

    *** ERROR: Module load completed but symbols could not be loaded for tihub3.sys

    Probably caused by : VirusUSB.sys ( VirusUSB+2ecb1 )

     

    Followup: MachineOwner

    ---------

     

    0: kd> !analyze -v

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    An attempt was made to access a pageable (or completely invalid) address at an

    interrupt request level (IRQL) that is too high.  This is usually

    caused by drivers using improper addresses.

    If kernel debugger is available get stack backtrace.

    Arguments:

    Arg1: fffffa8055a00018, memory referenced

    Arg2: 0000000000000002, IRQL

    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

    Arg4: fffff8800ae2ecb1, address which referenced memory

     

    Debugging Details:

    ------------------

     

     

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b8100

    GetUlongFromAddress: unable to read from fffff800032b81c0

     fffffa8055a00018 Nonpaged pool

     

    CURRENT_IRQL:  2

     

    FAULTING_IP:

    VirusUSB+2ecb1

    fffff880`0ae2ecb1 ??              ???

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

     

    BUGCHECK_STR:  0xD1

     

    PROCESS_NAME:  System

     

    ANALYSIS_VERSION: 6.3.9456.0 (debuggers(dbg).130703-2335) x86fre

     

    TRAP_FRAME:  fffff88006bfe450 -- (.trap 0xfffff88006bfe450)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=fffffa80200a5c60 rbx=0000000000000000 rcx=fffffa801f6c6270

    rdx=0000000036339da0 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff8800ae2ecb1 rsp=fffff88006bfe5e0 rbp=0000000000000000

     r8=fffffa801fc33650  r9=0000000000000030 r10=fffff8000300b000

    r11=fffff88006bfe728 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0         nv up ei pl nz na po nc

    VirusUSB+0x2ecb1:

    fffff880`0ae2ecb1 ??              ???

    Resetting default scope

     

    LAST_CONTROL_TRANSFER:  from fffff800030801a9 to fffff80003080c00

     

    STACK_TEXT: 

    fffff880`06bfe308 fffff800`030801a9 : 00000000`0000000a fffffa80`55a00018 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

    fffff880`06bfe310 fffff800`0307ee20 : fffffa80`200a5e9b fffffa80`200a5c60 fffffa80`200a5c60 fffffa80`200a5e9b : nt!KiBugCheckDispatch+0x69

    fffff880`06bfe450 fffff880`0ae2ecb1 : fffff880`01b19ced fffff880`06bfe630 fffff880`0a33e890 fffff880`0ae2fd9c : nt!KiPageFault+0x260

    fffff880`06bfe5e0 fffff880`01b19ced : fffff880`06bfe630 fffff880`0a33e890 fffff880`0ae2fd9c fffffa80`20e073b0 : VirusUSB+0x2ecb1

    fffff880`06bfe5e8 fffff880`06bfe630 : fffff880`0a33e890 fffff880`0ae2fd9c fffffa80`20e073b0 fffffa80`200a5c60 : cng!g_AesCtrSafeCtx <PERF> (cng+0x6aced)

    fffff880`06bfe5f0 fffff880`0a33e890 : fffff880`0ae2fd9c fffffa80`20e073b0 fffffa80`200a5c60 fffff880`0a350940 : 0xfffff880`06bfe630

    fffff880`06bfe5f8 fffff880`0ae2fd9c : fffffa80`20e073b0 fffffa80`200a5c60 fffff880`0a350940 fffff880`06bfe798 : tihub3+0x45890

    fffff880`06bfe600 fffffa80`20e073b0 : fffffa80`200a5c60 fffff880`0a350940 fffff880`06bfe798 fffffa80`20e07370 : VirusUSB+0x2fd9c

    fffff880`06bfe608 fffffa80`200a5c60 : fffff880`0a350940 fffff880`06bfe798 fffffa80`20e07370 fffffa80`1fc33650 : 0xfffffa80`20e073b0

    fffff880`06bfe610 fffff880`0a350940 : fffff880`06bfe798 fffffa80`20e07370 fffffa80`1fc33650 00000000`00000000 : 0xfffffa80`200a5c60

    fffff880`06bfe618 fffff880`06bfe798 : fffffa80`20e07370 fffffa80`1fc33650 00000000`00000000 fffff800`030845c1 : tihub3+0x57940

    fffff880`06bfe620 fffffa80`20e07370 : fffffa80`1fc33650 00000000`00000000 fffff800`030845c1 00000000`00000000 : 0xfffff880`06bfe798

    fffff880`06bfe628 fffffa80`1fc33650 : 00000000`00000000 fffff800`030845c1 00000000`00000000 fffffa80`200a5c60 : 0xfffffa80`20e07370

    fffff880`06bfe630 00000000`00000000 : fffff800`030845c1 00000000`00000000 fffffa80`200a5c60 fffffa80`1fc33650 : 0xfffffa80`1fc33650

     

     

    STACK_COMMAND:  kb

     

    FOLLOWUP_IP:

    VirusUSB+2ecb1

    fffff880`0ae2ecb1 ??              ???

     

    SYMBOL_STACK_INDEX:  3

     

    SYMBOL_NAME:  VirusUSB+2ecb1

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: VirusUSB

     

    IMAGE_NAME:  VirusUSB.sys

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  50116785

     

    FAILURE_BUCKET_ID:  X64_0xD1_VirusUSB+2ecb1

     

    BUCKET_ID:  X64_0xD1_VirusUSB+2ecb1

     

    ANALYSIS_SOURCE:  KM

     

    FAILURE_ID_HASH_STRING:  km:x64_0xd1_virususb+2ecb1

     

    FAILURE_ID_HASH:  {62c24f18-58b4-2dd6-4fd1-2e115a2e25ad}

     

    Followup: MachineOwner

    ---------

     

    Regards,

    Roberto.