KMODE_EXCEPTION_NOT_HANDLED after re-lettering system drive
Posted on 2004-04-24
Windows NT 4.0 Server SP6
I was trying to replace a flaky system drive by installing a new empty drive, establishing mirrors for the two partitions on it (C: and D:), waiting for it to sync up, breaking the mirror, and re-lettering the partitions.
I was able to complete most of this but after I broke the mirror and tried to change the old C: to something else so I could change the new partition to C: I was forced to reboot. On reboot I now get a BSOD before the login prompt appears:
STOP 0x0000001E (0xC0000005, 0xA0042EE9, 0x00000000, 0x00000004)
Address A0042EE9 has base at A0000000 win32k.sys
Irql: 1E sysver: F0000565
Right now I’ve got: a “bootable” F: on disk 0 and “bootable” G: on disk 2; D: is a mirrored data partition on disks 0 and 2; disk 1 is a RAID5 array full of data that has been untouched.
Things I’ve tried so far:
Created a boot floppy with a boot.ini that lets me boot from either F: or D: – same results
VGA mode for both bootable partitions – same results
Parallel NT install on F: (seen as C: on boot). It boots and lets me get to all the partitions except the mirrored one. I did this to replace pcAnywhere’s awgina.dll with msgina.dll – same results.
From the parallel install: CHKDSK /R on all partitions – no errors – same results
Removed the paging file on all partitions - complains about it missing and - same results
Re-seated all SCSI connectors - no help
Re-seated all memory and ran MEMTEST from CD - no errors - no help
I’m thinking there’s some app or driver that really needs to be on, or at least see, a partition lettered C: and if I could change one of the bootable partitions back to C: I’d be in business. But HOW can I do this? Maybe that's not the problem at all?