On 12/01/2015 12:28 AM, Joshua Springer wrote:
Hi, I've been developing an Android app for one of my classes. I am
familiar with programming and using computers in general, but not
virtualization software. I am trying to get Android Studio on my
computer, but having some serious problems. I installed Android Studio
on my computer the first time, and whenever I would run it, it would
freeze Windows (10) completely, with this error
<https://cdn.xtremerain.com/wp-content/uploads/2015/10/screenshot-CLOCK-WATCHDOG-TIMEOUT.png>.
I reinstalled Windows, and then reinstalled Android Studio, and it
worked fine for a day. Now I come back today and the same error is
happening. I don't feel like installing Windows again. What should I do?
I've tried running it in compatibility mode for 8.1, 7, and running as
administrator, as well. And I have two other machines, both Macs, which
run Android Studio and the emulators without a problem, although they
are slower. Please help!
Also, I should note that I'm using an i7 4790K @4.00GHz on a Gigabyte
Z97N-Gaming 5 motherboard with 16GB of RAM. Also I have a GTX 970 and
naturally the NVIDIA drivers, but I feel like this definitely wouldn't
affect the performance of Android Studio.
Joshua,
When are you seeing this crash? Visualization isn't involved unless
you're actively running an emulator. Otherwise, Android Studio is just
an ordinary Java desktop app. We also have no reports of this on the
Android issue tracker.
Generally speaking, a CLOCK_WATCHDOG_TIMEOUT is a hardware issue. It
means that one of your CPU cores failed to respond to an interrupt.
See Microsoft's documentation, here:
https://msdn.microsoft.com/en-us/library/windows/hardware/ff557211(v=vs.85).aspx
This isn't something that Android Studio should be able to cause
directly. Something else is more fundamentally wrong with your computer.
There's some troubleshooting tips in this thread:
http://answers.microsoft.com/en-us/windows/forum/windows_8-update/clockwatchdogtimeout-error/33b46641-fc90-45d9-8027-b834f44cfd03
Basically you're going to have to troubleshoot your system from the
ground up. (Make sure temperatures are within spec, remove software that
interfaces with the BIOS, clear your BIOS settings, etc.) If all of that
fails, you likely have a bad CPU.
--
Trevor Johns
Google Developer Programs, Android
http://developer.android.com
--
You received this message because you are subscribed to the Google Groups "Android
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/android-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/android-developers/n3l5d8%24fl0%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.
