Author Topic: [nSpire - Fixed] The reason why you should not overclock over limit  (Read 2928 times)

0 Members and 1 Guest are viewing this topic.

Offline Yeong

  • Not a bridge
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3739
  • Rating: +278/-12
  • Survivor of Apocalypse
    • View Profile
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.
Sig wipe!

Offline Adriweb

  • Editor
  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1708
  • Rating: +229/-17
    • View Profile
    • TI-Planet.org
Re: [nSpire - Fixed] The reason why you should not overclock over limit
« Reply #1 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
My calculator programs
TI-Planet.org co-admin.
TI-Nspire Lua programming : Tutorials  |  API Documentation

Offline calc84maniac

  • eZ80 Guru
  • Coder Of Tomorrow
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2897
  • Rating: +467/-17
    • View Profile
    • TI-Boy CE
Re: [nSpire - Fixed] The reason why you should not overclock over limit
« Reply #2 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.
"Most people ask, 'What does a thing do?' Hackers ask, 'What can I make it do?'" - Pablos Holman

Offline critor

  • Editor
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2079
  • Rating: +439/-13
    • View Profile
    • TI-Planet
Re: [nSpire - Fixed] The reason why you should not overclock over limit
« Reply #3 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
TI-Planet co-admin.

Offline calc84maniac

  • eZ80 Guru
  • Coder Of Tomorrow
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2897
  • Rating: +467/-17
    • View Profile
    • TI-Boy CE
Re: [nSpire - Fixed] The reason why you should not overclock over limit
« Reply #4 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"
"Most people ask, 'What does a thing do?' Hackers ask, 'What can I make it do?'" - Pablos Holman

Offline annoyingcalc

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1950
  • Rating: +140/-72
  • Found in Eclipse.exe
    • View Profile
Re: [nSpire - Fixed] The reason why you should not overclock over limit
« Reply #5 on: August 03, 2012, 01:35:42 pm »
I like that idea.
This used to contain a signature.

Offline critor

  • Editor
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2079
  • Rating: +439/-13
    • View Profile
    • TI-Planet
Re: [nSpire - Fixed] The reason why you should not overclock over limit
« Reply #6 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 ?
« Last Edit: August 03, 2012, 01:41:03 pm by critor »
TI-Planet co-admin.

Offline calc84maniac

  • eZ80 Guru
  • Coder Of Tomorrow
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2897
  • Rating: +467/-17
    • View Profile
    • TI-Boy CE
Re: [nSpire - Fixed] The reason why you should not overclock over limit
« Reply #7 on: August 03, 2012, 01:41:33 pm »
Probably should go with 70MHz just to be safe.
"Most people ask, 'What does a thing do?' Hackers ask, 'What can I make it do?'" - Pablos Holman

Offline DJ Omnimaga

  • Former TI programmer
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55835
  • Rating: +3151/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • DJ Omnimaga Music
Re: [nSpire - Fixed] The reason why you should not overclock over limit
« Reply #8 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.
In case you are wondering where I went, I left Omni back in 2015 to form CodeWalrus due to various reasons explained back then, but I stopped calc dev in 2016 and am now mostly active on the CW Discord server at https://discord.gg/cuZcfcF



Official Website |T-Shirt store | Reverbnation | Facebook | Youtube | Twitter | Spotify

Offline Yeong

  • Not a bridge
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3739
  • Rating: +278/-12
  • Survivor of Apocalypse
    • View Profile
Re: [nSpire - Fixed] The reason why you should not overclock over limit
« Reply #9 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:
Sig wipe!