BSOD might be cause of HDD?

[nemanjamadrid]

Hello. lately have been experiencing Blue Screen of Death.Check RAM via memtest and it's working fine,then i check with HDD scan and i get few things on HDD and i'm not sure if can be something really bad or like that.I will show you graphs that i got after scan.If someone with more experience can tell me that would be nice.

Link to chart: https://ibb.co/kjx5KS

Link to bar: https://ibb.co/kacNzS
Thanks in advance, and please explain to me if my HDD isn't working properly.
PS. i use SSD but it runs perfectly fine,unless this make it bad.

SSD: https://ibb.co/ibp7Yn

 

[SkyNetRising]

You have to fix memory settings first.
Make a photo of ram settings in BIOS with your phone.

 

[nemanjamadrid]

Ok gona upload pictures.if you want more just say so.
https://ibb.co/gdU7MJ
https://ibb.co/hoKP1J
https://ibb.co/dCRhoy
https://ibb.co/hhXBgJ
https://ibb.co/kvWtvd

 

[SkyNetRising]

In this screen - instead of 15-15-35 you have to put 18-17-39. Don't touch secondary timings.

 

[nemanjamadrid]

Just did and it wont boot

 

[SkyNetRising]

You obviously changed something more.
Reset BIOS settings and start again.

 

[nemanjamadrid]

I reseted and put on 18 17 39. Fucking machine won't boot. Does it have to do something with jedek 17?

 

[SkyNetRising]

You shouldn't change JEDEC table entries. In fact - I'm surprised your BIOS even allows that.

 

[nemanjamadrid]

I truly don't know what to do anymore.If i get another BSOD I'm giving it to repair.paid 2k euros for it and isnt working properly since i bought it. Not IT guy...

 

[stdragon]

A few observations worth noting

1. Crucial is regarded as a reliable brand, and the memory you have is as stock conservative as it gets for DDR4-2400. In your case, this is a good thing. Generally less complication, less trouble.

2. You've got a good motherboard. The ASRock Fatality series is good.

3. Per Crucial, you have the correct RAM part (SKU) picked out for your motherboard. So compatibility has been established. In theory, you should be all good here.

4. I've noticed your memory timing is set to 2133, which will support CL 15 per the JEDEC tables. That said however, it should be set for 2400 so it can adhere to the stock JEDEC table settings of CL 17.

5. As for modifying the JEDEC tables, I seriously doubt that's reprogramming the SPD chip. Most likely, you're just copying the values to BIOS, then making the change in BIOS which is overriding what's on the DIMM. Basically, it's a custom overclocking JEDEC profile.

That all said. I think it's time to take a step back and re-evaluate your current settings. Start with basics. No overclocking, no tweaking. Start with stock standard CPU and RAM (auto) settings first. To do this, clear your BIOS (CMOS) settings back to system defaults and go from there.

Also, be sure to check DIMM placement. I pulled up your manual online (link below to the PDF). It says to populate slots A2 and B2 for two DIMMs. Not sure why it matters (say opposed to A1 and B1), but safe to say it's best to go with what the manual says. It's on Page 17.

As for the BIOS settings, I'd stick with EZMode as on Page 56. Do NOT use XMP Profile mode for memory. Leave it to AUTO. If you must, adjust your boot settings and device options. But for the love of all that's holy, don't over clock or enable OCing of any type. Save settings and let it boot.

Once done, see if you can take another screenshot of the memory as reported in CPUZ like last time.

http://asrock.pc.cdn.bitgravity.com/Manual/Fatal1ty%20Z370%20Gaming%20K6.pdf

 

[nemanjamadrid]

Ok.So what i did is following. I placed 1 DIMM into A2 and 2 DIMM into B2. it didn't boot at all. I kept 1 DIMM into a2 socket and kept moving 2nd DIMM into 3 remaining. Didn't boot at all. Then i tried only with that one on A2 and it booted. Moved that DIMM into all 3 remaining sockets and it booted on all 4 sockets. I guess i have 1 RAM that is faulty.Right now I'm on 1 DIMM(8gb RAM). Do you think my other 8GB has some sort of problems? I even tried to return to previous state and it wont boot.So only way it works is when i keep that 1 DIMM into A2 socket and it works.Other one won't work at all. Please tell me what do you think it is? i'm 99% sure it's RAM that's faulty

 

[SkyNetRising]

Can you boot with single ram module, one - that you suspect it faulty?

 

[nemanjamadrid]

I can't boot with that "faulty one" but i can boot with other one. I just got this https://ibb.co/fswGWJ
Any idea what can it be?

 

[SkyNetRising]

Then don't use the faulty module.
Did you have both modules installed, when BSOD happened?

 

[nemanjamadrid]

nope only working one

 

[stdragon]

With the "faulty" DIMM, go ahead and test with Memtest86 just to be sure. If it flags errors, specifically in the same address range, yeah, a bad chip on the DIMM someplace. If the errors are completely random, usually it's a timing or voltage issue.

If you want to reduce the frustration regardless, give Crucial a call and start an RMA process. They should be able to assist in replacing the memory. Their RAM typically has a limited lifetime warranty.

Their contact info below (select language to change country).

http://www.crucial.com/usa/en/support-contact?cm_re=us-footer-_-us-support-_-us-support-contact

Their warranty info below

http://www.crucial.com/usa/en/company-warranty

 

[stdragon]

One last thing - re-seat the CPU back in the socked by removing and re-installing again. If any one of the 1151 pins on the socket don't have a good connection with the CPU (obstruction from dust, or perhaps an oily finger print from touching the bottom of the cpu..etc), you can get all sorts of errors. That's because the memory controller isn't on the MB, rather it's now on the CPU.

It should be obvious advice - but always unplug power from the computer, then press the power button to drain residual flea power. Now wait 60 seconds before removing or installing any component from the motherboard. Otherwise, you risk shorting out hardware causing irreparable damage to a component.

 

[nemanjamadrid]

It wont even boot memtest with faulty RAM...i can just press power and that's it