True Image 2013 BSOD

Larsa,

Have you performed a Windows update or installed any new software recently?

Are you using Try and Decide?

It looks as though one of the Acronis files has become corrupt or Windows registry has thrown a wobbly. The first thing to try is to run the True Image installer again and select 'repair' . If the problem still exists after rebooting the PC and you don't use Try and Deicde then Try and Decide can be disabled and that might be a temporary workaround.

Colin,

Yes, after the last successfull incremental backup Nov 2, I have run Windows Update four times (Nov 2, 7, 9 and 13) installing only Windows Defender defintions.

On Nov 11, there was an update installed to the software QucikTime and 'Apple program support' from Apple. Please note that I have got several BSOD before this Apple update.

Also - on Nov 2, there was an update installed to the software 'Classic Shell' from Ivosoft. Not sure if this last one was done before or after the successfull backup the same day. Thats all.

I have used Try and Decide once, sometime in October and I have run successfull backups after that.

As you recommended I have now also reinstalled True Image 2013 (selecting 'repair') and restarted my PC.
After that I started a new incremental backup today at 19.45. In the True Image Log from this session there are four entries, the last one being 'Pending operation 151 started: Creating partition image' the same minute at 19.45. Comparing the log from the last successfull incremental backup session on Nov 2, there are three log entries missing the first being 'Pending operation 148 started: Saving partition structure' about 12 min after the backup started.

There was today a 6 Gb backup file created but trying to access it gives an error message saying it is corrupt and True Imaqe does not recognize it.

At 20.34, i.e 49 minutes after the backup started I got a new BSOD but this time not caused by 'Acronis Try&Decide Volume Filter Driver' but by 'NT Kernel & System' according to the BSOD info below. Still I think I can blame Acronis True Image 2013 for this BSOD as well.

You mentioned that Try and Decide can be disabled as a workaround. How is that done?

==================================================
Dump File : 111312-40872-01.dmp
Crash Time : 2012-11-13 20:34:05
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 0x00000003
Parameter 2 : 0x88bb5ad0
Parameter 3 : 0x88bb5c3c
Parameter 4 : 0x83024e10
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+dee98
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+dee98
Stack Address 1 : ntkrnlpa.exe+2df2a1
Stack Address 2 : ntkrnlpa.exe+25ce5a
Stack Address 3 : ntkrnlpa.exe+25cd9d
Computer Name :
Full Path : C:\Windows\Minidump\111312-40872-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 144 080
==================================================

//Larsa

Where are you storing the images?

I'm not convinced that TIH is causing your NTkernel crash, but to disable Try and Decide, press Windows Start button + r and then type in Services.msc - from here you can disable or set to manual the ACDP service.

The images are stored on an external Lacie 1TB HDD connected thru eSATA.

I will disable the ACDP service and rerun a TI backup session and see what will happen. I get back to you later with the result.

/Larsa

Hmm, now I'm confused...

You talked about an ACDP service. I can't find that one on my system.
The services that I think belong to Acronis True Image 2013 are:
1) Acronis Nonstop Backup Service (started / automatic)
2) Acronis Schedule2 Service (started / automatic)
3) Acronis Sync Agent Service (started / automatic)

What am I missing ?

Well, after some research I found that the short name for 'Acronis Nonstop Backup Service' was AFCDPsrv.
Because this name was close to the ACDP service you mentioned I thought this must be the one.

After stopping this service I rerun the incremental backup. And this time I kept my eyes on the progress bar.
When the backup session was almost ready - time left was only 1 minute - I got a new BSOD again.

This time the BSOD was caused by the 'Acronis Try&Decide Volume Filter Driver' again, according to the BSOD info below.

What can I do next? I could send the Minidump files if that would help.

==================================================
Dump File : 111412-41699-01.dmp
Crash Time : 2012-11-14 02:36:05
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0xc046e878
Parameter 2 : 0xc0000185
Parameter 3 : 0x644d9be0
Parameter 4 : 0x8dd0f000
Caused By Driver : tdrpman.sys
Caused By Address : tdrpman.sys+6e6b4
File Description : Acronis Try&Decide Volume Filter Driver
Product Name : Acronis Try&Decide
Company : Acronis
File Version : 1,1,0,1061
Processor : 32-bit
Crash Address : ntkrnlpa.exe+dee98
Stack Address 1 : ntkrnlpa.exe+a3442
Stack Address 2 : ntkrnlpa.exe+a6d25
Stack Address 3 : ntkrnlpa.exe+90446
Computer Name :
Full Path : C:\Windows\Minidump\111412-41699-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 144 080
==================================================

From Microsoft:

This Stop message indicates that the requested page of kernel data from the paging file could not be read into memory. This Stop message is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.

Also from Microsoft:

The error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007A states that the requested page of kernel data from the paging file could not be read into memory. It appears that there are some issues with the hard disk.

Use check disk command for any errors on hard disk -

Warning: Microsoft does not recommend interrupting the CHKDSK process. Microsoft does not guarantee the integrity of the disk if the CHKDSK program is interrupted. For safety you can back up your data before using the check disk command.

Use the check disk commands as follows:
1. Click Start.
2. In search window type 'cmd' and ENTER. Right click and select 'Run as administrator'.
3. Type at the command prompt CHKDSK C: and press ENTER to scan the disk.
4. Then type CHKDSK C: /F /R and press ENTER to repair corrupt sectors, if there are any.

NOTE: The root drive has to be C: and the command may schedule a task at the system startup, if it does, then press Y to schedule a task and restart the computer to perform chkdsk.
Once chkdsk completes, boot to the desktop and then check.

James,
You were right.
The info above told me to do a backup before using CHKDSK - but as you know that was not possible.
Therefore I used DiskClone - but with no success, because DiskClone reported errors in several disk segments.
Well, I did had a consolidated backup from Nov 2 (I thought) so I tried CHKDSK anyway. But with no success - and it made my system unbootable..
Now was the time for me to get a new HDD - and at the same time I switched to a SSD.
Installed it and started to recover from the Nov 2 backup. NO success - the backup was corrupted. But I'm sure the consolidation operation was successful.
Luckily, I had another old backup from Oct 10 that worked - and I also managed to save my newer personal data from the erroneous HDD.
So after a couple of days of hard work - I'm now back in business. And I have now successfully run new Acronis True Image 2013 backups.

Larsa,

Sorry to here about the hardware issues and the backup file problems, but, I am also glad to here you are off to a good start with new hardware.

Be sure to validate your backups occasionally, to check for problems with the backup files. Never rely on just one backup.

James