Random BSOD - Memory handling error?

[Niksia]

I can't remember the exact code of the error but I'm sure the message had to do with memory. I've included a zip with everything from SF diagnostic. The only recent cause I can think of might be from when I installed a new motherboard, cpu and RAM. Sorry I can't explain this better! I think this is about the third BSOD I've had so far.

 

[koolkat77]

Welcome

You have two dumps which point toward memory

Usual causes: Device driver, memory, kernel STOP 0x0000001A: MEMORY_MANAGEMENT BSOD Index

[FONT=Verdana][SIZE=2]*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.[/SIZE][/FONT][FONT=Verdana] [SIZE=2]
[COLOR=Blue]
BugCheck 1A[/COLOR], {41790, fffffa8002549820, ffff, 0}[/SIZE] [/FONT][FONT=Verdana]
[SIZE=2]
Probably caused by : [COLOR=Blue]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355e4 )[/COLOR][/SIZE][/FONT]  [FONT=Verdana] [SIZE=2]

Followup: MachineOwner[/SIZE] [SIZE=2]
---------[/SIZE][/FONT]

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA BSOD Index

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

[FONT=Verdana][SIZE=2]*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Blue]BugCheck 50[/COLOR], {fffffa8c051d4b78, 0, fffff80003099ccb, 5}


Could not read faulting driver name
Probably caused by :[COLOR=Blue] memory_corruption[/COLOR] ( nt!MiDeleteAddressesInWorkingSet+27f )

Followup: MachineOwner[/SIZE][/FONT]

Suggestions:

Run memtest86+ preferably overnight for 8 passes following this tutorial:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Post back results when you're done

 

[Niksia]

I finally got around to running all the Memtests.

Results after one full pass were:

Both sticks: 89 errors
Stick 1, slot 1: 10 errors
Stick 1, slot 2: 21 errors
Stick 2, slot 1: 0 errors
Stick 2, slot 2: 0 errors

So, just one bad stick of memory? Hopefully?

 

[koolkat77]

Yes! Hopefully
Thanks for posting back.

 

[koolkat77]

Hi,

Did changing your ram solve your blue screen problems?

 

[Niksia]

No more blue screen, which is good! But I now get random instances where the monitor blanks out and the light flashes as if it's on but the computer isn't, but the computer is still running. :/ All the sound and video shuts off and I have to force the whole thing off and on again. I assume it's just because I've left the bad memory stick out and I'm now running on half the RAM I was before.

 

[koolkat77]

Hmm
Is this a new computer?

 

[Niksia]

Only the motherboard, cpu and memory sticks are new. I bought them in June as a long overdue upgrade. Not working out as planned.

 

[koolkat77]

Are all the parts compatible with each other?