Decklink.sys BSOD on HP Z800 w/Adobe CS6 (minidumps inside)

Blackmagic design Decklink studio 2 sd/h...
August 25, 2014 at 21:03:42
Specs: Windows 7 Professional, X5550 x 2 / 24GB
Dear all:

Preface: Blackmagic Design support hasn't been of any assistance (common, apparently), so I thought I'd try here. The problem happens when running Adobe Premiere Pro or After Effects CS6. I do not believe it to be a PP/AE problem as much as a Blackmagic problem, but I'm hoping someone here might be able to read the minidump better than I:

I've seen a few Blackmagic Decklink users (not to mention BMD Intensity Pro users) mention BSOD issues with their cards, particularly when using PP/AE (much less discussion about AVID Media Composer). Thinking all would be fine to install a Decklink Studio 2 in my HP Z800 (a certified workstation by Blackmagic), I went ahead and installed the card in one of the 16x PCIe slots.

I installed the Blackmagic drivers ("Desktop Video 10.1.2") from the BMD site, set video output on PP to include Blackmagic Playback and went to work. This setup seemed to work fine for about a week, until Premiere Pro locked up when playing back a sequence. A PROCESS_HAS_LOCKED_PAGES BSOD came up.

I tried to replicate the BSOD, and had no problem coaxing PP to lock up after playing the sequence once or twice, causing the BSOD again. Output from the Decklink to HDMI or SDI reflected the same lockup on my Sony LMD-940W field monitor via either the HDMI or SDI input. I was able to replicate the BSOD 3 times.

Additionally, RAM rendering in AE would (and still does without BSOD'ing) render two frames in a loop unless the output to the Decklink is shut off.

This is the third of the three minidump of the three BSODs:


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

Use !analyze -v to get detailed debugging information.

BugCheck 76, {0, fffffa80172b6b30, 1126, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+17dd6 )

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

8: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PROCESS_HAS_LOCKED_PAGES (76)
Caused by a driver not cleaning up correctly after an I/O.
Arguments:
Arg1: 0000000000000000, Locked memory pages found in process being terminated.
Arg2: fffffa80172b6b30, Process address.
Arg3: 0000000000001126, Number of locked pages.
Arg4: 0000000000000000, Pointer to driver stacks (if enabled) or 0 if not.
Issue a !search over all of physical memory for the current process pointer.
This will yield at least one MDL which points to it. Then do another !search
for each MDL found, this will yield the IRP(s) that point to it, revealing
which driver is leaking the pages.
Otherwise, set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\TrackLockedPages to a DWORD 1 value and reboot. Then the system
will save stack traces so the guilty driver can be easily identified.
When you enable this flag, if the driver commits the error again you will
see a different bugcheck - DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (0xCB) -
which can identify the offending driver(s).

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


PROCESS_NAME: Adobe Premiere

DEFAULT_BUCKET_ID: DRIVER_FAULT_0x76

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0x76

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER: from fffff800031ff989 to fffff80002ec4c00

STACK_TEXT:
fffff880`0e0d6a38 fffff800`031ff989 : 00000000`00000076 00000000`00000000 fffffa80`172b6b30 00000000`00001126 : nt!KeBugCheckEx
fffff880`0e0d6a40 fffff800`0317e677 : fffffa80`172b6b30 fffffa80`12845de0 fffffa80`00000000 fffffa80`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17dd6
fffff880`0e0d6a80 fffff800`02ecde44 : 00000000`00000000 fffffa80`15ed7060 fffffa80`172b6b00 00000000`00000000 : nt!PspProcessDelete+0x177
fffff880`0e0d6ae0 fffff800`031bd2d4 : fffffa80`15ed7060 00000000`00000000 fffffa80`2a1f45f0 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`0e0d6b40 fffff800`031bd884 : 00000000`00000100 fffffa80`15ed7060 fffff8a0`03659430 00000000`00000100 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`0e0d6bd0 fffff800`02ec3e93 : fffffa80`2a1f45f0 fffff880`0e0d6ca0 00000000`00000000 00000000`00000000 : nt!ObpCloseHandle+0x94
fffff880`0e0d6c20 00000000`77ca140a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00bff268 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ca140a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::NNGAKEGL::`string'+17dd6
fffff800`031ff989 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::NNGAKEGL::`string'+17dd6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5147d9c6

IMAGE_VERSION: 6.1.7601.18113

FAILURE_BUCKET_ID: X64_0x76_Adobe_Premiere_nt!_??_::NNGAKEGL::_string_+17dd6

BUCKET_ID: X64_0x76_Adobe_Premiere_nt!_??_::NNGAKEGL::_string_+17dd6

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x76_adobe_premiere_nt!_??_::nngakegl::_string_+17dd6

FAILURE_ID_HASH: {8b65707a-8f79-c444-0cea-e6c8118a263d}

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

Since that wasn't too specific, I turned on Windows 7's Driver Verifier. This time, the dump file traced the problem to decklink.sys:

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {7a, 2, 2e0000, fffffa80173c4660}

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

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

8: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 000000000000007a, MmUnmapLockedPages called when not at APC_LEVEL or below.
Arg2: 0000000000000002, current IRQL
Arg3: 00000000002e0000, virtual address being unmapped
Arg4: fffffa80173c4660, MDL address

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


BUGCHECK_STR: 0xc4_7a

CURRENT_IRQL: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: DesktopVideoHe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER: from fffff800033564ec to fffff80002ec8c00

STACK_TEXT:
fffff880`0983a7f8 fffff800`033564ec : 00000000`000000c4 00000000`0000007a 00000000`00000002 00000000`002e0000 : nt!KeBugCheckEx
fffff880`0983a800 fffff800`0336a62c : fffff880`05a701af fffff880`05a6b54f 00000000`002be900 fffffa80`16faeda0 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0983a840 fffff880`05a70206 : fffffa80`1bf01590 fffffa80`178fa590 fffffa80`18a67290 00000000`002be900 : nt!VerifierMmUnmapLockedPages+0x4c
fffff880`0983a880 fffffa80`1bf01590 : fffffa80`178fa590 fffffa80`18a67290 00000000`002be900 fffffa80`16faeda0 : DeckLink+0x7206
fffff880`0983a888 fffffa80`178fa590 : fffffa80`18a67290 00000000`002be900 fffffa80`16faeda0 fffff880`05cc6825 : 0xfffffa80`1bf01590
fffff880`0983a890 fffffa80`18a67290 : 00000000`002be900 fffffa80`16faeda0 fffff880`05cc6825 fffffa80`16fac180 : 0xfffffa80`178fa590
fffff880`0983a898 00000000`002be900 : fffffa80`16faeda0 fffff880`05cc6825 fffffa80`16fac180 fffffa80`18a67248 : 0xfffffa80`18a67290
fffff880`0983a8a0 fffffa80`16faeda0 : fffff880`05cc6825 fffffa80`16fac180 fffffa80`18a67248 fffffa80`18a67010 : 0x2be900
fffff880`0983a8a8 fffff880`05cc6825 : fffffa80`16fac180 fffffa80`18a67248 fffffa80`18a67010 fffff880`05a702e7 : 0xfffffa80`16faeda0
fffff880`0983a8b0 fffff800`03372860 : fffff880`0983a9c0 fffff880`05cc6a0f 00000000`00000000 00000000`00000001 : ksthunk!CKernelFilterDevice::DispatchIrp+0x11d
fffff880`0983a910 fffff880`05cc6825 : fffffa80`18a67248 fffffa80`18a67290 fffffa80`16faef80 fffffa80`16faed07 : nt!IovCallDriver+0xa0
fffff880`0983a970 fffff800`03372860 : fffffa80`18a67010 fffffa80`18b46060 fffffa80`00000000 fffffa80`16faeda0 : ksthunk!CKernelFilterDevice::DispatchIrp+0x11d
fffff880`0983a9d0 fffff800`031d350f : fffffa80`18a67010 fffffa80`18b46060 00000000`00000000 fffffa80`1bc88df0 : nt!IovCallDriver+0xa0
fffff880`0983aa30 fffff800`031c1504 : 00000000`00000000 fffffa80`18b46060 fffffa80`00000001 fffffa80`1bc88df0 : nt!IopCloseFile+0x11f
fffff880`0983aac0 fffff800`031c12c1 : fffffa80`18b46060 fffffa80`00000001 fffff8a0`020774f0 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`0983ab40 fffff800`031c1884 : 00000000`000001ec fffffa80`18b46060 fffff8a0`020774f0 00000000`000001ec : nt!ObpCloseHandleTableEntry+0xb1
fffff880`0983abd0 fffff800`02ec7e93 : fffffa80`18b73440 fffff880`0983aca0 00000000`7efa7000 00000000`00000000 : nt!ObpCloseHandle+0x94
fffff880`0983ac20 00000000`7765140a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`002be028 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7765140a


STACK_COMMAND: kb

FOLLOWUP_IP:
DeckLink+7206
fffff880`05a70206 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: DeckLink+7206

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: DeckLink

IMAGE_NAME: DeckLink.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53eacf78

FAILURE_BUCKET_ID: X64_0xc4_7a_VRF_DeckLink+7206

BUCKET_ID: X64_0xc4_7a_VRF_DeckLink+7206

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xc4_7a_vrf_decklink+7206

FAILURE_ID_HASH: {d8f7494f-3acd-0994-ef4b-48988da936ae}

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

And there I am. I've been trying to research what that dump file has to say, but actual editing work has kept me busy with paying jobs rather than on the internet trying to track down the issue. I've deselected Blackmagic playback in both PP and AE in the meantime, and all is well.

Anyone run across this before and found a solution? Because "eBay the P.O.S. Decklink card because of lousy driver code and put money down for a Quadro SDI" appears to be a pretty sound solution at this point.

Best,

-Kurt


See More: Decklink.sys BSOD on HP Z800 w/Adobe CS6 (minidumps inside)

Report •

#1
August 26, 2014 at 01:13:21
Have you been here?

Bug Check 0x76: PROCESS_HAS_LOCKED_PAGES
http://msdn.microsoft.com/en-us/lib...

Debugging memory leaks - DRIVER_VERIFIER_DETECTED_VIOLATION (C4): 0x62
http://msdn.microsoft.com/en-us/lib...


Report •

#2
August 26, 2014 at 04:21:04
The first link is what gave me the information about running the Driver Verifier for the second minidump.

I'll take a look at the page for debugging memory leaks when I have a chance.

-Kurt


Report •

#3
September 2, 2014 at 04:06:20
Per Blackmagic's request, I performed a clean wipe of v10.1.2 and installed the recently released v10.1.4. Fixed.

-Kurt


Report •

Related Solutions

#4
September 2, 2014 at 04:17:10
"Per Blackmagic's request, I performed a clean wipe of v10.1.2 and installed the recently released v10.1.4. Fixed"
Good news, thanks for getting back.

Report •

#5
September 5, 2014 at 20:19:22
Not quite done. The problem returned in a less severe manner.
I recently updated both my BMCC and BMPCC firmware with Blackmagic
Camera Utility v1.9.3. In doing so, the installer for the Camera Utility requested that I
remove Desktop Video (ridiculous way of packaging drivers, IMO; probably the source of the problem).

Having no other choice, I removed Desktop Video and proceeded with the firmware update.

Now, somehow, when doing this, the driver components from which the Decklink runs are somehow retained in the Camera Utility firmware/driver bundle, and - indeed - the Decklink's control panel through Windows + the "Blackmagic Playback" function in Premiere Pro remained available.

However, upon trying to edit today, I had some strange problems where rendered or yellow-bar H.264 footage began to hang up Premiere Pro. The Decklink
would not output any footage at all too. This is more or less what it would do
when it would BSOD, but it didn't BSOD initially.

I tried turning off Blackmagic Playback. Premiere Pro returned to normal
function. Turn it on, and the symptoms would resume.

I went ahead and turned Blackmagic Playback off in PP and AE for the afternoon so I could get some work done.

This evening, I proceeded to remove the remains of Desktop Video v10.1.4 from the computer - but Windows showed no evidence of the prior installation; only the Blackmagic Camera Utility.

Feeling adventurous - and also knowing I'd get a proper uninstaller this way - I installed Blackmagic's Desktop Video v10.2.1 without uninstalling the Utility or removing any known drivers manually, restarted, then started up PP and AE. I loaded up a project, turned Blackmagic Playback back on, and let the files load. I hit the play button and PP began playing rendered footage to the monitors and the Decklink.

This went smoothly for two 5-second clips. Then the video and audio freezed in PP, though the audio meters kept running. I tried restarting. AE wouldn't send anything out to the Decklink at all, nor even begin to play footage. I tried PP again, and it freezed the same way as before; what's more, I couldn't kill the process or process tree from the Task Manager, and resorted to doing so through Process Explorer.

Process Explorer effectively shut down the Premiere Pro process tree - and immediately BSODed the moment PP's window finally closed. I received a very familiar BSOD:

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

Use !analyze -v to get detailed debugging information.

BugCheck CB, {fffff880058d9a06, 0, fffffa8013173000, 1126}

Unable to load image \SystemRoot\system32\DRIVERS\DeckLink.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for DeckLink.sys
*** ERROR: Module load completed but symbols could not be loaded for DeckLink.sys
Probably caused by : DeckLink.sys ( DeckLink+33a06 )

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

8: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (cb)
Caused by a driver not cleaning up completely after an I/O.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff880058d9a06, The calling address in the driver that locked the pages or if the
IO manager locked the pages this points to the dispatch routine of
the top driver on the stack to which the IRP was sent.
Arg2: 0000000000000000, The caller of the calling address in the driver that locked the
pages. If the IO manager locked the pages this points to the device
object of the top driver on the stack to which the IRP was sent.
Arg3: fffffa8013173000, A pointer to the MDL containing the locked pages.
Arg4: 0000000000001126, The number of locked pages.

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


FAULTING_IP:
DeckLink+33a06
fffff880`058d9a06 33c0 xor eax,eax

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xCB

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER: from fffff8000321296f to fffff80002ed7c00

STACK_TEXT:
fffff880`0ac29a38 fffff800`0321296f : 00000000`000000cb fffff880`058d9a06 00000000`00000000 fffffa80`13173000 : nt!KeBugCheckEx
fffff880`0ac29a40 fffff800`03191677 : fffffa80`2ea33620 fffffa80`12845d90 fffffa80`00000000 fffffa80`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17dbc
fffff880`0ac29a80 fffff800`02ee0e44 : 00000000`00000000 fffffa80`2ea33620 fffffa80`2ea335f0 fffff800`032674f5 : nt!PspProcessDelete+0x177
fffff880`0ac29ae0 fffff800`02fde709 : fffffa80`2ea33620 fffffa80`2f546000 fffffa80`2f546ff0 fffffa80`2f546fe8 : nt!ObfDereferenceObject+0xd4
fffff880`0ac29b40 fffff800`0332bcce : fffffa80`000004e9 fffffa80`12fd0000 fffffa80`2ea33620 fffffa80`2f546ff0 : nt!MmFreeAccessPfnBuffer+0x29
fffff880`0ac29b70 fffff800`0334d3f0 : fffffa80`16474b01 00000000`00000080 fffffa80`128a7040 fffff800`03064e48 : nt!PfpFlushBuffers+0x23e
fffff880`0ac29c10 fffff800`03175ede : ffffffff`ff676980 fffffa80`16474b50 fffff880`0ac29db0 fffffa80`16474b50 : nt!PfTLoggingWorker+0xe0
fffff880`0ac29d40 fffff800`02ec8906 : fffff880`0345d180 fffffa80`16474b50 fffff880`034682c0 fffff880`0ac29e40 : nt!PspSystemThreadStartup+0x5a
fffff880`0ac29d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
DeckLink+33a06
fffff880`058d9a06 33c0 xor eax,eax

SYMBOL_NAME: DeckLink+33a06

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: DeckLink

IMAGE_NAME: DeckLink.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 540818f5

FAILURE_BUCKET_ID: X64_0xCB_DeckLink+33a06

BUCKET_ID: X64_0xCB_DeckLink+33a06

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xcb_decklink+33a06

FAILURE_ID_HASH: {69c3b1e1-75e4-f125-7b90-d37fcfd10517}

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

8: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (cb)
Caused by a driver not cleaning up completely after an I/O.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff880058d9a06, The calling address in the driver that locked the pages or if the
IO manager locked the pages this points to the dispatch routine of
the top driver on the stack to which the IRP was sent.
Arg2: 0000000000000000, The caller of the calling address in the driver that locked the
pages. If the IO manager locked the pages this points to the device
object of the top driver on the stack to which the IRP was sent.
Arg3: fffffa8013173000, A pointer to the MDL containing the locked pages.
Arg4: 0000000000001126, The number of locked pages.

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


FAULTING_IP:
DeckLink+33a06
fffff880`058d9a06 33c0 xor eax,eax

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xCB

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER: from fffff8000321296f to fffff80002ed7c00

STACK_TEXT:
fffff880`0ac29a38 fffff800`0321296f : 00000000`000000cb fffff880`058d9a06 00000000`00000000 fffffa80`13173000 : nt!KeBugCheckEx
fffff880`0ac29a40 fffff800`03191677 : fffffa80`2ea33620 fffffa80`12845d90 fffffa80`00000000 fffffa80`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17dbc
fffff880`0ac29a80 fffff800`02ee0e44 : 00000000`00000000 fffffa80`2ea33620 fffffa80`2ea335f0 fffff800`032674f5 : nt!PspProcessDelete+0x177
fffff880`0ac29ae0 fffff800`02fde709 : fffffa80`2ea33620 fffffa80`2f546000 fffffa80`2f546ff0 fffffa80`2f546fe8 : nt!ObfDereferenceObject+0xd4
fffff880`0ac29b40 fffff800`0332bcce : fffffa80`000004e9 fffffa80`12fd0000 fffffa80`2ea33620 fffffa80`2f546ff0 : nt!MmFreeAccessPfnBuffer+0x29
fffff880`0ac29b70 fffff800`0334d3f0 : fffffa80`16474b01 00000000`00000080 fffffa80`128a7040 fffff800`03064e48 : nt!PfpFlushBuffers+0x23e
fffff880`0ac29c10 fffff800`03175ede : ffffffff`ff676980 fffffa80`16474b50 fffff880`0ac29db0 fffffa80`16474b50 : nt!PfTLoggingWorker+0xe0
fffff880`0ac29d40 fffff800`02ec8906 : fffff880`0345d180 fffffa80`16474b50 fffff880`034682c0 fffff880`0ac29e40 : nt!PspSystemThreadStartup+0x5a
fffff880`0ac29d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
DeckLink+33a06
fffff880`058d9a06 33c0 xor eax,eax

SYMBOL_NAME: DeckLink+33a06

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: DeckLink

IMAGE_NAME: DeckLink.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 540818f5

FAILURE_BUCKET_ID: X64_0xCB_DeckLink+33a06

BUCKET_ID: X64_0xCB_DeckLink+33a06

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0xcb_decklink+33a06

FAILURE_ID_HASH: {69c3b1e1-75e4-f125-7b90-d37fcfd10517}

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

Ok. Time to flush v10.2.1 entirely. Went to Programs & Features in the Control Panel, and uninstalled Blackmagic Desktop Video v10.2.1 with the included uninstaller.

Restarted.

Reinstalled v10.2.1.

Restarted.
Fired up PP and AE. Turned on Blackmagic Playback in PP and set it for playback in AE as well.

At first - PP jammed up and the Decklink started showing AE's content on the reference monitor when the Premiere Pro window was selected. However, the jam cleared up in about 30 seconds, and the proper footage showed up for each respective program.

So far, I've been fiddling around with both PP and AE for about 15 minutes, and the Decklink has been completely happy displaying rendered and red-bar footage from PP, and RAM previews from AE. Can't get it to complain.

It works.

That said - now that I think of it - the previous time I had this problem, I may have reinstalled Desktop Video following an installation of Camera Utility, after removing a previous version of Desktop Video.

With this in mind, I have one theory regarding the problem (and it seems the only logical one to me, though I haven't done any testing that would prove one way or another):

There must be a problematic file/driver (or registry entry, though I'm not sure that would be the case - it would seem as if Decklink.sys itself may be the culprit, or something tied to it) included with the Camera Utility installer that is shared with Desktop Video. When Desktop Video is reinstalled on top of Camera Utility, the Desktop Video installer recognizes the problematic file as a current version, and doesn't override it as it should.

However, by using the Desktop Video uninstaller, all related files - including the problematic one - are wiped. When Desktop Video is then reinstalled, it performs a clean installation without fighting previously-installed files.

I'm going to try using a logger to see what files get removed and installed with Camera Utility and Desktop Video. Perhaps I can prove or disprove this theory.

Maybe all that is needed is a simple file cleaning utility to ensure a clean installation following any installation of Camera Utility - or simply the removal of the faulty file from Camera Utility.

Hope this helps anyone out there who has experienced a similar problem. From all my Google searches, it seems as if a similar driver installation issue may affect the Intensity Pro as well.

-Kurt


Report •

#6
September 5, 2014 at 20:51:44
"There must be a problematic file/driver (or registry entry"
Worth a try using IObit on whatever you think could be the problem. Reinstall the program if it is not listed & start the uninstall again.

Use IObit Uninstaller
http://www.softpedia.com/get/Tweak/...
http://www.freewarefiles.com/IObit-...
http://www.majorgeeks.com/files/det...
http://www.iobit.com/advanceduninst...
Do a Standard Uninstall & then the Powerful Scan to remove all the lurking bits.
http://i.imgur.com/olyCkcJ.gif
http://i.imgur.com/cKc5Chi.gif
http://i.imgur.com/HuWkaZo.gif


Report •

#7
September 5, 2014 at 21:21:17
That's fine for getting the program installed cleanly, but will IObit log the files uninstalled?

I'd like to see if my theory is correct - and whether reinstalling Desktop Video after installing Camera Utility results in a failure to update a file.

-Kurt


Report •

#8
Report •

#9
September 5, 2014 at 21:45:44
I was considering ZSoft Uninstaller for logging the uninstall.

I did have one brilliant, simple program in mind that logged both files and registry entries upon installation, but I can't remember the program for the life of me. InstallSpy seems as if it may do the trick.

That said, I've been experimenting logging the installations with msiexec, but I'm wondering whether the MS logs are TOO detailed for what I'm looking for. Might need them in the future, but it seems overkill if a program can show that a single file is not getting removed (or updated) on installation or removal.

I'll continue this in the morning; too tired now.

-Kurt


Report •

#10
September 6, 2014 at 02:53:30
"I did have one brilliant, simple program in mind that logged both files and registry entries upon installation, but I can't remember the program for the life of me"

Here are some of the older tools.
InstallWatch Pro 2.5
http://installwatch-pro.en.lo4d.com/
https://www.raymond.cc/blog/downloa...
Windows 8 / 7 / Vista / XP
InstallWatch 0.6.3
http://asic-linux.com.mx/~izto/chec...

InCtrl5
http://www.freewaregeeks.com/?page=...
http://www.freewaregeeks.com/downlo...
https://www.raymond.cc/blog/downloa...
Tutorial
http://www.raymond.cc/blog/archives...
http://www.extremetech.com/article2...

SpyMe Tools
http://www.softpedia.com/get/System...
http://www.softpedia.com/progScreen...
http://www.lcibrossolutions.com/spy...
Portable SpyMe Tools
http://www.softpedia.com/get/PORTAB...

========================================================]

Newer tools.
WhatChanged
http://majorgeeks.com/What_Changed_...
http://www.vtaskstudio.com/support....
WhatChanged Portable
http://www.softpedia.com/get/PORTAB...
http://www.softpedia.com/progScreen...

Directory Monitor
http://www.softpedia.com/get/System...
http://www.softpedia.com/progScreen...
http://www.deventerprise.net/Projec...
Portable Directory Monitor
http://www.softpedia.com/get/PORTAB...

TheFolderSpy
http://www.softpedia.com/get/System...
http://www.softpedia.com/progScreen...
http://venussoftcorporation.blogspo...

Track Folder Changes
http://www.softpedia.com/get/System...
http://www.softpedia.com/progScreen...
http://trackfolderchanges.codeplex....

SpyMe Tools
http://www.softpedia.com/get/System...
http://www.softpedia.com/progScreen...
http://www.lcibrossolutions.com/spy...
Portable SpyMe Tools
http://www.softpedia.com/get/PORTAB...

FolderChangesView
http://www.softpedia.com/get/System...
http://www.softpedia.com/progScreen...
http://www.nirsoft.net/utils/folder...

Disk Pulse
http://www.softpedia.com/get/System...
http://www.softpedia.com/progScreen...
http://www.diskpulse.com/

System Explorer
http://www.softpedia.com/get/System...
http://www.softpedia.com/progScreen...
http://systemexplorer.net/
System Explorer Portable
http://www.softpedia.com/get/PORTAB...


Report •

Ask Question