Frequent Memory Related BSODs, but Memcheck claims my RAM is fine

[Shaikoten]

Having left my computer on over my Christmas vacation, I came back to realize random browser plugins had begun crashing. No matter, I thought, these things happen. And then as I started using it, the BSODs started happening, something my previously healthy, well maintained PC hadn't had much of. I'm mostly getting MEMORY_MANAGEMENT, PAGED FILE IN NON PAGED AREA, win32ksys, and other seemingly memory related posts.

So I did the logical thing and checked my memory for problems. None detected by memcheck. I checked my hard drives for problems too, just in case. No worries there either. So I began reinstalling drivers. I did GPU drivers and chipset, to no avail. Disabled everything overclocked, but crashes still persisted. Checked heat, nothing out of the ordinary, and crashes didn't even happen while under load, or even while the computer was in active use.

Finally, after another random crash, my windows install refused to boot, so I tried methods to repair it: system restore, system repair, nothing seemed to help. So, having all my things backed up onto other drives already, I reinstalled windows. It BSOD'd during the WINDOWS INSTALL. And now, the next day after a fresh install, it's still BSODing.

I've tried the RAM in different configurations too. Using individual sticks, in different slots, but none of it seems to be improving stability. Annoyingly I can't find one thing that induces this crash to recreate it, so I'm at the mercy of whether it crashes or not to tell if it's fixed every time I try something. The last thing I have yet to try is changing voltages for CPU or RAM, as I have heard this could fix it.

My Specs:
Windows 7 Pro
i5 3570k
Biostar TZ77XE3
Geil Evo Veloce 2x8GB DDR3 14900
XFX HD6950 2GB (Using triple monitors... maybe an issue?)
USB Devices: Logitech MX518, Filco Majestouch 2, Topping TP30 Sound Card/Amplifier

Hopefully we can solve things together! I can PM my most recent minidump if someone wants to take a gander.

 

[johnbl]

your copy of the nt kernal and the windows win32k.sys in memory are corrupted
your bugcheck was in a win32k.sys but the image was corrupted so the cause of the corruption is the problem not the win32k.sys file.

note:
debugger reports 12 errors in your nt kernel and 37 errors in your win32k.sys file in memory before it gave up at 86% checking.
also you have a old windows build
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

eliminate windows from the problem by booting memtest86 on a CD and confirm that the test does not detect any memory errors.

if memtest86 works as expected, then you need to find out why the nt kernel and win32k.sys image was corrupted in memory. First thing to look for is to verify that the copies on the hard drive are not corrupted.
Use
cmd.exe as a admin
do a chkdsk / f /r on your hard drive to confirm the filesystem is ok
do sfc.exe /scannow to confirm your core OS files are ok.

if both pass, scan for malware using malwarebytes.

if you don't find any errors then, you will want to start updating drivers or remove all 3rd party drivers to find the cause of the corruption.

Sorry, its not much help. my guess is a BIOS update is needed or you got malware.

 

[Shaikoten]

Well I removed one of my RAM dimms in particular and it appears the problem has gone away. Yet since memtest was coming up clean, I wonder if it was a motherboard issue rather than a DIMM related issue. There's no emergency anymore, by any stretch, but I'm sort of curious if it's my motherboard or RAM. I'm thinking I may RMA the RAM since it's been a bit less than a year since I bought it.

 

[johnbl]

although it can be RAM, normally RAM would not selectively corrupt win32k.sys file and leave the others alone.
(each boot of the OS will load the file in a different place in memory)
I would confirm that the files are not corrupted on disk using the system file checker
sfc.exe /scannow

if the sfc.exe passes without errors, I would run a malware scan looking for malware/rootkits

if you have other memory dumps I will take a quick look and see if your wind32k.sys file is corrupted again.
if you do have the problem isolated to ram, check the timings for that stick. If they are correct then replace.

Well I removed one of my RAM dimms in particular and it appears the problem has gone away. Yet since memtest was coming up clean, I wonder if it was a motherboard issue rather than a DIMM related issue. There's no emergency anymore, by any stretch, but I'm sort of curious if it's my motherboard or RAM. I'm thinking I may RMA the RAM since it's been a bit less than a year since I bought it.