After doing some MORE searching, ASUS only has the 1.0.0.1045 driver (29 Dec 2010 updated) for Marvell on their site for my motherboard, yet on Stations-Drivers site, they 1.2.0.1019 (06 Mar 2012 update), but it is in French. I have no clue what is the latest driver at this point and what is safe to use.
If you start a thread in Drivers - Windows 7 Forums, the experts there will probably be able to advise you on where to find up to date drivers for the Marvell 91xx series.
Two more BSODs in the last 2 days
Both the same, both pointing to a hardware problem... I would recommend installing Windows to a hard disk drive instead of solid state drive and see if your system is more stable. This will determine if the SSD is compatible with your system or if there is an underlying problem that is being masked by the SSD being in the system.Code:Loading Dump File [D:\Kingston\BSODDmpFiles\wbsimpson11\Windows_NT6_BSOD_jcgriff2\032812-8860-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0360c000 PsLoadedModuleList = 0xfffff800`03851670 Debug session time: Wed Mar 28 19:51:16.638 2012 (UTC - 6:00) System Uptime: 0 days 2:00:21.402 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff8a001bbde48, 2, 0, fffff8000367df4b} Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+a0 ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffff8a001bbde48, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8000367df4b, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038bb100 fffff8a001bbde48 CURRENT_IRQL: 2 FAULTING_IP: nt!ExpScanGeneralLookasideList+a0 fffff800`0367df4b 418b40d8 mov eax,dword ptr [r8-28h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880039e7870 -- (.trap 0xfffff880039e7870) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000367df4b rsp=fffff880039e7a00 rbp=0000000000000001 r8=fffff8a001bbde70 r9=0000000000000004 r10=0000000000000000 r11=0000000000000100 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!ExpScanGeneralLookasideList+0xa0: fffff800`0367df4b 418b40d8 mov eax,dword ptr [r8-28h] ds:7a60:fffff8a0`01bbde48=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036881e9 to fffff80003688c40 STACK_TEXT: fffff880`039e7728 fffff800`036881e9 : 00000000`0000000a fffff8a0`01bbde48 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`039e7730 fffff800`03686e60 : 00000000`00000021 00000000`00000001 fffff6fb`80008438 fffff800`03829400 : nt!KiBugCheckDispatch+0x69 fffff880`039e7870 fffff800`0367df4b : 00000000`00000000 fffff800`038bbc40 00000000`00000000 00000000`00000006 : nt!KiPageFault+0x260 fffff880`039e7a00 fffff800`03673780 : 00000000`00000001 00000000`00000008 00000000`00000001 fffff800`038bbc40 : nt!ExpScanGeneralLookasideList+0xa0 fffff880`039e7a60 fffff800`03673cce : 00000000`00000008 fffff880`039e7ad0 00000000`00000001 fffffa80`00000000 : nt!ExAdjustLookasideDepth+0x40 fffff880`039e7a90 fffff800`03923fee : fffffa80`0ca76b60 00000000`00000080 fffffa80`0c9ee9e0 00000000`00000001 : nt!KeBalanceSetManager+0x1be fffff880`039e7c00 fffff800`0367a5e6 : fffff880`009b3180 fffffa80`0ca76b60 fffff880`009be0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`039e7c40 00000000`00000000 : fffff880`039e8000 fffff880`039e2000 fffff880`039e75c0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!ExpScanGeneralLookasideList+a0 fffff800`0367df4b 418b40d8 mov eax,dword ptr [r8-28h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!ExpScanGeneralLookasideList+a0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0xA_nt!ExpScanGeneralLookasideList+a0 BUCKET_ID: X64_0xA_nt!ExpScanGeneralLookasideList+a0 Followup: MachineOwner ---------
Also, what did you mean when you said you ran Memtest? Did you run Memtest, Memtest86+, or the Windows Memory Diagnostic tool?
Memtest86+ for several hours and everything came out fine
How many passes did Memtest86+ run?
I am not 100% sure on that. It ran for 5-6 hours throughout the day
It needs to run for at least 7+ passes. Do that, then consider replacing the SSD with an HDD to test whether it is an SSD incompatibility or faulty drive.
Ok, will do. Really hate having to reinstall everything again
Believe me, I feel your pain. I had to do a clean install of my system twice in the last three days. I am still getting my programs back on the system a second time right now.
Let us know when you've had a chance to swap the SSD for an HDD and test.
Quote