Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Certain BSODs (e.g., 0xc000021a) will say that the system has been shut down to prevent further problems. Obviously this is not actually the case since the message can be viewed on screen, however, the hard-drives are shut down. This is quite annoying because it adds unnecessary wear and tear to the drive and in all likelihood, the user is going to press the Reset button to reboot, requiring the drives to spin up again anyway.

Does anybody know of a way to configure Windows so that it does not turn off the hard-drives on a BSOD? There do not seem to be any related options that I can find; only an option to not reboot which is already selected.

share|improve this question
Is your computer BSODing frequently enough for this to actually become a problem? (stop everything is probably the safest thing to do when the OS has determined it is borked - what if the disk controller driver has malfunctionned?) – Mat Apr 21 '12 at 22:35
Even once is too much; and it’s a software issue. (It doesn’t actually stop everything now does it; the fans are still spinning, the video-card is still active…) – Synetech Apr 22 '12 at 0:50
First time I have seen someone actually want to live with frequent bsods rather than fix the real problem. One purpose of a bsod is to protect hardware from potential damage. – Moab Apr 22 '12 at 15:12
Who said anything about not fixing it or that it’s frequent? Once again, it is not a hardware issue; it is a software issue, and having the drives shut down for nothing only adds to the work since it increases the reboot time and adds wear-and-tear to the drives, thus increasing damage (if it really were trying to prevent damage, it would shut down the whole system, not just the drives). I don’t understand the complaints. People ask about preventing auto-restart on BSOD, and nobody whines about that; this is similar. If you don’t know, then just leave it, nagging doesn’t answer anything. – Synetech Apr 22 '12 at 15:42
Oh, and like I already said, IT ADDS UNNECESSARY WEAR-AND-TEAR and accumulation to the SMART data of ALL of the drives. Again, I don’t see why anyone would have such an objection to a simple configuration question. If I asked how to disable a memory dump on BSOD, you would have just answered it because you know how to, but because you don’t know how to disable shutting off the drives on BSOD, you question the reason for the question as though I’m asking something suspicious and malicious. :roll: – Synetech Apr 25 '12 at 3:12

Upon a reboot, everything gets reinitialized, even your hard drives. They couldn't get reinitialized without first spinning down and up again, this is similar to doing a reboot in which it also changes the speed of the drive. Keeping the drives in the state they were in at the crash is a very bad idea, especially when you are experiencing hardware related crashes.

I would be far more concerned as to why you are experiencing BSODs than to why you want to do this, apart from a Graphics issue that I resolved I never had any BSODs and you shouldn't have much either. You are better off obtaining a stable system than trying to do something that does not really matter.

Technically, one could rework the hardware / BIOS / OS to behave that way but that would be a high cost for a very small benefit. Currently, Windows can't do this because it has no control over it; I even doubt if someone ever had the idea to implement support for this kind of idea. The D really stands for Death...

Tip: If you want to spare out wear / tear, try minimizing the disk I/O your operating system performs. I would be far more concerned about the head than the platter(s), because the platter(s) are meant to rotate anyway. I often hear disk recovery stories where the heads got affected first, so I would think of it as the weakest component, of course statistics might tell otherwise. That's as far as I've heard about it...

share|improve this answer
What are you talking about? Most of the BSODs I have seen did not shut anything down. There is one specific BSOD that is shutting down (only) the hard-drives. And once again, it is a software issue, not a hardware problem. – Synetech Apr 25 '12 at 3:13
@Synetech: BSODs were you can continue using your OS sound cool; but joking aside, this is a hardware problem because re-initialization is part of the firmware of the HDD, not part of the software installed on your computer. – Tom Wijsman Apr 25 '12 at 12:07
What are you talking about? There are different kinds of BSODs, some with more information, some with less. Most of the usual ones leave the drives spinning, and this one shuts them down. For the final time, this is not a hardware issue. I can reproduce it by using specific files in a specific folder. It is likely a driver or memory access issue (possibly due to DEP). – Synetech Apr 26 '12 at 0:50
Re-initialization is inevitable regardless BSOD unless you change the firmware of your hardware. – Tom Wijsman Apr 26 '12 at 5:53

Actually, the drive is stopped for all the OS is concerned. The Blue Screen you see is quite exceptional because the file system driver itself could be the cause of the stop error. Which is why the core dump is written to the root of the system drive.

For all intents and purposes, the OS has no other control.

The fans spinning, hardrive moving, lights flashing are controlled by your BIOS/Motherboard/Powersuppy, which are outside the control of your OS. For more support, you should ask them.

share|improve this answer
It’s not the file-system driver (I can semi-reliably reproduce it by using/running/manipulating a few of the ZIP files in a specific folder). It is interesting that you are indicating that the OS is not the one shutting the drives down, but I don’t see how the BIOS or drive controllers would be the one to do so. Both the IDE and SATA drives are shut down when it happens and there are no events logged or dumps generated. This did not start until a week ago, right after I deleted some of the MS MFC/CRT DLLs from System32 and moved them to a separate directory in the path. – Synetech Apr 25 '12 at 3:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.