Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Windows Partition Gone


  • Please log in to reply

#1
Drumbum667

Drumbum667

    Member

  • Member
  • PipPipPip
  • 546 posts
So today I decided I was going to parition my computer to install Linux on the second partition. And when I restarted my comp it did the whole thing and then gave me an error. And Im getting a BSOD. This is the STOP Code: 0x00000024 (0x000190203, 0x84B10848, 0xc0000102, 0x00000000) I'm not totally sure about the number of zeros on all them because it flashes by fast. Also when I try to do a repair the Windows installation doesn't exist. It's just a partition. I dont mind totally wiping it as long as there's a way I can recover about 4 folders on my desktop that have some very vital information. I'd rather not wipe it . I was trying to recover it by using the Linux CD and now it says

mount: wrong fs type, bad option, bad superblock on /dev/hda1

missing codepage or other error

In some cases useful info is found in syslog - try

dmesg | tail or so

Edited by Drumbum667, 20 May 2007 - 03:36 PM.

  • 0

Advertisements


#2
Fenor

Fenor

    Trusted Tech

  • Retired Staff
  • 5,236 posts
Hi Drumbum667!

Do you have your windows XP CD? If you do, I want you to put it in and turn on your computer. When you are given the message press any key to boot from cd..., press a key and Windows Setup will start. At the first screen where you have to enter input, hit R to enter the Recovery Console. Then you will have to hit 1 to log into your windows installation and then just hit Enter for the Administrator password because it is normally blank unless you changed it. Once you are at the command prompt C:\WINDOWS I want you to type chkdsk /p /r. This will run a VERY THOROUGH check of both your hard drive and also your windows installation files and replace any that are missing/corrupt. Once it's done, type Exit and take out your Windows XP cd. Your computer will reboot itself.

NOTE: If you don't have your XP CD, you can download the Recovery Console ISO from HERE. You will need to burn that image onto a CD

Fenor
  • 0

#3
Drumbum667

Drumbum667

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 546 posts
I ran chkdsk /r because I had a revelation and remembered this happened to me before and I'm up and running. Lately I've become more and more self-sufficient on fixing my computer as well as others and it's all thanks to this site. Im downloading that ISO right now just encase Im trying to fix a comp and there is no XP CD to use. Thank you so much Fenor.
  • 0

#4
Fenor

Fenor

    Trusted Tech

  • Retired Staff
  • 5,236 posts
Glad I could help! :whistling:

Fenor
  • 0

#5
anzenketh

anzenketh

    BSOD Warrior/Computer Surgeon

  • Technician
  • 2,854 posts
Running a chkdsk /r may or may not fix your problem. (It is a great thing to do to attempt fix it though) To make sure it never happens again there are some windows tools that we can use to verify it is not a driver problem.

Blue screen error messages are one of the most misunderstood error messages out there in regards to windows.According to Microsoft, only 5-20% of these errors are actually caused by the OS. Only 10% are hardware related. The other 70% are the result of faulty drivers or software incompatibility. Based on those numbers, less than 15% of blue screen errors can be permanently resolved with an OS reinstall.

So we can correctly solve this issue we need to get the minidumps.

To get the Minidumps do the following

1 > create a new folder on the desktop and call it "dumpcheck" or whatever you like
2 > navigate to %systemroot%\minidump and copy the last few minidump files to that folder.%systemroot% is normally c:\windows. They are numbered by date. You can paste that address in address bar to get there.
3 > close the folder and right click on it and select Send to Compressed (zipped) Folder. Please do NOT compress them in .rar
4 > use the "add reply" option upload that zip file here as an attachment.


However at the same time there may be nothing wrong after running a chkdsk /r because it may have been a corrupted driver and chkdsk fixed it. There is a tool that we can use to make sure that is built into windows it is called the driver verifier but we need to check on what driver possible caused the issue if any.

Edited by tuxmaster, 21 May 2007 - 02:52 AM.

  • 0

#6
Drumbum667

Drumbum667

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 546 posts
When I went to the Minidump folder but there was nothing there.
  • 0

#7
anzenketh

anzenketh

    BSOD Warrior/Computer Surgeon

  • Technician
  • 2,854 posts
The minidumps are not created for all blue screen error message.

0x24: NTFS_FILE_SYSTEM
The NTFS_FILE_SYSTEM bug check has a value of 0x00000024. This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives.

chkdsk just might fix this blue screen error message as it is listed for a resolution.

From MSDN this is the resolution
Resolving the Problem

To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.

To resolve a nonpaged pool memory depletion problem: Either add new physical memory to the computer (thus increasing the quantity of nonpaged pool memory available to the kernel), or reduce the number of files on the Services for Macintosh (SFM) volume.

Go Ahead and download HDtune in my signature and run it not a quick check see if your hdd turns up all green.
  • 0

#8
Drumbum667

Drumbum667

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 546 posts
It came back perfect. All green.
  • 0

#9
anzenketh

anzenketh

    BSOD Warrior/Computer Surgeon

  • Technician
  • 2,854 posts
Sorry for the wait I just got promoted here and the logs are harder.

We want to run some memory tests

Get memory test programs

See if it comes up all A OK
  • 0

#10
Drumbum667

Drumbum667

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 546 posts
I wish I had time for the logs. Maybe I'll start from where I was in the summer. I already ran that a couple days ago when I installed new RAM came back perfectly.
  • 0

#11
anzenketh

anzenketh

    BSOD Warrior/Computer Surgeon

  • Technician
  • 2,854 posts
How much memory is in the system?

After running the chkdsk did the preformance improve?
Are you still getting blue screen error messages?
  • 0

#12
diabillic

diabillic

    Member 1K

  • Member
  • PipPipPipPip
  • 1,370 posts
It sounds to me like you didnt defrag your drive prior to partitioning it.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP