Hi MechBot9971.
From teh latest 3 BSODs, it appears to be a multi-fold issue, covering a storage and display. Moreover, out of these three, two are storage related, caused by Marvell.
So you need to uninstall Marvell, Marvell 91xx SATA 6G Controller.
But here is the complication. You have got some complications , both from the part of hardware and software. Aside of Marvell 91xx SATA 6G Controller, you have Generic Marvell 61xx RAID Controller too. That means that you will not be able to uninstall Marvell till you disable the RAID options in BIOS. That is desired, as you are not using any RAID array actually, and RAID is always troublesome.
Well, that will lead to even more problem, because an OS can boot in the storage controller with which it will installed only. Disabling RAID will not allow you to boot into the OS at all.
As I have said that it is a bad installation that you have got, there are some more odd stuff. Like two real time protection programs.
- Start Menu\Programs\AVG
- Start Menu\Programs\ESET
Deadly plan. Neither of them will work in practice.
The best for you would be to go for a
http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html
Before doing it, Disable RAID.
After the installation, dont use Marvell. Dont install Vircual CloneDrive back; and use one Antivirus only.
Then if the display related issue continues, we will pay attention to that; but till the Marvell issue will be there, no troubleshooting will go to an end.
________________________________________________________________________________________
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3D, {fffff880035990e0, 0, 0, fffff8800154af4d}
Unable to load image mv91xx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys ( mv91xx+33f4d )
Followup: MachineOwner
---------
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff880035990e0
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff8800154af4d
Debugging Details:
------------------
CONTEXT: fffff880035990e0 -- (.cxr 0xfffff880035990e0)
rax=fffffa800c199b00 rbx=fffffa800c1ab1d0 rcx=0000000000000000
rdx=fffffa800c1ab1d0 rsi=0000000000000000 rdi=fffffa800c1bbf70
rip=fffff8800154af4d rsp=fffff88003599ac0 rbp=fffffa800c19a0b0
r8=fffff88003f99100 r9=0000000000000000 r10=0000000000000001
r11=fffffa800c19a980 r12=fffffa800c1b74e8 r13=fffff8800357c0c0
r14=fffffa8009a89040 r15=fffff88003576040
iopl=0 nv up ei ng nz ac pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000293
mv91xx+0x33f4d:
fffff880`0154af4d cc int 3
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3D
PROCESS_NAME: System
CURRENT_IRQL: 7
LAST_CONTROL_TRANSFER: from fffffa8009a89040 to fffff8800154af4d
STACK_TEXT:
fffff880`03599ac0 fffffa80`09a89040 : fffff880`03f99100 00000000`80000001 fffffa80`0bffb008 00000000`00000000 : mv91xx+0x33f4d
fffff880`03599ac8 fffff880`03f99100 : 00000000`80000001 fffffa80`0bffb008 00000000`00000000 fffffa80`0c1998d0 : 0xfffffa80`09a89040
fffff880`03599ad0 00000000`80000001 : fffffa80`0bffb008 00000000`00000000 fffffa80`0c1998d0 fffffa80`0bf5f101 : 0xfffff880`03f99100
fffff880`03599ad8 fffffa80`0bffb008 : 00000000`00000000 fffffa80`0c1998d0 fffffa80`0bf5f101 fffff880`0155073a : 0x80000001
fffff880`03599ae0 00000000`00000000 : fffffa80`0c1998d0 fffffa80`0bf5f101 fffff880`0155073a 00000000`00000100 : 0xfffffa80`0bffb008
FOLLOWUP_IP:
mv91xx+33f4d
fffff880`0154af4d cc int 3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: mv91xx+33f4d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: mv91xx
IMAGE_NAME: mv91xx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4be3b5a1
STACK_COMMAND: .cxr 0xfffff880035990e0 ; kb
FAILURE_BUCKET_ID: X64_0x3D_mv91xx+33f4d
BUCKET_ID: X64_0x3D_mv91xx+33f4d
Followup: MachineOwner
---------
7: kd> lmvm mv91xx
start end module name
fffff880`01517000 fffff880`015a5000 mv91xx T (no symbols)
Loaded symbol image file: mv91xx.sys
Image path: mv91xx.sys
Image name: mv91xx.sys
Timestamp: Fri May 07 12:09:29 2010 (4BE3B5A1)
CheckSum: 0005299E
ImageSize: 0008E000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
