New build BSOD

#1
Hey everyone,

Just finished my 2 builds and mine runs great, my girlfriends is having some issues though, For some reason when i run prime95 the system will reboot itself or go to a bluescreen with something about drivers, or memory.. The system specs are

AMD Phenom II X4 955 Black Edition Deneb 3.2GHz
ASUS M5A87
G.SKILL Ripjaws X Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666)
Nvidia GTX 260
corsair 600w psu

Ive tried updating the drivers i could figure out and updating the bios. Any suggestions on how to troubleshoot this or ideas on the issue would be awesome, Has also crashed with memtest.

Here are a few minidump files View attachment 070311-20576-01.zip

Thanks
James
 


Captain Jack

Extraordinary Member
#2
Hello there,

Seems like it might be some Hardware. So I would recommend to run MemTest86+ single stick on different DIMM slot. Your BIOS is up to date (03/14/2011) so don't worry about it. Check the Motherboard manual and RAM manual and see if the voltages and timing are set correctly in BIOS. Here is a guide for Hardware Diagnostic Hardware Diagnostic | Captain Debugger

Code:
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002aba639, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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!KiUnlockKobjectArray+9
fffff800`02aba639 f0452108        lock and dword ptr [r8],r9d

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d16100
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  services.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002b325d8 to fffff80002ae6d00

STACK_TEXT:  
fffff880`02e87c38 fffff800`02b325d8 : 00000000`0000001e ffffffff`c0000005 fffff800`02aba639 00000000`00000000 : nt!KeBugCheckEx
fffff880`02e87c40 fffff800`02ae6382 : fffff880`02e88418 fffffa80`068b9550 fffff880`02e884c0 fffffa80`068b9610 : nt! ?? ::FNODOBFM::`string'+0x4987d
fffff880`02e882e0 fffff800`02ae4c8a : fffff880`02e88550 fffff800`02ada627 fffffa80`068b9550 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02e884c0 fffff800`02aba639 : fffff800`02b4c535 fffffa80`068b9550 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`02e88658 fffff800`02b4c535 : fffffa80`068b9550 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiUnlockKobjectArray+0x9
fffff880`02e88660 fffffa80`075ad7c0 : fffffa80`075b0ce0 fffffa80`075e8b90 fffffa80`0762c1e0 fffffa80`0762c620 : nt! ?? ::FNODOBFM::`string'+0x25bd0
fffff880`02e88920 fffffa80`075b0ce0 : fffffa80`075e8b90 fffffa80`0762c1e0 fffffa80`0762c620 fffffa80`07638680 : 0xfffffa80`075ad7c0
fffff880`02e88928 fffffa80`075e8b90 : fffffa80`0762c1e0 fffffa80`0762c620 fffffa80`07638680 fffffa80`07638e90 : 0xfffffa80`075b0ce0
fffff880`02e88930 fffffa80`0762c1e0 : fffffa80`0762c620 fffffa80`07638680 fffffa80`07638e90 fffffa80`0763ebe0 : 0xfffffa80`075e8b90
fffff880`02e88938 fffffa80`0762c620 : fffffa80`07638680 fffffa80`07638e90 fffffa80`0763ebe0 fffffa80`0764abe0 : 0xfffffa80`0762c1e0
fffff880`02e88940 fffffa80`07638680 : fffffa80`07638e90 fffffa80`0763ebe0 fffffa80`0764abe0 00000000`00001000 : 0xfffffa80`0762c620
fffff880`02e88948 fffffa80`07638e90 : fffffa80`0763ebe0 fffffa80`0764abe0 00000000`00001000 00000000`0000027c : 0xfffffa80`07638680
fffff880`02e88950 fffffa80`0763ebe0 : fffffa80`0764abe0 00000000`00001000 00000000`0000027c 00000000`00000080 : 0xfffffa80`07638e90
fffff880`02e88958 fffffa80`0764abe0 : 00000000`00001000 00000000`0000027c 00000000`00000080 00000000`00000000 : 0xfffffa80`0763ebe0
fffff880`02e88960 00000000`00001000 : 00000000`0000027c 00000000`00000080 00000000`00000000 00000000`00000000 : 0xfffffa80`0764abe0
fffff880`02e88968 00000000`0000027c : 00000000`00000080 00000000`00000000 00000000`00000000 fffffa80`06811000 : 0x1000
fffff880`02e88970 00000000`00000080 : 00000000`00000000 00000000`00000000 fffffa80`06811000 fffff8a0`0261d000 : 0x27c
fffff880`02e88978 00000000`00000000 : 00000000`00000000 fffffa80`06811000 fffff8a0`0261d000 00000000`00000080 : 0x80


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiUnlockKobjectArray+9
fffff800`02aba639 f0452108        lock and dword ptr [r8],r9d

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KiUnlockKobjectArray+9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiUnlockKobjectArray+9

BUCKET_ID:  X64_0x1E_nt!KiUnlockKobjectArray+9

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


#3
Thanks the problem is i dont have a usb drive to run memtest86 any other suggestions. its a new rig so i can rma the hardware if thats the cause.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.