BSOD / Random Freezes

danhazelwood said:

Operating system: Win 7 Ultimate 64bit (Install is about 3 weeks old)
MoBo: ASUS M4A79XTD EVO AM3 AMD 790X ATX AMD
Ram: OCZ Reaper HPC 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)
Processor: AMD Phenom II X4 955 Black Edition Deneb 3.2GHz
Hard Drives: OCZ Vertex Turbo OCZSSD2-1VTXT30G 2.5" 30GB SATA II MLC Internal Solid State Drive (SSD) (2x in RAID 0)
CPU Fan: ARCTIC COOLING Freezer 7 Pro Rev.2 92mm Fluid Dynamic CPU Cooler
Power Supply: Thermaltake Toughpower 700W

Freezes are completely at random though they are becoming more frequent. I can however recreate the freezing by playing Starcraft 2. BSODs happen maybe once out of every 7 or 8 freezes.

I have flashed my bios to the most up to date version, as well as run Memtest86+ overnight with 0 errors. I know this doesn't completely rule out Ram issues however. I also reformatted.

1-ASACPI.SYS

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.SYS file is date stamped from 2009 or 2010 (NOT 2005).

I updated ASACPI.SYS however i still froze while in Starcraft 2 menu's and actually got another BSOD while typing this the first time. Below is my newest BSOD.

Some additional symptoms i've gotten is every so often after a crash my computer will boot to windows, but will not recognize any usb devices including my mouse and headset. When i mean not recognized its like they don't even exist. My solution that has worked to get them back is to shut down my computer, unplug the power, and hit the power button 5 times (hearing a pop from my speakers and my monitor on light button kind of flashes). From what I've gathered form google ntkrnlmp.exe errors usually mean my motherboard is going bad but i'm not sure.


*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002cbdb65, fffff8800a1e5e80, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002cbdb65, Address of the instruction which caused the bugcheck
Arg3: fffff8800a1e5e80, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02cbdb65 498b08 mov rcx,qword ptr [r8]

CONTEXT: fffff8800a1e5e80 -- (.cxr 0xfffff8800a1e5e80)
rax=000000008e2a0003 rbx=fffff8800a1e6a08 rcx=fffffa8005604c50
rdx=bffff900c3001cc1 rsi=0000000000000005 rdi=0000000000000238
rip=fffff80002cbdb65 rsp=fffff8800a1e6860 rbp=fffffa8005604c50
r8=bffff900c3001cc0 r9=000000007fffffff r10=fffffa8005604c50
r11=0000000000000008 r12=0000000000000000 r13=0000000000000001
r14=0000000000000006 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210286
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02cbdb65 498b08 mov rcx,qword ptr [r8] ds:002b:bffff900`c3001cc0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: chrome.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002cbdb65

STACK_TEXT:
fffff880`0a1e6860 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16


FOLLOWUP_IP:
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02cbdb65 498b08 mov rcx,qword ptr [r8]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExpInterlockedPopEntrySListFault16+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

STACK_COMMAND: .cxr 0xfffff8800a1e5e80 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0

BUCKET_ID: X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0

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

Quick update I'm currently running memtest86 again as I noticed my motherboard was severly underclocking my ram so I set it to ocz's recomendations which are DDR3 1600 7-7-7-24 and 1.7 volts. My first test and I got one error back.. guess now the question is if its my ram or my mobo.

Have you completely ruled out your raid 0 array of OCZ Vertex Turbo SSDs?

I've got simular issues as you, same ssds in hardware raid 0, however... my pc now doesn't even boot up anymore.. (1 SSD crashed) after working trouble free for a year.

also, if you want these SSD in raid 0 you should upgrade the firmware on the device to the latest version and make sure windows isn't defragmenting them in the background.