What driver was it? On one of the threads that I am involved in on the Microsoft site it has been discovered that driver 2875 is not showing this issue.
Which Intel CPU are you using? Which driver are you using?
I am using an i7-4770K and it runs Intel HD 4600 graphics. I am not sure that driver 2875 will work for me because its readme only mentions 2nd and third generation graphics support (hd 2000, HD 3000).
I can confirm that the issue in question does exist under the following drivers: 3345, 3316, 3277, 3262. I tried some of the 8.0 drivers that I could find as well. Drivers 3272,3257 and 3186 cause WMC to have an all white welcome screen, so they were promptly removed. I have 3107 installed right now and it exhibits the same issue as I have been describing.
Unfortunately for me I am out of drivers to try.
However, I do have my gingers crossed for you. Please report back if it works or not along with the driver details to help out others who stumble upon this thread.
Windows 8.1 System Commit Issue
-
ewtaylo
- Posts: 119
- Joined: Wed Feb 08, 2012 4:54 pm
- Location:
-
HTPC Specs:
-
barnabas1969
- Posts: 5738
- Joined: Tue Jun 21, 2011 7:23 pm
- Location: Titusville, Florida, USA
-
HTPC Specs:
This is a very interesting thread. I don't use Win8, but it's interesting anyway.
I have one comment: It is always a good idea to close Media Center when you are not watching the TV. There are a few reasons for this. First, when any error/warning/info message is displayed while Media Center is running, it will "queue up" until someone presses OK. The result is that you may be forced to press OK many times when you want to start watching TV. This does not happen if Media Center is closed when the error/warning/info message occurred. Also, the PC will use more power with Media Center running. You will reduce your electric bill by closing Media Center.
I have one comment: It is always a good idea to close Media Center when you are not watching the TV. There are a few reasons for this. First, when any error/warning/info message is displayed while Media Center is running, it will "queue up" until someone presses OK. The result is that you may be forced to press OK many times when you want to start watching TV. This does not happen if Media Center is closed when the error/warning/info message occurred. Also, the PC will use more power with Media Center running. You will reduce your electric bill by closing Media Center.
-
3rob3
- Posts: 548
- Joined: Sun Aug 28, 2011 8:48 pm
- Location:
-
HTPC Specs:
ewtaylo,
I am using a Haswell i5 (4440 I think), which uses HD 4600 graphics. The driver I got (3277) was here:
http://us.msi.com/product/mb/Z87M-GAMING.html#download
It was only one night without the issue so it may not actually be fixed, but it has happened every other night except with this driver. Do you have the "Optimization" option in Media Center set to run every night?
Barnabas1969,
Good points, but try teaching my wife that
Actually, I have run like this since MCE2005 days and have never seen the queue'd up message scenario that I can remember.
I am using a Haswell i5 (4440 I think), which uses HD 4600 graphics. The driver I got (3277) was here:
http://us.msi.com/product/mb/Z87M-GAMING.html#download
It was only one night without the issue so it may not actually be fixed, but it has happened every other night except with this driver. Do you have the "Optimization" option in Media Center set to run every night?
Barnabas1969,
Good points, but try teaching my wife that
Actually, I have run like this since MCE2005 days and have never seen the queue'd up message scenario that I can remember.
-
ewtaylo
- Posts: 119
- Joined: Wed Feb 08, 2012 4:54 pm
- Location:
-
HTPC Specs:
alrighty, here is my nightly report.
3rob3- I hope things work out for you, but in my testing 3277 has the memory leak. I have tested all of the following and they all have it: 3383, 3345, 3316, 3277, 3262, 3107, 3055 and 3036. Drivers 3272, 3257 and 3186 have a weird all white main menu for WMC, so they got removed very quickly from my system.
Drivers that are reported to work under 8.1 are 2875 and 2884. However they are for 2nd and 3rd generation graphics only. I am tired of working on it tonight, but I may try to install one of them tomorrow just to see what happens.
Here is my latest attempt at a fix. I have installed the absolute latest video driver out there (3383). It has the issue, but I have now changed 8 monitor entries from 1024x768 or 1360x768 to 1920x1080. The concept here is to keep the video output at the desktop resolution even when windows switches video profiles when the tv is turned off.
Remember when you are doing the regedit that there are 5 entries per monitor that must change. In the top "00" key there are two sizes and the Skip entry. In the underlying "00" key there is another set of sizes.
I will have answers in about 12 hours.
@barnabas- I have seen the error/warning messages. If one of my Primes goes down I will get 3 messages per show it cant record. However, Like rob, try telling this to my 19 year old daughter... If this latest attempt does not get me going, I will be trying to add an alt-f4 to the logitech power off sequence and a green button on the power on sequence. That will fix it, but I will have to brace myself for the, "it takes 10 seconds for the picture to come on..." Doing this may also screw up the sequencing if my daughter shuts off the TV while in XBMC instead of WMC.
The real answer is to get Microsoft to fix the issue in DirectX 11.2. Who knows how long that will take.
3rob3- I hope things work out for you, but in my testing 3277 has the memory leak. I have tested all of the following and they all have it: 3383, 3345, 3316, 3277, 3262, 3107, 3055 and 3036. Drivers 3272, 3257 and 3186 have a weird all white main menu for WMC, so they got removed very quickly from my system.
Drivers that are reported to work under 8.1 are 2875 and 2884. However they are for 2nd and 3rd generation graphics only. I am tired of working on it tonight, but I may try to install one of them tomorrow just to see what happens.
Here is my latest attempt at a fix. I have installed the absolute latest video driver out there (3383). It has the issue, but I have now changed 8 monitor entries from 1024x768 or 1360x768 to 1920x1080. The concept here is to keep the video output at the desktop resolution even when windows switches video profiles when the tv is turned off.
Remember when you are doing the regedit that there are 5 entries per monitor that must change. In the top "00" key there are two sizes and the Skip entry. In the underlying "00" key there is another set of sizes.
I will have answers in about 12 hours.
@barnabas- I have seen the error/warning messages. If one of my Primes goes down I will get 3 messages per show it cant record. However, Like rob, try telling this to my 19 year old daughter... If this latest attempt does not get me going, I will be trying to add an alt-f4 to the logitech power off sequence and a green button on the power on sequence. That will fix it, but I will have to brace myself for the, "it takes 10 seconds for the picture to come on..." Doing this may also screw up the sequencing if my daughter shuts off the TV while in XBMC instead of WMC.
The real answer is to get Microsoft to fix the issue in DirectX 11.2. Who knows how long that will take.
-
barnabas1969
- Posts: 5738
- Joined: Tue Jun 21, 2011 7:23 pm
- Location: Titusville, Florida, USA
-
HTPC Specs:
I've found that it's much more reliable to use EventGhost to close/open the Media Center app based on various triggers, depending on how your system is setup. EG can even detect which app is currently in the foreground and make decisions based on that information. It's far better than a macro in your remote control.
-
3rob3
- Posts: 548
- Joined: Sun Aug 28, 2011 8:48 pm
- Location:
-
HTPC Specs:
Dang 
crashed again last night. This time the only error was that my video card did not meet Media Center's minimum requirements.
Sucks, but I'm probably going to have to go back to Win7 if I can't figure this out soon.
crashed again last night. This time the only error was that my video card did not meet Media Center's minimum requirements.Sucks, but I'm probably going to have to go back to Win7 if I can't figure this out soon.
-
ewtaylo
- Posts: 119
- Joined: Wed Feb 08, 2012 4:54 pm
- Location:
-
HTPC Specs:
3rob-
I have nothing to add at this time. Every single HD 4400/4600 driver that I can find has the memory leak issue. We 4400/4600 users are unable to install the HD 4000 drivers because the drivers that do not have the leak only go up to HD 4000. For me it is too much trouble to move back to 8 or 7 so I am moving on to prevention of the issue by the state in which WMC is left when the TV turns off.
barnabas- I am going to try out event ghost. I thought perhaps that someone would have already posted how to start up and shut down WMC but I dont seem to be able to find the correct search terms. Do you perchance have some tips on how to accomplish the feat of stopping and starting WMC?
I have nothing to add at this time. Every single HD 4400/4600 driver that I can find has the memory leak issue. We 4400/4600 users are unable to install the HD 4000 drivers because the drivers that do not have the leak only go up to HD 4000. For me it is too much trouble to move back to 8 or 7 so I am moving on to prevention of the issue by the state in which WMC is left when the TV turns off.
barnabas- I am going to try out event ghost. I thought perhaps that someone would have already posted how to start up and shut down WMC but I dont seem to be able to find the correct search terms. Do you perchance have some tips on how to accomplish the feat of stopping and starting WMC?
-
ewtaylo
- Posts: 119
- Joined: Wed Feb 08, 2012 4:54 pm
- Location:
-
HTPC Specs:
Nevermind, barnabas,
I installed it and messed around with it for a couple of hours. I think I mapped everything needed to my remote control. So how big of a nerd are you if your first reaction to eventghost is, "oh wow... This is cool!"
Here is the most exciting part of event ghost. If it is running and you turn off the TV there is a display disconnect event show in EG. Display Connect is show when you turn on the TV. I used those two items to shutdown and startup WMC.
Lets see if my daughter can control it now.
I have my commit memory trace running in the background so i can check on the levels by alt tabbing out of WMC.
This may be all the workaround I need until the display drivers are fixed.
I installed it and messed around with it for a couple of hours. I think I mapped everything needed to my remote control. So how big of a nerd are you if your first reaction to eventghost is, "oh wow... This is cool!"
Here is the most exciting part of event ghost. If it is running and you turn off the TV there is a display disconnect event show in EG. Display Connect is show when you turn on the TV. I used those two items to shutdown and startup WMC.
Lets see if my daughter can control it now.
I have my commit memory trace running in the background so i can check on the levels by alt tabbing out of WMC.
This may be all the workaround I need until the display drivers are fixed.
-
3rob3
- Posts: 548
- Joined: Sun Aug 28, 2011 8:48 pm
- Location:
-
HTPC Specs:
So I closed Media Center, leaving it at the desktop, before turning the TV off last night. Turned it on this morning and the "your system is running low on memory" message was there. Now I am really stumped!
-
ewtaylo
- Posts: 119
- Joined: Wed Feb 08, 2012 4:54 pm
- Location:
-
HTPC Specs:
So you had it at the desktop and there are no other WMC apps running or scheduled to run? Comskip or anything?
How much RAM in the system? Are you running any extenders?
Here is my morning report. I removed all registry mods that I had made (I did that a couple days ago and neglected to mention it). I installed eventghost and added the MCE remote and the MCE device.
I have event ghost triggering when the display comes and goes. It kills WMC when the display goes away and starts it when the display comes back. That part works well. The more intense part is that you have to map all your remote presses to WMC events. It is not too hard to do, but you do have to realize that it is a task you have to do. I went hours before I realized that eventghost was hooking all the incoming IR signals and they were not getting passed on.
Results with just adding this are as expected. When the TV is on the desktop and the full screen WMC use the same resolution/refresh rate. Therefore there is no memory leak. When the TV turns off WMC is closed and there is no memory leak. So for over 12 hours now I have had no dialog.
Next step will be to make the IR presses more robust and to add in XBMC to the equation.
How much RAM in the system? Are you running any extenders?
Here is my morning report. I removed all registry mods that I had made (I did that a couple days ago and neglected to mention it). I installed eventghost and added the MCE remote and the MCE device.
I have event ghost triggering when the display comes and goes. It kills WMC when the display goes away and starts it when the display comes back. That part works well. The more intense part is that you have to map all your remote presses to WMC events. It is not too hard to do, but you do have to realize that it is a task you have to do. I went hours before I realized that eventghost was hooking all the incoming IR signals and they were not getting passed on.
Results with just adding this are as expected. When the TV is on the desktop and the full screen WMC use the same resolution/refresh rate. Therefore there is no memory leak. When the TV turns off WMC is closed and there is no memory leak. So for over 12 hours now I have had no dialog.
Next step will be to make the IR presses more robust and to add in XBMC to the equation.
-
3rob3
- Posts: 548
- Joined: Sun Aug 28, 2011 8:48 pm
- Location:
-
HTPC Specs:
8Gb's ram.
Yep, just sitting at the desktop with no apps running. There was an extender connected for some amount of time.
Yep, just sitting at the desktop with no apps running. There was an extender connected for some amount of time.
-
barnabas1969
- Posts: 5738
- Joined: Tue Jun 21, 2011 7:23 pm
- Location: Titusville, Florida, USA
-
HTPC Specs:
No, you don't have to map all the IR commands to use the MCE plugin. If you read the thread on the EG forum about the service that intercepts those IR commands, you would have found my post explaining what to do.ewtaylo wrote:The more intense part is that you have to map all your remote presses to WMC events. It is not too hard to do, but you do have to realize that it is a task you have to do. I went hours before I realized that eventghost was hooking all the incoming IR signals and they were not getting passed on.
First, install the service in the "New way to get MCE Remote signals in EG (for Vista/Win7)" EG plugin. Then, apply this registry patch (copy all the code, and save it as a file with a .reg extension, and then double-click it):
Code: Select all
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da]
"RemoteName"="RC6 based MCE remote"
"EnableDebounce"=dword:00000001
"EnableVendorPassThrough"=dword:00000001
"DecoderID"=dword:00000001
"CodeSetID"=dword:00000000
"CodeBitLen"=dword:00000020
"CodeSetNum0"=dword:00000001
"CodeSetNum1"=dword:00000002
"CodeSetNum2"=dword:00000003
"CodeSetNum3"=dword:00000004
"CodeSetNumMask"=dword:00007000
"CodeSetNumShiftBits"=dword:0000000c
"CodeMatchMask"=dword:ffff0f00
"CodeMatchValue"=dword:800f0400
"DataMask"=dword:000000ff
"DataShiftBits"=dword:00000000
"ReportLength"=dword:00000003
"ReportDescriptor"=hex:05,0c,09,01,a1,01,85,01,19,00,2a,3c,02,15,00,26,3c,02,\
95,01,75,10,81,00,c0,06,bc,ff,09,88,a1,01,85,02,19,01,29,ff,15,00,25,01,95,\
01,75,08,81,00,c0,05,01,09,80,a1,01,85,03,19,01,29,ff,15,01,25,ff,95,01,75,\
08,81,00,c0,05,01,09,06,a1,01,85,04,05,07,19,e0,29,e8,75,01,95,08,81,02,19,\
00,29,90,26,ff,00,75,08,95,01,81,00,c0
"ReportMappingTable"=hex:01,00,00,00,04,00,1e,02,00,00,00,04,00,1f,03,00,00,00,\
04,00,20,04,00,00,00,04,00,21,05,00,00,00,04,00,22,06,00,00,00,04,00,23,07,\
00,00,00,04,00,24,08,00,00,00,04,00,25,09,00,00,00,04,00,26,00,00,00,00,04,\
00,27,0b,00,00,00,04,00,28,0a,00,00,00,04,00,29,1d,00,00,00,04,02,25,1c,00,\
00,00,04,02,20,1f,00,00,00,04,00,51,1e,00,00,00,04,00,52,21,00,00,00,04,00,\
4f,20,00,00,00,04,00,50,22,00,00,00,04,00,28,4e,00,00,00,01,08,02,0f,00,00,\
00,01,09,02,23,00,00,00,01,24,02,3b,00,00,00,01,04,02,16,00,00,00,01,b0,00,\
18,00,00,00,01,b1,00,17,00,00,00,01,b2,00,14,00,00,00,01,b3,00,15,00,00,00,\
01,b4,00,1a,00,00,00,01,b5,00,1b,00,00,00,01,b6,00,19,00,00,00,01,b7,00,6e,\
00,00,00,01,cd,00,10,00,00,00,01,e9,00,11,00,00,00,01,ea,00,0e,00,00,00,01,\
e2,00,26,00,00,00,01,8d,00,12,00,00,00,01,9c,00,13,00,00,00,01,9d,00,0c,00,\
00,00,03,82,00,29,00,00,00,03,83,00,2a,00,00,00,03,82,00
Now, you will have events in EG for all your remote control keypresses (ALL remotes, not just your Media Center remote!), AND the Media Center remote will control Media Center directly (without any interference from EG).
-
3rob3
- Posts: 548
- Joined: Sun Aug 28, 2011 8:48 pm
- Location:
-
HTPC Specs:
Before spending too much time configuring Event Ghost for this purpose (closing/opening Media Center when TV turns on/of) I suggest doing more testing. Mine still gives the low memory error every night even after closing Media Center before turning TV off.
-
barnabas1969
- Posts: 5738
- Joined: Tue Jun 21, 2011 7:23 pm
- Location: Titusville, Florida, USA
-
HTPC Specs:
I don't know anything about the memory problem, I'm staying on Windows 7. But EG is well worth the time investment. You'll be amazed what you can do with it. It's far superior to IR Server Suite, and new plugins (and new features to existing plugins) are added all the time.3rob3 wrote:Before spending too much time configuring Event Ghost for this purpose (closing/opening Media Center when TV turns on/of) I suggest doing more testing. Mine still gives the low memory error every night even after closing Media Center before turning TV off.
-
3rob3
- Posts: 548
- Joined: Sun Aug 28, 2011 8:48 pm
- Location:
-
HTPC Specs:
No doubt, very cool and powerful utility. I would like to mess around with it myself for other purposes.
-
ewtaylo
- Posts: 119
- Joined: Wed Feb 08, 2012 4:54 pm
- Location:
-
HTPC Specs:
barnabas-
I did see that thread, but I had not read that far into it. So now that I have it appears to me that when the new service is installed that it also removes those entries from the registry. So your fix is to simply add them back in. Do I understand that correctly?
Also, I had been trying to figure out how to get XBMC reintegrated because I had it working before I started all of this. It seems to me that by adding the registry keys back in that XBMC will also see the IR key presses once again. I am going to test it once I have the .reg file installed again. That will save a ton of work. Thank you very much.
3rob-
My system has 16gig of RAM. I have the process explorer memory graph up and running in the background at all times. In the past 24 hours I think the max commit memory was a touch over 9gig. At that time there were 4 executables or threads named something like mpeg2dvrms.exe running. I was not really paying attention so I am not sure if they were from the comskip or they were part of WMC.
Besides WMC, did you install any other WMC addons or such to your system? Mine is not exhibiting the same memory issue that yours is now that I shut it off when the TV is off.
I did see that thread, but I had not read that far into it. So now that I have it appears to me that when the new service is installed that it also removes those entries from the registry. So your fix is to simply add them back in. Do I understand that correctly?
Also, I had been trying to figure out how to get XBMC reintegrated because I had it working before I started all of this. It seems to me that by adding the registry keys back in that XBMC will also see the IR key presses once again. I am going to test it once I have the .reg file installed again. That will save a ton of work. Thank you very much.
3rob-
My system has 16gig of RAM. I have the process explorer memory graph up and running in the background at all times. In the past 24 hours I think the max commit memory was a touch over 9gig. At that time there were 4 executables or threads named something like mpeg2dvrms.exe running. I was not really paying attention so I am not sure if they were from the comskip or they were part of WMC.
Besides WMC, did you install any other WMC addons or such to your system? Mine is not exhibiting the same memory issue that yours is now that I shut it off when the TV is off.
-
barnabas1969
- Posts: 5738
- Joined: Tue Jun 21, 2011 7:23 pm
- Location: Titusville, Florida, USA
-
HTPC Specs:
Yes, you understand correctly. And, yes, if XBMC was receiving the key presses from the Media Center remote, then adding the registry patch will fix it too.ewtaylo wrote:barnabas-
I did see that thread, but I had not read that far into it. So now that I have it appears to me that when the new service is installed that it also removes those entries from the registry. So your fix is to simply add them back in. Do I understand that correctly?
Also, I had been trying to figure out how to get XBMC reintegrated because I had it working before I started all of this. It seems to me that by adding the registry keys back in that XBMC will also see the IR key presses once again. I am going to test it once I have the .reg file installed again. That will save a ton of work. Thank you very much.
-
barnabas1969
- Posts: 5738
- Joined: Tue Jun 21, 2011 7:23 pm
- Location: Titusville, Florida, USA
-
HTPC Specs:
Also, if my memory is correct, the only values that the plugin removes are:
CodeSetID
CodeSetNum0
CodeSetNum1
CodeSetNum2
CodeSetNum3
So, those should be the only ones you need to add. It won't hurt to add the others in the registry file that I pasted above (unless you've customized the ReportMappingTable), because the values in the file I pasted are the default values.
CodeSetID
CodeSetNum0
CodeSetNum1
CodeSetNum2
CodeSetNum3
So, those should be the only ones you need to add. It won't hurt to add the others in the registry file that I pasted above (unless you've customized the ReportMappingTable), because the values in the file I pasted are the default values.
-
3rob3
- Posts: 548
- Joined: Sun Aug 28, 2011 8:48 pm
- Location:
-
HTPC Specs:
mpeg2dvrms.exe is part of DVRMSToolbox, which you must be using for commercial skipping. 9Gbs of memory in use seems crazy to me.ewtaylo wrote:3rob-
My system has 16gig of RAM. I have the process explorer memory graph up and running in the background at all times. In the past 24 hours I think the max commit memory was a touch over 9gig. At that time there were 4 executables or threads named something like mpeg2dvrms.exe running. I was not really paying attention so I am not sure if they were from the comskip or they were part of WMC.
Besides WMC, did you install any other WMC addons or such to your system? Mine is not exhibiting the same memory issue that yours is now that I shut it off when the TV is off.
I have a bunch of add-ons (Amazon Instant, MediaBrowser 3, a theme), but none of those would be running after closing Media Center. Other than hardware, I had the exact same setup under Win7 with no issue.
-
barnabas1969
- Posts: 5738
- Joined: Tue Jun 21, 2011 7:23 pm
- Location: Titusville, Florida, USA
-
HTPC Specs:
I agree, unless you have a lot of system memory allocated to on-board video.3rob3 wrote:9Gbs of memory in use seems crazy to me.