INTERACT FORUM
More => Old Versions => Media Center 14 (Development Ended) => Topic started by: globetrotters1 on November 17, 2009, 06:21:58 am
-
The program is crashing when I start Theater View. The log says:
0053156: 1336: General: CMainUIWnd::Resize: Start
0053187: 1336: General: CDXCore::Initialize: Start
0053187: 1336: General: CDXCore::Initialize: Stopping previous instances
0053187: 1336: General: CDXCore::Terminate: Start
0053187: 1336: General: CDXCore::Terminate: Cleanup
0053187: 1336: General: CDXCore::Terminate: Release Direct3D
0053203: 1336: General: CDXCore::Terminate: Unload D3D.dll
0053203: 1336: General: CDXCore::Terminate: Clearing variables
0053203: 1336: General: CDXCore::Terminate: Finish (16 ms)
0053203: 1336: General: CDXCore::Initialize: Creating Direct3D
0053625: 1336: General: CDXCore::Initialize: Loading D3DX
0054312: 1336: General: CDXCore::Initialize: Choosing adapter
0054312: 1336: General: CDXCore::Initialize: Testing capabilities
0054312: 1336: General: CDXCore::Terminate: Start
0054312: 1336: General: CDXCore::Terminate: Cleanup
0054328: 1336: General: CDXCore::Terminate: Release Direct3D
0054328: 1336: General: CDXCore::Terminate: Unload D3D.dll
0054390: 1336: General: CDXCore::Terminate: Clearing variables
0054390: 1336: General: CDXCore::Terminate: Finish (78 ms)
0054390: 1336: General: CDXCore::Initialize: Finish (1203 ms)
0054406: 1336: General: CMainUIWnd::Resize: Finish (1250 ms)
0054422: 1336: General: CMCUICore::SetMode: Finish (2125 ms)
0054594: 1336: General: TopLevelExceptionFilter: Unhandled exception -- program crashing
0054594: 1336: General: TopLevelExceptionFilter: Message: 275, wParam: 3, lParam: 0, Window class: JRiver Theater View
Thanks for pointing me to the right problem solution...
-
Please see the stability link in my signature.
-
also try updating DirectX from.Microsoft.
-
Jim,
I'm not new to Media Center and just updated from MC13 to MC14 and it's interesting, the program doesn't crash if I switch the display view to Display #1... as soon as I switch to Display #2 (which is the TV out) it crashes
It might be a driver issue, I admit that. But probably it would be good to tell me what 'Message: 275, wParam: 3, lParam: 0, Window class: JRiver Theater View' means. That might lead me to the problem solution.
Oh, by the way: it's an installation on Win2003 Server SP2
-
would you please be so kind to translate for me, what
Message: 275,
wParam: 3,
lParam: 0,
in Window class: JRiver Theater View means
THANK YOU
-
Are you trying to use Tview thru an RDP session by chance? I have the same prob when I RDP to my server (2003 R2) as well and am yet to find a solution.
-
Are you trying to use Theater View thru an RDP session by chance? I have the same prob when I RDP to my server (2003 R2) as well and am yet to find a solution.
no "Remote Desktop Process" (RDP) session at all... just upgraded from a working MC13 (latest release) to the latest MC14 release
but the developers will tell me for sure what message=275, wParam=3 and iParam=0 means in good ol' English
-
Disable any third party plug-ins.
I don't know if those are MC errors.
-
Jim,
please be so kind and take me for serious!
There are NO third party plug-ins, it is a clean MC 14 install, there is NO virus scanner running as it is an internal server... it can be a driver problem, ok, but your developers have for sure a list of the crash messages (otherwise they wouldn't have programmed it that way), so please be so kind and tell me, what
message 275
wParam 3
iParam 0
means! I'd like to find the problem!
-
JimH, NO RESPONSE is a clear sign for me... do you call this "help" or "support"? I paid you good money for an upgrade from MC13... and think I'm entitled to get a kinda response from you...
YOU are the programmers... YOU have that list of error codes... and it's just looking up that list and give an short answer... but you are way too busy to make people buy the upgrade but then you don't help them when they run into a NEW problem... yes, I'm pissed about your behaviour... where the heck is your well-known good support from the past gone?
oh well
I suppose it is the same crash you fixed in version 100 - "1. Fixed: Playback with visualizations enabled could cause a crash." - as I use visualizations (which by the way got broken and cannot be re-programmed to something else in MC14)
I'll install the new version 101 and report back if the crash is gone
thanks sooo much!
Martin
globetrotters1
-
I answered above. I don't know.
I don't know if those are MC errors.
Did you try a google search?
You haven't said whether you've tried what I suggested above. DirectX, for example.
-
Jim,
I tried version 14.0.101 and have the same crash!
My whole house system, working fine with MC13 last version stands still as I cannot run Theater View at all (and all our touchscreens work only with that). Close to 300'000 music tracks and no music because the program crashes.
Tell me please, what these error codes mean - I did a log and asked nicely to translate me that error code. What does that error code mean?
My Win2003 operating system is at the latest stage, updated as it should be. Tell me please why I should update something which is simply part of the O/S and which I never have touched since the clean install. Did you change something which forces me to re-install a part of the O/S? Not really understandable for me... and furthermore: how should I know what the reason of this crash can be if you DON'T TELL me the meaning of that crash code?
So please be so kind to translate for me
message 275
wParam 3
iParam 0
Thank you!
No insult intended, I just need to solve this problem SOON
-
I think the issue may be that your hardware (or video driver) doesn't support windowed 3D, which is required by Theater View. Obviously this shouldn't crash.
Could you try 3D visualizations from Standard View and see if they work? If not, try updating your video drivers. It's normally best to get drivers directly from nVidia / ATI.
Thanks.
-
Matt,
it works on the same monitor (LCD #1) but crashes on monitor #2 (video)
I replaced DirectX from Micro$oft in the meantime - result: same crash!
I use 3D visualizations in Standard View and they work just fine
I told before that I fully accept if you tell me that it might be the graphics driver. Does this tell you my crash code? I just wanted to know what that code means to get somehow a handle to a possible problem solution
Isn't it also interesting that with the final version MC13 it worked fine and that now with the latest MC14 it doesn't? Somehow weird...
Ok, what I can do is change the whole O/S to Windows 7 Enterprise which I have here. I just need the GPT disk option as my disks are pretty huge in the meantime. So, if you tell me that this would be the best solution I'll do that. Just want to solve this problem please...
Thanks,
Martin
-
Matt,
it works on the same monitor (LCD #1) but crashes on monitor #2 (video)
I replaced DirectX from Micro$oft in the meantime - result: same crash!
The video card is failing when we ask if it supports windowed 3D. I can reproduce the crash (it should show a nice error screen) and it will be fixed next build. This won't help you that much since you'll still have the error screen.
Does this tell you my crash code? I just wanted to know what that code means to get somehow a handle to a possible problem solution
The final code isn't very meaningful (i.e. 275). That's just the windows message the program was processing when it crashed. However, seeing the whole log it's clear that it does "Testing capabilities" of the hardware and then begins a teardown because it failed. Shortly after the program crashes.
The logs aren't really meant to be readable by normal people. We often have to look at source code and concentrate while reading them to figure out what's happening.
Isn't it also interesting that with the final version MC13 it worked fine and that now with the latest MC14 it doesn't? Somehow weird...
Ok, what I can do is change the whole O/S to Windows 7 Enterprise which I have here. I just need the GPT disk option as my disks are pretty huge in the meantime. So, if you tell me that this would be the best solution I'll do that. Just want to solve this problem please...
Thanks,
Martin
I can't explain that. The 3D visuals and Theater View use the same foundation. If you can start one on monitor #2, you should be able to start the other.
I would recommend a video driver update straight from the manufacturer if you haven't done so.
Thanks.
-
Graphics software including driver replaced straight from the manufacturer - same result! sorry
Do you want me to produce another log and see if something changed?
-
I don't suppose the non-working monitor is doing anything funny with refresh rates is it?
This is the only reason I've ever managed to break something on only one monitor :)
-Leezer-
-
I don't suppose the non-working monitor is doing anything funny with refresh rates is it?
This is the only reason I've ever managed to break something on only one monitor :)
-Leezer-
Leezer, you don't know my setup, output #1 on my graphics card is the LCD computer monitor, output #2 is the NTSC video used on special touchscreens. With the same driver set it worked in MC13 like this, under WinXP and Win2003 server. In MC14 it doesn't work anymore, so something has been changed, killing the proper function of Theater View for me. Means: my whole house music system is dead!
Result: upgrade for $24 or so, new graphics card required for $200 or so... thanks a lot :(
-
I solved the whole problem with installing a new graphics controller, latest technology
thanks for the support, Matt