
UNSOLVED
KA
Ken A. Dienne
74 Posts
0
6854
April 28th, 2008 00:00
Is doing a 'hard shutdown' during startup more dangerous than doing one from the desktop?
Hi:
I defragged my XPS 720 (Vista) today, and afterward, I tried to restart, but my system got hungup as it was starting up. I had to hold the power button and then restart. I'm just wondering: can this cause any serious damage? And should I do anything along the lines of damage control now? I got a message saying, 'Windows didn't start up last time, and now it's going to try to fix the problem ...' It also asked me if there was a power outage during startup, and if so, it told me to choose 'Load Windows Normally'. Anyway, I've never had to do a hard shutdown during bootup before, so I'm a bit worried about it.
Thanks!
Ken A. Dienne
Responses (15)
Solutions (0)
DELL-Chris M
Community Manager
•
56891 Posts
•
232143 Points
1552
0
Posted April 28th, 2008 03:00
HuttFuzz,
The thing it can do in the long run is make your HDDs explode(s).
* In 10 years of desktop support, I have never heard of this happening.
DELL-Chris M (old account)
#IWork4Dell
- By HDD exploding i meant doing a hard shutdown put unnecessary stress on your hard drive, which can cause a harddrive failure in the long run. People always shut down computers like that at my work place and we got an hard drive failure at least once a month. Anyways, it might be from other causes i guess, since no customer has ever changed an hard drive for that reason in the last 10 years..
Ken A. Dienne
74 Posts
1552
0
Posted April 28th, 2008 05:00
Thanks for all your input, guys! I've done a full disk-check, so I guess I'll try not to worry about it. While we're on the topic, has anyone else had a problem with hangups after defragging? It's happened to me twice now. :(
Ken A. Dienne
All,
Hard powering off a system CAN, in fact, generate a hard drive failure. If the hard drive is in the middle of a "write" operation when power is cut, then the block being written can be corrupted. This failure mode is called an "incomplete write" or "write splice". If the data written to that particular location was corrupted beyond the drive's error correction ability, it will be reported back as an "incorrectible" read failure during any diagnostic performing a full surface "read" test.
The only way to correct the situation after it occurs to perform a good "write" to the exact location. This removes the location from the "pending" defect list and will result in with PASS condition during any diagnostic performing a full surface "read" test.
It's usually this failure that will cause your system to generate "unmountable boot volume" after a hang condition, lock up or reset from within the operating system.
Message Edited by Ryanh6178 on 04-28-2008 02:38 PMMessage Edited by Ryanh6178 on 04-28-2008 02:39 PM

LupercalH
99 Posts
1552
0
Posted April 28th, 2008 02:00
I've done this lots of times on a lot of systems, especially when installing new hardware. Windows gives you boot options so you can go into safemode if Windows won't load for some reason. The only time it can cause problems is during a BIOS update.
Sometimes systems hang up on boot, it happens. Don't panic, power down, wait a few seconds, reboot and choose to let Windows load normally.