DVD Shrink - 100% CPU usage, then crash.

  • Thread starter Thread starter Ian Jackson
  • Start date Start date
I

Ian Jackson

I would appreciate advice on the following:
When DVD Shrink is doing the encoding, the CPU usage is 100%. After
about 10 minutes, the computer crashes (presumably CPU overheats). I can
only overcome this by allowing an encoding run of (say) 10%, then pause
for a couple of minutes before doing another 10%, and so on.

OS is XP (SP2 not installed), 1.70GHz Intel Pentium 4, Bus Clock 100MHz,
Memory 1.28GB.

Does anybody else have this problem, and is there any fix?
Ian.
--
 
Does anybody else have this problem, and is there any fix?
Ian.
Click to expand...

Anything that pushed my CPU too hard was causing lock ups. I replaced
the fan and 100% CPU no longer causes any problems.
 
I would appreciate advice on the following:
When DVD Shrink is doing the encoding, the CPU usage is 100%. After
about 10 minutes, the computer crashes (presumably CPU overheats). I can
only overcome this by allowing an encoding run of (say) 10%, then pause
for a couple of minutes before doing another 10%, and so on.

OS is XP (SP2 not installed), 1.70GHz Intel Pentium 4, Bus Clock 100MHz,
Memory 1.28GB.

Does anybody else have this problem, and is there any fix?
Ian.
Click to expand...

Never actually had this problem but I have just tried a couple of tests.

If the DVD files are first ripped to HD for processing by DVD Shrink the cpu
runs at 99%

If DVD Shrink accesses the DVD in the DVD drive the cpu runs at about 25%

The "run analysis & backup in low priority mode" setting in preferences does
not appear to make any difference.
 
Anything that pushed my CPU too hard was causing lock ups. I replaced
the fan and 100% CPU no longer causes any problems.
Click to expand...
I had exactly the same problem.

I inadvertently left the connector off the CPU fan when I added a card
and without fail, the PC locked up about 3/4 of the way through each and
every process. As soon as I re-connected the pins, I haven't had a
problem..been two years now.
 
Back
Top