T
Tony
Recently our server performance dropped significantly and we started getting
memory error left and right. When we looked in TaskManager we saw an
instance of svchost.exe taking up 90% of our total RAM and over 1.3 gigs of
Virtual Memory! Another symptom of our problem was under the directory
\System32\NTMSData is a file called NTMSIDX which is a whopping 1.3 gigs!
I've enver seen this file over a few hundred Kilobytes.
If I delete this NTMSIDX file and reboot, some process during startup would
take an extremely long time (again, svchost.exe) using 90+% of the CPU. When
it finally stops, I look in NTMSData folder again and sure enough, that
NTMSIDX file is back as a gigantic 1.3 gig behemoth. Trying to edit the
NTMSIDX file during the time svchost.exe is taking forever to do "something"
affirms that it is writing tot he file, since I get a shared access
violation.
Furthermore, if I run tlist.exe with the -s switch, I see that the instance
of svchost.exe that's taking forever to load and writing to NTMSIDX is tied
to a subprocess called NTMS.
And also when svchost finishes, it keeps almost all my RAM and 1.3 gigs of
virtual memory allocated to itself indefinitely.
So my questions are:
1. Why is my NTMSIDX file so large?
2. Why does the NTMS process take such an enormous amount of resources? I
read on MSDN that NTMS is somethign to do with RSM, which is some database
that manages removable storage devices among other device management tasks.
We have nothign extreme on our machine and no hardware changes in this time.
We use no removable sotrage either.
3. How do I stop it from stealing all my system's resources?
memory error left and right. When we looked in TaskManager we saw an
instance of svchost.exe taking up 90% of our total RAM and over 1.3 gigs of
Virtual Memory! Another symptom of our problem was under the directory
\System32\NTMSData is a file called NTMSIDX which is a whopping 1.3 gigs!
I've enver seen this file over a few hundred Kilobytes.
If I delete this NTMSIDX file and reboot, some process during startup would
take an extremely long time (again, svchost.exe) using 90+% of the CPU. When
it finally stops, I look in NTMSData folder again and sure enough, that
NTMSIDX file is back as a gigantic 1.3 gig behemoth. Trying to edit the
NTMSIDX file during the time svchost.exe is taking forever to do "something"
affirms that it is writing tot he file, since I get a shared access
violation.
Furthermore, if I run tlist.exe with the -s switch, I see that the instance
of svchost.exe that's taking forever to load and writing to NTMSIDX is tied
to a subprocess called NTMS.
And also when svchost finishes, it keeps almost all my RAM and 1.3 gigs of
virtual memory allocated to itself indefinitely.
So my questions are:
1. Why is my NTMSIDX file so large?
2. Why does the NTMS process take such an enormous amount of resources? I
read on MSDN that NTMS is somethign to do with RSM, which is some database
that manages removable storage devices among other device management tasks.
We have nothign extreme on our machine and no hardware changes in this time.
We use no removable sotrage either.
3. How do I stop it from stealing all my system's resources?