MEP2014 will not shut down properly

Scenestealer wrote on 02/10/2014, 23:28

Hi

Just wonder if anyone else has seen this, but ever since installing MEP2014, I from time to time shut it down and the GUI disappears but later when I check Task Manager I see that the process is still running requiring End Process from there?

Peter

Last changed by Scenestealer on 02/10/2014, 23:28, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 1903, MEP2016, 2020 Premium and prior, VPX7, VPX11. Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 1903, MEP2015 Premium.

Comments

terrypin wrote on 03/10/2014, 16:29

Hi Peter,

I don't think I've had that one, but then I may not have known unless I'd gone looking for it in TM.

What does definitely happen occasionally is that I'll close it down because of a freeze or misbehaviour of some sort, and on trying to open it again I get a message that it already running. I assume that's because I was too impatient and MEP needs 'recovery time'.

Terry, East Grinsted, UK 

johnebaker wrote on 03/10/2014, 19:17

Hi

I have experienced something similar a couple of times and on both occassions I know it was caused by me trying to reopen MEP too quickly after closing it properly.

It appeared to delay the services stopping for a few minutes but they did shut down in the end allowing me to start MEP again.

John

Last changed by johnebaker on 03/10/2014, 19:17, changed a total of 1 times.

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

Scenestealer wrote on 04/10/2014, 00:30

Thanks for the feedback.

In my case I have found it running the next morning after MEP was closed and the computer put into sleep!

I am aware of the stituation with trying to open it too quickly and discovered that there is a lot of disk activity after closing and found this to be windows flushing video files out of the cache and replacing them with other irrelevant, sometimes very old files. It was taking several minutes for the "Disk Thrashing" to stop so I decided to disable the Superfetch service in Vista. This stopped the disk activity with no performance hit when using MEP, or any other program for that matter.

This had no bearing on the shutdown problem I am seeing as it was doing it before I disabled Superfetch.

Peter

Last changed by Scenestealer on 04/10/2014, 00:30, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 1903, MEP2016, 2020 Premium and prior, VPX7, VPX11. Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 1903, MEP2015 Premium.

johnebaker wrote on 04/10/2014, 00:45

Hi

. . . . In my case I have found it running the next morning after MEP was closed and the computer put into sleep! . . . .

It would.

When you put the computer to sleep is saves the state of the computer including all the current running processes, stops virtually everything running and goes into a very low power state.

When you wake the computer up it reloads the last known saved state, starts all the processes that were running when you put it to sleep and continues from where it left off.

If you want to stop everything and have the computer to start anew then you must shut it down not put it to sleep (hibernate)

John

Last changed by johnebaker on 04/10/2014, 00:45, changed a total of 1 times.

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

Scenestealer wrote on 04/10/2014, 01:00

Yes I am aware of that John and I was fairly sure that I had given MEP plenty of time to shut down, which it does now with my Superfetch tweak, before putting it to sleep. The sleep thing is a red herring as I can find it still running an hour later when wide awake.

Peter

Last changed by Scenestealer on 04/10/2014, 01:00, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 1903, MEP2016, 2020 Premium and prior, VPX7, VPX11. Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 1903, MEP2015 Premium.

johnebaker wrote on 04/10/2014, 01:20

Hi Peter

Thanks for the update, apologies if I appeared to be telling you how to suck eggs .

It sounds like something is holding the process open.  As the issue is there without Superfetch running it must be another process.

Have you checked the process tree for the MEP service or the service dependancies? 

You could use Process Monitor from Windows SysInternals to log exactly what is happening and hopefully find out the cause.

HTH

John

Last changed by johnebaker on 04/10/2014, 01:20, changed a total of 2 times.

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

Scenestealer wrote on 04/10/2014, 01:27

No problem here - I shouldn't have clouded the issue.

Thanks for the tips and link. I will do some fossicking when I get a moment.

Cheers

Last changed by Scenestealer on 04/10/2014, 01:27, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 1903, MEP2016, 2020 Premium and prior, VPX7, VPX11. Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 1903, MEP2015 Premium.