Intensity Pro BSOD HELP PLEASE!!!

Hi everyone,

So, first my specs:

AMD Phenom II 965
Gigabyte GA970A-D3
8 GB 1600MHZ RAM
AMD HD 6950


Ok, so here is my set up. Asus Monitor> Intensity Pro< Xbox (no HDMI splitter). BM Media Express 9.7.3 the problem- I have configured the BM settings (720p), for my xbox. Yes, I have made sure to set my xbox to 720p. However, when I run Media Express/Wirecast no picture. I do in fact have audio. I swapped HDMI cords so I have eliminated the simple issues. Now, the big issue, if I close Express/Wirecast with my xbox 360 still on, I get the BSOD. I tried re-installing 9.7.3/remove and replacing with earlier version/drivers. The weird part is, I randomly would have capture/full video after turning on the computer (not recent). Also, I have done endless driver updates, to the point I am not even being recommended any at ALL... So, I have officially hit a dead end for myself. The only other thing I could think of is my motherboard compatibility? However, as I said, I have had picture and more than once. I just ask, if anyone knows ANYTHING at all, please help.

Thanks!


[EDIT]: Sorry, also running Windows 7 Home Premium [EDIT]: 64-bit

By the fact you put 'x86' Would that mean you are running 32bit windows? If so then the Intensity isn't validated for 32bit, only 64bit Win 7.
You have checked the settings in the BM control panel (inside Windows Control panel) and made sure the input in there is set to the same as your source?

Thank you for your reply. I am currently running Windows 7 64-bit. As for the BM control panel, yes I verified all settings are set to 720p. As I said, I have had picture before I have up-to-date BMI drivers, windows, you name the driver, I guarantee I have it. The Intensity Pro is being recognized in my Device Manager also in BM Media Express/Wirecast. Oh, also enabled PnP with hopes that would get me somewhere... FAIL! I tried re-installing all BM drivers and still nothing. I think today I will try changing PCI-e slots... If you have any other recommendations, please throw them out there for me.

Thank you for your reply. I am currently running Windows 7 64-bit. As for the BM control panel, yes I verified all settings are set to 720p. As I said, I have had picture before I have up-to-date BMI drivers, windows, you name the driver, I guarantee I have it. The Intensity Pro is being recognized in my Device Manager also in BM Media Express/Wirecast. Oh, also enabled PnP with hopes that would get me somewhere... FAIL! I tried re-installing all BM drivers and still nothing. I think today I will try changing PCI-e slots... If you have any other recommendations, please throw them out there for me.

-well, swapping out PCI-e slots was a fail and made sure I clean installed everything. Hm, I'm starting to think a faulty card since I bought it from amazon. On that note, my brother has a intensity pro as well so later today ill try his and vice versa to see if its the card or my mother board... I figured I'd keep everyone posted!

Recent drivers have been known to cause BSODs. I recommend downgrading to BM driver version 9.6.8 until this has been confirmed as fixed.

What is your BSOD message?

I'm having a similar experience with my Gigabyte 990FXA-UD3 motherboard. Tried running multiple cards on the same motherboard, but could only get one card at a time to work. My BSOD message was:

PROCESS_HAS_LOCKED_PAGES

Don't wanna hijack your thread. Maybe I can help...

I've just installed v9.7.3 in order to support a newly acquired DeckLink Mini Recorder, alongside an Intensity Shuttle (and sometimes also an Intensity Pro) which has been 100% OK when running v9.70 (and previous drivers) on Win7 Pro 64 SP1.

