Windows 10- Locks up "waiting for cache"

Anonymous
2020-04-09T15:54:17+00:00

Window 10 was working very well until recently after upgrading to Windows Edge chrome (or at least the is the only event that I can associated to this issue) I am getting persistent OS stalls or "not responding" that affect all applications when running Edge. Common to see "waiting for cache" in lower left browser window when the the entire system stalls and stops responding. Common to see the cursor hour glass for 30 or more seconds before system and affected applications start to respond normally.

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2020-09-17T21:52:56+00:00

Uninstalled chrome and edge. Using Firefox with zero issues

Was this answer helpful?

20+ people found this answer helpful.
0 comments

62 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-09-10T10:58:30+00:00

    My hardware is also AMD - AMD Phenom(tm) II X6 1100T 3.31GHz with 16.0 GByte Ram. I just mention it because although it is a Chromium Edge software issue they may not have accounted for any subtle difference in the code needed to run with Intel/AMD processors.

    Thats some dam good tech work cluing in on the AMD cpu! I've been struggling with this issue for years via Chrome.

    Thought was the net adapter, then bad ssd, then switched to edge and that was fine until the update.

    Was just noticing the cpu spike when the waiting for cache froze. 

    Good work in here guys thanks a lot!!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-09-07T20:07:15+00:00

    For me, the problem would occur just about every time I opened Edge, a new tab, or navigated to a new site. 

    I just took the actions N1ck7 recommended and so far so good.  I have tried no other steps, so unless I post back here - this setting may be the real deal.  

    Thanks N1ck7!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-09-02T20:48:47+00:00

    Datasailor, I agree with you. That is all I did as well.

    Further to this, I think the problem may have been resolved in the 2020-08 Cumulatives, installed on my laptop and Surface Pro on 13th August.

     I have been using new Edge again since then with no issues at all.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-09-02T18:13:28+00:00

    I personally believe the root source of these issues lays within the both browser's chrome code and is not related to bios settings or hardware drivers, etc. Why? because all I had to do to resolve the issues was to stop using Google or Windows Chrome browsers. I did not have to make any bios or other radical changes to my system. I did not have to uninstall either or both chrome browsers (I did uninstall Google Chrome, but only to save memory space for more useful apps). Anyway I exclusively use Firefox now and I have not had any recurrences of my "waiting for Cache" and other issues listed in prior messages in this thread.

    Google and Microsoft need to resolve this, I am convinced it is not my workstation or me.

    Was this answer helpful?

    0 comments