INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: JRiver hang and crash [Solved (hardware problem)]  (Read 1230 times)

Wasper

  • Recent member
  • *
  • Posts: 29
JRiver hang and crash [Solved (hardware problem)]
« on: December 09, 2021, 07:37:53 pm »

Hello,

Using MC28 on Win11 64 bits but the problem was the same on Win10 64 bits.  While playing video, sounds stop randomly.  Mostly between video track change but it could occurs in the middle of a track.  MC will crash and a reboot is necessary.  Tried everything to fix it, rollback, upgrade, reinstall.  Got no solution.  Looking closely to logs file after every crash, I noticed a pattern.
Many device change event are raised as you can see in the log.  The GUID of the device removed is related to the usbaudio2.sys.  This driver shouldn't be used as I use the manufactured driver to play to usb DAC.  HDMI audio, jack audio are all disabled.  HDMI audio is disabled from the BIOS.  I tried to remove everything that isn't necessary for my use.  The removing of the device is the following call to the device change event.  Then, plenty more device change event raised.  I think those repeated call makes MC to crash.  Anyone can tell me what is happening, how to fix it?  Full log in attachment.

4811319: 7932: TV: CTVManager::OnDeviceChange: Start
4811319: 7932: TV: CTVManager::OnDeviceChange: Event type: 0x8004, data: 0xf958effb20, device type: 0x5
4811319: 7932: TV: CTVManager::RemoveDevice: Start
4811319: 7932: TV: CTVManager::RemoveDevice: ClassID {65E8773D-8F56-11D0-A3B9-00A0C9223196} Device \\?\USB#VID_2673&PID_1003#413-001#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\Wave
4811319: 7932: TV: CDeviceList::RemoveDevice: Start
4811319: 7932: TV: CDeviceList::RemoveDevice: Try removing \\?\USB#VID_2673&PID_1003#413-001#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\Wave
4811319: 7932: TV: CDeviceList::RemoveDevice: Finish (0 ms)
4811319: 7932: TV: CTVManager::ReleaseRemovedPlayers: Start
4811319: 7932: TV: CTVManager::ReleaseRemovedPlayers: Finish (0 ms)
4811319: 7932: TV: CTVManager::RemoveDevice: Finish (0 ms)
4811319: 7932: TV: CTVManager::OnDeviceChange: Finish (0 ms)
4811346: 8348: Playback: COutputPluginAudioRenderer::DoRenderSample: Correcting drift by 260.624 ms
4811347: 8348: Playback: COutputPluginAudioRenderer::DoRenderSample: Correcting drift by 129.205 ms
4811358: 7932: TV: CTVManager::OnDeviceChange: Start
4811358: 7932: TV: CTVManager::OnDeviceChange: Event type: 0x7, data: 0x0, device type: 0x0
4811358: 7932: TV: CTVManager::OnDeviceChange: Finish (0 ms)
4811362: 7932: TV: CTVManager::OnDeviceChange: Start
4811362: 7932: TV: CTVManager::OnDeviceChange: Event type: 0x7, data: 0x0, device type: 0x0
4811362: 7932: TV: CTVManager::OnDeviceChange: Finish (0 ms)
4811409: 7932: Handheld: CWMDMThread::SetNeedsEnumerateDevices: Start
4811410: 7932: Handheld: CWMDMThread::SetNeedsEnumerateDevices: Finish (0 ms)
4811410: 7932: Handheld: CWMDMThread::SetNeedsEnumerateDevices: Start
4811410: 7932: Handheld: CWMDMThread::SetNeedsEnumerateDevices: Finish (0 ms)
4811410: 5412: Handheld: CWMDMThread::Thread: Start
4811410: 5412: Handheld: CWMDMThread::Thread: Starting work loop
4811540: 7932: TV: CTVManager::OnDeviceChange: Start
4811540: 7932: TV: CTVManager::OnDeviceChange: Event type: 0x8000, data: 0xf958effb20, device type: 0x5
4811540: 7932: TV: CTVManager::OnDeviceChange: Finish (0 ms)
4811543: 7932: TV: CTVManager::OnDeviceChange: Start
4811543: 7932: TV: CTVManager::OnDeviceChange: Event type: 0x7, data: 0x0, device type: 0x0
4811543: 7932: TV: CTVManager::OnDeviceChange: Finish (0 ms)
Logged

