Intensity Shuttle Issue Streaming

Hey so I have a custom built computer I threw together a while ago that has the following specifications:

i7-3770k @ 3.50GHz
Asus Sabertooth Z77 Mobo
16 GB Ram
GTX 560
Asus Xonar Phoebus Sound Card
256 SSD
2T HD
2 Dell 24" monitors, HDMI
Win 7 64bit (6.1, Build 7601)
DX 11

My USB 3.0 controllers are:

Intel USB 3.0 eXtensible Host Controller (Intel 7 Series C216 Chipset Family) Driver: 1.08 (2/22/2013)
ASMedia XHCI Driver: 1.16.4.0 (11/8/2012)

I have the BlackMagic Desktop Video 9.7.1 and a BM Intensity shuttle using USB 3.0. Media Express (version 3.2) gives me no sound at all when trying to log and capture, but honestly I couldn't care less. I'm using XSplit 1.2.1303 and I can run it for about a half an hour or a bit more and then it crashes. The error is a IRQL NOT LESS OR EQUAL error and at the bottom of the blue screen it references blackmagicusbio.sys.

Does anyone have any idea why this doesn't work for me? I full uninstalled using Revo Uninstaller the BM software and XSplit, made sure my USB Controller drivers were up to date and reinstalled everything. Still happens. I use Decklink in the XSplit scene because the other one has crackled crappy sound. I also have both the XBox 360 (Black S, Model 1439) set to 720p and the BM Software set to 720p 59.94, as well as the Media Express set to 720p 59.94. Any help would be great. Thanks!

I'm encountering the same crash and BSOD as a new Intensity Shuttle USB owner. I own a Dell XPS 8500 Desktop with the following specs:

Intel Core i7 3770 3.40GHz
16GB DDR3
256GB SSD (Boot Drive)
2TB SATA HDD
AMD Radeon HD 7770
Blu-ray ROM + DVD+/-RW
Dell Wireless 1703 802.11b/g/n
Bluetooth v4.0+LE
Windows 7 Ultimate

The fault is occurring inside VidBlaster, but like the OP, it's not an instant issue. It takes about 60-90 minutes of running time before the fault crashed Windows. Please advise -- I have pasted the basic MiniDump info and a verbose analysis below -- it is pointing directly to BlackMagicUSBIO.sys as can easily be seen. Running version 9.7.1.0 and Express version 2.3.0.0. Thanks for any assistance.

- Frank



*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {30, 2, 0, fffff88012369751}

*** WARNING: Unable to verify timestamp for BlackmagicUsbIO.sys
*** ERROR: Module load completed but symbols could not be loaded for BlackmagicUsbIO.sys
Probably caused by : BlackmagicUsbIO.sys ( BlackmagicUsbIO+16751 )

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: 0000000000000030, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88012369751, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bd100
GetUlongFromAddress: unable to read from fffff800030bd1c0
0000000000000030 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
BlackmagicUsbIO+16751
fffff880`12369751 4883793000 cmp qword ptr [rcx+30h],0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: VidBlaster.exe

TAG_NOT_DEFINED_c000000f: FFFFF80000BA2FB0

TRAP_FRAME: fffff80000ba27e0 -- (.trap 0xfffff80000ba27e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa800f545e68 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88012369751 rsp=fffff80000ba2970 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000000 r10=fffff88005a32d40
r11=fffff80000ba2b58 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
BlackmagicUsbIO+0x16751:
fffff880`12369751 4883793000 cmp qword ptr [rcx+30h],0 ds:00000000`00000030=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e851a9 to fffff80002e85c00

STACK_TEXT:
fffff800`00ba2698 fffff800`02e851a9 : 00000000`0000000a 00000000`00000030 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba26a0 fffff800`02e83e20 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0f545bb8 : nt!KiBugCheckDispatch+0x69
fffff800`00ba27e0 fffff880`12369751 : fffffa80`0f545e68 fffffa80`12529000 fffffa80`0f545b30 fffffa80`0f545bb8 : nt!KiPageFault+0x260
fffff800`00ba2970 fffffa80`0f545e68 : fffffa80`12529000 fffffa80`0f545b30 fffffa80`0f545bb8 00000000`00000000 : BlackmagicUsbIO+0x16751
fffff800`00ba2978 fffffa80`12529000 : fffffa80`0f545b30 fffffa80`0f545bb8 00000000`00000000 00000000`00000000 : 0xfffffa80`0f545e68
fffff800`00ba2980 fffffa80`0f545b30 : fffffa80`0f545bb8 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`12529000
fffff800`00ba2988 fffffa80`0f545bb8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0f545b30
fffff800`00ba2990 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0c7a1580 : 0xfffffa80`0f545bb8


STACK_COMMAND: kb

FOLLOWUP_IP:
BlackmagicUsbIO+16751
fffff880`12369751 4883793000 cmp qword ptr [rcx+30h],0

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: BlackmagicUsbIO+16751

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: BlackmagicUsbIO

IMAGE_NAME: BlackmagicUsbIO.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 515110e9

FAILURE_BUCKET_ID: X64_0xD1_BlackmagicUsbIO+16751

BUCKET_ID: X64_0xD1_BlackmagicUsbIO+16751

Followup: MachineOwner
---------

Apparently, rolling back to 9.7 from 9.7.1 solved the issue -- no blue screens or crashes for 48 hours of constant uptime inside streaming applications. I read elsewhere that BM made a mistake somehow in 9.7.1 that is causing memory paging faults that didn't exist previously. Remember to:

1) Unplug the BM Intensity Shuttle;
2) Go to Control Panel and choose Programs -- uninstall the BM applications listed;
3) Restart your computer;
4) Download 9.7 from the support archive;
5) Install 9.7, still with the Shuttle unplugged;
6) Restart your computer again;
7) Plug in the Shuttle after booting is completed;
8) Allow the computer to run its installation process;
9) Restart your computer a third time; and
10) Go to your streaming application and choose the DecLink camera source (or "Intensity Shuttle" in some apps).

It's convoluted, but it did work for me.

- Frank

Does it do the same in 9.7.2?

Yes, it does if you simply uninstall and restart, installing 9.7.2 and rebooting again. going to try the method listed above.