Omnimaga

Calculator Community => TI Calculators => General Calculator Help => Topic started by: Yeong on August 03, 2012, 11:14:54 am

Title: [nSpire - Fixed] The reason why you should not overclock over limit
Post by: Yeong on August 03, 2012, 11:14:54 am
Well, I had this experience once, and I just wanted to share ;D

One time, I was bored, so I raised EVERYTHING in nover fully. :P
It worked for good few seconds with gbc4nspire, but then, it crashed and something awesome(?) happened. XD
Well, half of my stuffs were semi-wiped out. Technically, they went invisible. O.o
When I deleted the folders (with invisible stuffs) and reset the calc, it came back like a ghost! :D
The only way to fix it was to re-install OS (Thank god I had a copy of OS 3.1)
So, moral: Don't overclock more than you're supposed to XD

hmm maybe this should be moved to humor or something.
Title: Re: [nSpire - Fixed] The reason why you should not overclock over limit
Post by: Adriweb on August 03, 2012, 11:20:15 am
Well, just plain memory corruption :P

Happened to me while I was testing Nover at the time critor was creating it still, I got with undeletable folders / ghost items everywhere which caused me to reformat actually.

So yes, "limits" aren't there for nothing :P
Title: Re: [nSpire - Fixed] The reason why you should not overclock over limit
Post by: calc84maniac on August 03, 2012, 12:24:41 pm
Yes, this is caused by AHB overclocking. Typically around 75MHz seems to be the breaking point for AHB on CX, so it's good to stay quite a bit below that. However, as far as I know, CPU overclocking can only lead to a reboot at most.
Title: Re: [nSpire - Fixed] The reason why you should not overclock over limit
Post by: critor on August 03, 2012, 01:25:52 pm
Well, I had this experience once, and I just wanted to share ;D

One time, I was bored, so I raised EVERYTHING in nover fully. :P
It worked for good few seconds with gbc4nspire, but then, it crashed and something awesome(?) happened. XD
Well, half of my stuffs were semi-wiped out. Technically, they went invisible. O.o
When I deleted the folders (with invisible stuffs) and reset the calc, it came back like a ghost! :D
The only way to fix it was to re-install OS (Thank god I had a copy of OS 3.1)


Interesting experience. ;)

You now get the proof that I was not kidding with the red "Dangerous!" warning in Nover :P
Title: Re: [nSpire - Fixed] The reason why you should not overclock over limit
Post by: calc84maniac on August 03, 2012, 01:31:19 pm
Maybe you should be a little more specific with the warnings, like for CPU overclocking "May cause reboot", and for AHB overclocking "May corrupt filesystem"
Title: Re: [nSpire - Fixed] The reason why you should not overclock over limit
Post by: annoyingcalc on August 03, 2012, 01:35:42 pm
I like that idea.
Title: Re: [nSpire - Fixed] The reason why you should not overclock over limit
Post by: critor on August 03, 2012, 01:40:51 pm
Maybe you should be a little more specific with the warnings, like for CPU overclocking "May cause reboot", and for AHB overclocking "May corrupt filesystem"

I'll check if I can make this fit someway.

Do I let the AHB warning level at 75MHz ?
Title: Re: [nSpire - Fixed] The reason why you should not overclock over limit
Post by: calc84maniac on August 03, 2012, 01:41:33 pm
Probably should go with 70MHz just to be safe.
Title: Re: [nSpire - Fixed] The reason why you should not overclock over limit
Post by: DJ Omnimaga on August 03, 2012, 04:11:10 pm
Also if you only overclock your calc for cooking purposes, I doubt it will work, plus your calc will smell weird in class. Better stay within stable overclocking limits.
Title: Re: [nSpire - Fixed] The reason why you should not overclock over limit
Post by: Yeong on August 04, 2012, 09:00:53 am
I tried that with CD-ROM once. (Burn teh CD process) It ruined my frying pan though. D: