Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
This is what happens when you mess with things you don't understand.
There were viruses literally BURNING your mainboard just by setting wrong interrupt. (google for CIH if you are interested)
If you want to play with overclocking, buy a simpler device, some microcontroller, or even a set of transistors, attach it to oscilloscope and then watch what happens when mess with the clock and voltage. -
I agree with you that I mess with stuff that I don't fully understand (ofc did my research before I touched anything) but what does this have to do with the CIH virus lol, my bios is fine, my window boot files where corrupted due to the crash during the windows boot... I also am making sure to keep the voltage <1.35v as the manufacturer's max safe value is 1.4v @mt3o
-
For me it's ancient history, you know. I was a kid then.
CIH was an example that piece of software can wreck the hardware. Just like unstable code going rouge.
--wiki--
CIH's dual payload was delivered for the first time on April 26, 1999, with most of the damage occurring in Asia. CIH filled the first 1024 KB of the host's boot drive with zeros and then attacked certain types of BIOS. Both of these payloads served to render the host computer inoperable, and for most ordinary users the virus essentially destroyed the PC.
I decided to tweak my two years old-mild overclocking on my main/home pc, to get more juice out of it.
Started with small steps running benchmarks each time I upped the clock.
Didnt crash me once up until it crashed while windows was booting after restart.
I thought to myself, that's normal, now I just have to lower it a bit until I find the sweet spot.
After windows finished crash dumping, restarted, lowered clock from bios, and headed to boot windows.
Windows recovery came up to scan my installation, pretty normal after a bsod.
I was waiting for it to finish, thinking that ofc there is no error you silly windows, until the recovery said that it could not recognize the error.
Proceeding to boot normal windows via the correspndent button in the recovery, the recovery itself came up again scanning for errors. I waited again only for the same outcome, and restarted my pc.
Yeap the recovery again scanning for errors.
How the hell did my boot became corrupted after just a crash. I've been fighting since yesterday for hours to fix this shitty situation but to no avail. I really dont want to clean install...
I couldnt even sleep well last night thinking that I have to fix this after work today...
Fuck my life, fuck windows
undefined
crash
boot
windows