Adding new Ram

https://www.sevenforums.com/crashes-d...tructions.html

Dump file is indicating a core OS file as the cause, this may be caused by another driver. For that purpose you should enable driver verifier to determine that driver
Driver Verifier - Enable and Disable
Then upload the dump files which are created :)

Test the RAM
RAM - Test with Memtest86+

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff800031c4dd3, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800830dbf0, 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!ExFreePoolWithTag+43
fffff800`031c4dd3 418b45f0        mov     eax,dword ptr [r13-10h]

CONTEXT:  fffff8800830dbf0 -- (.cxr 0xfffff8800830dbf0)
rax=0000000000000000 rbx=fffffa800ffaa0a0 rcx=ff6bfa800ba79850
rdx=00000000484c764e rsi=fffffa8010efd010 rdi=fffffa800ffaa0a0
rip=fffff800031c4dd3 rsp=fffff8800830e5d0 rbp=fffffa801032d4f0
 r8=0000000000000000  r9=0000000000000000 r10=0000000000800001
r11=0000000000000004 r12=fffffa800a8a1000 r13=ff6bfa800ba79850
r14=fffff8a00b23d4e0 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExFreePoolWithTag+0x43:
fffff800`031c4dd3 418b45f0        mov     eax,dword ptr [r13-10h] ds:002b:ff6bfa80`0ba79840=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800031c4dd3

STACK_TEXT:  
fffff880`0830e5d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExFreePoolWithTag+0x43


FOLLOWUP_IP: 
nt!ExFreePoolWithTag+43
fffff800`031c4dd3 418b45f0        mov     eax,dword ptr [r13-10h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExFreePoolWithTag+43

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7951a

STACK_COMMAND:  .cxr 0xfffff8800830dbf0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ExFreePoolWithTag+43

BUCKET_ID:  X64_0x3B_nt!ExFreePoolWithTag+43

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

Hey Yowanvista, Thanks alot, how do I go about doing this?

the514 said:

Hey Yowanvista, Thanks alot, how do I go about doing this?

Instructions are in the first link

When I restart the system I go back into verifier correct? Then display verified drivers? and then what?

the514 said:

When I restart the system I go back into verifier correct? Then display verified drivers? and then what?

When you will enable driver verifier that will cause the system to BSOD when faulting driver(s) are detected. The minidumps created will help us to determine the driver and isolate the cause

Just enable it, use the PC normally until it crashes then boot into safe mode with networking. Then upload the most recent dump files which are located in C:\Windows\Minidump

Then you can safely disable Driver verifier :)

I will get back when my computer crashes, thannk you very much.

My computer froze with no BSOD, is it possible to get the dump files or do I need the BSOD?