BSOD ram?

[ripp3r]

Hi guys,

Here's the hardware:

Asus P7P55D-E
Intel i7950
Corsair XMS3 (1600 mhz)
2 x 500GB WD SATA 3 (attached to SATA 2 for RAID 1 purpose)
Asus HD5670

I've installed Win7 Ultimate x64, after one day I started with BSOD "PAGE FAULT IN NONPAGED AREA".

I did some tests and now I'm running with just one module of ram (2GB) but still problems.

I've uninstalled the AV (nod32) and installed avast. Everytime the same problem.

Windows memory test and memtest > no errors.


Now I'm going to change the ram completely and reinstall the OS 'cause I think that due to many BSOD, windows has something corrupted.

As attachment you can find all of my DMP files. Is there anybody that could confirm it's a ram-related problem?

Thankyou!

EDIT: Not all the dumps are referred to PAGE FAULT, after 11.10.2010 there are MEMORY_MANAGEMENT, SYSTEM_SERVICE_EXCEPTION, BAD_POOL_HEADER,...

 

[wish]

Hi,
Most of your dumps have memory corruption issue, could be bad RAM or drivers fault.

BugCheck 3B, {c0000005, fffff80002de11a5, fffff88008b0f140, 0}
Probably caused by : memory_corruption ( nt!MiUnmapViewOfSection+185 )

Start troubleshooting with uninstall AVG and replace it with MSE.
http://www.microsoft.com/security_essentials/

Another dump point to ntfs.sys --> perform checkdisk
Open Elevated CMD -> chkdsk /r /f

These drivers need to do update:

Rt64win7.sys Thu Feb 26 01:04:13 2009 --> [URL="http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=7&PFid=10&Level=3&Conn=2"]realtek NIC[/URL]
iaStorV.sys  Wed Apr 08 09:57:17 2009 ---> [URL="http://downloadcenter.intel.com/Default.aspx"]Intel Matrix Storage Manager driver [/URL]

If the problem persist then test your memory with memtes86 for at least 7 passes
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Log

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002de11a5, fffff88008b0f140, 0}

Probably caused by : memory_corruption ( nt!MiUnmapViewOfSection+185 )

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: fffff80002de11a5, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88008b0f140, 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!MiUnmapViewOfSection+185
fffff800`02de11a5 48833800        cmp     qword ptr [rax],0

CONTEXT:  fffff88008b0f140 -- (.cxr 0xfffff88008b0f140)
rax=ffff7a8005105d40 rbx=fffffa80058cf250 rcx=0500000000000010
rdx=0000000000004580 rsi=fffffa80049f9060 rdi=fffffa8003e8e510
rip=fffff80002de11a5 rsp=fffff88008b0fb10 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000001 r10=fffff80002de157c
r11=000000000031827c r12=0000000000010000 r13=0000000000000000
r14=000000000458ffff r15=0000000004580000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!MiUnmapViewOfSection+0x185:
fffff800`02de11a5 48833800        cmp     qword ptr [rax],0 ds:002b:ffff7a80`05105d40=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  SearchIndexer.

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002de15db to fffff80002de11a5

STACK_TEXT:  
fffff880`08b0fb10 fffff800`02de15db : 00000000`00000000 00000000`04580000 fffffa80`00000001 00000000`00000001 : nt!MiUnmapViewOfSection+0x185
fffff880`08b0fbd0 fffff800`02ac7993 : fffffa80`03e8e510 00000000`ffffffff fffffa80`049f9060 fffffa80`01f58150 : nt!NtUnmapViewOfSection+0x5f
fffff880`08b0fc20 00000000`7729fffa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`05a48cd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7729fffa


FOLLOWUP_IP: 
nt!MiUnmapViewOfSection+185
fffff800`02de11a5 48833800        cmp     qword ptr [rax],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiUnmapViewOfSection+185

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff88008b0f140 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_nt!MiUnmapViewOfSection+185

BUCKET_ID:  X64_0x3B_nt!MiUnmapViewOfSection+185

Followup: MachineOwner

 

[ripp3r]

Ehi thanks for your reply.

Today I'm going to change the ram (replace with only one of 2 gb). Then I start testing.


Thanks again.

 

[zigzag3143]

Ehi thanks for your reply.

Today I'm going to change the ram (replace with only one of 2 gb). Then I start testing.


Thanks again.

Good idea dont forget to check the mobo slots with known good ram.


Ken

 

[ripp3r]

Just an update:

New RAM > MemTest 44 times > NO ERRORS

Now I'm using SiSoft Sandra in BURN-IN mode for 20 hours.

 

[zigzag3143]

Just an update:

New RAM > MemTest 44 times > NO ERRORS

Now I'm using SiSoft Sandra in BURN-IN mode for 20 hours.

If you ran memtest for 44 passes you are more patient than I am.

Let us know how things turn out.


Ken

 

[Jonathan_King]

Just an update:

New RAM > MemTest 44 times > NO ERRORS

Now I'm using SiSoft Sandra in BURN-IN mode for 20 hours.

Just to clarify, you are using Memtest86+, not the Windows Memory Diagnostic Tool, correct?

 

[ripp3r]

Yes MemTest86+

 

[ripp3r]

If you ran memtest for 44 passes you are more patient than I am.
Ken

Well... the pc isn't mine

eheheheheh

 

[reventon]

What brand/model PSU are you using?

Try running this test too - http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html (run the Blend test as well as the Small FFT test)