i cant boot my work computer anymore it shows the windows boot screen and starts to load and then i get a BSOD with these: 0x00000024 (0x00190203, 0x8242F8B0, 0xc0000102, 0x00000000) i tried to use the repair on the win xp cd but it says it has not detected any hard drives. help?
Sounds like your HDD has Died... You can try it on another computer and that will tell you for sure. 2oG
i used hd tool on hirrens boot cd and scanned the hd and it had no bad sectors, so i dont think its the hd, i was able to use the computer earlier today and then it started to get a the bsod
Switch cables with known working ones other than that perhaps the controller on the mobo is shot,using a linux live cd should at least tell you everything else works apart from the hdd side of things
the cables are all connected and secure, i ran a Linux distro from a cd and it all works and i can explore the hd with it, i think the MBR is the problem but don't know how to fix it. I think what caused the problem is that before i got the BSOD my computer froze and i had to manually turn it off with the power button and then i just try to boot windows and when it starts to load i get the BSOD.
In order to repair the MBR you must be able to go to the recovery consol. If your XP disk can’t find the drives, then I’m lost…… : ( Here is a guide for repairing the MBR: http://helpdeskgeek.com/how-to/fix-mbr-xp-vista/ p.s That's why I use Acronis TrueImage to maintain an Image of my drive. I can repair the MBR or replace the entire drive in less that 5 minutes..
Ultimate boot cd maybe able to help http://www.ultimatebootcd.com/ I doubt it's the mbr,that error will bring up no disk or some other black boot screen,bsods are serious flaws in hardware more usually associated with drivers however software conflicts can cause it also.
Hey all Uh oh... this has absolutely nothing to do with the MBR. If I'm not wrong, this is a corruption of the ntfs.sys driver, which corrupts the entire file system. Even the windows installation cd would not work in this case (which explains your problem), since it wouldn't recognize the hard disk at all. One thing to try would be to extract the hard disk from the computer, copy the data out, and then run a chkdsk on the bad hard drive. More hard-core hard drive regenerator programs such as Spinrite might be needed. There's a good possibility that this will repair the disk, but depending on the level of corruption, the worst case scenario will call for a low-level format of the disk before it can work again. Best Regards
Remove the hard dive from the comp & either put it into another comp as a slave or put it in an external hdd housing,this assumes it gets detected,then open my computer,right click on faulty hdd icon ,left clik & hit properties,tools tab,hit check now button,select both boxes & run it,hopefully it will work if not you'll need a install disc & acronis or ghost imaging software,my advice get 1 more internal drive & 2 externals,clone the internal then unplug it,use the 2 externals for images if the externals are large enough you can image other computers as well,reason unplug internally cloned drive is in case of spike or whatever,dual sets of images in case 1 ext hdd fails,obviously i manually make images instead of scheduled EDIT: Forgot to mention use the link below for any issues you have with cloning they'll be best to assist as they specialize in it,advice is free http://radified.com/cgi-bin/yabb2/YaBB.pl
ok thanks i put the hd in another computer and checked for errors like you said and it all worked and it booted, but then i started to scan the computer for viruses and on the second scan it got a BSOD with: KERNEL_STACK_INPAGE_ERROR 0x00000077 (0x00000001, 0x00000000, 0x00000000, 0xF8A58D24) ?
The numbers will lead you to the cause however from my experience it becomes real technical i usually reformat assuming it ain't a hardware thing,you can run chkdsk/r from the install cd by selecting repair & use the command line as well http://searchwinit.techtarget.com/tip/0,289483,sid1_gci841587,00.html http://support.microsoft.com/kb/315266
Hey ricky... This issue can occur if a requested page of kernel data could not be read from the paging file into memory, or the master boot record is infected with a virus. Try the instructions on this page: http://support.microsoft.com/kb/315266 Best Regards
