Random freeze and restart after new SSD install

[Ad Hominem]

I'm getting random freezing and restarting after I installed a new Samsung 970 EVO. These almost never come with a BSOD. Sometimes the PC goes right into rebooting and other times it just crashes to a black screen with my display not detecting any input.

I've tried a few things to fix this
Update BIOS to latest
Reinstall windows 10
install Samsung drivers for SSD
clean GPU driver install
install LAN drivers
disable power managment in Device Manager
ran a few commands in power shell to check for corruption against a known image
and probably a lot more that I can't remember right now because I've been trying to fix this for so long

Windows 10 64 bit
i7 7800k
MSI z370 Gaming M5
EVGA 1080ti FTW 3
TridentZ 3200 RAM (8GB x 2)

I'm at a loss for trying to figure out what is causing this. I tried using windows event viewer but these crashes don't always come with an error before hand. Has anyone heard or dealt with something like this? This only started once I installed the new hard drive, so I'm thinking it has something to do with that, but I don't know what else to do.

It almost never happens while gaming, although occasionally it does. Most often it seems like it happens when watching youtube or doing simple stuff like writing this post (happened 3 times trying to write this).

[Ad Hominem]

DudeSau©e™님이 먼저 게시:

Ad Hominem님이 먼저 게시:

How do I look for rapid mode? Is that something like a BIOS option or in the Samsung software?

Samsung Magician software, there's an option to enable. Then you restart. It partitions some of your RAM. You can reverse if you don't like the feature. I tried it and ended up not using it.

Ah I see it. Says that it is not supported for whatever reason.

[Bad 💀 Motha]

NVME doesn't support Rapid Mode cause it's pointless for such fast drives

[Ad Hominem]

So, none of the utilities or drivers fixed my crashing issue. So I started to poke around in my BIOS to see if anything looked out of place or I had inadvertently changed something that would cause this. While fiddling around in BIOS it froze and crashed on me. I keep forgetting to run a memory test overnight but this BIOS freeze makes me think I've got a bad RAM stick. Running 16GB (2x8GB) of TridentZ RGB 3200 CL14.

I tried returning my CPU to stock (remove all core boost) which didn't work. Then I tried to disable XMP which also didn't work. After that it froze in BIOS.

Just popped one stick out, so I guess I'll see if I got lucky and pulled the right one. Hopefully I can get this thing figured out so I can begin the process to solve it. It's hard though because aside from yesterday morning, it ran fine the rest of the day with gaming and watching youtube. I'm not sure how a bad RAM module would allow the system to work fine half the time, but that's what is happening. Gskill apparently has limited lifetime warranty on DRAM memory modules and these arent that old, I'm really hoping I've found the problem.

[GOD RAYS ON ULTRA™]

Ad Hominem님이 먼저 게시:

So, none of the utilities or drivers fixed my crashing issue. So I started to poke around in my BIOS to see if anything looked out of place or I had inadvertently changed something that would cause this. While fiddling around in BIOS it froze and crashed on me. I keep forgetting to run a memory test overnight but this BIOS freeze makes me think I've got a bad RAM stick. Running 16GB (2x8GB) of TridentZ RGB 3200 CL14.

I tried returning my CPU to stock (remove all core boost) which didn't work. Then I tried to disable XMP which also didn't work. After that it froze in BIOS.

Just popped one stick out, so I guess I'll see if I got lucky and pulled the right one. Hopefully I can get this thing figured out so I can begin the process to solve it. It's hard though because aside from yesterday morning, it ran fine the rest of the day with gaming and watching youtube. I'm not sure how a bad RAM module would allow the system to work fine half the time, but that's what is happening. Gskill apparently has limited lifetime warranty on DRAM memory modules and these arent that old, I'm really hoping I've found the problem.

If you run out of luck just reset your cmos using the motherboards jumper. I've had bios get mucked up before from changing this and changing that. Sometimes a good cmos reset will do the trick.

[Ad Hominem]

DudeSau©e™님이 먼저 게시:

If you run out of luck just reset your cmos using the motherboards jumper. I've had bios get mucked up before from changing this and changing that. Sometimes a good cmos reset will do the trick.

