Is my new 64GB's of DDR4 RAM bad after 2 days?

SaVeLeViAtHaN2017

Commendable
Feb 6, 2017
5
0
1,510
Thank you for checking my post. Sorry for length.
I'm trying to avoid verbose descriptions that waste your time, without being too concise, though.

At the time of writing this post, I can pass POST can I cannot boot. Nor can I get past any sort of Windows Startup Repair or even access a Windows boot disc without a BSOD or unresponsive lock-up.
I recently replaced all major hardware.



Context:
Two weeks ago, my computer started sporadically restarting all by itself with no warning.
After one day of trying different things to find a solution I could no longer even successfully boot to Windows.
During that day of testing, when MemTest could actually complete its tests (in between the random restarting) it reported no errors. RAM not the cause, apparently.
But strange issues stacked up and my computer became simply inoperable so I decided to abandon ship - I bought a new up-to-date motherboard which was incompatible with my CPU and RAM, so I bought a new CPU and RAM, too.


Surely $1K worth of new parts would solve ALL my problems, right? Wrong.

________________________


Here's what I bought:

Motherboard
ASUS ROG MAXIMUS IX HERO

CPU
Intel Core™ i7-7700K Processor (8M Cache, up to 4.50 GHz)

RAM
64GB (4 sticks) of Corsair Dominator Platinum Series DDR4 DRAM 3000MHz

Cooling
I swapped out my computer case's two top 120mm fans for a Corsair H100i liquid CPU cooler.
It's doing great - CPU temp staying under 40°C.

Hard Drives
I did not replace any hard drives. They were, and are, all performing well still, to my knowledge.
I run two RAID arrays. Each array consists of two identical mechanical drives - 4 physical drives total.

PSU
EVGA 850watt GQ Power Supply (fully modular)


Anyway, so all the new parts came in, I installed them, got a successful POST pretty much instantly.
Left BIOS settings as very modest; didn't do any performance boosting/overclocking.
Needed Windows boot disc to go further.
I guess since I wasn't reinstalling my Windows 7 Ultimate, Windows threw a fit when it detected all the new hardware and it had to run startup repairs using the boot disc.
Finally got logged back into Windows for the first time after new motherboard etc and performance was HORRIBLE. After hours of installing new chipset drivers etc from the ASUS disc that came with the motherboard, everything appeared to be fine.

At this time, I did bump up the clocking a little bit in BIOS. Still no POST issues and got back into Windows just fine.
So . . . everything ran fine for 2 days, during which I used Photoshop, played Overwatch and League of Legends - no bad signs.

And then . . .
Woke up yesterday, checked computer - found only a black screen with a Windows cursor I could move around the screen. No start bar, task manager, etc. Nothing I did caused any response.
Pressed reset button. Booted back up (I forget if I then booted into Safe Mode at this time). The instant I typed my Windows login password and pressed ENTER, it blue screened.

That was the last time I saw Windows.
Still POSTs just fine, but all Windows Startup Repair attempts, or attempts to load a Windows boot disc result in either a BSOD or a complete lock-up and force me to power down or restart.

I snapped photos of all unique blue screens that happened yesterday
Combined into one long image, sorted chronologically, top is first, bottom is latest:
-http://i.imgur.com/AJYeULe.jpg-

________________________


What I've tried, since.
I clearly need to reinstall Windows, etc, but do I have a more serious hardware failure to deal with first?

  • ■ Disconnected all unnecessaries (including case's front panel buttons and LEDs and USB ports) from the motherboard, leaving only: main power cable, CPU power cable, case fans, and the optical CD Drive.
    ■ Conducted tests using only one stick of RAM at a time.
    ■ Defaulted BIOS back to factory settings.
    ■ Used the "MEMOK!" button on my motherboard to auto tune RAM to a compatible configuration, even though my RAM never seemed to prevent POST.
    ■ Ran lots of MemTest86 tests, which freeze before they finish. But they do report millions of errors before my computer locks up.
Nothing's for sure, but it looks like my motherboard is ok.
RAM and CPU are my biggest suspects.

I'd like to share my MemTest v7.2 results:
Using the -CPU configuration options-, I told it to use only 1 of my 8 CPU's (which are just logical cores?) for the tests as a way to test the CPU chip, too (this was my idea - I'm not sure if it even works this way . . .).
The results are interesting: All but one core cannot start Test #5. Two cores freeze IMMEDIATELY no matter what, so far.
-Screenshot of MemTestv7.2's 14 Different Tests-
By default, MemTest runs through all 14 tests, starting with 0, on until 13. Then it repeats the whole process 3 times, since multiple passes is set to 4 by default.

