N
Nick
Help on a BSOD would be very much appreciated...
I am running Win2k SP4, and just decided to shrink my main partition
from 120GB to 110GB so that I could fiddle about with linux. To do
this, I used Partition Magic 7.0.
As expected, Partition magic required a reboot to carry this out.
After the reboot, I got the first strangeness, Windows couldn't find
my profile, and said it was creating a new profile.
I rebooted again, and this time I got a BSOD
(INACCESSIBLE_BOOT_DEVICE) just after the Windows loading screen
appeared. Unfortunately, this was repeatable.
I've tried the following with partial success and managed to get
Windows back again, but can't seem to find a permenant solution:
1. Re-boot using the Last Known Configuration.
THIS WORKS, Windows seems OK, and I don't seem to have lost
anything... But when I reboot again using the default configuration, I
get the same old BSOD. I'm pretty sure that it is not a driver issue
on boot-up. Could it be that the LKC changes the start of the Windows
boot process?
2. Using the recovery console.
I've tried using my Emergency Repair Disk (which I created just before
resizing the partition). This makes no difference. Still a BSOD.
CHKDSK can't find anything wrong.
I've also used FIXBOOT and FIXMBR. No help either.
3. Using Partition magic rescue diskettes.
PM can't find anything wrong with the partition.
My system config:
Asrock K78SX (Motherboard)
Athlon 2GHz
256MB RAM
IBM IC5L1200AW207 (120MB IDE HDD) Primary
IBM IC35L090AW207 (80MB IDE HDD) Slave. Just data storage
Asus AGP-V9520 (Graphics)
I don't suppose that it has anything to do with the 1024 cylinder
limit for a bootable drive. I thought that this had been fixed for
Win2k.
Any ideas would be very gratefully received or else I suppose it's a
reinstall (and I'd just got everything working except for the
DirectX-3d, but that's another story...)
Thanks,
Nick
I am running Win2k SP4, and just decided to shrink my main partition
from 120GB to 110GB so that I could fiddle about with linux. To do
this, I used Partition Magic 7.0.
As expected, Partition magic required a reboot to carry this out.
After the reboot, I got the first strangeness, Windows couldn't find
my profile, and said it was creating a new profile.
I rebooted again, and this time I got a BSOD
(INACCESSIBLE_BOOT_DEVICE) just after the Windows loading screen
appeared. Unfortunately, this was repeatable.
I've tried the following with partial success and managed to get
Windows back again, but can't seem to find a permenant solution:
1. Re-boot using the Last Known Configuration.
THIS WORKS, Windows seems OK, and I don't seem to have lost
anything... But when I reboot again using the default configuration, I
get the same old BSOD. I'm pretty sure that it is not a driver issue
on boot-up. Could it be that the LKC changes the start of the Windows
boot process?
2. Using the recovery console.
I've tried using my Emergency Repair Disk (which I created just before
resizing the partition). This makes no difference. Still a BSOD.
CHKDSK can't find anything wrong.
I've also used FIXBOOT and FIXMBR. No help either.
3. Using Partition magic rescue diskettes.
PM can't find anything wrong with the partition.
My system config:
Asrock K78SX (Motherboard)
Athlon 2GHz
256MB RAM
IBM IC5L1200AW207 (120MB IDE HDD) Primary
IBM IC35L090AW207 (80MB IDE HDD) Slave. Just data storage
Asus AGP-V9520 (Graphics)
I don't suppose that it has anything to do with the 1024 cylinder
limit for a bootable drive. I thought that this had been fixed for
Win2k.
Any ideas would be very gratefully received or else I suppose it's a
reinstall (and I'd just got everything working except for the
DirectX-3d, but that's another story...)
Thanks,
Nick