I've been able to get them all installed and the drivers loading OK (after a few attempts) and everything is fine when running the BM Control panel and viewing the incoming video in Media Express. It's when trying to use the DirectShow interface in something like Adobe FMLE that the problems start. I've had more BSODs this morning than I've had in the last 12 months, and none of those were attributable to BM drivers, whereas every one of these was. Most involve the BlackmagicUsbIo.sys driver (eg DRIVER IRQL_NOT_LESS_OR_EQUAL, Stop 0x000000D1), so given that the Shuttle has been fine under previous versions I can only attribute this to the v9.7.3 driver rather than anything else in the system (which hasn't changed, not even any Windows updates).

However, despite all these BSODs, which seem to occur when trying to access/change settings or initiate communication with any of the BM devices, once they are set up (e.g. as camera sources in VidBlaster) they run fine, and I've been able to switch between three camera sources for well over an hour, using a MiniRecorder, Intensity Pro and Intensity Shuttle, so I'm hopefully that these are minor bugs which will be eliminated in the next version (or two).

Hello!!!


WE HAVE THE VERY SAME PROBLEM:

my system is:
AMD FX-8350
Gigabyte 990FXA-UD3 - the same problem persists on ASROCK 970 Pro 3
Corsair 2x8GB kits
Intensity Pro and Decklink SDI
Asus HD 7850
ssd
1TB HDD
Windows 7 SP1 64bit
Issues persist on Wirecast, Adobe flash media encoder, and in Blackmagick Media express as well


WE'VE DESTROYED 3 SETS OF RAM 2X8GB already with THESE BSOD ISSUES THAT WE'VE GET FROM BLACKMAGIC DRIVERS AND MOTHERBOARDS INTEROPERABILITY PROBLEMS.


So for a moment we've discovered that the issues are generated due to BM driver problems. At least so says windows verifier. We've contacted both: 2 times Gigabyte support - and get any normal answer to our issues, just the standard stuff "check the supported memory" , Blackmagic support - they provided with outdated supported hardware link

We've tested the system with other video card HD 5770, with no luck. Still the BSOD persists.

Never the less we've also tested system without the BM cards, and the system worked just fine.

If well get any solutions well post. Good luck BSOD brotherhood


P.S. I just forgot to mention, we've got two identical sets... Irony isn't it?


UPDATE 1: The fault is generated when only Intensity Pro is on the motherboard. DeckLink SDI seams to function properly when installed solely.

UPDATE 2: Sad news from BM Support - AMD CHIP-SETS ARE NOT SUPPORTED!!! "Of course it is not worth mentioning in recommendations!!!!"

Code: Select all

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\062113-17565-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c50670
Debug session time: Fri Jun 21 11:11:13.671 2013 (UTC + 3:00)
System Uptime: 0 days 0:01:26.013
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 76, {0, fffffa8011485b30, 83e, 0}

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

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

2: 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: fffffa8011485b30, Process address.
Arg3: 000000000000083e, 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:  MediaExpress.e

DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x76

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002dbd989 to fffff80002a82c00

STACK_TEXT: 
fffff880`08d888f8 fffff800`02dbd989 : 00000000`00000076 00000000`00000000 fffffa80`11485b30 00000000`0000083e : nt!KeBugCheckEx
fffff880`08d88900 fffff800`02d3c677 : fffffa80`11485b30 fffffa80`06cfa950 fffffa80`00000000 fffffa80`00000002 : nt! ?? ::NNGAKEGL::`string'+0x17dd6
fffff880`08d88940 fffff800`02a8be44 : 00000000`00000000 fffffa80`11485b30 fffffa80`11485b00 fffff800`02e124f5 : nt!PspProcessDelete+0x177
fffff880`08d889a0 fffff800`02b89709 : fffffa80`11485b30 fffffa80`081ef000 fffffa80`081efd08 fffffa80`081efd00 : nt!ObfDereferenceObject+0xd4
fffff880`08d88a00 fffff800`02ed6cce : fffffa80`0000020c fffffa80`082bc000 fffffa80`11485b30 fffffa80`081efd08 : nt!MmFreeAccessPfnBuffer+0x29
fffff880`08d88a30 fffff800`02ef83f0 : fffffa80`115ecb01 00000000`00000080 fffffa80`06cfb040 fffff800`02c0fe48 : nt!PfpFlushBuffers+0x23e
fffff880`08d88ad0 fffff800`02d20ede : ffffffff`ff676980 fffffa80`115ecb50 fffff880`08d88c70 fffffa80`115ecb50 : nt!PfTLoggingWorker+0xe0
fffff880`08d88c00 fffff800`02a73906 : fffff800`02bfde80 fffffa80`115ecb50 fffff800`02c0bcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`08d88c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt! ?? ::NNGAKEGL::`string'+17dd6
fffff800`02dbd989 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

FAILURE_BUCKET_ID:  X64_0x76_MediaExpress.e_nt!_??_::NNGAKEGL::_string_+17dd6

BUCKET_ID:  X64_0x76_MediaExpress.e_nt!_??_::NNGAKEGL::_string_+17dd6

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

2: 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: fffffa8011485b30, Process address.
Arg3: 000000000000083e, 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:  MediaExpress.e

DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x76

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002dbd989 to fffff80002a82c00

STACK_TEXT: 
fffff880`08d888f8 fffff800`02dbd989 : 00000000`00000076 00000000`00000000 fffffa80`11485b30 00000000`0000083e : nt!KeBugCheckEx
fffff880`08d88900 fffff800`02d3c677 : fffffa80`11485b30 fffffa80`06cfa950 fffffa80`00000000 fffffa80`00000002 : nt! ?? ::NNGAKEGL::`string'+0x17dd6
fffff880`08d88940 fffff800`02a8be44 : 00000000`00000000 fffffa80`11485b30 fffffa80`11485b00 fffff800`02e124f5 : nt!PspProcessDelete+0x177
fffff880`08d889a0 fffff800`02b89709 : fffffa80`11485b30 fffffa80`081ef000 fffffa80`081efd08 fffffa80`081efd00 : nt!ObfDereferenceObject+0xd4
fffff880`08d88a00 fffff800`02ed6cce : fffffa80`0000020c fffffa80`082bc000 fffffa80`11485b30 fffffa80`081efd08 : nt!MmFreeAccessPfnBuffer+0x29
fffff880`08d88a30 fffff800`02ef83f0 : fffffa80`115ecb01 00000000`00000080 fffffa80`06cfb040 fffff800`02c0fe48 : nt!PfpFlushBuffers+0x23e
fffff880`08d88ad0 fffff800`02d20ede : ffffffff`ff676980 fffffa80`115ecb50 fffff880`08d88c70 fffffa80`115ecb50 : nt!PfTLoggingWorker+0xe0
fffff880`08d88c00 fffff800`02a73906 : fffff800`02bfde80 fffffa80`115ecb50 fffff800`02c0bcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`08d88c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt! ?? ::NNGAKEGL::`string'+17dd6
fffff800`02dbd989 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

FAILURE_BUCKET_ID:  X64_0x76_MediaExpress.e_nt!_??_::NNGAKEGL::_string_+17dd6

BUCKET_ID:  X64_0x76_MediaExpress.e_nt!_??_::NNGAKEGL::_string_+17dd6

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



In July 2013, after some testing, I found that Asus AMD boards are generally more compatible with Blackmagic cards than my Gigabyte AMD 990FX board. In particular, I've found that one can only use an Intensity Pro card in a given card slot once per OS installation on the Gigabyte board. The PROCESS_HAS_LOCKED_PAGES error seems to be related to instances in which either (1) the card has been used on the board previously with a given OS install, but it is not in the slot it was in when the driver was installed, or (2) the card is in the same slot it previously occupied from a prior OS+driver install. In the case of (2), moving the card to a new slot will cause the card to function, but it will not function in the prior card slot ever again.

On an Asus 990X, my experience is that once the drivers are installed, the card will operate only in the slot in which it was first installed. Any change in position without reinstallation will cause the card not to function. Reinstallation of the OS and driver will allow the card to function in any slot. I say this after deleting files, cleaning registries, you name it. I've also had success with the Intensity Pro on an Asus 760G microATX, but I did no card swapping, so I can't comment on what will happen if cards are moved with that chipset.

The Gigabyte 990FX exhibits the same behavior in Microsoft Windows and Ubuntu Linux, so my suspicion is that this is a firmware issue. More specifically, it seems that the Gigabyte board either keeps a record of prior card locations, or it facilitates the card to keep that record in some manner.

My success was with the Asus M5A99X EVO R2.0. The M5A99FX PRO R2.0 seems to be a similar enough board that I'd expect similar results. The Asus Sabertooth 990FX R2.0 is likely a better overclocker that both either of the aforementioned Asus boards, and I'm cautiously optimistic that it's a winner, too.

I wish that Asus AMD ATX boards had 7 slots with a PCIe x8 or x16 on the outside edge, but they only have 6 slots, and only the Sabertooth has x8 on the edge. A working system is way more important at this point.

If there's any clarification needed, please ask. Happy to help, if I can.