First Round of Tests (done with RAM stick #1 alone plugged into primary DIMM slot)
Core# | Freezes at: [Test#]-[Percentage Completed]
0 | 4-100%
1 | 7-100%
2 | 0-0%
3 | 0-0%
4 | 4-100%
5 | 4-100%
6 | 3-100%
7 | 4-100%


All seem to freeze RIGHT before starting the next test; they get to 100% then everything stops/goes unresponsive. I'm forced to restart with restart button on motherboard.

Before I recorded the data above, I did earlier MemTest tests and they got a little further - they didn't freeze at Test #4 or #7, BUT they did all find errors. Millions of errors. Here's an example screenshot:
-http://i.imgur.com/cucAf2E.jpg-
(Notice the 500,000+ errors already logged. One test logged -over 28 million-.)

I had time to run two more rounds of tests on a few cores, still using that same RAM chip as before.
Core# | Freezes at: [Test#]-[Percentage Completed]
2 | 0-0%
3 | 0-0%
6 | 4-100%


Cores #2 and #3 giving same result! Not looking good for the CPU, right?

Last (incomplete) round, using same RAM chip:
Core# | Freezes at: [Test#]-[Percentage Completed]
2 | 0-0%
6 | 3-100%


Core #2 STILL not budging - freezes right as Test #0 starts.


Lastly, I did one more incomplete round using a different RAM chip in same primary DIMM slot:
Core# | Freezes at: [Test#]-[Percentage Completed]
0 | 3-100%
2 | 0-0%
3 | 0-0%


Both cores #2 and #3 still causing computer to freeze before any progress happens.
Does this not condemn the new CPU?

And what of the millions of errors reported during the MemTests . . ?

________________________

Electricity
I've lived in the same house for 5 years. Home computer has used same wall outlet and electrical box breaker the whole time.
My surge protector is new and high enough capacity to handle what I'm throwing at it.
Though, as has been the case since I moved, it tells me there's a grounding fault. It's an old house with crappy grounding. Always been that way.

________________________


It's a mess, but I'm hoping for a simple solution.

If you have ANY ideas, I'm all ears!


Thanks for reading.
 

Zerk2012

Titan
Ambassador
https://www.asus.com/us/ROG-Republic-Of-Gamers/ROG-MAXIMUS-IX-HERO/specifications/
Windows® 10 64-bit
Windows® 8.1 64-bit *8
Windows® 7 32-bit *8
Windows® 7 64-bit *8
*8 Windows® 8.1 64-bit and Windows® 7 32/64-bit are only supported when using 6th Generation Intel® Processors
That is part of your problem you got to run windows 10 and never did a fresh install that is also bad.
Your other problem is going to be not buying the memory in a matched set of 4 sticks as in one package instead of 2 sets of 2 sticks. (you usually can work around this)
 

SaVeLeViAtHaN2017

Commendable
Feb 6, 2017
5
0
1,510
(Sorry for late response. No internet access.)


Interesting. I missed that note about OS support for 7th gen processors.
Here's a relevant article I just reviewed.

Looks like all/most next gen processors will require Win10 or up.
The day had to come, eventually.


I never thought about making sure to buy all RAM chips in the same package.
Because of subtle physical differences from batch to batch, I assume.
Here's a relevant Tom's Hardware post on the subject.
Now I know . . .

________________________

Still currently unable to complete any MemTests or even load a Windows 7 Ultimate boot disc - I get blue screens or complete lock-ups.
All hard drives are still unplugged.
Has to be a hardware failure somewhere.

I have new, different RAM coming in today, as well as another CPU (same 7th gen Intel model), and will do more tests tonight.


Thanks for the info, Zerk2012.
 

Zerk2012

Titan
Ambassador
I don't think you will be able to do anything without windows 10 right now.
When you get the new CPU reset CMOS and do a fresh install.
The memory should of worked but if using XMP profile with 2 packs of sticks sometimes the secondary timings are wrong like the tRFC also to run it at 3k speed you might need at bump the voltage up a bit 0.05, the MC voltage a bit or even OC the CPU some.
 

SaVeLeViAtHaN2017

Commendable
Feb 6, 2017
5
0
1,510
New RAM and CPU came in.

First I tried using the RAM - just one stick at a time.
Same results. Tons of MemTest errors found . . . but, once again - all (or maybe just most) errors were reported by core #3.

So I left one stick of the new RAM in my motherboard's primary DIMM slot and tried the new CPU.
Another MemTest - and it was flawless. Zero errors; all 14 tests passed.

So then I plugged in my original 64GB DDR4 RAM, all 4 sticks. Also flawless. No errors.

Then I tried using a Windows 10 boot USB that I made a few days ago.
No BSOD's. No lock-ups. Ran perfectly. I installed Win10 no problem, onto a RAID array using two old mechanical drives.


Next day I reinstalled Windows 10, using same boot USB, onto an M.2 SSD.
And that's what I'm using now. Everything running very smoothly.

________________________

It was the CPU all along.

This thread is solved.
 
Uninstall Nortons thats causing one of the crashes then use their removal tool

The ntfs.sys 0x24 stop error can mean corrupt files or the / a hdd is stuffed

Upload the dmp files to onedrive then post the link

And if you do a clean install delete all partitions / unplug all the hdd's except the one you're installing windows on. Connect them after you install windows

 

SaVeLeViAtHaN2017

Commendable
Feb 6, 2017
5
0
1,510

Ok, I see. You referenced "ntfs.sys 0x24" from one of my blue screen photos.
I got it. Thanks for looking that up.

By "stuffed", do you mean the hard drive being full/already at max capacity?