On 24-5-2014 0:54, Michael Torrie wrote:
> On 05/23/2014 09:26 AM, Ronak Dhakan wrote:
>> Even I am surprised, python errors should stay in python. But I am
>> sure that the reboot is triggered exactly when I run some faulty
>> code. And usually I change the code after reboot, so I haven't
>> checked whether the same code is able to repeat the reboot. This
>> happens even in simple code of 10-15 lines for drawing a polygon.
>> There was a problem while creating the post asking the question. Here
>> it is now:
>> https://groups.google.com/d/msg/comp.lang.python/WINUrOfAey4/pvbnapLrRcsJ
> Almost certainly you are experiencing a hardware fault.  Possibly bad
> RAM.  Windows will not let user-space code crash the operating system.
> Though user-space code could trigger something in the kernel that then
> faults.  This is likely what's happening here.  But the real cause is
> probably hardware. If it's not RAM, then it might be video hardware
> failing.

Or the computer has been infected by malware.



Reply via email to