Computer BSOD's When it Realizes It's Alone

Same BCC 3B.. You reinstalled windows recently right?

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, 1, fffff880094bcb80, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )

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: 0000000000000001, Address of the instruction which caused the bugcheck
Arg3: fffff880094bcb80, 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: 
+0
00000000`00000001 ??              ???

CONTEXT:  fffff880094bcb80 -- (.cxr 0xfffff880094bcb80)
rax=0000000000000000 rbx=fffff880094bdc90 rcx=0000000000100010
rdx=fffff880094bdd10 rsi=fffff880094bdd10 rdi=fffff80002ce18d3
rip=0000000000000001 rsp=fffff880094bd568 rbp=fffff880094bec20
 r8=fffff880094bde70  r9=fffff80002ee911c r10=fffff880094bec20
r11=fffff80002c62000 r12=0000000000000000 r13=fffff880094be600
r14=0000000000000000 r15=fffff880094bdc10
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
00000000`00000001 ??              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Skype.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000001

STACK_TEXT:  
fffff880`094bc2b8 fffff800`02ce1be9 : 00000000`0000003b 00000000`c0000005 00000000`00000001 fffff880`094bcb80 : nt!KeBugCheckEx
fffff880`094bc2c0 fffff800`02ce153c : fffff880`094bc500 fffff800`02cba301 fffff800`02e39ec8 fffff880`094be9e0 : nt!KiBugCheckDispatch+0x69
fffff880`094bc400 fffff800`02d0df6d : fffff800`02efd864 00000000`00000000 fffff800`02c62000 fffff880`094bd328 : nt!KiSystemServiceHandler+0x7c
fffff880`094bc440 fffff800`02d0cd45 : fffff800`02e29788 fffff880`094bc4b8 fffff880`094bd328 fffff800`02c62000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`094bc470 fffff800`02d1ddc1 : fffff880`094bd328 fffff880`094bcb80 fffff880`00000000 fffff800`02ce18d3 : nt!RtlDispatchException+0x415
fffff880`094bcb50 fffff800`02ce1cc2 : fffff880`094bd328 fffff880`094bdc90 fffff880`094bd3d0 fffff880`094bdd10 : nt!KiDispatchException+0x135
fffff880`094bd1f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceHandler+7c
fffff800`02ce153c b801000000      mov     eax,1

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceHandler+7c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c

BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c

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

waserza said:

i tested them both at the same time for 8 passes, got errors, took the ram out, put one stick in, tested for eight passes, all clear, then i took that one out, put another one in, and the PC wouldn't POST. I tried it in each slot, same thing each time

That would seem that piece of RAM is faulty then.