2013 Archives

[labayojb]

Well...things were looking up.  They really were.  Then this morning - top corner of the device is warm and won't wake up.

So the problem still persists.  I will continue doing some investigating; it really seems like some process that decides to go amuck and just burns CPU time to the point where the whole system is locked.  Haptic feedback on the 'start' button in the middle still works while this is happening.

[labayojb]

Additional information:
Looking through system and application event logs; not super-duper helpful, but I have 3 standout errors that I'm suspecting are related.  These are the events that occurred between last usage and this morning's lock-up:

1) A timeout was reached (30000 milliseconds) while waiting for the Google Update Service (gupdate) service to connect.

2) DCOM got error "1053" attempting to start the service gupdate with arguments "/comsvc" in order to run the server: <UUIDsomethingorother>

3) A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Apple Mobile Device service.

iTunes (or the Apple Mobile Device service) or the Google updating service are now officially suspect.

[padgett]

I'd suggest checking the configuration for both updaters and turn off automatic updates. Might also be able to stop the two services and then disable them. Can still invoke manually if needed.

Aslo look in Task Manager under STARTUP for things you do not need.

[didopido]

---

labayojb wrote:

Well...things were looking up.  They really were.  Then this morning - top corner of the device is warm and won't wake up.

So the problem still persists.  I will continue doing some investigating; it really seems like some process that decides to go amuck and just burns CPU time to the point where the whole system is locked.  Haptic feedback on the 'start' button in the middle still works while this is happening.

---

I had the same exact symptoms you are describing. That was with Win8.1. Haven't seen it happening with Win8 and the older ver. of the WiFI drivers. But that is really bad news, since I would like to upgrade to Win8.1 one day.

Why is so hard for Acer to reproduce this problem and find a solution?

They have tools that we, the regular users don't and they design and made the tablet.  

[didopido]

---

labayojb wrote:

Additional information:
Looking through system and application event logs; not super-duper helpful, but I have 3 standout errors that I'm suspecting are related.  These are the events that occurred between last usage and this morning's lock-up:

1) A timeout was reached (30000 milliseconds) while waiting for the Google Update Service (gupdate) service to connect.

2) DCOM got error "1053" attempting to start the service gupdate with arguments "/comsvc" in order to run the server: <UUIDsomethingorother>

3) A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Apple Mobile Device service.

iTunes (or the Apple Mobile Device service) or the Google updating service are now officially suspect.

---

When I was experiencing the same issue, I didn't have anything  Apple installed. This may limit the suspects in your list.

But also it may be something totally different, not showing in your list. I had almost all of my startup apps disabled and was still getting the same sleep problem.

[padgett]

You may also have to go through services.msc and turn things off. May also need to look at RUN and RUN Once in the registry.

Just be glad it is not a root kit.

[labayojb]

So it isn't iTunes/Apple.  Had the service stopped and this morning the tablet was frozen/asleep/burning CPU time again.

Looking through event logs there are no errors indicated by either the Apple mobile device service or Google update.  There were some errors with WSearch.exe...

I've also seen a weird system log message indicating an unexpected shutdown (event ID 6008).  The really weird thing about this message is that it is logged sometime in the middle of the night - last night at 5:04:52am and the previous night at 5:36:34am.  The times reported occur sometime *after* the last log messages were recorded in the event log prior to shutdown/restart.

Still diagnosing...to be continued...

[Liliha]

im getting the same issues here, and i also have both mentioned apps installed, will look into this also ..

[david_mayor]

Hello,

I have the same problem as you. If I close it or if I put in standby by briefly pushing the top right button, I can switch it on again only if I do it quickly. Otherwise, after some time (I don't know how much time to be honest), I have to push the button a long time to force it to shut down before being able to fully restart it...

I don't understand why there is no reaction from Acer about that, knowing that Windows 8.1 will be out in about two weeks !

David

[labayojb]

Well, I was off on vacation for the past 4 days but had the w510 with me.  No incidents had occurred at that time.  I can't seem to nail down a pattern of any kind of when this happens or what could potentially cause it.  It's a tad frustrating to be honet.  

Liliha & david_mayor -

Do both of you also experience the CPU utilization/upper corner of the device getting warm and burning through battery as well?

Also, do both of you have microSD cards installed on your machines?