Wasper

  • Recent member
  • *
  • Posts: 29
Re: JRiver hang and crash
« Reply #1 on: December 09, 2021, 09:22:38 pm »

Hello again, just adding some precision about my question.


Logged

jmone

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 14463
  • I won! I won!
Re: JRiver hang and crash
« Reply #2 on: December 09, 2021, 09:25:05 pm »

What version of MC are you using (there were some fixes for crashes in the latest versions).  Also the MC Devs will want this file - C:\Users\delim00\AppData\Roaming\J River\Media Center 28\Crash.dmp
Logged
JRiver CEO Elect

Wasper

  • Recent member
  • *
  • Posts: 29
Re: JRiver hang and crash
« Reply #3 on: December 09, 2021, 10:33:34 pm »

I'm using MC28 stable channel.  Problem was there on MC27.  Noticed it around 2 weeks ago. Log+Dump here: https://drive.google.com/file/d/1T1CCpGiUkN4_S_3sC7QT5vcJ1Mf81Vmb/view?usp=sharing
Logged

jmone

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 14463
  • I won! I won!
Re: JRiver hang and crash
« Reply #4 on: December 09, 2021, 10:39:07 pm »

Try 28.0.92 from the top of the board.  It has some crash fixes in it, though the crash dump will help help the devs. 
Logged
JRiver CEO Elect

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72438
  • Where did I put my teeth?
Re: JRiver hang and crash
« Reply #5 on: December 10, 2021, 07:27:03 am »

Is it a crash (program disappears) or a hang (program becomes unresponsive)?

Antivirus often causes problems like this.  What are you using?
Logged

jmone

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 14463
  • I won! I won!
Re: JRiver hang and crash
« Reply #6 on: December 10, 2021, 02:13:48 pm »

His txt files says its a crash and it produced a DMP file.
Logged
JRiver CEO Elect

Wasper

  • Recent member
  • *
  • Posts: 29
Re: JRiver hang and crash
« Reply #7 on: December 10, 2021, 08:40:35 pm »

Hello again,

pretty sure it isn't antivirus, as all JRiver files and media files are in the exclusion list following the recommendations here.  I switched to MC last version and increased DAC buffer and MC buffer.  Played 9 hours without hang and crash.  Jumped on USB external HDD, song started playing for 2 seconds before the hang.  Looked at the logs, same as always...  The bug doesn't always happens when rendering from external drive. It happened with internal drive as well.  The OS is on SSD, 8Gb rams, I7, 2 years old.  Performance should be ok.  I don't know if the TV: CTVManager logs are related to video playback. If not, it could be nice to turn off this service as I don't use it.  Normally the external HDD is set to never power down so it shouldn't raise the OnDeviceChange event.  Anyway, I ran without it attached to the computer and the event got raised anyway and the crash seemed to happen as often.  In either case, it should be handled correctly by MC!

