BSOD MSI 890FXA-GD70 w/ 2xIntel SSD 520 120GB SSD RAID 0

[chapmunger]

I am getting hard lockups and BSOD from the following
MB: MSI 890FXA-GD70
CPU: AMD Phenom II X6 1100T
HD: 2xIntel SSD 520 120GB SSD RAID 0
VID: ATI FirePro V4800

I have flashed BIOS on MB to the latest and I have rebuilt the machine a second time quite carefully. Loaded all the absolute latest drivers. I have run Memtest etc from the Ult Boot CD and no crashes.

It seems it is a driver issue of some kind.

Please see attached files. Thanks! I am pulling my hair out!

 

[chapmunger]

I should have added the RAM spec of course because this could be a RAM problem:
RAM is 8GB total or 4x2GB - two of the Newegg products were purchased below so all 4 slots are populated
G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9D-4GBRL

Also no overclocking! JUst trying to get things stable 1st!

 

[writhziden]

Antivirus Software:

smc.exe	c:\program files (x86)\symantec\symantec endpoint protection\12.1.671.4971.105\bin64\smc.exe	2328	8	1024	8192	3/11/2012 2:36 PM	12.1.671.4971	2.47 MB (2,591,232 bytes)	6/17/2011 5:32 PM
ccsvchst.exe	c:\program files (x86)\symantec\symantec endpoint protection\12.1.671.4971.105\bin\ccsvchst.exe	1656	8	1024	16384	3/11/2012 2:36 PM	10.1.2.14	134.01 KB (137,224 bytes)	6/17/2011 5:32 PM
ccsvchst.exe	c:\program files (x86)\symantec\symantec endpoint protection\12.1.671.4971.105\bin\ccsvchst.exe	1344	8	1024	3072	3/11/2012 2:38 PM	10.1.2.14	134.01 KB (137,224 bytes)	6/17/2011 5:32 PM

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\chapmunger\Windows_NT6_BSOD_jcgriff2\031112-15210-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5a000 PsLoadedModuleList = 0xfffff800`02e9f670
Debug session time: Sun Mar 11 00:13:13.124 2012 (UTC - 6:00)
System Uptime: 0 days 0:04:46.289
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff88001308c08, 2, 8, fffff88001308c08}

Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+2bf0 )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff88001308c08, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff88001308c08, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f09100
 fffff88001308c08 

CURRENT_IRQL:  2

FAULTING_IP: 
Ntfs! ?? ::NNGAKEGL::`string'+2bf0
fffff880`01308c08 55              push    rbp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  explorer.exe

TRAP_FRAME:  fffff8800a580fb0 -- (.trap 0xfffff8800a580fb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88001308c08 rbx=0000000000000000 rcx=fffff8800a581180
rdx=fffff8800a582770 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001308c08 rsp=fffff8800a581148 rbp=fffff8800a581280
 r8=fffff8800a581900  r9=fffff8800a581280 r10=fffff8800a582970
r11=fffff8800a5811b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
Ntfs! ?? ::NNGAKEGL::`string'+0x2bf0:
fffff880`01308c08 55              push    rbp
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd61e9 to fffff80002cd6c40

FAILED_INSTRUCTION_ADDRESS: 
Ntfs! ?? ::NNGAKEGL::`string'+2bf0
fffff880`01308c08 55              push    rbp

STACK_TEXT:  
fffff880`0a580e68 fffff800`02cd61e9 : 00000000`0000000a fffff880`01308c08 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0a580e70 fffff800`02cd4e60 : 00000000`000000e9 00000000`00000000 fffff800`02ce1845 fffff880`01269840 : nt!KiBugCheckDispatch+0x69
fffff880`0a580fb0 fffff880`01308c08 : fffff800`02d02a7c 00000000`00000001 fffffa80`09667000 fffffa80`08c92d01 : nt!KiPageFault+0x260
fffff880`0a581148 fffff800`02d02a7c : 00000000`00000001 fffffa80`09667000 fffffa80`08c92d01 fffffa80`08d1aea0 : Ntfs! ?? ::NNGAKEGL::`string'+0x2bf0
fffff880`0a581150 fffff800`02d024fd : fffff880`01269834 fffff880`0a582770 00000000`00000000 fffff880`01219000 : nt!_C_specific_handler+0x8c
fffff880`0a5811c0 fffff800`02d012d5 : fffff880`01269834 fffff880`0a581238 fffff880`0a5820a8 fffff880`01219000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0a5811f0 fffff800`02d12361 : fffff880`0a5820a8 fffff880`0a581900 fffff880`00000000 ffff5fff`ffffffff : nt!RtlDispatchException+0x415
fffff880`0a5818d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x135


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs! ?? ::NNGAKEGL::`string'+2bf0
fffff880`01308c08 55              push    rbp

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  Ntfs! ?? ::NNGAKEGL::`string'+2bf0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_Ntfs!_??_::NNGAKEGL::_string_+2bf0

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_Ntfs!_??_::NNGAKEGL::_string_+2bf0

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\chapmunger\Windows_NT6_BSOD_jcgriff2\031012-22963-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`0285a000 PsLoadedModuleList = 0xfffff800`02a97e70
Debug session time: Sat Mar 10 22:15:14.047 2012 (UTC - 6:00)
System Uptime: 0 days 0:02:55.014
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8009348b30, fffffa8009348e10, fffff80002bd2300}

