When a computer freezes or takes years to respond, What's

stuck in an infinite loop inside a function

>>59125509
0/10

CPU load is near 100% so there aren't spare cycles to handle user input/update the display.

This can happen for many reasons, but in general you can imagine that the computer is just busy doing other things.

>>59125489
The computer is sometimes busy fucking your mom.

Do computers just outright freeze anymore. I can understand a buggy program but not the is itself. Last time I remember this was way back when Linux disk I/O used to make everything halt.

>>59125489


>app is working
>app is stuck
>some other app is bugged/stuck
>windows is doing shit
>windows turned off the HDD and its turning on again
>HDD turned off and on for some reason
>SATA cord is bad
>PSU is bad
>mobo is killing the HDD (iv'e had cases that this actually happened)
>HDD is dying
>PSU is exploding literally
>computer is dying instantly
>computer explodes

>>59125631
i have an fx 6300. sometimes I push that piece of trash to the limit and my computer will freeze up for a bit. Sometimes it doesn't unfreeze and I have to hold the button in. only generally if i'm gaymen or rendering as well as doing some other things at the same time though.

>>59125653

>mobo has Alzheimer's disease

unfair scheduler,
scheduler allowing a monopolizing process to take over

>>59125489
"must always be doing something". Actually not.

CPUs can sleep forever if no interrupts happen (eg: no runnable procs, so no timers set).

>>59125657

what the fuck are you doing to your computer, i have a fx 6300 to, i get it to 100% frecuently and it never freezes holy shit

>>59125706
try and render something then launch total war and see what happens. hell even just youtube and total war will do it sometimes

>>59125593
/thread

>>59125489
>A computer must always be doing something
Nope
In fact, your computer is doing nothing 99% of the time.
http://duartes.org/gustavo/blog/post/what-does-an-idle-cpu-do/