|
DVD Shrink Freezing during backup
|
|
|
pany
Junior Member
|
17. June 2004 @ 07:16 |
Link to this message
|
|
First ? This was posted in another room but had no hits after 3 days?I guess I picked the wrong room (software).
I have been using DVD Shrink 3.1.7 for a few weeks without a problem. Now, when I am doing a backup DVD Shrink freezes my PC and I must reboot. It never freezes at the same point (ie. using the same movie it freezes at 10%; 18%; 6%; 46%). I am using Nero to burn the DVD but it fails during backup. This happens with all DVD?s.
I am using a HP Athalon 1.1ghz, 80gb Hard drive, 384 mb RAM. I have at least 50gb on the hard drive and lately try to run DVD Shrink with at least 175mb of RAM free. My system is XP Home and my DVD Drive is a Lite-On LDW-811S.
I have removed DVD Shrink and re-installed but still have same problem.
If I switch to DVD-X-Copy Platinum it copies and burns without a problem...but I would rather use DVD Shrink.
I know that this topic has come up before. I have read all the theories. Just to let you all know that I have seen and have tried.
I disable my screensaver while running DVD Shrink.
I tried running on low priority,
I tried running it while my Anti-Virus was disabled,
I tried running it by un-attaching Nero from Shrink,
I tried running it with the PC case open and a household fan cooling down the drive (easier than installing a new fan and much quicker to test-also keeps the drive cooler than a PC exhaust fan),
I tried each of the above separately and in different combinations.
Still no success. I tried running it with Task Manager open and it seems to constantly have around 96-100% CPU usage at all times while running Shrink. When the system froze it showed over 100meg of Ram (Physical Memory) available. So it does not look like a memory problem.
Of course when it freezes I cannot bring up Task Manager or anything else.
It would fail anywhere between 8% and 86% encoded. No rhyme or reason as to when it will freeze. Also when I first started to use Shrink it would encode in about a half hour. Now it shows in the estimated time to encode of around 1 hour.
Any suggestions?????
|
|
Advertisement
|
 |
