| Event Id | 119 |
| Source | disk |
| Description | The driver for device <device name> delayed non-paging Io requests for <number> ms to recover from a low memory condition. |
| Event Information | Here is the information from a new group post: "When a memory allocation request comes down and there, are not enough pages available to service the request, Mm puts the requester on hold for a certain period, and signals the WS manager to start trimming working sets and write out modified and mapped pages to disk. If the page writers arent able to free up a sufficient number of pages within this time frame, and there are a large number of modified pages waiting to be written out to the pagefile, the system bugchecks: 0x0000004D. In order to assist the modified page writer, the disk driver blocks all other IO requests until a sufficient number of pages have been freed. It then logs an informational event stating the period during which non-paging requests were queued. It looks like someone is allocating a large number of pages and dirtying them thus resulting in a large number of modified pages. You might want to look at all applications that are running when these events are logged and narrow them down to determine the root cause. PS: Overall, this event is no reason for alarm and can be safely ignored". |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.