![]() So I tried reverting back to NVIDIA 384.98 to see if anything changed but it was still freezing. It would still freeze even if all my code did was define a variable and then initialize it. I don't think the contents of the code mattered. I closed the IPython tab (which was idle) in Spyder when the new TF session in the terminal was initializing variables and then my computer froze completely. Training completed in Spyder IPython tab and another file was run in terminal.Training completed in Spyder console and Python was idle and I closed the console tab in Spyder.It also has happened some other times like. But I noticed it would usually happen during the run of n(tf.global_variables_initializer()) in any of the files. This would happen with different files, not one specific file. However, if I was playing music through Spotify, it would continue playing without any interruption. Couldn't use Ctrl + Alt + F1 to login into a virtual console and kill the process as keyboard also became unresponsive. However the other times when I'd terminate, my entire computer would freeze and become unresponsive. After that, sometimes when I'd terminate TF code (either with ^C in terminal or closing IPython tab in Spyder) it would successfully terminate with KeyBoardInterrupt. I had changed my NVIDIA driver version to 387.12 some time ago. GPU model and memory: GeForce GTX 950M, 2GB. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |