W
williamgault
Don't let the blue screen trick you, it's actually not a video error but rather it occurs on multiple PCs after USOCOREWORKER.EXE gobbles up all the memory. Does anyone know how to reign in this Microsoft update service that's causing issues?
Sample eventlog from a PC, spaced it out and put in commas for readability:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory:
usocoreworker.exe (5316) consumed 5,612,122,112 bytes,
svchost.exe (5900) consumed 464,953,344 bytes,
and MsMpEng.exe (3796) consumed 350,650,368 bytes.
Following this event PCs with 8GB of RAM will freak out and then eventually blue screen with errors like VIDEO DXGKRNL FATAL ERROR.
I mean, really, do we need to upgrade to 16 GB of RAM so Microsoft's update services stop crashing computers?
Basically what I'm asking is if anyone knows how to put an upper limit on this service so it stops crashing computers or if they are aware of a fix for it, or alternatively if anyone knows what happens if you disable it long term? Disabling it has fixed the issues on the many computers we see this issue.
Continue reading...
Sample eventlog from a PC, spaced it out and put in commas for readability:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory:
usocoreworker.exe (5316) consumed 5,612,122,112 bytes,
svchost.exe (5900) consumed 464,953,344 bytes,
and MsMpEng.exe (3796) consumed 350,650,368 bytes.
Following this event PCs with 8GB of RAM will freak out and then eventually blue screen with errors like VIDEO DXGKRNL FATAL ERROR.
I mean, really, do we need to upgrade to 16 GB of RAM so Microsoft's update services stop crashing computers?
Basically what I'm asking is if anyone knows how to put an upper limit on this service so it stops crashing computers or if they are aware of a fix for it, or alternatively if anyone knows what happens if you disable it long term? Disabling it has fixed the issues on the many computers we see this issue.
Continue reading...