BSoD on startup after partition juggling
Today I adjusted the Windows 7 Partition to give it more space. After this, I had bootloader issues, so I had to flag the partition as boot. This is the only flag on this partition at the moment. I used the 7 DVD to automatically fix the boot record and restarted. I got to the login screen and when I entered the password the system BSoDs. It reboots and I hit restart normally and it bluescreens immediatly. It reboots again, and both options, Startup Repair and Start Normally cause a bluescreen. I tried running the DVD again, but it also causes a bluescreen. All of them have no filename on the error screen, just the BSoD error message.
March 24th, 2009 12:40am

What error message shows up on the screen?- John
Free Windows Admin Tool Kit Click here and download it now
March 24th, 2009 1:44am

What tool did you use to adjust your Windows 7 partition?
March 24th, 2009 2:46am

STOP:0x00000024(0x000C22D2,0x00000010,0x00000000,0x00000000)When I run the Startup Repair option, it gives the standard "Problem has been detected, restart, disable antivirus, try CHKDSK, check hard drive configuration" message and then gives the technical information shown above. I'm pretty sure that the error is the same for all the other options I have seen.
Free Windows Admin Tool Kit Click here and download it now
March 24th, 2009 2:51am

DarienHawk67 said:What tool did you use to adjust your Windows 7 partition?I used the Gparted live cd.I also used it to move around partitions on a previous 7 install and I just had to restore the bootloaders.
March 24th, 2009 2:52am

GParted is great for uses prior a Windows 7 installation. This is not a solution to you present problem, but you may want to use the built-in functionality that is native to Windows Vista/7 to extend an existing partition. This way, you reduce the possibility of ending up in a situation similar to yours. The real question now is what to do now to get your system booting normally. Try this. If possible, boot with the DVD. At the first screen, hit <shift><f10> to enter the WinPE environment. Normally, you will see x:\sources> as the prompt. Type c: to get to the WinPE c drive. Do a dir command to list the contents. If you DO NOT SEE a windows folder, type d: to get the WindPE d drive. Again do a dir. On whatever drive letter you see your Windows installation is where you will want to run your chkdsk. Dont worry if the drive letters dont match what you used to actually see in Windows 7. The important thing is that you see the folders PerLogs, Program Files, Users, and Windows. If you did a clean install of Windows 7 allowing it to do its defaults, normally, your Windows installation will be on the d drive while in the WinPE environment. Now, use chkdsk to check your volume. Ex, chkdsk d: /F Let us know what happens.
Free Windows Admin Tool Kit Click here and download it now
March 24th, 2009 3:31am

7 DVD still bluescreens, I can try checks from a linux live cd.The problems with the DVD seem to suggest some sort of hardware problem.
March 24th, 2009 11:59pm

After using ntfsfix in Linux, the system got further along in the boot process before bluescreening but the filesystem seems to be accessable from linux. I'm thinking the best option at this point is to copy all the data off the drive and reinstall Windows. Do the 7 backup features help with restoring from this kind of backup?
Free Windows Admin Tool Kit Click here and download it now
March 25th, 2009 1:21am

If you boot from a Linux disk and are able to access and copy your files, you should be good to go with a clean installation of Windows 7. Just make sure that when you copy your files from the botched Windows installation, you copy them to another NTFS or FAT32 formatted disk. Do not use a disk that is formatted with ext3, ZFS, RiserFS, or any other format that Linux recognizes. If you copy your files to an external, FAT32 disk (do be aware that FAT32 does not support files sizes over 2GB) or NTFS disk, you can easily reload Windows 7 and then recopy the files back.
March 25th, 2009 3:01am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics