>overclock i5 2500k computer from 3.3 to 4.0 >increase

There is little reason to believe you fucked your hardware.
I'm fairly sure you have a softwre problem. If an update crashes, bad things happen. What happens if you boot into a live linux on a stick/disk? If it's stable on live, backup your data and reinstall windows.

OC problems with CPUs are usually either degradation (needs more voltage over time) or sudden death. None of those should happen with the slight increase you need for 4GHz. How much voltage did you give though? And did you fully reset your BIOS, or just went down with the multiplier?

>>379241
I just went up with the multiplier, and increased the vcore a little bit.

Honestly, BIOS said "computer failure due to bad OC" and when it booted up i used CPU-Z and it told me it was back to under 1.3 vcore and back to 3.3 ghz, so i assume that its fine as it is.

i do NOT have a linux partition, but i do have a small USB, i could probably try from there.

I have to remind you that the original crash happened while it was updating, another very odd thing could be that the PC fucked up for some reason due to OC at first, and then it got fixed but since it crashed and restarted while updating it became another cause.

As it stands, doing nothing, just updating windows and no browsers open, the PC aint crashing. Will post update as it happens. I am quite fucking scared right now due to my financial situation making it unable to replace this system.


Best case scenario would be an easy to fix software failure (also installed avast pre-crash) But a PSU issue would not be the worst case scenario either.

>>379246
Yeah of course, your first crash was most probably because of the OC, but such a crash will not fuck your hardware. It can however easily lead to software problems, especially if it happens during an update.
Which is why you should always do updates on a system that is confirmed stable.

My first guess would be some line in your registry or in some hidden system directory was only half finished when the crash happened and causes problems now whenever it is referenced by something.

I've been overclocking systems for decades, this stuff happens all the time. Which is why benchmarkers will always do a fresh install on a stock system, then install everything they need, and only then start overclocking. Never the other way around or you are just begging for problems.

>>379270
Fuck. I installed win 7 64 bit on an SSD then overclocked all of this without updating. I guess now i know better.


Would PROPERLY updating everything fix it? its strange how the crashes only happened when i was using chrome, but after turning off the PSU for a while and trying it again the updates installed properly (after a few tries of "failure to install updates").

Should i still experience errors?

>>379272
Personally, I would reinstall to be sure you don't have any software problems.
But you might be just fine after updating to latest service pack, it's hard to tell.

Remember correlation is not causation, and unless you can reliably provoke an error, it doesn't mean much.

Of course, it is possible that your PSU is fucked. But looking at the situation...
you did something that is great at provoking crashes;
you had a crash during the time your OS is the most sensitive to it;
problems during this time can lead to more random crashes later, especially with the updating process and seemingly random software;
and you had additional problems after experiencing this crash.

The most likely answer is usually the correct one.
Freak problems like some part just being fucked out of the blue can always happen, but I'd first try to solve whatever makes sense before chaotically blaming things.

>>379274
well, still strange. But after the complete update i am running a full virus scan (last time i had a few micro stuttering and virus scan solved it)

Once i am done with it i am gonna check if playing games while the browser is open crashes the PC again. If it does so, i am gonna probably reformat the entire SSD and reinstall, and the next time do updates before anything else.


If, however, i am lucky and there are no unforeseen consequences and everything is fixed, i might try to re-clock to 4.0.

People claim to take to a stable 4.0 with a vcore of stock 1.300 in my CPU, however i seem to be unlucky and i need at least 1.315 to stress test. However just in case i might leave it at 1.320 vcore with 4.0 ghz to be sure. That would be the ideal way the computer would stay at least until i leave for germany in about a year and a half.


Kinda related question:

Does the program known as "DBAN" deletes everything, even the firmware of an SSD/HDD/Flash drive? or can it be used as a good tool to reformat a drive before installing anything in it? I thought about using it each time to delete any corrupt traces of previous OS however i keep having in my mind the doubt that if i use it and deletes the things that should not be deleted i would just brick the SSD.

>>379280
Most things that are really bad can not be detected at runtime, so unless you click on every blinking banner on your favorite porn site, your anti virus should not find anything.
I don't know anyone really into computers who still uses runtime anti virus. Windows defender is really good nowadays and causes a lot less incompatability problems with other software, and for a deep check just use an anti virus boot/rescue disk since that can actually detect a lot more.


Every CPU is different, one of my 4790K needed 1.3Vcore for 4.4GHz and another one reached 4.9GHz with 1.3V on the same board.
You also have to factor in different motherboards behave differently (the people posting their results usually use high end boards), and that you probably didn't measure with a good multimeter.
You might easily be off the real value by as much as 0.05V, and that is not even considering LLC settings which also skewer things.
Just go for the voltage that works for you. And if you can not cool whatever voltage you have to give for 4.4 or 4 or whatever, then just go a bit lower in frequency.

Oh, and DBAN does not work on SSDs according to their site.
Not an expert on storage, but I don't think anyone programming a reformating tool would make it erase firmware. Not sure if that is even possible without some serious workarounds.

>>379302
It doesn't really work on anything.

Hard disks and SSDs have had their own "ATA secure erase" command for over a decade, and that actually does erase sectors the hard disk has remapped (on SSDs, it makes it regenerate the hardware encryption key). DBAN doesn't do this, it just tells the device to write data.

This means that an adversary that's prepared to tinker with the firmware can read every remapped sector on a DBAN'd hard disk

If you want to securely erase a hard disk or SSD, use the tool it comes with: https://ata.wiki.kernel.org/index.php/ATA_Secure_Erase