BSOD after attempting to increase size of C drive partition

[Roger Fink]

I think I really may have stepped in it here. Tonight I tried to increase
the size of my C drive partition on my desktop from 40gb to 80gb using
Partition Magic. C is the only partition, the other 40gb was unallocated,
the drive is an 80gb Maxtor 7200 IDE (not sure of the correct description
but it's not a SATA drive). The boot went past the Windows spalsh screen but
after that to BSOD. Not connected to the Internet, antivirus was disabled,
GoBack was turned off, and the Partition Magic screen progress messages
during the operation seemed normal. Here is the BSOD message, which
reappeared after rebooting as well:

<STOP (lots of numbers)

Inacessible boot device.

If this is the first time you've seen this error screen, restart your
computer.If this screen appears again, folloew these steps.

Check for viruses on your computer. Remove any newly installed hard drives
or hard drive controllers. Check your hard drive to make sure it is properly
configured and terminated. Run CHKDSK /F to check for hard drive corruption
and then restart your computer.

Refer to your Getting Started manual for more information on troubleshooting
STOP errors.>

FWIW, I'd just done a thorough AV scan.

This may be more than I can fix myself, but the place to find that out is
here.

 

[John John - MVP]

I think I really may have stepped in it here. Tonight I tried to increase
the size of my C drive partition on my desktop from 40gb to 80gb using
Partition Magic. C is the only partition, the other 40gb was unallocated,
the drive is an 80gb Maxtor 7200 IDE (not sure of the correct description
but it's not a SATA drive). The boot went past the Windows spalsh screen but
after that to BSOD. Not connected to the Internet, antivirus was disabled,
GoBack was turned off, and the Partition Magic screen progress messages
during the operation seemed normal. Here is the BSOD message, which
reappeared after rebooting as well:

<STOP (lots of numbers)

Those "(lots of numbers)" are the most important part of the error
message! I'm guessing that it's an 0x7b error but it would be better if
we had the numbers.

Had you uninstalled GoBack before doing the partition resizing?
Certainly you had made a proper backup or image of the drive before you
attempted to resize the partition? Can the Partition Magic utility undo
the partitioning job?

You can try booting to the Recovery Console and running the Chkdsk /r
and Fixboot commands but to tell you the truth a botched up partition
job on a disk with a GoBack MBR is bad news!

John

 

[John John - MVP]

I think I really may have stepped in it here. Tonight I tried to increase
the size of my C drive partition on my desktop from 40gb to 80gb using
Partition Magic. C is the only partition, the other 40gb was unallocated,
the drive is an 80gb Maxtor 7200 IDE (not sure of the correct description
but it's not a SATA drive). The boot went past the Windows spalsh screen but
after that to BSOD. Not connected to the Internet, antivirus was disabled,
GoBack was turned off, and the Partition Magic screen progress messages
during the operation seemed normal. Here is the BSOD message, which
reappeared after rebooting as well:

<STOP (lots of numbers)

Those "(lots of numbers)" are the most important part of the error
message! I'm guessing that it's an 0x7b error but it would be better if
we had the numbers.

Had you uninstalled GoBack before doing the partition resizing?
Certainly you had made a proper backup or image of the drive before you
attempted to resize the partition? Can the Partition Magic utility undo
the partitioning job?

You can try booting to the Recovery Console and running the Chkdsk /r
and Fixboot commands but to tell you the truth a botched up partition
job on a disk with a GoBack MBR is bad news!

John

 

[Roger Fink]

Those "(lots of numbers)" are the most important part of the error
message! I'm guessing that it's an 0x7b error but it would be better
if we had the numbers.

Had you uninstalled GoBack before doing the partition resizing?
Certainly you had made a proper backup or image of the drive before
you attempted to resize the partition? Can the Partition Magic
utility undo the partitioning job?

You can try booting to the Recovery Console and running the Chkdsk /r
and Fixboot commands but to tell you the truth a botched up partition
job on a disk with a GoBack MBR is bad news!

John

Thanks John, sorry it took so long to reply to this – they had me under
sedation. Here are the error numbers:

<STOP: 0X0000007B (0XF681B84C, 0XC000000E, 0X00000000, 0X0000000).
Inaccessible boot device...>

I’m afraid I have to walk under the picture of Chairman Mao (Gates?) on this
one. I’ve done this procedure with no problem 4 or 5 times, which means I
uninstalled GoBack 4 or 5 times (rather than merely disable it). Some people
get wiser as they get older, but not everyone.

I did do a back up all my data including email to an external drive a few
days earlier, so I didn’t really lose anything to speak of. And I keep a
laptop around with the same programs installed and configured as in the
desktop. The laptop is the performance equal of (or better than) the desktop
in every way except probably longevity, and it doesn’t sound like a power
plant either. So with my old keyboard and monitor hooked up to it I’d say I
got off fairly lucky, but I'd still rather fall victim to events beyond my
control rather than ones I could control but didn't.

I’d consider trying to have it fixed rather than me wiping the drive if
there is a decent chance to salvage what’s there, but out of commission at
the moment. So any opinions on that would be appreciated.

Totally OT, but the dates in the laptop (for instance in Explorer and Tbird)
are configured backwards from what I’m used to and prefer. The Help file
shows how to change this so I went into Regional Options to change it but
the date configuration was shown exactly backwards (06/28/2009) from what
was appearing on the screen (28/06/2009). When I changed the configuration
to 28/06/2009 everything on the machine then read 06/28/2009, so problem
solved.

 

[JM]

I experienced this some years ago. It seems as NT systems don't like
partition size changes. I adjusted the size of the partition, and it would
boot once, then the second boot would be the bsod. Adjusting the partition
slightly (with another machine) it would boot once more. I ended up backing
up and did a in place reinstall was the only way I could get it to not bsod.

 

[Pegasus [MVP]]

I experienced this some years ago. It seems as NT systems don't like
partition size changes. I adjusted the size of the partition, and it
would
boot once, then the second boot would be the bsod. Adjusting the
partition
slightly (with another machine) it would boot once more. I ended up
backing
up and did a in place reinstall was the only way I could get it to not
bsod.

I have gone through numerous partition size changes, mostly without any
problems. In the case reported by the OP, Partition Magic may have damaged
something. This is why I usually create an image before I change the
partition size. It takes some time but it's the safe way to go.