Jump to content

DMS hangs at the end of recording


jirim100

Recommended Posts

DMS 3.0.1.3 hangs at the end of recording (and don't start post recording task) -> then Windows 10 system restart. 

Here is the output from analyzing operating system crash dump file in WinDbg.exe application.

Support.zip is attached. Crash happened about  30.05.2021 13:30:50.

I don't expect you solve this problem (or maybe (?) wrap affected code around by try,catch,finally), but I think, you should be at least to know about it. 

 

Spoiler






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


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

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`13a00000 PsLoadedModuleList = 0xfffff807`1462a390
Debug session time: Sun May 30 13:30:10.101 2021 (UTC + 2:00)
System Uptime: 18 days 0:17:56.813
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
18: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000047, Exception code that caused the bugcheck
Arg2: fffff80713cee8ba, Address of the instruction which caused the bugcheck
Arg3: fffff8876e6ae460, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

*** WARNING: Unable to verify timestamp for emBDA64.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-B7NHU71

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 20

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 81

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000047

BUGCHECK_P2: fffff80713cee8ba

BUGCHECK_P3: fffff8876e6ae460

BUGCHECK_P4: 0

CONTEXT:  fffff8876e6ae460 -- (.cxr 0xfffff8876e6ae460)
rax=0000000000000000 rbx=0000000000000001 rcx=ffffcc0380849d10
rdx=fffff8876e6ae600 rsi=0000000000000001 rdi=0000000000000001
rip=fffff80713cee8ba rsp=fffff8876e6ae9a0 rbp=ffff9f00765c0180
 r8=fffff8876e6ae5f8  r9=0000000000000000 r10=00000000000007d0
r11=000000000000002c r12=0000000000000000 r13=ffffffffffffffff
r14=0000000000000000 r15=0000000000000010
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040286
nt!RtlRaiseStatus+0x4a:
fffff807`13cee8ba 80c3ff          add     bl,0FFh
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  DVBVservice.exe

STACK_TEXT:  
fffff887`6e6ae9a0 fffff807`13cee6c6 : ffffdf04`85d96050 fffff807`2aabf4e2 00000000`00000002 ffffdf04`85d96100 : nt!RtlRaiseStatus+0x4a
fffff887`6e6aef40 fffff807`2aa9fc31 : ffffdf04`85d96100 ffffdf04`85d96000 ffffdf04`85d96000 ffffdf04`66337000 : nt!KeReleaseSemaphore+0x166
fffff887`6e6aefc0 ffffdf04`85d96100 : ffffdf04`85d96000 ffffdf04`85d96000 ffffdf04`66337000 fffff887`00000002 : emBDA64+0x6fc31
fffff887`6e6aefc8 ffffdf04`85d96000 : ffffdf04`85d96000 ffffdf04`66337000 fffff887`00000002 fffff887`6e6af060 : 0xffffdf04`85d96100
fffff887`6e6aefd0 ffffdf04`85d96000 : ffffdf04`66337000 fffff887`00000002 fffff887`6e6af060 00000000`00000000 : 0xffffdf04`85d96000
fffff887`6e6aefd8 ffffdf04`66337000 : fffff887`00000002 fffff887`6e6af060 00000000`00000000 ffffdf04`68c26120 : 0xffffdf04`85d96000
fffff887`6e6aefe0 fffff887`00000002 : fffff887`6e6af060 00000000`00000000 ffffdf04`68c26120 ffffdf04`66337000 : 0xffffdf04`66337000
fffff887`6e6aefe8 fffff887`6e6af060 : 00000000`00000000 ffffdf04`68c26120 ffffdf04`66337000 fffff807`2aaa9b15 : 0xfffff887`00000002
fffff887`6e6aeff0 00000000`00000000 : ffffdf04`68c26120 ffffdf04`66337000 fffff807`2aaa9b15 00000000`00000000 : 0xfffff887`6e6af060


SYMBOL_NAME:  emBDA64+6fc31

MODULE_NAME: emBDA64

IMAGE_NAME:  emBDA64.sys

STACK_COMMAND:  .cxr 0xfffff8876e6ae460 ; kb

BUCKET_ID_FUNC_OFFSET:  6fc31

FAILURE_BUCKET_ID:  0x3B_c0000047_emBDA64!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a1d80dad-652a-fbbf-75a2-09405f732c27}

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

18: kd> lmvm emBDA64
Browse full module list
start             end                 module name
fffff807`2aa30000 fffff807`2ab23000   emBDA64  T (no symbols)           
    Loaded symbol image file: emBDA64.sys
    Image path: \SystemRoot\System32\drivers\emBDA64.sys
    Image name: emBDA64.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Apr  6 06:26:19 2020 (5E8AAF6B)
    CheckSum:         000FB0DF
    ImageSize:        000F3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

 

 

support.zip

Edited by jirim100
Link to comment

Looks like the driver for your Hauppauge WinTV-soloHD (emBDA64.sys) crashed when the DMS tried to release the device:

 

30.05.21 13:30:02.100 TRecording           Release          Hauppauge WinTV-soloHD DVBT Tuner (11)
30.05.21 13:30:02.100 TRecording           Free             Hauppauge WinTV-soloHD DVBT Tuner (11)
... no regular end, because the last call does not return, thus completely blocking the DMS
30.05.21 13:31:03.476 Start App            ------------------------------------------------------------
30.05.21 13:31:03.476 DVBViewer Media Server 3.0.1.3

 

"em" in emBDA64.sys stands for eMPIA. Actually it is no driver from Hauppauge, but from the chipset manufacturer.

 

Link to comment

Version on this web "wintv-solo_dual_quadhd_5_2020_0406_38125.exe" (for "WinTV-soloHD") I have already installed.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...