BSOD only when using Blackmagic capture card

jedman1

New Member
Messages
4
So like the title says, I have a Blackmagic Intensity capture card which I sometimes use while working to output live TV to an external monitor.
I have had 4 BSOD in last 24 hrs.
The error says this (see attached pic)
The machine has been rock solid other than this. Ive done some pretty heavy After Effects work for hours on end with no crashes.
FWIW. I had a lot of trouble with Intel management interface drivers and eventually left them out. I have one PCI Simple Communications controller in Device Manager that has an exclamation mark, but other than that everything is working fine.
With the Intel drivers installed, Optimization would not work on the SSD, Explorer would hang then restart and the hard drives connected to the Intel ports would identify in device manager as jumbled messes of letters, weird stuff indeed.
I kind of feel like this could be an obvious example of....
Man goes to doctor and says "It hurts when I do this". Doctor says "Well, dont do that"....... Solved.
More interested if this is a bad install and am I wasting my time to persevere with it.
Specs are-
3930k
Gigabyte X79 UD5
32gb 1600 Ram
GTX 580 3gb
Samsung 830 256gb SSD for system drve.
Interestingly I had same install of Windows 8 on a WD Cavier Black 2TB platter drive on same machine as a test for a few weeks before making the change on my SSD. It performed flawlessly. No issues with Intel drivers, no Blue screens. Just not quite as fast.
Any thoughts/help greatly appreciated.
 

My Computer

System One

  • OS
    Windows 8
Set a registry bit and wait for a new BSOD?
Code:
Loading Dump File [C:\Users\Johannes\Downloads\SF_20-11-2012\SF_20-11-2012\111912-9812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols\*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9200 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
Machine Name:
Kernel base = 0xfffff801`32e78000 PsLoadedModuleList = 0xfffff801`33142ae0
Debug session time: Mon Nov 19 11:28:56.376 2012 (UTC + 1:00)
System Uptime: 0 days 0:31:06.037
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 76, {0, fffffa801c711080, 83e, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+31a32 )
Followup: MachineOwner
---------
7: 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: fffffa801c711080, 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:
------------------

DEFAULT_BUCKET_ID:  DRIVER_FAULT_0x76
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x76
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80133474752 to fffff80132ef2740
STACK_TEXT:  
fffff880`033958e8 fffff801`33474752 : 00000000`00000076 00000000`00000000 fffffa80`1c711080 00000000`0000083e : nt!KeBugCheckEx
fffff880`033958f0 fffff801`33295ed7 : fffffa80`1c711080 00000000`00000000 fffffa80`1c711368 fffffa80`21ce2480 : nt! ?? ::NNGAKEGL::`string'+0x31a32
fffff880`03395930 fffff801`332bd2d1 : fffffa80`1c711050 fffffa80`1c711050 fffffa80`1c711348 0001160e`00014b32 : nt!PspProcessDelete+0x18b
fffff880`033959b0 fffff801`32ee9169 : 00000000`00000000 00000000`00000000 fffffa80`1c711348 fffffa80`1c711080 : nt!ObpRemoveObjectRoutine+0x61
fffff880`03395a10 fffff801`3329e412 : 00000000`00000001 fffffa80`1b0cfb00 fffffa80`1b0cfb00 00000000`00000000 : nt!ObfDereferenceObjectWithTag+0x89
fffff880`03395a50 fffff801`332bd2d1 : fffffa80`21ce2050 00000000`00000000 00000000`00000000 fffffa80`21ce2000 : nt!PspThreadDelete+0x1e6
fffff880`03395ab0 fffff801`32ee9169 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`21ce2080 : nt!ObpRemoveObjectRoutine+0x61
fffff880`03395b10 fffff801`32ed6177 : fffffa80`21ce2080 00000000`00000000 00000000`00000000 fffffffe`9a5f4400 : nt!ObfDereferenceObjectWithTag+0x89
fffff880`03395b50 fffff801`32f2b641 : fffffa80`1b0cfb00 fffff801`32ed60e8 fffff801`3310eb60 fffff801`32f80700 : nt!PspReaper+0x8f
fffff880`03395b80 fffff801`32e9a625 : fffff801`3316e180 00000000`00000080 fffff801`32f2b500 fffffa80`1b0cfb00 : nt!ExpWorkerThread+0x142
fffff880`03395c10 fffff801`32ed8e56 : fffff801`3316e180 fffffa80`1b0cfb00 fffff801`331c8880 fffffa80`18e42040 : nt!PspSystemThreadStartup+0x59
fffff880`03395c60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::NNGAKEGL::`string'+31a32
fffff801`33474752 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::NNGAKEGL::`string'+31a32
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  50875b31
BUCKET_ID_FUNC_OFFSET:  31a32
FAILURE_BUCKET_ID:  0x76_nt!_??_::NNGAKEGL::_string_
BUCKET_ID:  0x76_nt!_??_::NNGAKEGL::_string_
Followup: MachineOwner
---------

Check if there is a new driver for your capture card.
 

My Computer

System One

  • OS
    Win 8 Enterprise RTM
    System Manufacturer/Model
    N53SN
    CPU
    sandy bridge
    Motherboard
    N53SN
    Memory
    24gb
    Graphics Card(s)
    550M
    Screen Resolution
    1080p
Thanks for getting back.
Forgive my ignorance, What do you mean- Set a Registry bit?
Blackmagic driver is 9.6.8 dated 8th November. I dont think there is a newer version.
 

My Computer

System One

  • OS
    Windows 8
set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackLockedPages to a DWORD 1 value and reboot

is what it says.

If you don't know what this means or how to do this, you might not even want to try. It's only for diagnostics, and it seems clear that the driver of your capture card is not fully windows 8 compatible yet.
 

My Computer

System One

  • OS
    Win 8 Enterprise RTM
    System Manufacturer/Model
    N53SN
    CPU
    sandy bridge
    Motherboard
    N53SN
    Memory
    24gb
    Graphics Card(s)
    550M
    Screen Resolution
    1080p
So you are saying add-
TrackLockedPages to a DWORD 1 value
-to the registry folder specified to find out exactly what hardware component is causing it?
 

My Computer

System One

  • OS
    Windows 8
That's what the debugger says, not me.
 

My Computer

System One

  • OS
    Win 8 Enterprise RTM
    System Manufacturer/Model
    N53SN
    CPU
    sandy bridge
    Motherboard
    N53SN
    Memory
    24gb
    Graphics Card(s)
    550M
    Screen Resolution
    1080p
To set the dword to 1...
 

My Computer

System One

  • OS
    Win 8 Enterprise RTM
    System Manufacturer/Model
    N53SN
    CPU
    sandy bridge
    Motherboard
    N53SN
    Memory
    24gb
    Graphics Card(s)
    550M
    Screen Resolution
    1080p
Back
Top