OC causing BSoD

[safarihunter]

I recently took apart my computer to do a thorough cleaning and improvement on my cable management. After I put my computer back together I got in any game and soon after starting it would crash, this escalated to getting the BSoD quite frequently even when I was only trying to log into windows. The error codes on the BSoD were always changing each time and this became a cycle of restarting until I turned off the computer. I tried taking my hardware out to localize the problem but nothing worked, not even reseating my cpu or gpu or taking out all my connections and cleaning and putting them back in. I even did a factory reset on windows. killing all of my previous files.

 

I found that once I turned off my OC that it fixed the problem, but once I turned it back on the BSoD persisted, I've used OC on this rig for a while and want to continue. Is my motherboard partially broken or is this a software issue? I'd rather not have to get another motherboard but I'm guessing its what I'll have to do to get my OC back. 

 

Thank you for your help!

 

Parts list:

CPU: i5 6600k

GPU: GTX 1070

MOBO: Asus Z170-A

CPU Cooler: Kracken X61

[Guest]

Try to re-seat the memory.

Memory is likely the issue over the board unless the cpu is getting too hot, may also cause BSODs.

 

[Whiro]

2 minutes ago, safarihunter said:

I found that once I turned off my OC that it fixed the problem, but once I turned it back on the BSoD persisted, I've used OC on this rig for a while and want to continue. Is my motherboard partially broken or is this a software issue? I'd rather not have to get another motherboard but I'm guessing its what I'll have to do to get my OC back

If the oc is the problem I would suggest starting your oc process from scratch. Reset all settings and than start again. Maybe some settings get messed up who knows.

[Badger906]

While hardware failure is the easiest to point the finger at due to recent cleaning you could help shed some light on the situation by locating your blue screen dump files. Usually located c:\Windows\memory.dump

[safarihunter]

1 hour ago, Badger906 said:

While hardware failure is the easiest to point the finger at due to recent cleaning you could help shed some light on the situation by locating your blue screen dump files. Usually located c:\Windows\memory.dump

How do I fins that?

[safarihunter]

1 hour ago, ShrimpBrime said:

Try to re-seat the memory.

Memory is likely the issue over the board unless the cpu is getting too hot, may also cause BSODs.

 

I have reseated the memory several times, could the memory be damaged and only react when I am overclocking?

[Guest]

2 hours ago, safarihunter said:

I have reseated the memory several times, could the memory be damaged and only react when I am overclocking?

Well yea that information is super useful!!!!!......... lol.

 

Does it happen only when you are overclocking? If so, then it's a result of unstable overclock.

 

Edit, I didn't clearly read your first post, I'm sorry.

[safarihunter]

1 minute ago, ShrimpBrime said:

Well yea that information is super useful!!!!!......... lol.

 

Does it happen only when you are overclocking? If so, then it's a result of unstable overclock.

yes It's only when I'm overclocking, so what should I look for to see if it is an unstable OC? would taking the computer apart and putting it back together really cause that?

[Guest]

2 hours ago, safarihunter said:

yes It's only when I'm overclocking, so what should I look for to see if it is an unstable OC? would taking the computer apart and putting it back together really cause that?

Yes. for a few reasons.

Different temps (worse?)

Cpu Degradation.

Memory is delicate. you can not just drop it on the table and careful not to bang it off the case stuff like that. (not saying you did any of that....)

Or something changed in the profile?

[safarihunter]

2 minutes ago, ShrimpBrime said:

Yes. for a few reasons.

Different temps (worse?)

Cpu Degradation.

Memory is delicate. you can not just drop it on the table and careful not to bang it off the case stuff like that. (not saying you did any of that....)

Or something changed in the profile?

ok, so how should I go about fixing an unstable OC?

[Guest]

1 minute ago, safarihunter said:

ok, so how should I go about fixing an unstable OC?

If I was you, Id test the memory with everything at default first.

Then re do the overclock from scratch.

[safarihunter]

test the memory? like put it in one of my buddies rigs and test it that way?

[Beerzerker]

Something such as Prime 95 as an example can be used to test RAM under load for errors.
If the sticks are having issues it will indicate such, however it won't tell you what the problem is aside from it exists.

 

I will say errors such as "IRQ not less or equal" when seen normally means you don't have enough voltage to your RAM to keep it stable, that particular error message meaning that in most cases.

[Whiro]

8 minutes ago, ShrimpBrime said:

If I was you, Id test the memory with everything at default first.

Then re do the overclock from scratch.

I suggested that as well but I’ve been ignored  

[Guest]

Lol it happens. 

[Guest]

5 minutes ago, Beerzerker said:

Something such as Prime 95 as an example can be used to test RAM under load for errors.
If the sticks are having issues it will indicate such, however it won't tell you what the problem is aside from it exists.

 

I will say errors such as "IRQ not less or equal" when seen normally means you don't have enough voltage to your RAM to keep it stable, that particular error message meaning that in most cases.

I agree to this 100%

[safarihunter]

thank you everyone that has helped! I will be trying this tonight.