Author: skyline69_uk
Subject: Help on IRP_MJ_READ Process Name!
Posted: 09 November 2014 at 2:24pm
I had looked at Repurposed but as it was only 8GB total and nothing over the usual p5 since Friday morning it didn't seem like it should have affected anything and looked fairly normal if not actually low! ![]()
Edited by skyline69_uk - 11 hours 51 minutes ago at 2:56pm
Subject: Help on IRP_MJ_READ Process Name!
Posted: 09 November 2014 at 2:24pm
I had looked at Repurposed but as it was only 8GB total and nothing over the usual p5 since Friday morning it didn't seem like it should have affected anything and looked fairly normal if not actually low!
The Free I confirmed from both RamMap and Resource Manager (RamMap shows just over 10GB zero'd already and over 17GB under the Free column).
The Mapped File use is 1.3GB with 340MB active and the rest standby - I had emptied the standby list yesterday for some testing and then refilled it with MKTLIST etc. to see if it held overnight (which it didn't).
This morning the MTKLIST file was gone from the cache again as were most non-system files (the last machine restart was Friday)???? Repurposed would suggest that no other applications had reclaimed any real amount of memory to eat into the free stuff so it's disappearance would be a bit of a mystery to say the least.
The hard page faulting seems normal for the memory used but it would be hard to tell as I didn't get a look at perfmon when the problem had happened as it resolved itself again too fast :(.
I'll check the page faulting and watch under Disk in PE for physical reads for the process tomorrow if I can get it to start running slow again.
I'm going to monitor the Cache within perfmon too tomorrow to see if that helps any.
Currently today FASTIO is happening all the time now (apart from the initial first run this morning).
I'm going to watch the memory usage when the staff come back into again tomorrow and look for any weirdness.
It is definitely a strange one, almost like something was resetting the standby list when the problem occurs but not being driven by the expected Windows reasons i.e. memory pressure.
Brian
Edited by skyline69_uk - 11 hours 51 minutes ago at 2:56pm