Memory strikes again or..?

doobu

Reputable
Jan 1, 2015
21
0
4,510
Hey everyone. Hope all is well. I recently RMA'ed my Corsair Vengeance (2x4GB).

Previously I was getting tons of BSODs (kernel, memory management, ati driver, kernel over and over). I put the GPU/CPU/Memory through stress tests and nothing failed originally.

So, I RMA'ed and purchased a new hard drive and memory. I installed the components and booted up to install Windows 7.

Boom. Memory Management BSOD while trying to install. So. I pulled out one stick and Windows 7 installed perfectly (this was after 4 attempts with both modules in the board). Put in the other one. Boom, back to the same BSODs as before.

So, another memtest and they failed instantly when paired. When ran by themselves in each slot and they pass after 6 iterations each.

I will randomly get:

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000E2CA565, 0xFFFFF8800789A810, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION

I'm not sure what's wrong. Is it my mother board flirting with death? I'm not in a place to purchase tons of hard ware at the moment. I did update my BIOS just in case there were instability problems. Seems to be a non-factor.

Can anyone share some insight on where to go next? The CPU seems fine as well (no failures on intel diagnostic scans).
 

doobu

Reputable
Jan 1, 2015
21
0
4,510


Asus P8Z68-V LX. i5-2500k. CX600 Power supply, Corsair Vengeance 1600, and AMD Sapphire 6800 HD.

Every Who Crashed report says software. The same thing before I did a fresh re-install on a new hard drive.

Had no issues up until this year (Machine was built in late 2012). All my graphics drivers are updated, BIOS updated, etc. Just had a real bad crash when I awoke this morning.


This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000E6B9319, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe

And also:

This was probably caused by the following module: cng.sys (cng!AppHashComputeFileAttributes+0xEC95)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000E6B9319, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
 

doobu

Reputable
Jan 1, 2015
21
0
4,510


I did. I ran memtest on all four slots with each module in each and they passed every time. When ran together they throw errors (when in both sets of slots).

They never seem to blue screen when running games (dyling light, wow, CS, etc.) but will throw the error when sitting idle, or browsing the web.

I've tested the RAM and update the BIOS to the newest versus from Asus' website, replaced my hard drive, and RMA'ed the RAM and re-tested it.

It was doing this before so I thought it was the RAM...perhaps the RAM was never bad..
 

doobu

Reputable
Jan 1, 2015
21
0
4,510
Sorry I was gone so long. I had a ton of work and thanks to my machine, I couldn't do a lot. Had to stay late many a days.

I bought a new mother board (AsRock z97), new processor (g3258 for OCing when I get to it), new GPU (GTX 750 ti SC).

I boot up into bios fine (thing is rather quick). I'm using my RAM and PSU from my old unit. The RAM passed memtest individually in each slot alone, but failed together. I assumed it was the mobo acting up.

So, I build everything last night. We're up and running in the bios fine and I boot to CD to install to the new HD. Boom. Memory Management. Then irql_not_less_or_equal.

I'm thinking my last machine was fine....and perhaps...PSU? The voltage wasn't fluctuating but I noticed one of the connectors from the PSU that connects to the hardrive had some residue on it. It looks almost like as if it overheated a bit, but I've seen no damage on the ole hard drive.

 

doobu

Reputable
Jan 1, 2015
21
0
4,510
I am about to try that. It's very weird. I assumed my old mother board did it. So, I went ahead and got a budget overclocker system (when I get some more time I will..for now I want it to be stable) and I can't even boot. Soon as I attempt to install windows, it sits for so long then dumps the Memory Management.

This RAM is technically brand new since I RMA'ed it already before. And yes they did come as a pair.
 

doobu

Reputable
Jan 1, 2015
21
0
4,510
A problem has been detected and windows has been shut down. 0x00000024.

Sigh. That is with voltage at 1.55. I'm about to buy a laptop and forget building rigs anymore. It made it to 45% on the install...so..yay? I get to wipe the drive and try again. I am literally about to throw this in the trash.
 

doobu

Reputable
Jan 1, 2015
21
0
4,510
Kept the voltage at 1.55 and pushed the 1333 to 1600 and Windows finally installed. Whether or not it is stable..I cannot tell yet since I am still installing all of the drivers.
 

Tradesman1

Legenda in Aeternum
With Win sometimes and I have no idea why, it won't want to install with more than a single stick, doesn't matter if 2, 4 or 8 GB sticks, but it will install on a single stick and then add the rest and no problems, think I've had 25 plus folks here on the forums try this and all is good, then they load the rest of the DRAM and are problem free. (and this happens with both AMD and Intel rigs)
 

doobu

Reputable
Jan 1, 2015
21
0
4,510
I installed on 2 sticks. I upped the voltage on the RAM and set it to 1600 instead of 1333. All drivers installed and no crashes yet...not sure exactly what the culprit was/is. PSU fading or RAM needing a kick in the ass.
 

Tradesman1

Legenda in Aeternum
On a Z678, good possible is the BIOS, this chipset never got alot of attention, it wasn't out that long before the Z77 came out and took the market over, the Z68 was overly embraced by users either, which contributed to it not getting a lot of attention. The extra voltage is perfectly safe so think you'll be fine ;)
 

doobu

Reputable
Jan 1, 2015
21
0
4,510
crash dump file: C:\Windows\Minidump\032615-16988-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002B2B28F, 0xFFFFF88006BEDC50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System

Back to this again...ugh. I think you're right about the RAM...I don't know what to think anymore. Same ole errors as before.