|
2011-04-17
, 22:47
|
|
Posts: 356 |
Thanked: 217 times |
Joined on Aug 2010
@ Netherlands
|
#2
|
|
2011-04-17
, 22:54
|
|
Posts: 209 |
Thanked: 203 times |
Joined on Jun 2010
@ Portugal
|
#3
|
|
2011-04-17
, 23:28
|
|
Posts: 275 |
Thanked: 389 times |
Joined on Feb 2010
@ Sydney
|
#5
|
|
2011-04-18
, 00:56
|
Posts: 842 |
Thanked: 1,197 times |
Joined on May 2010
|
#6
|
The Following 3 Users Say Thank You to RobbieThe1st For This Useful Post: | ||
|
2011-04-18
, 05:22
|
Posts: 1,163 |
Thanked: 1,873 times |
Joined on Feb 2011
@ The Netherlands
|
#7
|
|
2011-04-18
, 05:48
|
Banned |
Posts: 778 |
Thanked: 337 times |
Joined on Jun 2010
|
#8
|
|
2011-04-18
, 06:07
|
Posts: 1,751 |
Thanked: 844 times |
Joined on Feb 2010
@ Sweden
|
#9
|
|
2011-04-18
, 11:43
|
Posts: 82 |
Thanked: 25 times |
Joined on Apr 2011
|
#10
|
Does anyone knows wha this is? or is it just a plain overclock unstable reboot thing, since its clearly related to the overclocking of the device?
(is there maybe a way to check a log file, via xterm, for where i can look for errors?)
thankyou.