Linked by Thom Holwerda on Fri 17th Dec 2010 22:06 UTC, submitted by poundsmack
Permalink for comment 454084
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2010-06-02
Same way as any operating system - memory corruption in kernel space - either by failing hardware, overheating, or installing drivers that arn't reeeeally compatible.
The days of bsoding through opening a malicious jpeg are over (arguably) but there are still lots of very common non-userspace ways to get a bsod. My last desktop would bsod whenever i accidentally bumped it - turns out i was missing a few standoffs when i assembled it and it was shorting the motherboard to the case
I had a bsod on my first week of vista trying to install an unsigned driver that wasn't as compatible as i thought it was.
EDIT: You can of course see whether or not it restarts by default after a bsod by investigating the setting (Win+Pause > Advanced System Settings > Startup and Recovery > System Failure).
Edited 2010-12-19 08:16 UTC