Windows 7 BSOD - Transfering Files from one Harddrive to another

[Admiral]

This is a fantastic forum you provide!

The Problem:
I am getting a BSOD when transfering a file from a SSD attached to a Marvell SATA controller to a HDD attached to an Intel SATA controller.

Before I start replacing Harddrives I am hopeful, you might be able to shed some light on the real culprit from the minidump logs. This is a new install and all drivers are up-to-date.

To through another wrench into the mix, I am running windows 7 64bit on 2 OCZ Agility 3 SSD in raid 0 mode. (I mention this only because i have had problems with OCZ agility 3 SSD going bad on other machines)


System Specs:
OS: Windows 7 Professional SP1 64bit
CPU: i7-2600k 3.40GHz
Memory: 16gig Corsair DDR3 (recent Memtest - no problems)
Motherboard: ASUS P8z68-V Pro Gen 3
GPU: Onboard Intel HD Graphics 3000, 2 Nvidia 560TIs (LucidVirtu not installed yet)

Please let me know if you need any additional information
Thank you very much for your help!

 

[Admiral]

It was the Marvell controller. Even though I had the latest drivers installed from the ASUS website, it was not the LATEST release from Marvell. After upgrading to the latest Marvell Controller driver, no more BSOD. Finding the driver was a real pain. In the end this website helped me find it: Link Removed - Invalid URL (even if you dont feel comfortable installing a driver from a 3rd party site, it can help you find the EXACT version number you are looking for, this can really help when searching manufacturer's websites.)

 

[Trouble]

Great job. Glad you were able to resolve your problem and thanks for posting back and updating your thread with the solution that worked for you.
Unfortunately the single dump file that you attached did not prove very helpful and didn't include much in the way of a suggestion as to what might be the problem:

BugCheck 3D, {fffff80000b9bf60, 0, 0, fffff8800168078e}
Probably caused by : ntkrnlmp.exe ( nt!KiInterruptHandler+29 )
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff80000b9bf60
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff8800168078e
Debugging Details:
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
CURRENT_IRQL:  5
EXCEPTION_RECORD:  fffff80000b9c708 -- (.exr 0xfffff80000b9c708)
[COLOR=#ff0000][U][B]Cannot read Exception record @ fffff80000b9c708[/B][/U][/COLOR]
TRAP_FRAME:  fffff80000b9c7b0 -- (.trap 0xfffff80000b9c7b0)
[COLOR=#ff0000][U][B]Unable to read trap frame at fffff800`00b9c7b0[/B][/U][/COLOR]
LAST_CONTROL_TRANSFER:  from fffff800036cb2e9 to fffff800036cbd40
STACK_TEXT:  
fffff800`00b9b6a8 fffff800`036cb2e9 : 00000000`0000003d fffff800`00b9bf60 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9b6b0 fffff800`036c7629 : 00000000`00000002 00000000`00000002 fffff800`00b9bf60 fffff800`036f6da0 : nt!KiBugCheckDispatch+0x69
fffff800`00b9b7f0 fffff800`036f6a6d : fffff800`038d3d20 fffff800`03814d8c fffff800`0364f000 fffff800`00b9c708 : nt!KiInterruptHandler+0x29
fffff800`00b9b820 fffff800`036f5845 : fffff800`03814d84 fffff800`00b9b898 fffff800`00b9c708 fffff800`0364f000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b850 fffff800`037067c1 : fffff800`00b9c708 fffff800`00b9bf60 fffff800`00000000 fffffa80`173984e8 : nt!RtlDispatchException+0x415
fffff800`00b9bf30 fffff800`036cb3c2 : fffff800`00b9c708 fffffa80`17387b60 fffff800`00b9c7b0 00000000`00000000 : nt!KiDispatchException+0x135
fffff800`00b9c5d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiInterruptHandler+29
fffff800`036c7629 90              nop
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  nt!KiInterruptHandler+29
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2
FAILURE_BUCKET_ID:  X64_0x3D_nt!KiInterruptHandler+29
BUCKET_ID:  X64_0x3D_nt!KiInterruptHandler+29

However, BlueScreenView did suggest that the Marvell Controller might be the culprit

Dump File

Crash Time

Bug Check String

Bug Check Code

Parameter 1

Parameter 2

Parameter 3

Parameter 4

Caused By Driver

Caused By Address

032812-16910-01.dmp

3/28/2012 14:47

INTERRUPT_EXCEPTION_NOT_HANDLED

0x0000003d

fffff800`00b9bf60

00000000`00000000

00000000`00000000

fffff880`0168078e

mv91xx.sys

mv91xx.sys+3178e

In any event, nice work.
Thanks for joining our community and we hope to continue to see you around the forum.
Regards
Randy