Question / Help Fighting BSOD

[Magnethead]

So my new laptop came in today and I got everything set up on it. Sorta. Keep in mind everything i'm using here worked on my Win7 desktop.

The USB capture card (USB ATV) shows a black screen, as well as one of my webcams (which was red until I set the resolution correctly, a generic Inland product). One of my webcam (logitech C270) and the onboard webcam both work separate, but I will get 2 black frames if I try to PIP them.

I tried PIPing the ATV and the C270, which will be my most common field use config, and I got a BSOD: ACP_INDEX_MISMATCH. Bugcheck is 0x0001 ( 0x732d2e09, 0x00, 0xffffe, 0xfffff880092a9b60 ) via system event viewer.

After the restart, the USB ATV module worked properly and the C270 worked properly. But as soon as I tried to PIP them, same BSOD came up again.

After re-start, USB ATV came back as a red screen.

Where is a good place to start debugging?

Thanks in advance.

 

[Magnethead]

I just tried to PIP the USB ATV capture module and the onboard webcam, gave me the same BSOD.

The inland camera does not even show in device manager anymore, so something with it is screwed up.

The USB capture module is a Sabrent USB-AVCPT using the drivers from Sabrent's site, it registers in Device Manager as a "STK1160 Grabber" capture device. I've uninstalled and reinstalled it. On my XP machine, it comes up as "SynTek STK1160".

synopsis:

Onboard: works
Logitech C270: works
USB Capture: works
Inland Webcam: not in device manager

Onboard + Logitech C270: Black Frames
Onboard + USB Capture: BSOD
Logitech C270 + USB Capture: BSOD

Laptop is HP Elitebook 2560p with i5-2540m dual core hyperthreading processor.

 

[Magnethead]

Log file is attached.

Also, I should clarify. I can have 2 devices in the sources box... But only one can be checked. If i check both, that is when it BSOD's.

 

[Magnethead]

I have attached screenshots of my current situation. If I check both sources, I get a BSOD. I don't understand why it would work solo but not together.

I also double checked that the driver files are same ones as my Win 7 desktop where everything worked, and they do match.

I just did a uninstall, restart, reinstall of OBS. BSOD is still there. Meanwhile, If I try to PIP the C270 and the onboard camera, the 270 will not go active and it only shows the onboard camera. So I guess those 2 are conflicting some way or another. I've tried different USB port configurations (this laptop only has 3 ports).

I'll never stream from the onboard camera, but perhaps it leads to a clue.

 

[Magnethead]

so I've completely reinstalled OBS, I installed the proper Logi C270 driver, and I uninstalled and reinstalled the STK1160 driver module.

What am I missing? It still crashes when I try to run both streams.

 

[dping]

so I've completely reinstalled OBS, I installed the proper Logi C270 driver, and I uninstalled and reinstalled the STK1160 driver module.

What am I missing? It still crashes when I try to run both streams.

I dont know what the conflict is but have you tried OBS Multiplatform?
https://obsproject.com/download#mp

 

[Magnethead]

I dont know what the conflict is but have you tried OBS Multiplatform?
https://obsproject.com/download#mp

I can do that.

I went to my "friends" at TSF (used to be a volunteer there for hardware). http://www.techsupportforum.com/forums/f299/apc-index-mismatch-1061026.html

Maybe this will help pinpoint the issue. I'll run SFC and see what it finds and report back, then I'mm switch to the MP version.

I'd run sfc /scannow in the command prompt window.

While OBS.exe is running its calls to a kernel system file "ntkrnlmp.exe" This is the culprit making too many APC calls. Its possible the file is corrupt.

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00000000747d2e09, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000fffe, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff880093fcb60, Call type (0 - system call, 1 - worker routine)

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


BUGCHECK_P1: 747d2e09

BUGCHECK_P2: 0

BUGCHECK_P3: fffe

BUGCHECK_P4: fffff880093fcb60

FAULTING_IP: 
+0
00000000`747d2e09 ??              ???

CPU_COUNT: 4

CPU_MHZ: a22

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2a

CPU_STEPPING: 7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x1

PROCESS_NAME:  OBS.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 10.0.10240.9 x86fre

LAST_CONTROL_TRANSFER:  from fffff80002cc57a9 to fffff80002cc6200

STACK_TEXT:  
fffff880`093fc928 fffff800`02cc57a9 : 00000000`00000001 00000000`747d2e09 00000000`00000000 00000000`0000fffe : nt!KeBugCheckEx
fffff880`093fc930 fffff800`02cc56e0 : fffffa80`08641600 00000000`0012dc48 fffff880`093fca88 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`093fca70 00000000`747d2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`0012e558 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x747d2e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceExit+245
fffff800`02cc56e0 4883ec50        sub     rsp,50h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceExit+245

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5609efa0

IMAGE_VERSION:  6.1.7601.19018

FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245

BUCKET_ID:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245

PRIMARY_PROBLEM_CLASS:  X64_0x1_SysCallNum_4_nt!KiSystemServiceExit+245

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1_syscallnum_4_nt!kisystemserviceexit+245

FAILURE_ID_HASH:  {e506ede0-d282-2e4c-5056-6cb373197a73}

Followup:     MachineOwner

 

[Magnethead]

Installed multiplatform and the C++ redists it requires. I added the onboard webcam and the C270 and both displayed at the same time, I added the USB capture module and boom, APC index mismatch. So we got improvement, but in the wrong place.

