BSOD during backup/system image writing

[tomasjevne]

Hi!

I have had serious issues with BSODs during scheduled backups (many attempted, none succeeded) the past few days. It happens with the Windows 7 backup tool and 3rd party tools.
I am not sure what to think, but ntoskrnl.exe is supposedly a culprit.

My system is Win 7 x64 Ultimate
Asus Sabertooth x58
Intel i7 950 @ stock
3x4 GB Corsair Vengeance

Thing is, I have not had a blue screen for a long time. Relevant changes to system:
External NAS added (could be a reason, I suppose) Synology Disk Station with Synology Assistant installed on my computer for monitoring and administration.

Microsoft USB Keyboard added.

No other new hardware or drivers have been installed

Crashdump from the tool provided in the forum sticky and performance monitor report are attached (I hope).

 

[tomasjevne]

No-one?

 

[tomasjevne]

If it's any help, the error shown was INTERRUPT_EXCEPTION_NOT_HANDLED. My Windows installation is without the SP1.

I have not experienced any BSODs outside of running backups. Could it be that my backup tries to include my NAS as well?

I think there is ample free space for a system image (over 350 GB) on the drive I use for backups.

Been trying to solve this, but the issue persists with regards to ntoskrnl.exe.

 

[tomasjevne]

Ok, if there's something I have left out that people need to know, please tell me. I have run Memtest 86 all night, and no errors were found. My CPU works fine for Prime 95 stress-testing.
I updated my Intel chipset drivers, and I have the latest BIOS from ASUS. I am officially unable to figure out what this is.

Has anyone ever had issues related to backups/system imaging? No 3rd party utility will work, and I ran chkdisk for my system partition as well and still no go. I've cleaned my registry and it seems I am out of options.

 

[tomasjevne]

In case anyone should experience the same issues, I am going to post my solution.

Not unexpectedly, it was Marvell's 6 GB SATA driver that caused the issue. I had updated it, since it seemed like a good idea.

It wasn't.

Uninstalling mv91xx resolved any issue regarding these Blue Screens.