|
|
Moderator
|
17. June 2004 @ 09:56 |
Link to this message
|
Well you've certainly done your homework!
I'll take a stab at it and suggest that updating your ASPI could possibly help (and certainly couldn't hurt).
Here's a good link to the download and instructions:
http://www.hazza.dsl.pipex.com/faq.htm#ASPI
Let us know if this helps :)
My killer sig came courtesy of bb "El Jefe" mayo.
The Forum Rules You Agreed To! http://forums.afterdawn.com/thread_view.cfm/2487
"And there we saw the giants, and we were in our own sight as grasshoppers, and so we were in their sight" - Numbers 13:33 |
|
kyle808
Junior Member
|
17. June 2004 @ 13:00 |
Link to this message
|
|
have you tried uninstalling 3.1.7 and install Shrink 3.0 Beta? That might work... 3.0 Beta works good for me.. no problems.
|
|
pany
Junior Member
|
18. June 2004 @ 07:01 |
Link to this message
|
Nephilim
Quote:
I'll take a stab at it and suggest that updating your ASPI could possibly help (and certainly couldn't hurt).
Tried this last night. I downloaded v 4.71 from adaptec, as v.4.60 is not for XP. After installation I ran Nero Infotools and ASPICK and got the following:
[img]c:/zzz/aspick.gif " border=0>
[img]c:/zzz/nerosys.gif " border=0>
[img]c:/zzz/neronero.gif " border=0>
If the above charts come out clear... you will see according to ASPICK that I am missing WOWPOST.EXE & WINASPI.DLL. In Nero Infotool it shows that for the Nero Aspi it installed WINASPI32.DLL and is working properly, but in Infotool the System Aspi is corrupted.
Anyway I rebooted and then tried to copy a disk. It froze at 17%. I had also installed FreeRam XP Pro which showed that at the time the system froze I had 80meg of Free Ram. The Shrink Encoding screen showed a buffer of 51meg and a rate of 1783kb/s. Even though it showed 17% done it also showed it had 1hr 3min left to go.
What should I do to complete the ASPI install. The guide talks about Part1 & Part2 but 4.71 does not have it segeragted into parts. Or does it appear ok??
|
|
pany
Junior Member
|
18. June 2004 @ 07:11 |
Link to this message
|
kyle808
Quote:
have you tried uninstalling 3.1.7 and install Shrink 3.0 Beta?
If all else fails I will give it a try...but where did you get that version from. Can't find it anywhere, most of the 3.0 links link to the new version and the DVDShrink.com site does not show that version anymore.
|
|
pany
Junior Member
|
18. June 2004 @ 07:32 |
Link to this message
|
Nephilim
The charts did not come out, I will try again:
|
|
pany
Junior Member
|
18. June 2004 @ 07:35 |
Link to this message
|
Nephilim
The aspick chart:
|
|
kyle808
Junior Member
|
18. June 2004 @ 08:18 |
Link to this message
|
well, just so you know.. in Nero it also shows my ASPI for "system" is corrupted, but Nero's ASPI shows be working fine, and DVDshrink and Nero works perfectly, so I don't know what to tell you.
Have you ever thought maybe you need a new burner or DVD-ROM drive... maybe it's your drive that's malfunctioning. try to borrow another drive to rip it to see what happens.
|
|
pany
Junior Member
|
18. June 2004 @ 10:01 |
Link to this message
|
Quote:
Have you ever thought maybe you need a new burner or DVD-ROM drive
The dvd drive works fine with all other programs. If I use Platinum X-Copy I have no problem burning. The problem I am having is the encoding part in DVD Shrink. The Analyzing of the disk in Shrink goes thru fine. It is when it encodes that the system freezes.
|
|
kyle808
Junior Member
|
18. June 2004 @ 10:18 |
Link to this message
|
|
Have you tried another ripper like DVD Decryptor? Maybe you can rip it with DVD Decryptor and then open the files in Shrink and then try backing up again, if it works then you know there's an issue with Shrink and your dvd drive.
maybe you can try ripping to another physical hard drive, not just another partition to see what happens.
have you tried to switch your drive to master or slave, or vice versa.. maybe a faulty IDE cable, try a new one.
Try another stick of memory...
I usually have to try every possible troubleshooting steps when I run into weird problems myself when I get problems. Sounds like you already tried everything, but it wouldn't hurt if you try my suggestions too. good luck.
|
Member
|
18. June 2004 @ 11:54 |
Link to this message
|
|
I used to have simliar problems with my old tower. Check the bios and see if you can run your processor at a lower clock speed. I had a 1050MHz Athlon in this tower, and it was crashing repeatedly (started one day and gradually got worse.) I looked in the bios to see if there might be anything I could change, and I had the option to run my processor at 900MHz, after which it never crashed again. I can't say whether it was a 900MHz processor originally that was overclocked, as that computer was passed onto me as a gift, but do check your bios and see if you can't run your processor at a slower clock speed.
Afterdawn channel on IRC: irc.stormchat.org #ad_buddies
|
AfterDawn Addict
1 product review
|
18. June 2004 @ 12:05 |
Link to this message
|
pany
Download Force Aspi and give it try. When you've installed it then check it using Nero's info tool it will state that Aspi is correctly installed and working.
Force aspi has now been updated to 4.71.2
http://forceaspi18.w.interia.pl/
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. |
|
pany
Junior Member
|
21. June 2004 @ 06:52 |
Link to this message
|
Sophocles
Quote:
Download Force Aspi and give it try.
Thanks for the link. I was able to load ASPI succesfully.
However, still cannot get through the encoding on Shrink.
I will try to look at my Bios next. If not might try to boost my RAM to 512meg from 384 even though that does not look like the problem since when it freezes it always has at least 80 meg available.
|
AfterDawn Addict
1 product review
|
21. June 2004 @ 07:04 |
Link to this message
|
|
Try a couple of simple things first, check your DMA settings. If your Burner is set to P10 then that alone could cause hangups. Make sure hard disk is defragmented. If you have applications running in the background shut them down during encode.
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. |
|
Galbin
Suspended due to non-functional email address
|
21. June 2004 @ 07:10 |
Link to this message
|
Of course...the opposite may be true. One of your memory chips may be expiring. Try removing one chip at a time. DVD Shrink should run fine with only a single 128 meg chip.
|
|
pany
Junior Member
|
23. June 2004 @ 06:41 |
Link to this message
|
Sophocles
Quote:
check your DMA settings
The Primary & Secondary IDE Settings in Device manager show DMA if available.
Mattrage , Galbin
Have not checked the Bios or the memory chips yet. However I think my next step will be to convert from FAT32 to NTFS, and then go from there.
|
AfterDawn Addict
1 product review
|
23. June 2004 @ 07:08 |
Link to this message
|
|
pany
Good idea.
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. |
|
JoeyDryer
Newbie
|
23. June 2004 @ 13:22 |
Link to this message
|
|
I have had the same problem. I have a win2000 sys (3.0 GHz HT, 2Gb ram, brand new Plextor drive). DMA is fine, ASPI is updated. It even freezes in safe mode for god sake. ARGH! Anybody know of a valid link with a more stable older version?
|
AfterDawn Addict
1 product review
|
23. June 2004 @ 13:35 |
Link to this message
|
|
JoeyDryer
I'm not sure I completely understand your question could you elaborate a bit?
" Please Read!!! Post your questions only in This Thread or they will go unanswered:
Help with development of BD RB: Donations at: http://www.jdobbs.com/. |
Senior Member
|
23. June 2004 @ 14:02 |
Link to this message
|
I also had a similar problem with Win2k/NTFS/2.6GHzP4/512DDR with only the essential S/W loaded. As it went, I DL'd DVD Shrink a couple of weeks ago, and it started out problem-free. Then the bugs. I changed (increased) my virtual memory settings, and things seem to be going OK right now. Here is a good discussion (with fixes) concerning virtual memory:
http://aumha.org/win5/a/xpvm.php
You may also be on the verge of a hardware failure problem. The best way to check memory is through a free diagnostic offered by Microsoft: http://oca.microsoft.com/en/windiag.asp . If you get bad chip readings, and they are the same for each module, the chances are that the MB is what is going bad. Intel also has a similar program for its CPU's, however, I don't know about AMD.
|
|
pany
Junior Member
|
24. June 2004 @ 06:06 |
Link to this message
|
Doc409
Quote:
I also had a similar problem
Thanks, I will try these tonight to see if there is a problem.
Last night I converted from FAT32 to NTFS and continue to have same problem.
|
Staff Member
2 product reviews
|
24. June 2004 @ 06:11 |
Link to this message
|
|
You should also remember that just because you have free memory, it doesn't mean Windows will use it. Windows has very specific ideas about when it "needs" to use virtual memory, and if you don't have enough it can "run out" while there's still physical memory free. It's happened to me with CCE before.
|
|
JoeyDryer
Newbie
|
24. June 2004 @ 07:05 |
Link to this message
|
|
You were right on the money about the memory. I have long been having problems with random freezing, and it turns out that at least on stick was screwy. So, right now I am trying to clean up the aftermath it caused to Windows from all the crashing. I'll let everybody know if this all worked.
|
|
JoeyDryer
Newbie
|
24. June 2004 @ 10:54 |
Link to this message
|
|
Works great!
|
|
Advertisement
|
|
|
Senior Member
|
24. June 2004 @ 11:51 |
Link to this message
|
|
JoeyDryer...
It sounds like you used the MS memory diagnostic??? Before I came across it, I thought that memory was either good or bad...sort of like a light bulb. Not so, and this is why checking one stick at a time through boot-up won't always root out a bad stick. Memory can work fine until it has to use a certain routine...and then it will freeze the system in what seems random.
|
