a PC with XP, PQmagic partition RESIZED, and now XP will not boot STOP

[martin55555]

hy there PPL

so, my great problem is the following:

There is a PC, 40 gig HDD, running XP SP2 all fine.

I had to backup the PC, so I decided to RESIZE the 40 GB only partition to 2 smaller 20-20 gig, (the XP and programs were 8 gig so this should be ok) (I wanted to GHOST the first partition to the second)

after resizing with Powerquest PQmagic 8, the PC will not boot any more, STOP error occurs.

is there a way I can fix this?

CHEERS and many thanks if someone could help me !

Martin from Hungary.

 

[erikhertzel]

What is your STOP error code?

Erik

 

[martin55555]

the STOP error is this:

http://www.martin555.dyndns.org/STOP_error.JPG

update to the error problem: DURING the partition RESIZE in PQ magic 8, pqmagic had a problem , I can not exactly remember " error copying " or something. so the partition resize process was not really complete.

Do I have some chance ? like FILE SCAVENGER or ONTRACK easyrecovery or GETDATABACK for NTFS only like this?



thanks for everything you can help!

 

[TheLad]

Well if all else fails, you can slave the hard disk into another machine to get your data back.

Can you boot into the Recovery Console and run a CHKDSK /F on the C:? I am presuming the Bluescreen error suggests that although I am not familiar with your language

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[bcastner]

http://support.microsoft.com/?kbid=228888&sd=RMVP

 

[martin55555]

Stop 0x00000024 or NTFS_FILE_SYSTEM

This Stop message, also known as Stop 0x24, indicates that a problem occurred within Ntfs.sys, which is the driver file that allows the system to read and write to NTFS volumes.


--says Microsoft. Now, how do I start repairing this? assuming, file system is OK?

 

[erikhertzel]

There is good info. on this:

The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.

Possible Resolutions:

Malfunctioning SCSI and Advanced Technology Attachment (ATA) hardware or drivers can also adversely affect the system's ability to read and write to disk, causing errors. If using SCSI hard disks, check for cabling and termination problems between the SCSI controller and the disks. Periodically check Event Viewer for error messages related to SCSI or FASTFAT in the System log or Autochk in the Application log.
Verify that the tools you use to continually monitor your system, such as virus scanners, backup programs, or disk defragmenters are compatible with Windows XP. Some disks and adapters come packaged with diagnostic software that you can use to run hardware tests.
To test hard disk or volume integrity

Method 1:

In the Run dialog box, in the Open box type:
cmd

Start the Chkdsk tool, which detects and attempts to resolve file system structural corruption. At the command prompt type:
chkdsk drive: /f

Method 2:

Double-click My Computer, and then select the hard disk you want to check.
On the File menu, click Properties.
Click the Tools tab.
In the Error-checking box, click Check Now.
In Check disk options, select the Scan for and attempt recovery of bad sectors check box. You can also select the Automatically fix file system errors check box.
If the volume you are checking is in use, a message asks whether you want to delay disk error checking until the next time you restart your computer. After you restart, disk error checking runs and the volume chosen is not available to run other tasks during this process. If you cannot restart the computer due to the error, use safe mode or Recovery Console.

If you are not using the NTFS file system, and the system partition is formatted with the file allocation table (FAT16 or FAT32) file system, long file name (LFN) information can be lost if hard disk tools are started from an MS-DOS command prompt. A command prompt appears when using a startup floppy disk or when using the command prompt startup option on multiple boot systems that use FAT16 or FAT32 partitions with Microsoft® Windows® 95 OEM Service Release 2 (OSR2), Microsoft® Windows® 98, or Microsoft® Windows® Millennium Edition (Me) installed. Do not use tools meant for other operating systems on Windows XP partitions!

Nonpaged pool memory might be depleted, which can cause the system to stop. You can resolve this situation by adding more RAM, which increases the quantity of nonpaged pool memory available to the kernel.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q312582

 

[linney]

Does "PQ magic 8" have an Undo or Rescue Disk or similar?

HOW TO: Install and Use the Recovery Console for Windows XP (Q307654)

http://support.microsoft.com/support/kb/articles/q307/6/54.asp

Try the ChkDsk /r, look at FixBoot and FixMbr too.



You might be able to make use of BartPE (a mini XP self contained on a bootable CD and run from CD).

http://www.nu2.nu/pebuilder/

The same might be possible with a parallel install of XP.

266465 - HOW TO: Perform a Parallel Installation of Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;266465&FR=1&PA=1&SD=HSCH

You can do the same with XP. Don't install any unnecessary programs just some virus scanners, keep the parallel installation as simple as possible.

Or the paragraph in this article.

"To install Windows XP to a new folder (to perform a parallel installation):"

How to install or upgrade to Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;316941&FR=1&PA=1&SD=HSCH

If it all gets too much there is always repairing windows by running it over itself. You will lose all your windows updates (no problem if you substitute them with SP2) but your files and programs will be untouched.

How to Perform an In-Place Upgrade (Reinstallation) of Windows XP (Q315341)

http://support.microsoft.com/support/kb/articles/q315/3/41.asp

HOW TO: Take Ownership of a File or Folder in Windows XP (Q308421)

http://support.microsoft.com/support/kb/articles/q308/4/21.asp

Data recovery.
PC Inspector

http://www.pcinspector.de/file_recovery/UK/welcome.htm

 

[martin55555]

people !!!!!!!!!!!!

I simply can not believe this. I got EVERYTHING back.

so this thread can be closed now.

the trick:

DO NOT ATTEMPT to do ANYTHING with the disk which will cause a WRITE command. NO recovery console, no reinstall, NOTHING.

google for this : FILE SCAVENGER, or other tool: Ontrack EASYRECOVERY or GETDATABACK for NTFS.

with this tools, with the simpliest "quick" search you can access ALL your lost files which are not overwritten. EVEN ON RAID ARRAYS, TOO!! (rebuild, etc)

so, you install one of this proggys on a GOOD WORKING test PC or service PC, plug the BAD HDD as secondary, GET ALL FILES as a copy back, (partition image would be better: you erase the old bad HDD, and from the image you reistall)

ok then: you have at least a FILE COPY from everything. then:

http://www.ptdd.com/

go for the Partition Table Doctor.

launch the auto repair: reboot the old , bad HDD in its own PC environment, and there you go. if the problem was SOFTWARE-caused, I believe 90 % can be solved like this (PQmagic partition resize , sudden power off, etc)

I am really happy now.

cheers.

 

[trojanman]

You should at least thank everyone for their suggestions...

 

[martin55555]

of course, thanks to everyone for the effort and suggestions..