L4 Stops Working and isn't quite right!

Over the past few weeks I have noticed that after L4 signs in and synchronizes it becomes stuttery and I get a "not responding" message. I have also noticed that L4 isn't quite as smooth as it normally is and seems to be chewing resources.

It seems to happene after the program has been running for an hour or so. Almost same time every day. I have checked updates and scheduled tasks all to no avail.

Is this a known or common issue?

Any help would be appreciated. I have been losing days over this. I have run checks and counter checks. I have restarted the computer. I have run anti virus software (AVG) etc. and all of my drivers are up to date.

I also notice that the speakers are crackly from time to time. Usually when I am watching something on line. Not at first but after a while. I have very good internet and modem is a ok.

I have a HP Laptop running Windows 7 32 bit Home Premium, i7 processor, 4 gig ram, 500 Gig HD and a 1 gig graphics card.

Find more posts tagged with

Comments

Keep Smiling 4 Jesus :)

Almost same time every day. I have checked updates and scheduled tasks all to no avail.

For Logos, if have diagnostic logging enabled, could look in Logos4.log file for repeating pattern.

For Windows, wonder if "at" being used ?

Keep Smiling [:)]

Mark Stevens

https://community.logos.com/discussion/comment/342982#Comment_342982

05407.Logos4.log

I have attached my log file from a recent day. Not sure what it says.

What do you mean "at" being used? [:)]

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/343041#Comment_343041

What do you mean "at" being used?

The AT command schedules commands and programs to run on a computer at

a specified time and date. The Schedule service must be running to use

the AT command.

AT [\\computername] [ [id] [/DELETE] | /DELETE [/YES]]

AT [\\computername] time [/INTERACTIVE]

[ /EVERY:date[,...] | /NEXT:date[,...]] "command"

\\computername Specifies a remote computer. Commands are scheduled on the

local computer if this parameter is omitted.

id Is an identification number assigned to a scheduled

command.

/delete Cancels a scheduled command. If id is omitted, all the

scheduled commands on the computer are canceled.

/yes Used with cancel all jobs command when no further

confirmation is desired.

time Specifies the time when command is to run.

/interactive Allows the job to interact with the desktop of the user

who is logged on at the time the job runs.

/every:date[,...] Runs the command on each specified day(s) of the week or

month. If date is omitted, the current day of the month

is assumed.

/next:date[,...] Runs the specified command on the next occurrence of the

day (for example, next Thursday). If date is omitted, the

current day of the month is assumed.

"command" Is the Windows NT command, or batch program to be run.

Keep Smiling [:)]

Mark Stevens

https://community.logos.com/discussion/comment/343045#Comment_343045

Huh...?

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/343048#Comment_343048

Huh...?

Apologies: should have included explanation about at command usage:

Windows has a command "AT" that can be used to schedule items to run, which does not appear in Task Scheduler. In an administrative command prompt, typing at shows if anything has been scheduled to run at a future time:

By the way, looking in my Windows 7 Task Scheduler, noticed many tasks, including some with daily repeats:

Windows only shows scheduled tasks in the lowest level folder so can take a bit of effort to see daily tasks (clicking folders to see what tasks are in them).

Curious about time of day when Logos 4 is not quite right ?

Keep Smiling [:)]

Mark Stevens

https://community.logos.com/discussion/comment/343053#Comment_343053

I am sorry, I am still lost!

Mark Stevens

https://community.logos.com/discussion/comment/343058#Comment_343058

I managed to work out what a command prompt is. I ran it and nothing! Thanks for the suggestion.

Dave Hooton

Over the past few weeks I have noticed that after L4 signs in and synchronizes it becomes stuttery and I get a "not responding" message. I have also noticed that L4 isn't quite as smooth as it normally is and seems to be chewing resources.

Enable diagnostic logs, run L4 and upload logos4.log just after this happens -- read carefully http://wiki.logos.com/Diagnostic_Logging

You might also try monitoring processes to see what is happening.

High usage processes will be at the top after you click "Average CPU". You can provide a similar screenshot as follows -- http://wiki.logos.com/Screenshot