Acer Chromebook 315 CB315-3H, model # N19Q3 freezes

Printz1
Printz1 Member Posts: 2 New User
edited July 2 in Chromebooks

I have an Acer Chromebook 315 CB315-3H, model # N19Q3> it was a gift from my son last Christmas/ I have continuous, on-going and annoying problem with freezing screen and cursor freezing. The only way I can get off/out of the screen in to do a forced restart. Please advise how I can resolve this. Thanks.

[Edited the thread to add model number to the title and add issue detail]

Answers

  • billsey
    billsey ACE Posts: 34,672 Trailblazer

    What apps and extensions do you have installed? In almost all cases symptoms like that can be traced to something running that's not behaving.

    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.
  • Printz1
    Printz1 Member Posts: 2 New User

    I don't think I have any apps loaded other than what it came with, I only use for paying bills and occasionally checking email and/or shopping online. I did install drivers, etc to connect with my HP printer.

  • billsey
    billsey ACE Posts: 34,672 Trailblazer

    When it's frozen, can you still move the mouse pointer around, or is it also frozen? If the pointer is frozen it often points to something that takes over the bus and doesn't ever give it back to other tasks. That is more likely to be hardware if you don't have other apps installed. If the mouse pointer still moves it's less likely to be hardware and more difficult to diagnose. Since your son got this for you less than a year ago it might be worthwhile to go ahead and open a ticket with Acer support, since it should still be in warranty.

    Click on "Like" if you find my answer useful or click on "Yes" if it answers your question.
  • Marjan68
    Marjan68 Member Posts: 1 New User

    I have the same problem with my external, wireless mouse since a couple of days. Tried all the simple things, nothing helps. My mouse keeps freezing with every move. I even ordered a wired mouse online this afternoon, but I think it happened after the last update from Chrome OS last week.