Hello Folks,
when I open a new notebook in Mathematica, type 2+2 and press shift+return or select Evaluation → Evaluate Cell from the menu, the cell highlights for a few seconds, then the “ploing” system sound is played and nothing happens. In the menu, under Evaluation->Quit Kernel, both Options “Local” and “Link Snooper” are deactivated(grey), so I assume no Kernel is running. If I choose “Start Kernel”->“Local” from the menu, after about a second, the familiar “Ploing” sound is played and after that everything is the same. Does this mean the kernel crashes? What can I do? Is there any log file, or some error message from which i can get an idea where to look next? reinstalling mathematica and/or rebooting the system didn’t help…
Meanwhile, I am pretty sure the kernel crashes instantly on startup. A bit more Information:
System is Windows 10 Pro 1903, 64 bit
Processor Core i7 3770
16GB System Memory
Mathematica version was a fresh Download of 12.1 Student Edition a few days ago, and it worked the first time I tried it.
Now I reinstalled it, uninstalled it, deleted the Mathematica Folder in %user%\AppData\Roaming, installed it again, but nothing has changed.
It even beeps when it is showing the splash screen. When I then open a new Notebook and go t Help->Why the beep? It shows me:
The kernel Local has quit (exited) during the course of an evaluation.
When I go to Edit->Preferences, it shows a popup “Formatting Notebook contents” and then keeps beeping repeatedly. The Notebook window freezes and sais “no response” in the title. I then have to kill the mathematica process via task manager.
I had a similar problem today. Try to unplug your internet connection (or disable your ethernet adapter in WIN) and run Mathematica. If it works, then go to preferences and in tab Internet & mail uncheck Allow the Wolfram System to access to internet. Then it should work normally with the internet.
I transferred it to my Thinkpad now(running Xubuntu), there it works fine… Still don’t know what the issue was or how i could have figured it out. I searched hours for a log file or a meaningful error message.
Thank you for your suggestion, if I need it on the Windows machine again, I will try that.