Part of the logs that caused the last crash.  Audio Accum Bytes reached 0 bytes right after multi events launch and the crash occured.  A lot of ms involved in the latest lines of the logs that could have overpasses the allowed latency.  However, I do think, is the lack of data sent to the DAC that are the main cause of my headache and this arrived prior of the the refreshing device thread!  I could, and probably, saying stupid thing though and sorry for weird english.
Code: [Select]
32939176: 4736: Playback: CBitrateMonitor::UpdateBitrate: Accum audio bytes 79680, video bytes 5982258, time period 1459.3352999999999611 ms, bitrate 33224000
32939225: 8112: TV: CTVManager::OnDeviceChange: Start
32939225: 8112: TV: CTVManager::OnDeviceChange: Event type: 0x7, data: 0x0, device type: 0x0
32939225: 8112: TV: CTVManager::OnDeviceChange: Finish (0 ms)
32939225: 8112: TV: CTVManager::OnDeviceChange: Start
32939225: 8112: TV: CTVManager::OnDeviceChange: Event type: 0x7, data: 0x0, device type: 0x0
32939225: 8112: TV: CTVManager::OnDeviceChange: Finish (0 ms)
32939337: 8112: TV: CTVManager::OnDeviceChange: Start
32939337: 8112: TV: CTVManager::OnDeviceChange: Event type: 0x8000, data: 0x812a72f4f0, device type: 0x5
32939337: 8112: TV: CTVManager::OnDeviceChange: Finish (0 ms)
32939375: 8112: Handheld: CWMDMThread::SetNeedsEnumerateDevices: Start
32939375: 8112: Handheld: CWMDMThread::SetNeedsEnumerateDevices: Finish (0 ms)
32939530: 8112: TV: CTVManager::OnDeviceChange: Start
32939530: 8112: TV: CTVManager::OnDeviceChange: Event type: 0x7, data: 0x0, device type: 0x0
32939530: 8112: TV: CTVManager::OnDeviceChange: Finish (0 ms)
32939560: 8112: Handheld: CWMDMThread::SetNeedsEnumerateDevices: Start
32939560: 8112: Handheld: CWMDMThread::SetNeedsEnumerateDevices: Finish (0 ms)
32939621: 8112: Handheld: CWMDMThread::SetNeedsEnumerateDevices: Start
32939621: 8112: Handheld: CWMDMThread::SetNeedsEnumerateDevices: Finish (0 ms)
32939716: 8112: TV: CTVManager::OnDeviceChange: Start
32939716: 8112: TV: CTVManager::OnDeviceChange: Event type: 0x7, data: 0x0, device type: 0x0
32939716: 8112: TV: CTVManager::OnDeviceChange: Finish (0 ms)
32939776: 8112: TV: CTVManager::OnDeviceChange: Start
32939776: 8112: TV: CTVManager::OnDeviceChange: Event type: 0x7, data: 0x0, device type: 0x0
32939776: 8112: TV: CTVManager::OnDeviceChange: Finish (0 ms)
32939790: 8112: Handheld: CWMDMThread::SetNeedsEnumerateDevices: Start
32939790: 8112: Handheld: CWMDMThread::SetNeedsEnumerateDevices: Finish (0 ms)
32939960: 8112: TV: CTVManager::OnDeviceChange: Start
32939960: 8112: TV: CTVManager::OnDeviceChange: Event type: 0x7, data: 0x0, device type: 0x0
32939960: 8112: TV: CTVManager::OnDeviceChange: Finish (0 ms)
32941187: 3576: Playback: CVideoRefreshRateThread::Thread: Using madVR to monitor refresh rate
32941394: 4736: Playback: CBitrateMonitor::UpdateBitrate: Accum audio bytes 0, video bytes 11060518, time period 2217.9805999999998676 ms, bitrate 39888000
32942433: 7016: Handheld: CWMDMThread::Thread: Command line: /AnalyzeDevices "C:\Users\delim00\AppData\Roaming\J River\Media Center 28\Temp\Devices (input) - 7016.xml" "C:\Users\delim00\AppData\Roaming\J River\Media Center 28\Temp\Devices (output) - 7016.xml"
32942433: 7016: Handheld: CWMDMThread::Thread: Running worker
32942433: 7016: Handheld: CWMDMThread::Thread: Enumerating devices
32942433: 7016: General: RunProgram: Start
32942433: 7016: General: RunProgram: Filename: C:\Program Files\J River\Media Center 28\JRWorker.exe / Parameters: /AnalyzeDevices "C:\Users\delim00\AppData\Roaming\J River\Media Center 28\Temp\Devices (input) - 7016.xml" "C:\Users\delim00\AppData\Roaming\J River\Media Center 28\Temp\Devices (output) - 7016.xml"
32942437: 7016: General: RunProgram: Running process...
32942437: 7016: General: RunProgram: Waiting for completion
0000002: 3944: General: JRWorker::ProcessCommand: Start
0000002: 3944: General: JRWorker::ProcessCommand: Processing AnalyzeDevices task...
0000004: 3944: General: JRWorker::ProcessCommand: Calling EnumerateDevices...
0000004: 3944: Handheld: CAnalyzeDevices::CAnalyzeDevices: Start
0000004: 3944: Handheld: CAnalyzeDevices::CAnalyzeDevices: Finish (0 ms)
0000004: 3944: Handheld: CAnalyzeDevices::EnumerateDevices: Start
0000004: 3944: Handheld: CAnalyzeDevices::EnumerateWPDDevices: Start
0000007: 3944: Handheld: CAnalyzeDevices::EnumerateWPDDevices: Found 1 Windows Portable Devices
0000008: 3944: Handheld: CAnalyzeDevices::EnumerateWPDDevices: Found device (ID: \\?\swd#wpdbusenum#{b0c649e0-9c8b-11eb-b320-806e6f6e6963}#0000000008100000#{6ac27878-a6fa-4155-ba85-f98f491d4f33})
0000020: 3944: Handheld: CWPDHelper::GetDeviceExtendedInfo: Start
0000021: 3944: Handheld: CWPDHelper::GetDeviceExtendedInfo: Finish (0 ms)
0000021: 3944: Handheld: CAnalyzeDevices::EnumerateWPDDevices: DeviceInfo: (name: TOSHIBA EXT - D:, uid: $$?$swd#wpdbusenum#{b0c649e0-9c8b-11eb-b320-806e6f6e6963}#0000000008100000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}$0, volume root: D:\, drive: 1, drive letter: D:, ignore: 0)
0000021: 3944: Handheld: CAnalyzeDevices::EnumerateWPDDevices: Adding device to device list
0000021: 3944: Handheld: CAnalyzeDevices::EnumerateWPDDevices: Finish (17 ms)
0000021: 3944: Handheld: CAnalyzeDevices::EnumerateUSBDevices: Start
0000021: 3944: Handheld: CMSCDeviceEnumerator::GetAllRemovableDisks: Start
0000021: 3944: Handheld: CMSCDeviceEnumerator::GetAllRemovableDisks: Removable drives found:
0000021: 3944: Handheld: CMSCDeviceEnumerator::GetAllRemovableDisks: Finish (0 ms)
0000021: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Start
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Enumerating GUID_DEVINTERFACE_VOLUME...
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Analyzing device 0
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: GetDeviceInterfaceDetailData returned 1 for \\?\storage#volume#{b0c649c6-9c8b-11eb-b320-806e6f6e6963}#0000000020100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Start
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR: STORAGE\VOLUME\{B0C649C6-9C8B-11EB-B320-806E6F6E6963}#0000000020100000
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR (parent): ROOT\VOLMGR\0000
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Finish (0 ms)
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Analyzing device 1
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: GetDeviceInterfaceDetailData returned 1 for \\?\storage#volume#{b0c649c7-9c8b-11eb-b320-806e6f6e6963}#0000000008100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Start
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR: STORAGE\VOLUME\{B0C649C7-9C8B-11EB-B320-806E6F6E6963}#0000000008100000
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR (parent): ROOT\VOLMGR\0000
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Finish (0 ms)
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Analyzing device 2
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: GetDeviceInterfaceDetailData returned 1 for \\?\storage#volume#{b0c649c6-9c8b-11eb-b320-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Start
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR: STORAGE\VOLUME\{B0C649C6-9C8B-11EB-B320-806E6F6E6963}#0000000000100000
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR (parent): ROOT\VOLMGR\0000
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Finish (0 ms)
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Analyzing device 3
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: GetDeviceInterfaceDetailData returned 1 for \\?\storage#volume#{b0c649c6-9c8b-11eb-b320-806e6f6e6963}#000000e8ad700000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Start
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR: STORAGE\VOLUME\{B0C649C6-9C8B-11EB-B320-806E6F6E6963}#000000E8AD700000
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR (parent): ROOT\VOLMGR\0000
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Finish (0 ms)
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Analyzing device 4
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: GetDeviceInterfaceDetailData returned 1 for \\?\storage#volume#{b0c649e0-9c8b-11eb-b320-806e6f6e6963}#0000000008100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Start
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR: STORAGE\VOLUME\{B0C649E0-9C8B-11EB-B320-806E6F6E6963}#0000000008100000
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR (parent): ROOT\VOLMGR\0000
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Finish (0 ms)
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Analyzing device 5
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Device interface invalid
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Enumerating GUID_DEVINTERFACE_DISK...
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Analyzing device 0
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: GetDeviceInterfaceDetailData returned 1 for \\?\scsi#disk&ven_samsung&prod_ssd_860_evo_m.2#4&31bbc50&0&010000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Start
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR: SCSI\DISK&VEN_SAMSUNG&PROD_SSD_860_EVO_M.2\4&31BBC50&0&010000
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR (parent): PCI\VEN_8086&DEV_9DD3&SUBSYS_20748086&REV_30\3&11583659&0&B8
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Finish (0 ms)
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Analyzing device 1
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: GetDeviceInterfaceDetailData returned 1 for \\?\usbstor#disk&ven_toshiba&prod_external_usb_3.0&rev_5438#20191004003078f&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Start
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR: USBSTOR\DISK&VEN_TOSHIBA&PROD_EXTERNAL_USB_3.0&REV_5438\20191004003078F&0
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBRoot: USB\VID_0480&PID_0820\20191004003078F
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Finish (0 ms)
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Data: VID_0480, PID_0820, REV_5438
0000022: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Getting device name...
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Getting drive letter from DevicePath...
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: CreateFile returned: 812
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Getting drive letter from SBP2 info...
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: ParentIdPrefix:
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Getting drive letter by searching for matching sysinfo...
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Found device (vendor: 0480, product: 0820, device id: 20191004003078F&0, drive letter: , add new: 1)
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Analyzing device 2
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: GetDeviceInterfaceDetailData returned 1 for \\?\scsi#disk&ven_toshiba&prod_hdwl120#4&31bbc50&0&020000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Start
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR: SCSI\DISK&VEN_TOSHIBA&PROD_HDWL120\4&31BBC50&0&020000
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: USBSTOR (parent): PCI\VEN_8086&DEV_9DD3&SUBSYS_20748086&REV_30\3&11583659&0&B8
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetDeviceUSBStrings: Finish (0 ms)
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Analyzing device 3
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Device interface invalid
0000023: 3944: Handheld: CMSCDeviceEnumerator::GetMSCDevices: Finish (1 ms)
0000023: 3944: Handheld: CAnalyzeDevices::EnumerateUSBDevices: Finish (1 ms)
0000023: 3944: Handheld: CAnalyzeDevices::EnumerateDevices: RetVal = 1
0000023: 3944: Handheld: CAnalyzeDevices::EnumerateDevices: Finish (19 ms)
0000023: 3944: General: JRWorker::ProcessCommand: EnumerateDevices succeeded...
0000023: 3944: Handheld: CAnalyzeDevices::GetDevices: Start
0000023: 3944: Handheld: CAnalyzeDevices::GetDevices: 1 devices found
0000023: 3944: Handheld: CAnalyzeDevices::GetDevices: Finish (0 ms)
0000060: 3944: General: JRWorker::ProcessCommand: Task completed in 56 ms, result = 0
0000060: 3944: General: JRWorker::ProcessCommand: Finish (57 ms)
32942596: 7016: General: RunProgram: Finished
32942596: 7016: General: RunProgram: Done waiting
32942596: 7016: General: RunProgram: Finish (162 ms)
32942596: 7016: Handheld: CWMDMThread::Thread: Worker finished (return: 0)
32942596: 7016: Handheld: CWMDMThread::Thread: Enumeration succeeded -- processing results
32942846: 7016: Handheld: CWMDMThread::CheckProxyDriveExistence: Start
32942846: 7016: Handheld: CWMDMThread::CheckProxyDriveExistence: Finish (0 ms)
32942847: 7016: Handheld: CWMDMThread::Thread: Finish (3670 ms)
32942847: 8112: Handheld: CWMDMThread::ProcessMainThreadMessage: Start
32942847: 8112: Handheld: CWMDMThread::ProcessMainThreadMessage: Done enumerating
32942847: 8112: Handheld: CHHManagerMap::EnumDevices: Start
32942847: 8112: Handheld: CHHManagerMap::EnumWMDMDevices: Start
32942847: 8112: Handheld: CHHManagerMap::EnumWMDMDevices: Getting device list from WMDM thread
32942847: 8112: Handheld: CHHManagerMap::EnumWMDMDevices: Getting handheld manager for $$?$swd#wpdbusenum#{b0c649e0-9c8b-11eb-b320-806e6f6e6963}#0000000008100000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}$0
32942847: 8112: Handheld: CHHManagerMap::EnumWMDMDevices: Updating device
32942847: 8112: Handheld: CHHManager::SetDeviceInfo: Start
32942847: 8112: Handheld: CHHManager::SetDeviceInfo: Finish (0 ms)
32942847: 8112: Handheld: CHHManager::UpdateDevice: Start
32942848: 8112: Handheld: CHHManager::UpdateDevice: PDTName: ''; DisplayName: 'TOSHIBA External USB 3.0 (D:)'
32942848: 8112: Handheld: CHHManager::UpdateDevice: Loading PDTInfo: ''
32942849: 8112: Handheld: CHHManager::UpdatePluginDeviceInfo: Start
32942849: 8112: Handheld: CHHPluginThread::ProcessCommand: Start
32942849: 8112: Handheld: CHHPluginThread::PerformFunctionCall: Start
32942849: 8112: Handheld: CHHPluginThread::PerformFunctionCall: Posting message to plugin thread
32942849: 8112: Handheld: CHHPluginThread::PerformFunctionCall: Blocking until call completes
32942849: 4828: Handheld: CHHPluginThread::Thread: Message (Type: 0, Function: 2)
32942849: 4828: Handheld: CHHPluginThread::Thread: Command = 1030
32942860: 8112: Handheld: CHHPluginThread::PerformFunctionCall: Finish (result: 0) (10 ms)
32942860: 8112: Handheld: CHHPluginThread::ProcessCommand: Finish (10 ms)
32942860: 8112: Handheld: CHHManager::UpdatePluginDeviceInfo: Finish (10 ms)
32942860: 8112: Store: CPonoPlayerHelper::GetRunCustomDeviceHandlingTaskInBackground: Start
32942860: 8112: Store: CPonoPlayerHelper::GetIsInternalStorage: Start
32942860: 8112: Store: CPonoPlayerHelper::GetIsInternalStorage: Finish (0 ms)
32942860: 8112: Store: CPonoPlayerHelper::GetRunCustomDeviceHandlingTaskInBackground: Finish (0 ms)
32942860: 8112: Handheld: CHHManager::UpdateDevice: Finish (12 ms)
32942860: 8112: Handheld: CHHManagerMap::EnumWMDMDevices: Finish (13 ms)
32942860: 8112: Handheld: CHHManagerMap::EnumDevices: Finish (13 ms)
32942860: 8112: Handheld: CWMDMThread::ProcessMainThreadMessage: Finish (13 ms)
32942909: 8112: Database: CMediaInfoArraySort::Sort: Files: 2628; Elapsed ms: 2.667
32942909: 8112: Database: CSearchFilesHelper::GetResults: Search: [Media Sub Type]=[Music Video] ((-[Filename (path)]=" v2" -[Name]=" v2") or [Filename]="bootleg") ~sort=[Name]; Elapsed ms: 42.826
32942945: 8620: Sharing Plugins: CUDPSocketReader::Accept: Finish (21164 ms)
32942946: 4876: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
32942946: 4876: Sharing Plugins: CHTTPListenerWorker::HandleRequest: UDP: 10.0.0.38: M-SEARCH: http://239.255.255.250:1900*
32943127: 4876: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (181 ms)
32943127: 8620: Sharing Plugins: CUDPSocketReader::Accept: Start
32943127: 8620: Sharing Plugins: CUDPSocketReader::Accept: Description: CListenerBase::CListenerBase [UDP]
32943609: 4736: Playback: CBitrateMonitor::UpdateBitrate: Accum audio bytes 0, video bytes 8149562, time period 2214.4641000000001441 ms, bitrate 29440000
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72438
  • Where did I put my teeth?
Re: JRiver hang and crash
« Reply #8 on: December 11, 2021, 08:01:22 am »

Look through the "Weird Problems" topic for ideas.  It's in my signature. 
Logged

Wasper

  • Recent member
  • *
  • Posts: 29
Re: JRiver hang and crash
« Reply #9 on: January 01, 2022, 09:53:57 am »

Found the problem.  After trying everything, and I mean everything.  I discovered that my HTPC was overheating.  Thought at first it was normal as I use MadVr with average setting. But the CPU Load was really low (under 15%) and temp over 90 and many peak at max 100 Celsius.  Fortunately a good air dust remover did the job and my temp are back below 85 (70-75).  Since then no more hang.

I found one other problem while testing.  MediaCenter will sometimes stay in opening mode after stopping playback while the file is launching.  Then, I need to close Media Center and restart it.  My need is that when the playlist contains a HDR file, I stop playback, run a script to to toggle HDR on windows and relaunch playback.  All of this is done automatically by a plugin that catch the track change event.

Finally, Around 6 months ago, I started to have occasionally ( around 50%)  a problem when resuming playback form pause.  If it stay on pause for a little bit too long, I got no sound on resume.  Maybe someone faced this problem and can help?
Logged
Pages: [1]   Go Up