INTERACT FORUM

Please login or register.

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

Author Topic: Media Center 18 has stopped woking  (Read 1066 times)

coderego

  • Junior Woodchuck
  • **
  • Posts: 78
Media Center 18 has stopped woking
« on: January 30, 2013, 08:29:11 am »

Hi all,

This morning I started up my trusty JRiver 18 (18.0.122) to watch some media. As soon as i hit play, it crashes and gives me the Media Center 18 has stopped working popup.

Any ideas? Thanks!
Logged

coderego

  • Junior Woodchuck
  • **
  • Posts: 78
Re: Media Center 18 has stopped woking
« Reply #1 on: January 30, 2013, 08:30:20 am »

from my log file:
0023182: 4832: General: TopLevelExceptionFilter: Unhandled exception -- program crashing
0023182: 4832: General: TopLevelExceptionFilter: Message: 977, wParam: 93026280, lParam: 4
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42441
  • Shoes gone again!
Re: Media Center 18 has stopped woking
« Reply #2 on: January 30, 2013, 02:07:12 pm »

Is it only when you play?

What if you try different files or audio output modes?

If it just started, think about what else on the system might have changed.
Logged
Matt Ashland, JRiver Media Center

coderego

  • Junior Woodchuck
  • **
  • Posts: 78
Re: Media Center 18 has stopped woking
« Reply #3 on: February 01, 2013, 08:15:09 am »

Happened when I played any file, audio or video. Tried several different formats.

Solution was to switch Audio Output modes twice (changed it to something different and then back again) and it stopped crashing.

Either way, this was an unhandled exception in the code rather than a handled and reported error. As such, any system config changes are not really relevant. 
Logged

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42441
  • Shoes gone again!
Re: Media Center 18 has stopped woking
« Reply #4 on: February 01, 2013, 08:35:45 am »

Either way, this was an unhandled exception in the code rather than a handled and reported error. As such, any system config changes are not really relevant. 

Since we load the third-party audio driver into our process there's a little more nuance than that.

Regardless, I'm glad it's working now.
Logged
Matt Ashland, JRiver Media Center
Pages: [1]   Go Up