I've got the MSI z370 gaming M5 which has an incredibly useful reset cmos button on the back, which I've had to use a few times mucking around. My settings now are pretty stock though I guess it wouldnt hurt to give it a try. I really dont want to do the RMA process unless I'm damn sure. I need to try the removed stick in a new slot, it's so sporadic and hard to replicate that I need to just wait and see if it's actually fixed or not. Usually booting and right after boot are the most likely times for it to crash from what it was doing, and so far so good.

[Bad 💀 Motha]

If the bios is locking up, yes RMA the motherboard. Not much other choice and no ways to fix that issue yourself

What you could try a bios reflash

[Ad Hominem]

Bad 💀 Motha님이 먼저 게시:

If the bios is locking up, yes RMA the motherboard. Not much other choice and no ways to fix that issue yourself

What you could try a bios reflash

That wouldn't be the ram?

[Bad 💀 Motha]

To make the bios lockup, doubtful. Won't hurt to try other ram though. If the ram was really that bad, I doubt you get through any OS install without problems, or even boot an os properly

[Ad Hominem]

Bad 💀 Motha님이 먼저 게시:

To make the bios lockup, doubtful. Won't hurt to try other ram though. If the ram was really that bad, I doubt you get through any OS install without problems, or even boot an os properly

It's pretty sporadic, but it has gotten a lot worse. Used to be the odd crash and reboot once in a blue moon but now it might take 10 tries of locking up during the boot process, or crashing moments after loading windows before it would go all day without another issue. Like yesterday it failed to boot over and over and got into OS just to crash repeatedly until it finally just didn't crash and wen't all day.

A lot of times it would crash but not even begin the boot process, just hang on a black screen with no display output, and pressing reset or power button wouldn't always bring it out of that state. Sometimes had to hit the switch on the power supply to get it going again.

Now that I removed a stick I've been trying all the things that usually make it happen but havent gotten a crash yet. Gonna give it a day or two to see if it rears its ugly head again or if I found the issue. Also want to try a different ram slot in case it's not the stick that's bad but rather the slot.

It's really odd to me that it could crash repeatedly many times and then start working again, but I guess it depends on how the components failed. I would think if something was bad it would just stop working, instead of working some of the time.

[Bad 💀 Motha]

Well now THAT does sound like issue with either particular stick of ram or maybe the slot it was using. If one stick of ram makes the system stable again, power down and try the questionable ram stick in a different slot and then test again. Also whenever reinserting ram, ensure it is seen by both the bios and os

[Ad Hominem]

Bad 💀 Motha님이 먼저 게시:

Well now THAT does sound like issue with either particular stick of ram or maybe the slot it was using. If one stick of ram makes the system stable again, power down and try the questionable ram stick in a different slot and then test again. Also whenever reinserting ram, ensure it is seen by both the bios and os

How important is it to have the sticks in the right slots per the mobo manual? Like if I put it in another slot (maintaining A and B channel for dual channel) does it make a difference?

So system was working great all day yesterday and this morning with 1 stick, for sanity check I put the questionable stick back in its normal slot, and within 30 minutes crashed twice.

Trying a different slot now.

[Bad 💀 Motha]

What slots were they in before?
If were in slots 1 and 3, try slots 2 and 4 instead

[Ad Hominem]

they were in A2 and B2 per the manual. Got em now in A2 and B1, the questionable stick was in B2. I might need to remove my cooler to get to the other one, I got one of those massive noctua coolers.

[Bad 💀 Motha]

Just slide or unclip the cooler fan, install the ram, reinstall the cooler fan

[Ad Hominem]

I already have the second fan unclipped and just kinda dangling off the CPU cooler fins.

It's also a ♥♥♥♥♥♥ up situation to get to in other ways. I have a rosewill thor case so it's massive and I had to build my desk around the PC because it's too big to move in and out from under the desk. It's in the corner of an L. And I have the 4 120mm fans on the side panel so it's hard to even get the side panel off because of the fan wires. So without taking part of my desk apart I don't have a lot of room to work on it in place.

It's not a bad setup when everything is working, I swear lol

Is there any adverse conditions to having the ram in the wrong slots, assuming you still maintain dual channel? I verified this in CPU-Z that I am still in dual channel memory mode and both sticks area showing full capacity and speed.