Guest Virgilijus Posted September 20, 2008 Posted September 20, 2008 I have been using Retrospect for quite some time with no problems. Recently I upgraded the hard drive to a larger drive and now Retrospect abends with a BSOD when it starts. After trying to fix the problem with them, it was figured out that the Volume Shadow Copy is the culprit. Why would VSC start causing problems just because I changed to a larger hard drive??? I am running win-xp sp3.
Guest JS Posted September 20, 2008 Posted September 20, 2008 Re: backup causes BSOD Did you have multiple partitions on your old drive and was at least one of those partitions formatted NTFS? Your new drive may need a second partition (source volume for VSC) formatted as NTFS. How Volume Shadow Copy Service Works: http://technet.microsoft.com/en-us/library/cc785914.aspx (Note: see the section titled: System Provider, located about two thirds down the article.) JS http://www.pagestart.com "Virgilijus" <Virgilijus@discussions.microsoft.com> wrote in message news:30980CD4-1B34-443A-A7EA-6950F6473139@microsoft.com... >I have been using Retrospect for quite some time with no problems. >Recently > I upgraded the hard drive to a larger drive and now Retrospect abends with > a > BSOD when it starts. After trying to fix the problem with them, it was > figured out that the Volume Shadow Copy is the culprit. Why would VSC > start > causing problems just because I changed to a larger hard drive??? I am > running win-xp sp3.
Guest Gerry Posted September 20, 2008 Posted September 20, 2008 Re: backup causes BSOD Please provide a copy of the Stop Error Report. The problem could well be Retrospect. A Google search of Retrospect + BSOD produced an unexpected large number of results. -- Hope this helps. Gerry ~~~~ FCA Stourport, England Enquire, plan and execute ~~~~~~~~~~~~~~~~~~~ Virgilijus wrote: > I have been using Retrospect for quite some time with no problems. > Recently I upgraded the hard drive to a larger drive and now > Retrospect abends with a BSOD when it starts. After trying to fix > the problem with them, it was figured out that the Volume Shadow Copy > is the culprit. Why would VSC start causing problems just because I > changed to a larger hard drive??? I am running win-xp sp3.
Guest Bob Harris Posted September 20, 2008 Posted September 20, 2008 Re: backup causes BSOD Have you tried contacting the makers of Retrospect? You might want to ask them if your version has any known issues with (1) disk size, (2) partition size, (3) XP SP3. The only related experience I have had is that the Microsoft backup program called NtBackup.exe became unreliable after I upgraded to SP3 for XP. And, when it fails, it fails with a message that it is trying to start shadow copy. Coincidence? Fortunately, the PC does not blue screen. "Virgilijus" <Virgilijus@discussions.microsoft.com> wrote in message news:30980CD4-1B34-443A-A7EA-6950F6473139@microsoft.com... >I have been using Retrospect for quite some time with no problems. >Recently > I upgraded the hard drive to a larger drive and now Retrospect abends with > a > BSOD when it starts. After trying to fix the problem with them, it was > figured out that the Volume Shadow Copy is the culprit. Why would VSC > start > causing problems just because I changed to a larger hard drive??? I am > running win-xp sp3.
Guest Virgilijus Posted September 21, 2008 Posted September 21, 2008 Re: backup causes BSOD JS, Yes I have 3 partitions on the drive and all of them are formatted with NTFS. "JS" wrote: > Did you have multiple partitions on your old drive and was at least one of > those partitions formatted NTFS? > Your new drive may need a second partition (source volume for VSC) formatted > as NTFS. > > How Volume Shadow Copy Service Works: > http://technet.microsoft.com/en-us/library/cc785914.aspx > (Note: see the section titled: System Provider, located > about two thirds down the article.) > > JS > http://www.pagestart.com > > > "Virgilijus" <Virgilijus@discussions.microsoft.com> wrote in message > news:30980CD4-1B34-443A-A7EA-6950F6473139@microsoft.com... > >I have been using Retrospect for quite some time with no problems. > >Recently > > I upgraded the hard drive to a larger drive and now Retrospect abends with > > a > > BSOD when it starts. After trying to fix the problem with them, it was > > figured out that the Volume Shadow Copy is the culprit. Why would VSC > > start > > causing problems just because I changed to a larger hard drive??? I am > > running win-xp sp3. > > >
Guest Virgilijus Posted September 21, 2008 Posted September 21, 2008 Re: backup causes BSOD Gerry, I get the following: Stop 0x00000019 with the parameters of (0x00000020,0xE38B5740,0xE38B5760,0x0C040201). Even though I have it set to write a mini-dump and the blue screen claims that it was written, there NEVER is a dump there. "Gerry" wrote: > Please provide a copy of the Stop Error Report. > > The problem could well be Retrospect. A Google search of Retrospect + > BSOD produced an unexpected large number of results. > > > -- > > > > Hope this helps. > > Gerry > ~~~~ > FCA > Stourport, England > Enquire, plan and execute > ~~~~~~~~~~~~~~~~~~~ > > Virgilijus wrote: > > I have been using Retrospect for quite some time with no problems. > > Recently I upgraded the hard drive to a larger drive and now > > Retrospect abends with a BSOD when it starts. After trying to fix > > the problem with them, it was figured out that the Volume Shadow Copy > > is the culprit. Why would VSC start causing problems just because I > > changed to a larger hard drive??? I am running win-xp sp3. > > >
Guest Virgilijus Posted September 21, 2008 Posted September 21, 2008 Re: backup causes BSOD Bob, I have and they are the ones that said that it was with VSC. They have no issues with drive size or partition size, nor with XP-SP3, at least none that they have stated. "Bob Harris" wrote: > Have you tried contacting the makers of Retrospect? You might want to ask > them if your version has any known issues with (1) disk size, (2) partition > size, (3) XP SP3. > > The only related experience I have had is that the Microsoft backup program > called NtBackup.exe became unreliable after I upgraded to SP3 for XP. And, > when it fails, it fails with a message that it is trying to start shadow > copy. Coincidence? Fortunately, the PC does not blue screen. > > "Virgilijus" <Virgilijus@discussions.microsoft.com> wrote in message > news:30980CD4-1B34-443A-A7EA-6950F6473139@microsoft.com... > >I have been using Retrospect for quite some time with no problems. > >Recently > > I upgraded the hard drive to a larger drive and now Retrospect abends with > > a > > BSOD when it starts. After trying to fix the problem with them, it was > > figured out that the Volume Shadow Copy is the culprit. Why would VSC > > start > > causing problems just because I changed to a larger hard drive??? I am > > running win-xp sp3. > > >
Guest Gerry Posted September 21, 2008 Posted September 21, 2008 Re: backup causes BSOD Background information on Stop Error message http://msdn2.microsoft.com/en-us/library/ms793223.aspx A pool header issue is a problem with Windows memory allocation. Device driver issues are probably the most common, but this can have diverse causes including bad sectors or other disk write issues, and problems with some routers. (By theory, RAM problems would be suspect for memory pool issues, but I haven't been able to confirm this as a cause.) Source: http://aumha.org/a/stop.htm Are there any yellow question marks in Device Manager? Right click on the My Computer icon on your Desktop and select Properties, Hardware,Device Manager. If yes what is the Device Error code? Try Start, Run, type "sigverif.exe" without quotes and hit OK. What drivers are listed as unsigned? Disregard those which are not checked. Are you backing up to tape? http://snipurl.com/3scxa [forums_dantz_com] A long thread that may be woth investigating: http://www.techspot.com/vb/topic94820.html -- Hope this helps. Gerry ~~~~ FCA Stourport, England Enquire, plan and execute ~~~~~~~~~~~~~~~~~~~ Virgilijus wrote: > Gerry, > > I get the following: Stop 0x00000019 with the parameters of > (0x00000020,0xE38B5740,0xE38B5760,0x0C040201). > > > Even though I have it set to write a mini-dump and the blue screen > claims that it was written, there NEVER is a dump there. > > > > "Gerry" wrote: > >> Please provide a copy of the Stop Error Report. >> >> The problem could well be Retrospect. A Google search of Retrospect + >> BSOD produced an unexpected large number of results. >> >> >> -- >> >> >> >> Hope this helps. >> >> Gerry >> ~~~~ >> FCA >> Stourport, England >> Enquire, plan and execute >> ~~~~~~~~~~~~~~~~~~~ >> >> Virgilijus wrote: >>> I have been using Retrospect for quite some time with no problems. >>> Recently I upgraded the hard drive to a larger drive and now >>> Retrospect abends with a BSOD when it starts. After trying to fix >>> the problem with them, it was figured out that the Volume Shadow >>> Copy is the culprit. Why would VSC start causing problems just >>> because I changed to a larger hard drive??? I am running win-xp >>> sp3.
Recommended Posts