If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Why does msinfo32.exe take 49.9 of resources and freeze the computer?
I have taken to running Process Monitor with the processes sorted by CPU usage, so that I can "quickly" suspend msinfo32exe when it grabs "half" the cpu and freezes everything else. Usually I notice this when PaleMoon is running and suddenly the mouse pointer just stops. Then begins the move mouse on the desk and aim for the procmon window, then try to get the pointer on msinfo32 and then suspending/ terminating it is "simple". Googleing it leads me to the conclusion that MS seems to believe I really do want to run it, when what I want to know is why is it running in the first place? Why is it running up to eight copies, and why is it hogging resources so much? Does anyone have any good ideas on how to prevent this, or is this another MS "enhancement to my computer experience" whether I like it or not? grumble pyotr -- pyotr filipivich The question was asked: "Is Hindsight overrated?" In retrospect, it appears to be. |
Ads |
#2
|
|||
|
|||
Why does msinfo32.exe take 49.9 of resources and freeze the computer?
pyotr filipivich wrote:
I have taken to running Process Monitor with the processes sorted by CPU usage, so that I can "quickly" suspend msinfo32exe when it grabs "half" the cpu and freezes everything else. Usually I notice this when PaleMoon is running and suddenly the mouse pointer just stops. Then begins the move mouse on the desk and aim for the procmon window, then try to get the pointer on msinfo32 and then suspending/ terminating it is "simple". Googleing it leads me to the conclusion that MS seems to believe I really do want to run it, when what I want to know is why is it running in the first place? Why is it running up to eight copies, and why is it hogging resources so much? Does anyone have any good ideas on how to prevent this, or is this another MS "enhancement to my computer experience" whether I like it or not? Did you leave logging on and on and on and ... All those events are getting logged while ProcMon is running. Filtering only changes what you see. ALL events are still logged. When that logfile gets huge, not only does it require lots of resources to keep updating such a huge file but can also eat up your free disk space with a huge log file. Did you try clearing its logfile to start anew each time you start ProcMon? By Process Monitor, I have to assume you are talking about SysInternals' (now owned by Microsoft) Process Monitor, not the Performance Monitor included in Windows. Neither of those start msinfo32.exe so you started that program. The problem with the huge logfile mentioned above is when using Process Monitor (ProcMon). I haven't use Performance Monitor often enough to know how big its logfile will get or if it even has a logfile function. Stop the monitoring in ProcMon (Ctrl+E or click the magnifying glass toolbar button). Clear its logfile (Ctrl+X or eraser-across-page toolbar icon). Then start monitoring anew (Ctrl+E to toggle on the monitoring). Once I realized ProcMon was storing ALL events in a logfile and that was causing the slowdown, I realized it was a user error in how I was using ProcMon. I thought it was logging only the events that I allowed via filtering. Nope, it logs them all and filtering is just a view of what you want to select from the entire logfile. |
#3
|
|||
|
|||
Why does msinfo32.exe take 49.9% of resources and freeze the computer?
VanguardLH on Mon, 18 Dec 2017 22:12:56 -0600 typed in
alt.windows7.general the following: pyotr filipivich wrote: I have taken to running Process Monitor with the processes sorted by CPU usage, so that I can "quickly" suspend msinfo32exe when it grabs "half" the cpu and freezes everything else. Usually I notice this when PaleMoon is running and suddenly the mouse pointer just stops. Then begins the move mouse on the desk and aim for the procmon window, then try to get the pointer on msinfo32 and then suspending/ terminating it is "simple". Googleing it leads me to the conclusion that MS seems to believe I really do want to run it, when what I want to know is why is it running in the first place? Why is it running up to eight copies, and why is it hogging resources so much? Does anyone have any good ideas on how to prevent this, or is this another MS "enhancement to my computer experience" whether I like it or not? Did you leave logging on and on and on and ... All those events are getting logged while ProcMon is running. Filtering only changes what you see. ALL events are still logged. When that logfile gets huge, not only does it require lots of resources to keep updating such a huge file but can also eat up your free disk space with a huge log file. Did you try clearing its logfile to start anew each time you start ProcMon? I don't have ProcMon logging anything. And msinfo32 will start up before I start Procmon. What happens is all of a sudden the computer drops to a crawl, the mouse pointer doesn't move, if I am patient, I'll work it over to a short cut, start it, wait for it, work the pointer to the column CPU, sort by usage, and work it down to msinfo32, and evenutal I'm able to suspend. (If I am not patient, I use the BRS interupt to reboot) Basically, I'm moving the mouse, then waiting for the screen to catch up, then seeing if where I moved the mouse 15 seconds ago is the correct spot, if not try again, and see if it's now in the correct spot, and repeat - until either I can kill msinfo32, or it deigns to return the use of the mouse/keyboard/computer in general to me. Which still leaves me with this annoying problem that msinfo32 is starting up just to start up and interfere with my computer experience - whether I had procmonitor running or not. At least with procmonitor running, I cut out several steps where I'm moving and clicking hoping I found the shortcut when the mouse gets polled. -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#4
|
|||
|
|||
Why does msinfo32.exe take 49.9% of resources and freeze the computer?
On Mon, 18 Dec 2017 21:12:02 -0800, pyotr filipivich
wrote: VanguardLH on Mon, 18 Dec 2017 22:12:56 -0600 typed in alt.windows7.general the following: pyotr filipivich wrote: I have taken to running Process Monitor with the processes sorted by CPU usage, so that I can "quickly" suspend msinfo32exe when it grabs "half" the cpu and freezes everything else. Usually I notice this when PaleMoon is running and suddenly the mouse pointer just stops. Then begins the move mouse on the desk and aim for the procmon window, then try to get the pointer on msinfo32 and then suspending/ terminating it is "simple". Googleing it leads me to the conclusion that MS seems to believe I really do want to run it, when what I want to know is why is it running in the first place? Why is it running up to eight copies, and why is it hogging resources so much? Does anyone have any good ideas on how to prevent this, or is this another MS "enhancement to my computer experience" whether I like it or not? Did you leave logging on and on and on and ... All those events are getting logged while ProcMon is running. Filtering only changes what you see. ALL events are still logged. When that logfile gets huge, not only does it require lots of resources to keep updating such a huge file but can also eat up your free disk space with a huge log file. Did you try clearing its logfile to start anew each time you start ProcMon? I don't have ProcMon logging anything. And msinfo32 will start up before I start Procmon. What happens is all of a sudden the computer drops to a crawl, the mouse pointer doesn't move, if I am patient, I'll work it over to a short cut, start it, wait for it, work the pointer to the column CPU, sort by usage, and work it down to msinfo32, and evenutal I'm able to suspend. (If I am not patient, I use the BRS interupt to reboot) Basically, I'm moving the mouse, then waiting for the screen to catch up, then seeing if where I moved the mouse 15 seconds ago is the correct spot, if not try again, and see if it's now in the correct spot, and repeat - until either I can kill msinfo32, or it deigns to return the use of the mouse/keyboard/computer in general to me. Which still leaves me with this annoying problem that msinfo32 is starting up just to start up and interfere with my computer experience - whether I had procmonitor running or not. At least with procmonitor running, I cut out several steps where I'm moving and clicking hoping I found the shortcut when the mouse gets polled. Seems like the big question is why is msinfo32.exe starting and running? That's most odd. You should be able to prevent that from happening. -- Char Jackson |
#5
|
|||
|
|||
Why does msinfo32.exe take 49.9% of resources and freeze the computer?
pyotr filipivich wrote:
VanguardLH: pyotr filipivich wrote: I have taken to running Process Monitor with the processes sorted by CPU usage, so that I can "quickly" suspend msinfo32exe when it grabs "half" the cpu and freezes everything else. Usually I notice this when PaleMoon is running and suddenly the mouse pointer just stops. Then begins the move mouse on the desk and aim for the procmon window, then try to get the pointer on msinfo32 and then suspending/ terminating it is "simple". Googleing it leads me to the conclusion that MS seems to believe I really do want to run it, when what I want to know is why is it running in the first place? Why is it running up to eight copies, and why is it hogging resources so much? Does anyone have any good ideas on how to prevent this, or is this another MS "enhancement to my computer experience" whether I like it or not? Did you leave logging on and on and on and ... All those events are getting logged while ProcMon is running. Filtering only changes what you see. ALL events are still logged. When that logfile gets huge, not only does it require lots of resources to keep updating such a huge file but can also eat up your free disk space with a huge log file. Did you try clearing its logfile to start anew each time you start ProcMon? I don't have ProcMon logging anything. As soon as you enable it capturing events, yep, it is LOGGING. The default when loading ProcMon (and after defining any filters) is to start capturing. Even if you disable capture in a session of ProcMon and clear its log, capture is enabled by default in the next session you start when loading ProcMon. That's why you can see past events that it logged. That's why you can define filters to change the *view* of what you see in the log (not what gets added to the log -- which is EVERYTHING gets put into the log). If you don't enable capture mode then you won't see any new events so there is little use (just past past events, not new events) for ProcMon. And msinfo32 will start up before I start Procmon. What's the point of leaving msinfo32 loaded if it will never change anything it listed from the prior scan? You can load it, look at its scan results, maybe save it, and then exit. Or you can load msinfo32, look at what it scanned now, and then later do a refresh to see if there were any changes. I don't see a setting in msinfo32 that has it re-poll for hardware changes at some periodic interval. If ProcMon is showing event from the msinfo32.exe process then that program is [still] scanning. On my computer, the scanning is done within a second of loading msinfo32 (versus Piriform's Speccy that takes much longer to do a scan). If msinfo32.exe is sucking up half the CPU usage then it is scanning (the first one it does when loaded or by having it do a refresh). What happens is all of a sudden the computer drops to a crawl, the mouse pointer doesn't move, if I am patient, I'll work it over to a short cut, start it, wait for it, work the pointer to the column CPU, sort by usage, and work it down to msinfo32, and evenutal I'm able to suspend. (If I am not patient, I use the BRS interupt to reboot) Either the problem is with msinfo32 (which should not be sucking up lots of CPU time because its scan should be quick) or because you have a huge logfile in ProcMon which is choking the data bus on your mobo between your memory and CPU and storage media. Which still leaves me with this annoying problem that msinfo32 is starting up just to start up and interfere with my computer experience - whether I had procmonitor running or not. At least with procmonitor running, I cut out several steps where I'm moving and clicking hoping I found the shortcut when the mouse gets polled. msinfo32 doesn't "just start up". YOU load it manually, as a startup program you added to your Startup folder (or the All Users one), as a scheduled event, or by some other means msinfo32.exe because a startup program. If you don't want it to load on logging into Windows, try using msconfig.exe to see if it is listed as a Startup Item. If it is not listed there, use SysInternals' AutoRuns to check more startup locations (in the file system or in the registry). |
#6
|
|||
|
|||
Why does msinfo32.exe take 49.9% of resources and freeze thecomputer?
pyotr filipivich wrote:
so that I can "quickly" suspend msinfo32.exe Upload it to virustotal.com and scan it ? It's probably a coin miner you picked up or something. Just because malware has a "name you recognize", doesn't mean it's a good guy. Obviously the run policy has nothing to do with Microsoft, and it's running eight copies for some other reason, unrelated to your computer usage. Paul |
#7
|
|||
|
|||
Why does msinfo32.exe take 49.9% of resources and freeze the computer?
In message , Char Jackson
writes: [] Seems like the big question is why is msinfo32.exe starting and running? That's most odd. You should be able to prevent that from happening. That does seem to be the question. Then, as VanguardLH says it should run in a second or so, I think Paul's question of whether it's malware that has replaced your normal msinfo32.exe might be a good question. A lazy way forward, especially if you don't need what it does, would be to rename it to something else, so that whatever is starting it would not succeed in doing so. However, I don't know what it actually _does_, so if Windows needs it, that could break your system. If Windows _doesn't_ need it, then you _might_ get some indication - such as a popup window headed Fred saying "Fred can't find msinfo" - of what is triggering it, though you might not. -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf Grief generates a huge energy in you and it's better for everybody if you harness it to do something. - Judi Dench, RT 2015/2/28-3/6 |
#8
|
|||
|
|||
Why does msinfo32.exe take 49.9% of resources and freeze the computer?
"J. P. Gilliver (John)" on Tue, 19 Dec 2017
12:31:12 +0000 typed in alt.windows7.general the following: In message , Char Jackson writes: [] Seems like the big question is why is msinfo32.exe starting and running? That's most odd. You should be able to prevent that from happening. That does seem to be the question. Then, as VanguardLH says it should run in a second or so, I think Paul's question of whether it's malware that has replaced your normal msinfo32.exe might be a good question. A lazy way forward, especially if you don't need what it does, would be to rename it to something else, so that whatever is starting it would not succeed in doing so. However, I don't know what it actually _does_, so if Windows needs it, that could break your system. If Windows _doesn't_ need it, then you _might_ get some indication - such as a popup window headed Fred saying "Fred can't find msinfo" - of what is triggering it, though you might not. Sounds like a plan. Ufda. pyotr -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#9
|
|||
|
|||
Why does msinfo32.exe take 49.9% of resources and freeze the computer?
Char Jackson on Tue, 19 Dec 2017 01:20:25 -0600
typed in alt.windows7.general the following: Basically, I'm moving the mouse, then waiting for the screen to catch up, then seeing if where I moved the mouse 15 seconds ago is the correct spot, if not try again, and see if it's now in the correct spot, and repeat - until either I can kill msinfo32, or it deigns to return the use of the mouse/keyboard/computer in general to me. Which still leaves me with this annoying problem that msinfo32 is starting up just to start up and interfere with my computer experience - whether I had procmonitor running or not. At least with procmonitor running, I cut out several steps where I'm moving and clicking hoping I found the shortcut when the mouse gets polled. Seems like the big question is why is msinfo32.exe starting and running? That's most odd. You should be able to prevent that from happening. If I knew why, I would. Grumble. But as I said earlier - querying MS on the subject tells me all the good things it des and why I might want to run it. (I had similar miscommunication years back. Query: why can't I access my file?" Answer "Access is a powerful database program..." But I digress.) This morning Msinfo grabbed control of my computer before I'd started process monitor. -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#10
|
|||
|
|||
Why does msinfo32.exe take 49.9% of resources and freeze the computer?
VanguardLH on Tue, 19 Dec 2017 01:47:01 -0600 typed in
alt.windows7.general the following: I don't have ProcMon logging anything. As soon as you enable it capturing events, yep, it is LOGGING. The How do I enable it to capture events? Or unable that? -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#11
|
|||
|
|||
Why does msinfo32.exe take 49.9% of resources and freeze the computer?
VanguardLH on Tue, 19 Dec 2017 01:47:01 -0600 typed in
alt.windows7.general the following: And msinfo32 will start up before I start Procmon. What's the point of leaving msinfo32 loaded if it will never change anything it listed from the prior scan? You can load it, look at its scan results, maybe save it, and then exit. Or you can load msinfo32, look at what it scanned now, and then later do a refresh to see if there were any changes. I am not starting msinfgo32.exe something else is, and I have no idea what it is. I want to kill it "with fire" because it locks the computer up for between 2 to five minutes. As I didn't start it, I don't know why it is running - or what it is doing anyway. -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#12
|
|||
|
|||
crucial tangent detail Why does msinfo32.exe take 49.9% of resources and freeze the computer?
Ufda - my mistake.
I'm _not_ running Process Monitor I'm running Process Hacker. which still doesn't answer why Msinfo32 is starting itself.. pyotr filipivich on Mon, 18 Dec 2017 21:12:02 -0800 typed in alt.windows7.general the following: VanguardLH on Mon, 18 Dec 2017 22:12:56 -0600 typed in alt.windows7.general the following: pyotr filipivich wrote: I have taken to running Process Monitor with the processes sorted by CPU usage, so that I can "quickly" suspend msinfo32exe when it grabs "half" the cpu and freezes everything else. Usually I notice this when PaleMoon is running and suddenly the mouse pointer just stops. Then begins the move mouse on the desk and aim for the procmon window, then try to get the pointer on msinfo32 and then suspending/ terminating it is "simple". Googleing it leads me to the conclusion that MS seems to believe I really do want to run it, when what I want to know is why is it running in the first place? Why is it running up to eight copies, and why is it hogging resources so much? Does anyone have any good ideas on how to prevent this, or is this another MS "enhancement to my computer experience" whether I like it or not? Did you leave logging on and on and on and ... All those events are getting logged while ProcMon is running. Filtering only changes what you see. ALL events are still logged. When that logfile gets huge, not only does it require lots of resources to keep updating such a huge file but can also eat up your free disk space with a huge log file. Did you try clearing its logfile to start anew each time you start ProcMon? I don't have ProcMon logging anything. And msinfo32 will start up before I start Procmon. What happens is all of a sudden the computer drops to a crawl, the mouse pointer doesn't move, if I am patient, I'll work it over to a short cut, start it, wait for it, work the pointer to the column CPU, sort by usage, and work it down to msinfo32, and evenutal I'm able to suspend. (If I am not patient, I use the BRS interupt to reboot) Basically, I'm moving the mouse, then waiting for the screen to catch up, then seeing if where I moved the mouse 15 seconds ago is the correct spot, if not try again, and see if it's now in the correct spot, and repeat - until either I can kill msinfo32, or it deigns to return the use of the mouse/keyboard/computer in general to me. Which still leaves me with this annoying problem that msinfo32 is starting up just to start up and interfere with my computer experience - whether I had procmonitor running or not. At least with procmonitor running, I cut out several steps where I'm moving and clicking hoping I found the shortcut when the mouse gets polled. -- pyotr filipivich Next month's Panel: Graft - Boon or blessing? |
#13
|
|||
|
|||
Why does msinfo32.exe take 49.9% of resources and freeze thecomputer?
pyotr filipivich wrote:
VanguardLH on Tue, 19 Dec 2017 01:47:01 -0600 typed in alt.windows7.general the following: And msinfo32 will start up before I start Procmon. What's the point of leaving msinfo32 loaded if it will never change anything it listed from the prior scan? You can load it, look at its scan results, maybe save it, and then exit. Or you can load msinfo32, look at what it scanned now, and then later do a refresh to see if there were any changes. I am not starting msinfgo32.exe something else is, and I have no idea what it is. I want to kill it "with fire" because it locks the computer up for between 2 to five minutes. As I didn't start it, I don't know why it is running - or what it is doing anyway. If you want to do an offline scan of the computer, you can make a scanning disk with a Bitdefender download. https://www.bitdefender.com/support/...ue-cd-627.html http://download.bitdefender.com/resc...-rescue-cd.iso To avoid trouble, you can do the necessary work on another computer. As some malwares will prevent downloads from sites which host such tools. ******* Your symptoms are puzzling from another point of view. Are you running a high core count processor ? Or is it only a dual core processor. If eight copies of the program are running, and they're using 50% CPU, you must have something like an 8C 16T processor. It's either that, or the Affinity of each copy of the executable, is pointed at a specific core. Which doesn't make a lot of sense. Normally there isn't a lot of interest in modifying affinity settings. https://en.wikipedia.org/wiki/Processor_affinity In this example, Photoshop is being forced to run on CPU0 core. http://www.tech-recipes.com/wp-conte...r3-448x500.jpg Paul |
#14
|
|||
|
|||
Why does msinfo32.exe take 49.9% of resources and freeze the computer?
pyotr filipivich wrote:
VanguardLH : As soon as you enable it capturing events, yep, it is LOGGING. The How do I enable it to capture events? When you load ProcMon, it is already enabled to capture (logging). Even if you disabled it in a prior session of ProcMon, a new session of ProcMon will have logging enabled by default. Or unable that? Mentioned in my first reply to you. |
#15
|
|||
|
|||
Why does msinfo32.exe take 49.9% of resources and freeze the computer?
pyotr filipivich wrote:
I am not starting msinfgo32.exe something else is, and I have no idea what it is. So follow the instructions already provided to you on how to investigate and find startup items. We're not there. You'll have to do the work. You'll have to find the startup item that loads msinfo32.exe and delete or disable it. |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|