UNSOLVED
please helo ! dell 9100 getting BSOD and can't do anything
have a Dell dimension 9100 and just the other day when I turned on my computer I got this msg
A problem has occured error and Windows has been shut to down to prevent damage. If this is the first time seeing this message restart your computer. If you see this message again, take the following steps:
Disable/ uninstall any anti virus software, disk defragmentation or back up utilities. Check your hard drive configuration and check for any updated drivers. Run CHKDSK/F to check for hardrive corruption and restart your computer
Stop: 0x00000024 (0x00190203, 0x86597CAO, 0xc0000102, 0x00000000)
the problem is I cant even get past that screen, so I don;t know how I can do the things their telling me to do if I can't ever get past that screen, I've read something bout getting a tool to see if your harddrive is the problem but on dell it says my harddrive is a HARD DRIVE, 160GB, Serial ATA, 7.2K, 8MEGB, GENERIC, so I guess I can't do that ?, any help would be great guys thanks alot, preferablly a solution where I can keep the data I have on my comp.
684
0
Posted March 22nd, 2007 16:00
Reboot and press F12 before XP tries to load. Run the extended tests on the hard drive. Copy any error messages and contact Dell for replacement, if you're still under warranty.
If no error messages, boot from your XP Installation CD. You may have to change the boot sequence in BIOS (press F2 before XP tries to load) to put CD first in tbe boot sequence, and then follow the instructions here to attempt to repair the NTFS file system:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q228888
Ron
684
0
Posted March 23rd, 2007 02:00
hey guys thanks for all the replies, I'm bout to try them out, sorry I'm like computer so I was wondering how do I " Chkdsk /f /r " if all I get when I turn my computer on is the BSOD and it just sorta dies from there lol684
0
Posted March 23rd, 2007 02:00
If your hardware passes the extended tests, you can follow the steps from Microsoft by runing 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. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r
Message Edited by evhwolfgang on 03-22-2007 10:35 PM684
0
Posted March 23rd, 2007 02:00
These steps will allow you to run chkdsk and a few other DOS style tools. It will also get you to a place where you can install a backup of your registry if yours is corrupt (assuming there is a backup to be restored) if its needed. I hope chkdsk works for you, because that's pretty much all the microsoft support pages say to do.
To run the Recovery Console from the Windows XP startup disks or the Windows XP CD-ROM, follow these steps:
1. Insert the Windows XP CD-ROM into the CD-ROM drive, and then restart the computer. Watch the screen for a message that says "press any key to boot from CD". When you see this message, slap your keyboard immediatly. You don't have time to think about it because the message goes away and it will just go back to that error message. There's a slight possibility that you won't get this message and it will just boot the CD without bothering you about it. The goal is to get to a screen that says "welcome to setup". When you see that screen, that hard part is pretty much over.
2. When the "Welcome to Setup" screen appears, press R to start the Recovery Console.
3. If you have a dual-boot or multiple-boot computer, select the installation that you must access from the Recovery Console. (you can probably ignore this step)
4. When you are prompted, type the Administrator password. If the administrator password is blank, just press ENTER.
5. At the command prompt, type the appropriate commands to diagnose and repair your Windows XP installation. You'll be at the recovery console prompt at this point. It will look like the old DOS prompt: C:\>_ In your case, this is where you'll type chkdsk /f /r and pray.
For a list of commands that are available in Recovery Console, type recovery console commands or help at the command prompt, and then press ENTER.
For information about a specific command, type help commandname at the command prompt, and then press ENTER.
6. To exit the Recovery Console and restart the computer, type exit at the command prompt, and then press ENTER.
Message Edited by evhwolfgang on 03-22-2007 10:54 PM684
0
Posted March 24th, 2007 01:00
If KirkD's fix solves the problem, then I'd suspect that the battery on the motherboard is dying/dead and should be replaced (~$3.00)
Ron
684
0
Posted March 24th, 2007 01:00
Before you do somthing drastic, try to reset the BIOS by removing the CMOS battery. First remove UNPLUG the computer, then hold the power button in for about ten seconds to drain the power supply. Open up the tower and remove the button battery; note which side is up. Then hold in the power button for another ten seconds or so, and then replace the battery; make sure it's well seated. Put the cover back on, plug in and start the computer. After the boot page, you should see a page that says the BIOS is looking for drives, Wait a while; it may take several minutes for the detection to occur. Everything should be OK from this point. If this doesn't work, then try some of the other fixes. I have used this several times successfully, once with the ...0024 error.Dimension 9100, Win XP, 3.0 GHz P4, 2 GB DDR2 533 MHz RAM, 160 GB SATA II Samsung, 300 GB SATA II Seagate, 250 GB SimpleTech USB (WD Drive), Nvidia Go 6800 (425/825 MHz), Dell 1901 FP UltraSharp
Inspiron E1705, Win Vista Premium, T7200 Core 2 Duo (4MB, 2.0 GHz 667MHz), 1 GB DDR2 677 MHz RAM, 2 GB Transcend 150X SD RamBoost, 120 GB Samsung HD, Nvidia Go 7900 GS, 17” Sharp UltraSharp TrueLife Wide-Screen WUXGA684
0
Posted March 24th, 2007 02:00
Acually not. I had installed a new battery because of BSOD problems and it didn't help. The crash with ...0024 error came out of the blue (no pun). Usually get BSOD only when new (problematic) software is added. Most recent software problem was conflict betwee System Mechanic and Zone Alarm Firewall.This is an interesting fix, as if you are impatient and don't wait for the BIOS to slowly do the drive identification, you will probably re-boot too soon. After a re-boot, there will still be a long wait, but you won't see the drive ident info.684
0
Posted March 24th, 2007 04:00
I don't know how drastic running chkdsk is, but that's the recommended first step from Microsoft KB, but the BIOS detection trick may work too. Please be careful if you don't have a lot of experience working inside the physical computer. Honestly, chkdsk or the dell diag tools should be the first troubleshooting steps. They don't risk lost screws and static discharges.
Message Edited by evhwolfgang on 03-24-2007 12:23 AM339
0
Posted March 24th, 2007 12:00
you don't even need to touch the battery to kill the power coming from it. there's a jumper on the motherboard that resets the bios. it does the samething as removing the battery. the reason they put that jumper on motherboards is because those batteries are sensitive. look for the reset bios jumper when you need to erase your bios.
jeffro04
57 Posts
684
0
Posted March 22nd, 2007 12:00