photo

spiritfly

shared this problem
4 months ago

Employees Involved

photo

SCM

Admin

Statistics

13
Comments
1
Views

Share

Tags

12
votes

SCM Crashing Every Few Hours

I have only one task enabled which is scheduled to run every minute. It only scrapes google for content and is set to produce articles in a folder. It takes keywords from file and uses internal "Soft Spinner".

I seems to be working well, however for some reason I find SCM closed after a few hours. I never noticed how exactly SCM closes, because it happens after 5+ hours after I start it, but it seems like there is no message or anything, it is simply closed when I look at the monitor.

This is the only task that is running and it seems to be working pretty well while I watch. Do you have any ideas?

Add Comment

Comments (13)

photo Employee
10

Are you running this on windows server 2008 etc?

photo
8

No, on a windows 10 machine, but I do access the machine with remote desktop if that matters.

photo Employee
9

spiritfly wrote:

No, on a windows 10 machine, but I do access the machine with remote desktop if that matters.
If you are able to, can you look at the System error log for anything SCM related.

https://www.cyberlink.com/support/faq-content.do?id=10449

photo
11

SCM wrote:

spiritfly wrote:

No, on a windows 10 machine, but I do access the machine with remote desktop if that matters.
If you are able to, can you look at the System error log for anything SCM related.

https://www.cyberlink.com/support/faq-content.do?id=10449

http://prntscr.com/ebsgx5

http://prntscr.com/ebsgzr

  1. Application: SEOContentMachine.exe

    Framework Version: v4.0.30319

    Description: The process was terminated due to an internal error in the .NET Runtime at IP 66FA919B (66E10000) with exit code 80131506.

  1. Faulting application name: SEOContentMachine.exe, version: 4.17.2.20, time stamp: 0x58aae7f1

    Faulting module name: clr.dll, version: 4.6.1586.0, time stamp: 0x575a139f

    Exception code: 0xc0000005

    Fault offset: 0x0019919b

    Faulting process id: 0x2d74

    Faulting application start time: 0x01d28c6357537809

    Faulting application path: C:\Users\Mega\AppData\Local\SEOContentMachine4\SEOContentMachine.exe

    Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll

    Report Id: cbed2aa4-014e-4440-8f30-90718c5e45de

    Faulting package full name:

    Faulting package-relative application ID:

photo Employee
11

Thanks for posting this, the problem is phantomjs.exe and the way .NET tries to launch and manage the process.

The same problem happens on Windows Server 2008.

I've tried many things so far unable to find fix to the problem.

Its the first time I've had it reported happening on Windows 10.

photo Employee
15

Can you try updating your version of .NET to the newest?

photo
9

SCM wrote:

Can you try updating your version of .NET to the newest?
Just tried to update with the lastest version 4.6.2: http://prntscr.com/eby0q6

Apparently I have the latest.

Do you have any other suggestions?

photo
10

I've restarted the PC to check if it somehow affects this, but just noticed this in the first few seconds after launch of SCM: http://prntscr.com/ec0k1j

I was also getting it the past few days while it was crushing, but I never read it and thought it was caused by something else.

photo
10

By the way, same thing when I try to install this hotfix: http://prntscr.com/ec0mqz

photo Employee
10

Can you send me a quick email again and I will give you download link to private beta fix.

photo
8

SCM wrote:

Can you send me a quick email again and I will give you download link to private beta fix.
Just wanted to tell you, the setup you sent on my email didn't help. It's still crashing randomly after a few hours of work. :(

photo Employee
9

spiritfly wrote:

SCM wrote:

Can you send me a quick email again and I will give you download link to private beta fix.
Just wanted to tell you, the setup you sent on my email didn't help. It's still crashing randomly after a few hours of work. :(
Yes you are correct according to my testing, updating to .NET 4.5 hasn't fixed any of the issues.

I have another idea on how to fix things.

Leave Comment

photo