SFC /scannow returned "Windows Resource Protection did not find any integrity violations" so the NT kernel is healthy it appears.

 

[dping]

Installed multiplatform and the C++ redists it requires. I added the onboard webcam and the C270 and both displayed at the same time, I added the USB capture module and boom, APC index mismatch. So we got improvement, but in the wrong place.

SFC /scannow returned "Windows Resource Protection did not find any integrity violations" so the NT kernel is healthy it appears.

What about one of the webcams and the USB capture modules.

 

[Magnethead]

What about one of the webcams and the USB capture modules.

I just did the C270 and the USB capture and it "worked" but I couldn't get the canvas to match the resolution of either camera so I had blank space to the side. I exited and reopened OBS and it came up with a blank frame for half a second then it went to APC mismatch BSOD.

 

[dping]

I just did the C270 and the USB capture and it "worked" but I couldn't get the canvas to match the resolution of either camera so I had blank space to the side. I exited and reopened OBS and it went straight to APC mismatch BSOD.

that is probably because of the auto preview + everything is a global source. unplug the USB camera for now. I dont have a good answer for you. It is probably a conflict between the multiple capture devices.

 

[Magnethead]

I was hoping to do a bi-directional PIP feed, one facing downtrack and one showing the next coming pair. Everything works on my desktop, not sure why not on the laptop. Guess I will continue poking a stick at it then. It's hard to get a USB webcam with a wide focal range that can see the starting line and 1/4 mile simultaneously in focus. I have a camcorder that can, thus using the capture device. I'd hate to put money down on a different USB capture card and have the same issue.

 

[Magnethead]

Aw F it. its only money. Amazon primed a Hauppauge USBLive2 to be dropped off tomorrow. Hopefully that will behave being a name brand and all.

 

[dping]

Aw F it. its only money. Amazon primed a Hauppauge USBLive2 to be dropped off tomorrow. Hopefully that will behave being a name brand and all.

I believe Hauppauge cards only work with OBS Multiplatform, just fyi.

 

[Magnethead]

I believe Hauppauge cards only work with OBS Multiplatform, just fyi.

If it works I'll be happy. If not, Amazon has friendly returns. I like multi-platform's improved UI anyways,

 

[Magnethead]

This is along the lines of what I want to do, streaming to youtube because livestream's server likes to crash and burn in my experience as a viewer. But I only want to do 2 cameras to keep from cluttering the screen so much (Motor Mania has a full time producer that switches between all 3 cameras every run, I'm setting mine up as autonomous as possible- he does this frame at the start of each broadcast to make sure all 3 work.)

Camcorder viewing from starting line down track (USB capture), and C270 USB webcam looking behind to show the next pairs in line.

 

[dping]

This is along the lines of what I want to do, streaming to youtube because livestream's server likes to crash and burn in my experience as a viewer. But I only want to do 2 cameras to keep from cluttering the screen so much (Motor Mania has a full time producer that switches between all 3 cameras every run, I'm setting mine up as autonomous as possible- he does this frame at the start of each broadcast to make sure all 3 work.)

Camcorder viewing from starting line down track (USB capture), and C270 USB webcam looking behind to show the next pairs in line.

Maybe disable the onboard webcam from device manage and just use those two...

 

[Magnethead]

Think I made progress, kinda.

I went thumbing through some sabrent archives and found the Vista/7 x86 driver (I've been using the x64 driver).

APC mismatch BSOD is gone (knock on wood), but if I close OBS and reopen, the sabrent audio comes through, but not the video. Just a black screen. I can close it again and open yawcam and it pulls the video just fine. close that and open OBS, still black. Just restarted computer, and still black.

I just removed the sabrent source and added the onboard webcam, and same thing....black window (and the camera's LED only lit briefly before turning off). Like OBS isn't even trying to pull the source.

 

[dping]

Think I made progress, kinda.

I went thumbing through some sabrent archives and found the Vista/7 x86 driver (I've been using the x64 driver).

APC mismatch BSOD is gone (knock on wood), but if I close OBS and reopen, the sabrent audio comes through, but not the video. Just a black screen. I can close it again and open yawcam and it pulls the video just fine. close that and open OBS, still black. Just restarted computer, and still black.

I just removed the sabrent source and added the onboard webcam, and same thing....black window (and the camera's LED only lit briefly before turning off). Like OBS isn't even trying to pull the source.

probably shouldn't have any software running that is trying to hook those captures. that is usually what causes the black screen. you could try unplugging and replugging but if there is some sort of addon software included in that new driver, maybe its that. older driver working on install then not usually means something like that or windows 10 just doesn't like the driver. check device manager?

 

[Magnethead]

probably shouldn't have any software running that is trying to hook those captures. that is usually what causes the black screen. you could try unplugging and replugging but if there is some sort of addon software included in that new driver, maybe its that. older driver working on install then not usually means something like that or windows 10 just doesn't like the driver. check device manager?

Still windows 7 professional x64. The sabrent x64 driver is what was BSODing, i found the x32 driver and this is what I have now.

I don't have OBS and yawcam open together. I close one and open the other (I know 2 programs cant use one camera). Boggles me that yawcam can access the video but OBS can't.

Related note- sometimes when i select the sabrent device, a little read box appears in top left corner, sometimes it doesn't. right clicking to fill screen doesn't change anything.