Hello all,
Since I got my new desktop with Windows 8 in December, I have been running into problems with the Virus TI.
When I am working in projects on FL Studio 10 with the Virus TI's plug-ins loaded and the Virus TI connected, I am getting random BSODs.
There's not really a specific action on how to trigger the BSOD, but it mainly happens when I am making a change in the plug-in (turning a knob) or playing the loaded preset of the Virus TI in the sequencer.
Here are the specifications of my desktop:
Windows 8 64-bit
Intel Core i7 3770 @ 3.40 GHz
8GB DDR3 RAM
Acer Predator G3620 (model of the desktop and motherboard according to Belarc Advisor)
FL Studio 10 running in 32-bit
I had a BSOD earlier when using the Virus TI and FL Studio but I solved this problem by updating my external soundcard's driver. However, I have no idea what the problem is here as I tried to re-install all the software and drivers from the Virus.
Here is the information about the BSOD I got via the Debugging Tools:
Edit: I am sorry if the code below is a bit messy. The debugging report didn't use any breaks after all sentences or the forum doesn't recognize the breaks.
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\020313-14250-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*C:\Windows\Symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows 8 Kernel Version 9200 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9200.16461.amd64fre.win8_gdr.121119-1606Machine Name:Kernel base = 0xfffff802`ec405000 PsLoadedModuleList = 0xfffff802`ec6cfa80Debug session time: Sun Feb 3 19:12:48.787 2013 (UTC + 1:00)System Uptime: 0 days 5:16:31.424Loading Kernel Symbols..........................................................................................................................................................................Loading User SymbolsLoading unloaded module list.......................******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 44, {fffffa8008053b80, f7a, 0, 0}
Probably caused by : USBXHCI.SYS ( USBXHCI!TransferRing_CompleteIsochTD+1f1 )
Followup: MachineOwner---------
3: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************
MULTIPLE_IRP_COMPLETE_REQUESTS (44)A driver has requested that an IRP be completed (IoCompleteRequest()), butthe packet has already been completed. This is a tough bug to find becausethe easiest case, a driver actually attempted to complete its own packettwice, is generally not what happened. Rather, two separate drivers eachbelieve that they own the packet, and each attempts to complete it. Thefirst actually works, and the second fails. Tracking down which driversin the system actually did this is difficult, generally because the trailsof the first driver have been covered by the second. However, the driverstack for the current request can be found by examining the DeviceObjectfields in each of the stack locations.Arguments:Arg1: fffffa8008053b80, Address of the IRPArg2: 0000000000000f7aArg3: 0000000000000000Arg4: 0000000000000000
Debugging Details:------------------
IRP_ADDRESS: fffffa8008053b80
FOLLOWUP_IP: USBXHCI!TransferRing_CompleteIsochTD+1f1fffff880`087642ed 488d4b48 lea rcx,[rbx+48h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x44
PROCESS_NAME: System
CURRENT_IRQL: 2
TAG_NOT_DEFINED_c000000f: FFFFF88000AA5FB0
LAST_CONTROL_TRANSFER: from fffff802ec54d761 to fffff802ec480340
STACK_TEXT: fffff880`00a9e4d8 fffff802`ec54d761 : 00000000`00000044 fffffa80`08053b80 00000000`00000f7a 00000000`00000000 : nt!KeBugCheckExfffff880`00a9e4e0 fffff880`012dae9d : 00000000`00000001 fffffa80`10cfd000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xac5afffff880`00a9e5c0 fffff880`012edb02 : fffffa80`08053b80 fffff880`00000001 fffffa80`10cfd020 fffffa80`11346680 : Wdf01000!FxRequest::CompleteInternal+0x65dfffff880`00a9e650 fffff880`087642ed : fffffa80`11346680 fffffa80`10cfd3d0 00000000`00000001 fffff802`ec4ac1f3 : Wdf01000!imp_WdfRequestComplete+0x176fffff880`00a9e6b0 fffff880`08765fe0 : fffffa80`11346810 fffffa80`11346810 fffffa80`0c059cc0 fffffa80`10cb5928 : USBXHCI!TransferRing_CompleteIsochTD+0x1f1fffff880`00a9e720 fffff880`08756205 : fffffa80`0c059cc0 fffffa80`0c059cc0 00000000`00000000 00000000`00000000 : USBXHCI!TransferRing_TransferEventHandler+0x14dcfffff880`00a9e7e0 fffff880`0876e78c : 00000000`00000004 fffffa80`0c059cc0 00000000`000001e0 00000000`00000000 : USBXHCI!Endpoint_TransferEventHandler+0x5dfffff880`00a9e860 fffff880`08758f5e : 00000000`00000260 fffffa80`0c059cc0 fffffa80`00000002 fffff802`00000002 : USBXHCI!UsbDevice_TransferEventHandler+0x7cfffff880`00a9e8b0 fffff880`01361717 : fffffa80`0bc40df8 fffff802`ec5d8653 0000057f`f43bf298 fffff880`00a9e9f0 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0x40efffff880`00a9e980 fffff802`ec4756a8 : fffff880`00a77f00 fffff880`00a77f00 fffffa80`0bc40df8 fffff880`00a9ea00 : Wdf01000!FxInterrupt::DpcHandler+0xc3fffff880`00a9e9b0 fffff802`ec4a71b0 : fffff880`012cf6d4 00001fa0`00ff00ff 00000000`00000000 00000000`00000002 : nt!KiExecuteAllDpcs+0x198fffff880`00a9eaf0 fffff802`ec4ab67a : fffff880`00a75180 fffff880`00a75180 00000000`00000000 fffff880`00a80f40 : nt!KiRetireDpcList+0xd0fffff880`00a9ec60 00000000`00000000 : fffff880`00a9f000 fffff880`00a99000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: USBXHCI!TransferRing_CompleteIsochTD+1f1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBXHCI
IMAGE_NAME: USBXHCI.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 505ab2a7
BUCKET_ID_FUNC_OFFSET: 1f1
FAILURE_BUCKET_ID: 0x44_USBXHCI!TransferRing_CompleteIsochTD
BUCKET_ID: 0x44_USBXHCI!TransferRing_CompleteIsochTD
Followup: MachineOwner---------
Alles anzeigen
I hope you guys can help me out with solving the problem! I love the Virus TI and I want to use it's amazing sound in every project I have!
