Solved Random BSOD: Faulty RAM, or just borked windows?

[Spike]

Hi.

I have a computer that randomly crashes during the day.
Minidumps refer to ntoskrnl.exe.
I've read a few of the threads here related to ntoskrnl, but I'm not getting any wiser.

Tried a full reinstall of Windows 7 Pro 64-bit, but that didn't seem to help either

I recently changed the RAM from one single 2GB-chip to Two 2GB-chips. Could it be the chips?

Spike

View attachment 287342

 

[Golden]

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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[YoYo155]

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;

lmvm [COLOR=Blue][U][B]Rt64win7[/B][/U][/COLOR]
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:        [COLOR=Red][U][B]Mon May 16 17:53:31 2011[/B][/U][/COLOR]

• Driver Reference Table - Rt64win7.sys

Description: Win7 and WinServer 2008 R2 Auto Installation Program
Version: 7.075
Update Time: 2013/9/24
File Size: 5962k

Download




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

!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>
    [COLOR=Blue][B]Image: SavService.exe[/B][/COLOR]
    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!

 

[Spike]

Thanks for the feedback guys..
I'll try out these steps..

Regarding Sophos.. this is something i cannot remove due to some silly corporate policy..
I cannot begin to understand why the company have launched Sophos to all users.. Huge piece of crap IMO..

Spike

 

[Spike]

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

Attached new MSINFO32.nfo
View attachment 287471

Edit: Found the "unsolved" button.. lol

 

[YoYo155]

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.

 

[Spike]

I'll try again..
New MSINFo attached
View attachment 287583

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..
see attached screenshot:

View attachment 287584

 

[Golden]

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

 

[Spike]

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

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

 

[YoYo155]

A few things come to mind.

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?
View attachment 287604

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?

View attachment 287605

 

[Spike]

I Ran at least 8 or more tests on every test i ran..
They are now located in slot XMM1 and XMM3, wich I have understood it to be the two paired slotes i have to use..

Yes. I'm no longer using the original Ram chip (damn you HP).
The ram installed now is :
502745 Corsair Value S. DDR3 1333MHz 4GB CL9
Kit w/2x 2GB, Unbuffered, CL9-9-9-24, 240pin, 1.5V, for Intel and AMD
DDR3

(2 chips of 2GB each)

Spike

 

[YoYo155]

Thanks for the update .
You're using a compatible RAM specification-wise (at least on paper).
Now that the modules are operating in the same channel are you still getting errors?

 

[Spike]

Thanks for the update .
You're using a compatible RAM specification-wise (at least on paper).
Now that the modules are operating in the same channel are you still getting errors?

Yes... the memtest screenshot i posted is from running both chips in same channel..

Good to know that I actually didn't F up by ordering wrong chips.. hehe..

I've built many computers over the years.. but I've not rebuilt OEM pc's before.. so that being a potential problem never crossed my mind..

This just makes me hate HP even more.. LOL

Spike

 

[Spike]

I've kinda given up..
I've now reinstalled the original chip, and will run a mem test over night..
If that passes, I'm sending the new chips back to the vendor...
There's only so much time i want to spend on this machine..

Spike

 

[YoYo155]

It's your decision , just make sure to update which ever way things turns-out .

 

[Spike]

It's your decision , just make sure to update which ever way things turns-out .

Luckily for me, I'm not the one paying for a new computer if i decide to pull the plug, hehe..
Going to be interesting to see what the memtest says in the morning..

And what the vendor says if i decide to return the chips.

Thanks for all your help so far, anyways. Much appreciated!

Spike

 

[YoYo155]

Hi .
Yes it will be interesting what both the vendor and the current (ongoing?) memtest86+ run will
have in store for us.
I'm happy I could help, keep updating for future reference .

 

[Spike]

The latest test with the original chip passed AOK..
Doing one more shot with the new chips in a different machine..
Suddenly found out that the neighbouring office had a compatible mobo, LOL.

 

[Spike]

The latest test with the original chip passed AOK..
Doing one more shot with the new chips in a different machine..
Suddenly found out that the neighbouring office had a compatible mobo, LOL.

Chips shipped to vendor..

The tests during the night on the other machine went balistic..
25 passes and 8-9 error messages..

 

[YoYo155]

I'm not sure what you meant by balistic, whether it being good or bad .
Now with the original modules, how are things going?