PC Freeze during encoding process

[dafaba]

Dax52-Thanks, that link is great! I got the Shrink 3.0 beta 5 and the encoding process completed successfully, but I could not get that data backed up to a dvdr that would play. I shrunk it and then tried to use Nero to back it up but could not get a good copy that worked. I also plan to try reloading Nero to see if that fixes the problem with the current shrink.

rbrtpl-Yes I reloaded W2k after reformatting the hard drive, then updated all the drivers, and got all the windows updates. And the encoding process locks up anywhere from 1% - 99% it is very random.

I also Defraged the hard drive a few times, it was really needed, but did not fix the problem.

Thanks people, I report more progress later. (I hope there is progress!)

[Chewy]

At 100% compression in reauthor mode shrink isn't doing any real work,
at anything less(which is more compression) it's having to work your computer
hard. The reason 3.2 is so fast and efficient is it's using everything available
to do a difficult job. If 3.2 will rip a movie at 100% but not at say 70%,
I would tend to believe something's wrong with hardware or the OS or both.

[dafaba]

rbrtpl- I think I misunderstood your question when I first answered it, I have had the encoding process lock up on discs that didn't need any compression and on discs that require up to 50% compression. It happens on almost all backups. Most of the time my backups are compressed about 50% give or take 10 or so %. But every once since I started working on this problem I'll get a disc to work, but then the next disc will lockup. The Shrink 3.0 beta 5, did shrink a disc without locking up, but now I need to figure out how to get a good burn from the files it created. I'm sure it's simple, just need to figure it out. However I wish I could get the current version of shrink to work like it did for five months straight before it rolled over and died.

[Chewy]

What version of DirectX are you using and does everything look ok
in device manager, displayadapters(driver date recent), agp(in sys devices)
driver current? What's the chipset for the motherboard?

[Taelon]

Hi again dafaba, I'd also like to know the answers to rbrtpl's questions, as well as the SATA drivers you are using. I'm glad you had success with 3.0b5, could you try version 3.1.2 which you can also find here

I searched thru some of my notes, the only time I've had Shrink lock-up on me was in the midst of summer when the FSB was set @ 175, dropping it to 170 solved the problem. Is your system overclocked at all?

[blutach]

If it is a Nero conflict, try uninstalling it with the Clean Tool. You can burn with DVD Decrypter: Backup --> Select backup target --> ISO image file and burn with DVD Decrypter

Any chance of posting your latest Nero log - it is located at C:\Program Files\Ahead\Nero\NeroHistory.log

Regards

[dafaba]

Hello all, here are some of the answers you requested, plus a log of the steps I have taken in the last two days.

DirectX 9.0c
Nforce3 250 ChipSet, Driver version 8.18.5, 10/10/05
Everything in device manager is up to date & checks out.
Temps in my area are mild, 40-70 and falling everyday.
I burned away during the summer when the temps were 90+ for
weeks and never had a problem.
I don't think my problems is with Nero as I do not get to
the burning process.

log...
10/20
1. Updated GfxC Drivers, restart
2. Updated Chipset Drivers, restart
3. Spybot S&D, scan found nothing
4. Ad-Aware se,found Alexa.? Zapped her. Rescan, found no threats.
5. Updated NVIDIA IDE / SATA driver for nForce3 series V 510, restart
6. Reloaded current dvdshrink, restart
7. Attemped backup, Full disc 56.3% compression, locked system @ 3%., Hard Boot
8. Loaded dvdshrink 3.1.2
9. Attemped backup, Full disc 56.3%, locked system @ 73%, hard boot

10/21
1. Unistalled shrink 3.1.2
2. reinstalled shrink 3.2.0.15, restart.
3. reinstalled Nero 6
(doing this to see if I can get new info in nerohistory log as all info in the current log is only from the very few good burns I've had since problems started.)
3. Attempted backup, pc locked at 1%, hard boot.
4. No Nero log as burning process was never reached.

After the last hard boot I went to post this message and my computer locked up, first time it's done that outside of dvdshrink, so I hard booted, and it happened again, hard boot again, open a IE and then my pc rebooted. I then let it sit there powered off for 10-15 minutes, now I'm back up and haven't crashed. This is very strange however. I'm kinda thinkin it might be the power supply. My PS is a 450W Coolmax that is about 10 months old, and I'm sure these hard boots are not helping anything.
My buddy is going to come over tomorrow and look some things over, he is a master with both hardware and software but knows nothing of dvdshrink or related programs. But something good may come out of it.
Thanks again to all of you pitching in ideas, I really appreciate it and I will report on my progress later in the weekend.

[Chewy]

Can you try 2 or 3 things,
underclock the cpu but not the ram in bios
underclock the ram but not the cpu
disconnect a few optional items(case fans) from the powersupply
remember only do One item at a time

[dafaba]

I am not overclocking, so I will try to disconnect a couple of the fans first.
Thanks.

[Chewy]

If the cpu or ram is starting to go, often it will run underclocked but
not at it's regular settings. For example, a 2Ghz cpu, underclocked to
1.5Ghz, might work, just a way to isolate the problem.
The best way is to start exchanging components one at a time, however
most people don't have spares just laying around.

[blutach]

Moved to General Computing (it's looking like that sorta problem)

Regards

[Chewy]

I am getting the general idea that shrink 3.2 might stress a computer,
especially after prolonged exposure to high compression.

[dafaba]

Well the problem has been fixed, in a way.
My pc checks out 100%, nothing wrong.
But dvdshrink still locks up on the encoding process.
I tried everything, and I won't go into details.
The problem was fixed but transferring the burner to my old dell, and it works on that system, it's so slow, but it works. I may try it again on my main pc someday, but for now this works and it frees up my main pc for other things.
Thanks for all the help, and I hope I can pitch in a few ideas on other peoples problems in the future.

[Chewy]

Sounds like it MIGHT be a power supply
issue.

[dafaba]

That very well could be the case, but since evertything else works I don't want to buy a new one until I start seeing more problems.