 |
 |
» » lucky_week | I just installed the ImageModeler 4.0.2 demo.
If I start the program, and just do nothing more,
I notice it uses a LOT of CPU - between 20% and 35%.
I have a Pentium 4 3.0 GHz E "Prescott" -socket478,
this is a very hot CPU model, and I use a Zalman Cu 7000B fan.
The fan speed is controlled by the temperature of the CPU,
so I notice right away when the CPU load is increased.
But then, when I opened a model, and tried to navigate in the 3d space..
I suddenly saw that the CPU load was down to 5% - 10%.
So I tried to turn the program on / off and load models, and this is what I found out:
When starting IM, CPU load will be very, very high (20-35%). This high CPU load will continue forever, unless you..: Click on the blue Space Manipulator icon in the lower right corner of the 3D View Workspace.
(Pressing then "N" keyboard shortcut will not help...!)
If you choose "File" -> "New", the high CPU load will start again.
The "click navigate icon" fix to stop the high CPU load
only works when turning on the blue Space Manipulator in 3D Space.
Clicking the red Image Manipulator icon when showing image(s) will not decrease the CPU load. This means that when starting a new project and importing images,
placing markers, calibrating etc., the high CPU load will be there all the time.
Is this high CPU load issue fixed in the retail 4.0.3 upgrade? |
lucky_week | I just noticed:
Whenever ImageModeler.exe is in the "very high CPU load mode",
there is also another process that is using a lot of CPU cycles..:
C:\WINDOWS\system32\CSRSS.exe
Of its 12 threads, there are 4 that increases their CPU load together with ImageModeler.exe
These 4 threads are 4 instances of
C:\WINDOWS\system32\CSRSRV.dll!CsrValidateMessageString+0x180
ImageModeler.exe and CSRSS.exe / CSRSRV.dll are together using ca. 50% CPU load.
And since I have a HyperThread enabled PC, I believe 50% is maximum,
meaning they would have used 100% CPU load if I had disabled HyperThreading..
Is this issue only in the demo version of ImageModeler?
I can not understand why not anyone have asked about this in the forum before.
Or is it just my PC?
My OS is Windows XP Pro SP1, I have a Nvidia Quadro FX 4000 (AGP8X) graphic card,
I am using ForceWare 77.56 WHQL drivers,
and my GDI+ library (GdiPlus.dll) is version 5.01.3101.0000
Apple Quicktime Pro 7.0.4 is installed, and TechSmith EnSharpen 1.0.1 codec is installed.
I have an M-Audio / Midiman "Oxygen8" MIDI controller connected to an USB port,
using driver "C:\WINDOWS\system32\usbkt1x1.dll" version 4.1.21 |
lucky_week | Thanks for your reply!
I am 100% sure I do not have the Nimda.E worm! (Or any other worm/trojan)
I read about it in http://www.trendmicro.com/vinfo/vi [...] EE&VSect=T
and in
http://www3.ca.com/securityadvisor [...] x?ID=10397
I have none of the symptoms described in these pages.
To verify that my
C:\WINDOWS\system32\csrss.exe file really is OK, I did 3 things:
1. I uploaded it to the free online scan site
http://virusscan.jotti.org/
and 15 of 15 scanner's results was "Found nothing"
2. I compared file checksums:
I generated checksums for C:\WINDOWS\system32\csrss.exe:
[code:1:2bf67a27ce]CRC-32: FDE17D49
MD5: B82CD0AD8B605F64EAD6C46D70A2C993
SHA-1: D35FE3415D73546BEA7F1B84A8DB53628881342A[/code:1:2bf67a27ce]
I then inserted the original Windows XP cd, and extracted out its csrss.exe to C:\TEMP
by opening a Command Prompt and entering
expand D:\I386\CSRSS.EX_ C:\temp\csrss.exe
[code:1:2bf67a27ce]C:\temp>expand D:\I386\CSRSS.EX_ C:\temp\csrss.exe
Microsoft (R) File Expansion Utility Version 5.1.2600.0
Copyright (C) Microsoft Corp 1990-1999. All rights reserved.
Expanding d:\i386\csrss.ex_ to c:\temp\csrss.exe.
d:\i386\csrss.ex_: 1714 bytes expanded to 4096 bytes, 138% increase.[/code:1:2bf67a27ce]
Then I generated the file checksums for C:\temp\csrss.exe:
[code:1:2bf67a27ce]CRC-32: FDE17D49
MD5: B82CD0AD8B605F64EAD6C46D70A2C993
SHA-1: D35FE3415D73546BEA7F1B84A8DB53628881342A[/code:1:2bf67a27ce]
3. I compared the two csrss.exe files:
I used the "DOS 5 File Compare Utility", C:\WINDOWS\system32\fc.exe,
by opening a Command Prompt and entering
fc /B C:\WINDOWS\system32\csrss.exe C:\temp\csrss.exe
[code:1:2bf67a27ce]C:\temp>fc /B C:\WINDOWS\system32\csrss.exe C:\temp\csrss.exe
Comparing files C:\WINDOWS\SYSTEM32\csrss.exe and C:\TEMP\CSRSS.EXE
FC: no differences encountered[/code:1:2bf67a27ce]
So, my csrss.exe is the orginal one;
4096 bytes
32-bit time_t (Time Date Stamp) 0x3B7D846F = 17/08/01 20:54:07
created 23. august 2001, 12:00:00 (GMT w/o DST)
modified 23. august 2001, 12:00:00 (GMT w/o DST)
Also, if it had been the Nimda.E one,
it would have been strange that it only reacted to ImageModeler..! |
woodyrulesok | Did anything ever come of this?
MatchMover does something very similar.
As soon as mm is launched the cpu reading shoots to 100% and stays there constantly. As soon as mm is closed cpu level drops to normal.
Not really an issue except if your running any other programs at the same time like maya for example. This happened wth matchmover 3 and 4. |
» »
|
 |
 |
|