• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Why did they have to make the BSOD so ugly? (poll)

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
"It happens all too often, unfortunately."

Agreed. And 90% of the time it's due to an incorrect setup for capturing the dump, (page file not large enough, not enough free disk space on system partition, ASR software/BIOS setting) or errors with disk management software (afamgt.sys, otman5/vsp.sys, etc).
 
I also get the BSOD when i overclock too much, but i also got it once when i tried to put my system disk on a raid channel courtesy of the Via vt6410 chip. I don't know what was more sad - the fact that i thought ATA133 had an advantage over ATA100, or the fact that i would get that damn thing everytime i loaded up a game and was doing good in it (like a positive score in CS).

Oh, and if audio is still functioning during a BSOD, you should hear something like "I'm sorry. I can't let you do that". lolz.

And, i agree with Sunner. But, a BSOD displaying pr0n may be counterproductive. You may be pursuaded to cause BSODs at work instead of doing your work. If the boss comes over and says wtf r u doing, you can say "Hey, I can't help if Microsoft cares about its customers":laugh: lol
 
Back
Top