United Kingdom
Mines same no point attaching logs though as it's same everytime nothing has changed. Bring back restart on resume! I'm getting sick of it!
MP1-4070_BUG_Resuming_from_Standby_not_working (1 Viewer)
- Thread starter Sebastiii
- Start date
Hi I notice you are using HD 4000 graphics. Have you tried upgrading the HD 4000 driver to the latest using the intel driver update utility via http://www.intel.com/p/en_US/support/detect?iid=dc_iduu
There was a documented bug in the HD drivers that caused a similar issue on my HTPC with HD 3000 graphics which fixed some of my problems.
Regards,
Markus
Last edited:
For me when the black screen comes up if you press the start key on the keyboard you can get back to the desktop and do anything else its MP that shows a black screen and freezes. 3-4mins later it will work. Tonight the server was already on and MP worked withing 30seconds but when the server was asleep and I turn the MP on in the kitchen even though the server wakes up MP doesnt respond for 3-4mins with a black screen.
There is no point me attaching the logs as it has been the same since the restart on resume was removed.
There is no point me attaching the logs as it has been the same since the restart on resume was removed.
Last edited:
@markus_g: Usually I am using always the latest drivers, but I will double check it again this evening.
I have two more remarks:
1) My system is perfectly stable, if MePo is not running. During the last weeks I have always closed MePo before Standby to prevent the black screen and started MePo again if I want to watch a DVD with MePo or do something similar. I had never experienced any problems ! But if I leave MePo running during Standby, it shows the black screen of death (BSOD) approx. every second standby/resume cycle. After applying the fix "MP1-2559-Solve_inconsistent_TVService_detection_from_TVServer_in_TVHome, V16" MePo crashed only after 3-5 days. Much better, but still annoying...
2) My computer isn't going into a real standby, as the CPU fan is still running, if I experience the BSOD. Therefore I expect the error somewhere in the "go-to-sleep" code...
*Update: Just checked, I am using the latest Intel driver 9.18.10.3165
I have two more remarks:
1) My system is perfectly stable, if MePo is not running. During the last weeks I have always closed MePo before Standby to prevent the black screen and started MePo again if I want to watch a DVD with MePo or do something similar. I had never experienced any problems ! But if I leave MePo running during Standby, it shows the black screen of death (BSOD) approx. every second standby/resume cycle. After applying the fix "MP1-2559-Solve_inconsistent_TVService_detection_from_TVServer_in_TVHome, V16" MePo crashed only after 3-5 days. Much better, but still annoying...
2) My computer isn't going into a real standby, as the CPU fan is still running, if I experience the BSOD. Therefore I expect the error somewhere in the "go-to-sleep" code...
*Update: Just checked, I am using the latest Intel driver 9.18.10.3165
Last edited:
First time resume worked fine. Second time no audio. Stopping TV and starting it again fixed that. Both time after resume TV swiched back to windowed view (left hand TV, right hand menue)
So far so good. My mp is working like a charm. No fault after this per release! Thanks!
Hi
As requested, I'm posting in this thread the problem I am having. It appears to be exactly the same as the issue cyberfix is having (mentioned in other thread - linked below).
We don't believe it is related to the bug mentioned in this thread but I think kiwijunglist and Owlsroost wanted it stated here to help come up with a solution.
SETUP
Running an Acer RL80 with HD3000 GPU and Windows 8 64bit. (Latest drivers)
Connected via HDMI to Marrantz receiver and then HDMI to Panasonic plasma.
TV server is installed locally although I'm sure it's TV related.
PROBLEM
Put PC to S3 Standby with MePo running fullscreen.
Wake PC from S3 Standby to find Desktop (NOT black screen) is visible instead of MePo. (MePo doesn't show in taskbar either.)
Desktop is not usable because MePo still appears to have full screen focus. (Ctrl-Alt-Del shows MePo still running in task manager.)
Turn off Amp for 20 seconds.
Turn on Amp.
MePo is back and displaying perfectly!
(In 20% of cases MePo also then pops up with a crash dialog, although this appears to be a secondary issue.)
Details are in the following thread. https://forum.team-mediaportal.com/...-in-task-manager-after-upgrade-to-1-4.120603/
I'm really hoping you can help or at least point to an issue in the logs. I know it's not your problem that I use the free MePo the way I do, but MePo has been our main setup for ages now, we use it all day and unfortunately is made is difficult for the wife & kids to use.
Log attached from 12_08_13 is with the above desktop problem but without the crash at the end.
As requested, I'm posting in this thread the problem I am having. It appears to be exactly the same as the issue cyberfix is having (mentioned in other thread - linked below).
We don't believe it is related to the bug mentioned in this thread but I think kiwijunglist and Owlsroost wanted it stated here to help come up with a solution.
SETUP
Running an Acer RL80 with HD3000 GPU and Windows 8 64bit. (Latest drivers)
Connected via HDMI to Marrantz receiver and then HDMI to Panasonic plasma.
TV server is installed locally although I'm sure it's TV related.
PROBLEM
Put PC to S3 Standby with MePo running fullscreen.
Wake PC from S3 Standby to find Desktop (NOT black screen) is visible instead of MePo. (MePo doesn't show in taskbar either.)
Desktop is not usable because MePo still appears to have full screen focus. (Ctrl-Alt-Del shows MePo still running in task manager.)
Turn off Amp for 20 seconds.
Turn on Amp.
MePo is back and displaying perfectly!
(In 20% of cases MePo also then pops up with a crash dialog, although this appears to be a secondary issue.)
Details are in the following thread. https://forum.team-mediaportal.com/...-in-task-manager-after-upgrade-to-1-4.120603/
I'm really hoping you can help or at least point to an issue in the logs. I know it's not your problem that I use the free MePo the way I do, but MePo has been our main setup for ages now, we use it all day and unfortunately is made is difficult for the wife & kids to use.
Log attached from 12_08_13 is with the above desktop problem but without the crash at the end.
Last edited:
Hi Sebastiii,
here are two new crash logs. A detailed description was has happened:
1) 19.8., 20:33 Switched on TV and MePo displayed the home screen. The clock in the upper right corner was stuck at 4:06. MePo does not react on any remote inputs. I had to switch to the Windows desktop and close MePo with the Task Manager
2) 20.8., 6:44: Watched yesterday evening a movie with MePo and pressed the off button (->standby) on my remote afterwards. The screen dimmed down to black (as usual) but it suddenly appears again in full brightness. Again MePo doesn't react on any inputs and I had to use the Task Manager this morning to close it.
Hope you are able to locate this nasty error. Good luck !
here are two new crash logs. A detailed description was has happened:
1) 19.8., 20:33 Switched on TV and MePo displayed the home screen. The clock in the upper right corner was stuck at 4:06. MePo does not react on any remote inputs. I had to switch to the Windows desktop and close MePo with the Task Manager
2) 20.8., 6:44: Watched yesterday evening a movie with MePo and pressed the off button (->standby) on my remote afterwards. The screen dimmed down to black (as usual) but it suddenly appears again in full brightness. Again MePo doesn't react on any inputs and I had to use the Task Manager this morning to close it.
Hope you are able to locate this nasty error. Good luck !
- Thread starter
- Moderator
- #20
For Case 1:
I can see that : PS: Error in getting master volume - audio device is not active (DEVICE_STATE_NOTPRESENT) so maybe related like slikvik but not sure.
For Case 2 : affectively it seems the standby was not ready to go in staby, there is a log line and PC wake up and i'm not sure that 'master volume issue' is related but that possible.
I can see that : PS: Error in getting master volume - audio device is not active (DEVICE_STATE_NOTPRESENT) so maybe related like slikvik but not sure.
For Case 2 : affectively it seems the standby was not ready to go in staby, there is a log line and PC wake up and i'm not sure that 'master volume issue' is related but that possible.