Probably caused by : hardware_disk

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8009348b30, Terminating object
Arg3: fffffa8009348e10, Process image file name
Arg4: fffff80002bd2300, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa8009348b30

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_RECORD:  fffff88001ed8b78 -- (.exr 0xfffff88001ed8b78)
ExceptionAddress: 0000000077514e8f
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 000007fefd47d8a8
   Parameter[2]: 00000000c000000e
Inpage operation failed at 000007fefd47d8a8, due to I/O error 00000000c000000e

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000007fefd47d8a8

EXCEPTION_PARAMETER3:  00000000c000000e

IO_ERROR: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

EXCEPTION_STR:  0xc0000006_c000000e

FAULTING_IP: 
+23a
00000000`77514e8f ??              ???

BUGCHECK_STR:  0xF4_IOERR_C000000E

FOLLOWUP_IP: 
+23a
000007fe`fd47d8a8 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk

BUCKET_ID:  X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk

Followup: MachineOwner
---------


[/list]

These are pointing to your hard disks. Is your SSD firmware and are your SSD controllers all up to date for both drives?

 

[chapmunger]

Thanks writhziden! Since I am running RAID 0 w/ 2 Intel SSD and the file listed in event viewer is ntfs.sys I thought that there was a good chance that it was either an SSD firmware issue or a RAID controller driver.

But these are the 'super tested' Intel 520 series with Sandforce controller w/ one whole extra year of testing!

The MB BIOS is the latest and I loaded default settings. RAID 0 setup in controller was vanilla with no tweaking so I am inclined to agree with you, especially because I can not read the dumps like you.

I also experience a fair amount of hard freezes or lockups - more than BSOD's for sure.

I am off to Intel's website to check out firmware and flashing these drives - but sheeesh! I though that by buying Intel SSD I would not have to go through this!

I don't like risking making a brick if the flash fails!

Thanks again! I'll let you know what happens.

 

[chapmunger]

Update: I mistyped. The Intel drives are in fact 120GB 510 series NOT 520. Oops...sorry about that. Firmware is PPG4 which per Intel website is the latest firmware for these drives. Therefore I am not going to flash firmware. Also I should have said that OS is Win7x64. What I have done is register and post for support at Intel SSD support forum. Hopefully someone at Intel may be interested. I am going to go to the MSI forums as well.

 

[writhziden]

When you set up the drives, did you run Diskpart's clean command on them (not clean all, just clean)? We have some useful tutorials for SSDs on here depending on what you are trying to do to set yours up.

http://www.sevenforums.com/tutorials/113967-ssd-alignment.html
http://www.sevenforums.com/tutorials/149969-ssd-install-transfer-operating-system.html
http://www.sevenforums.com/tutorials/91339-ssd-hdd-optimize-windows-reinstallation.html
http://www.sevenforums.com/tutorials/70822-ssd-tweaks-optimizations-windows-7-a.html
​

 

[chapmunger]

writhziden, thanks again for weighing in I appreciate your help. I did not use Diskpart clean but the disks were brand new and had never been used. I guess that could be it - but I am not sure why Intel would send out disks that were so thoroughly tested that required this step right out of the box. I am familiar with this step from when I have had to reassign SSD's out of a RAID array to singles I've used diskpart clean to wipe the MBR. Alignment is not needed for Win7x64 - I think Win7 handles that natively. I will look at the other links and let you know what happens. I have posted this identical problem in BOTH Intel and MSI forums as well. IF you are curious you can take a look.

2x510 120GB RAID 0 on MSI 890FXA-GD70 w/ AMD SB850 Lockups and BSOD

MSI 890FXA-GD70 w/ 2xIntel 510 120GB in RAID 0 on Locks up and BSOD

 

[writhziden]

I also question whether your current power supply is enough to handle your configuration: MSI 890FXA-GD70 w/ 2xIntel 510 120GB in RAID 0 on Locks up and BSOD

May be something to consider...

 

[chapmunger]

Here are the specs

Antec
EA-380D Green
Series
EarthWatts Green
Spec
Type
ATX12V v2.3 / EPS12V
Maximum Power
380W Continuous power
Fans
80mm low noise cooling fan
PFC
Active
Main Connector
20+4Pin
+12V Rails
2
PCI-Express Connector
1 x 6-Pin
SATA Power Connector
5
SLI
No
CrossFire
No
Energy-Efficient
80 PLUS BRONZE Certified
Over Voltage Protection
Yes
Input Voltage
100 - 240 V
Input Frequency Range
47 - 63 Hz
Output
+3.3V@20A, +5V@20A, +12V1@17A, +12V2@15A, [email protected], [email protected]
Approvals
UL, CUL, FCC, TUV, CE, CB, C-tick, CCC, BSMI
Dimensions
3.4" x 5.9" x 5.5"
Weight
3.6 lbs.
Features
Connectors
1 x Main connector (20+4Pin)
1 x 4+4 Pin ATX/EPS 12V
4 x Peripheral
5 x SATA
1 x Floppy
1 x PCI-E

 

[writhziden]

Based on what you have in the system, I calculated a need of 410 W. I estimated some hardware since I was not sure. You are welcome to see what you obtain: eXtreme Outer Vision - eXtreme tools for computer enthusiasts

Your motherboard is considered high end, by the way.