Random BSOD: Faulty RAM, or just borked windows?

Code:

On Wed 25/09/2013 11:39:22 AM GMT your computer crashed
crash dump file: E:\BSOD\092513-34101-01.dmp
uptime: 22:30:29
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0xA (0xFFFFFB8007871E08, 0x2, 0x1, 0xFFFFF80002ADF971)
Error: IRQL_NOT_LESS_OR_EQUAL

Please use MemTest86+ to check for memory errors. Run a minimum of 8 passes or until you receive an error.

RAM - Test with Memtest86+

Please upload a new instance of the MSINFO32 file.

Start> RUN> "MSINFO32" without the quotes then hit [Enter].
In "MSINFO32" go to, File> Save> name it your user-name and upload.

Please update your network driver;

Code:

lmvm Rt64win7
start             end                 module name
fffff880`050d2000 fffff880`05156000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Mon May 16 17:53:31 2011

• Driver Reference Table - Rt64win7.sys

No code has to be inserted here.
Download




Use RevoUninstaller to completely remove Sophos Anti-Virus, use Microsoft Security Essentials
as a reliable alternative.

Code:

!process
GetPointerFromAddress: unable to read from fffff80002d03000
PROCESS fffffa8008c604e0
    SessionId: none  Cid: 0524    Peb: 7efdf000  ParentCid: 022c
    DirBase: 69537000  ObjectTable: fffff8a002904c00  HandleCount: <Data Not Accessible>
    Image: SavService.exe
    VadRoot fffffa8007711a80 Vads 491 Clone 0 Private 40638. Modified 280663. Locked 0.
    DeviceMap fffff8a0027dcc60
    Token                             fffff8a00b846060
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
    ElapsedTime                       00:00:00.000
    UserTime                          00:00:00.000
    KernelTime                        00:00:00.000
    QuotaPoolUsage[PagedPool]         168096
    QuotaPoolUsage[NonPagedPool]      79352
    Working Set Sizes (now,min,max)  (36709, 50, 345) (146836KB, 200KB, 1380KB)
    PeakWorkingSetSize                62721
    VirtualSize                       367 Mb
    PeakVirtualSize                   441 Mb
    PageFaultCount                    2156383
    MemoryPriority                    BACKGROUND
    BasePriority                      8
    CommitCharge                      42873

        *** Error in reading nt!_ETHREAD @ fffffa80088a57e0

Post back with the results!

Bah..
I mistakenly marked this as solved.. is there an undo button?

Attached new MSINFO32.nfo
Attachment 287471

Edit: Found the "unsolved" button.. lol

Hi thanks for the update :) .
A question though, did you create the MSINFO32 file before updating the network driver?
Because it wasn't updated at the time of creation.

Are the two RAM chips the same make/model/specifications?

A few things come to mind.

Spike said:

I've run the Memtest several times now..

Running either of the two chips alone in any slot works fine.. no errors..

As soon as I insert BOTH chips, I get an error.. even if those slots have passed earlier tests..

How many passes are you letting each module run for?
You need at least 7 if no errors are found prior to that.

What channels are you running the two modules in?
Attachment 287604

Spike said:

Yes.. Taken straigth out of the same package from the shop

Meaning you're no longer using the OEM RAM that came with your OEM PC, what are the timings and latency of the new RAM you're using now?

Attachment 287605