|
|||||||
This is a discussion on Rollback RX taking a lot of cpu within the RollBack Rx forums, part of the Disaster Recovery Programs category; Lately, I've seen one of the cores of my 2-core processor getting 100% occupied during something like 10-20 minutes at ...
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Lately, I've seen one of the cores of my 2-core processor getting 100% occupied during something like 10-20 minutes at a time, for no apparent reason. Using Process Explorer, I found that the processes occupying the cpu are either System or SHDSERV.exe. When it is System, Process Explorer tells me that it is the Shield.sys thread that is occupying the cpu. At these times, if I try to open the GUI of Rollback RX, it takes very long (1 minute or more) to open.
When this happens, Rollback RX isn't supposed to be doing anything special, like taking a snapshot or defragging. Can someone help me to solve this issue? Has anyone seen any similar behavior? I've only seem a similar, but apparently more limited version of this problem in post http://horizondatasys-forum.com/roll...k-process.html and that post doesn't mention any solution. Thanks in advance for any help. |
|
|||
|
Some more information.
My operating system: Windows Vista Business SP2 32 bit. When it is System that is taking the cpu, Process Explorer says that the thread is Shield.sys+0x6dbc. I guess that 0x6dbc is the address of the routine that is being executed within Shield.sys. This may help to understand what is going on. My version of Rollback Rx is 9.0, build 2694141964. Last edited by kabluiii; 03-03-2010 at 05:52 AM. Reason: Adding some further information |
|
|||
|
Quote:
Yes, the lack of a resolution is true of almost of all threads. People get a complex problem and discuss it in the Forum. They are eventually sent to the Service Ticket system. If their problem gets solved, hardly anyone reports back to the Forum to let the rest of us know. Which is exactly the same situation we would see if the problem didn't get solved. Now, I would continue on and on in this vein, but I live in a glass house and throwing stones is not a good idea.
__________________
Cheers, DMC
|
|
||||
|
Quote:
I think that our development team would need some log files to see what disk activity is occuring on your PC. For this you would need to submit a support ticket (as advised by DMC Campbell): Please attach the following 3 files and include them in your support ticket. You can submit your support request at http://support.horizondatasys.com setup.log (c:\program files\shield) subconsole.log (c:\program files\shield) 128.dat (c:\program files\shield) Thanks. |
|
|||
|
Quote:
My real name is Luis (Portuguese), but it's ok if you call me Bluii or Ka ![]() I understand what you say, and I was not complaining about not finding a resolution. I just mentioned the fact to explain why I was posting about this problem despite having found a similar problem posted in another thread. Last edited by kabluiii; 03-07-2010 at 10:06 AM. Reason: Correct spelling error |
|
|||
|
Quote:
Incidentally, during this manually started defrag, what I observed was very similar to the "spontaneous" activity that I had observed before: Periods of activity of System (thread Shield.sys+0x6dbc) interspersed with shorter periods of activity of SHDSERV.exe. A possibility would be that Rollback RX was autonomously performing defrags, and not stopping them when I started to use the computer. I have the program configured to not perform any automatic defrags. |
|
|||
|
Quote:
Regards, Luis |
![]() |
| Thread Tools | |
| Display Modes | |
|
|