Question:
Computer experts help please. :)?
Laura
2009-02-12 07:54:39 UTC
Right this might be a little long so sorry if it is.

right this Morning i started up my computer and on the windows xp login thing, I have 2 accounts, So anyway i accidentally clicked on the wrong one and then realizing my mistake i clicked switch user quickly before it could load any more. So it logs off while making a lot of noises, Then i try and logon to my account on the computer but it only comes up with the wallpaper of the other account then goes back to the login screen

So i turn it off using the power button, And i try turning it back on but then it comes up with this blue screen which says

A problem has been detected and windows has shut down to prevent any other problems to your computer
If this is the first time you have seen the stop error screen on your computer, Restart your Computer, If it is not the first time then follow this steps

then it says all these really complicated things to do

Technical Information
***STOP: 0x00000024 (0x00190203, 0x8A8ACA70, 0x0000101, 0x00000000)

Right so then it just stays on that screen, Then i turn it off manually then it comes up with start Windows normally or in safe mode. So what do i do!!
If you need more information then i can give it to you, But i cant be bothered to type it all out :L
Thanks
Thirteen answers:
☆Star12☆
2009-02-12 08:24:54 UTC
Okay, i get this same blue screen a lot, but not when doing wat u done, mine does that sometimes wen im on the internet. Copy down the technical information somewhere. Start windows normally, and if the blue screen keeps coming up, you'll have to ring up where u got the pc from for advice or do a complete recovery, a complete recovery should be the very last option, i say this because, doing a complete recovery takes your computer back to the state it was when bought - brand new. This means u will lose everything - downloads, pictures, music etc. You will not be able to get any of this back, so i advise you to back everything up onto a CD before doing this. May i remind u, u will lose EVERYTHING, so be sure before doing it. (e.g: if u bought ur computer fixed with thr old msn, and u downloaded the new windows live messenger, it will be gone and the old msn will be there OR if u had old internet and u downloaded internet explorer 7, explorer 7 will not be on ur pc but the old internet will. To do this, when u turn ur computer on, straight away press F11 on ur keyboard, follow the instructions from there. The other option is a system recovery, which takes your computer back to a certain date u choose, for example if u choose yesterday, u will not lose anything, apart from anything u downloaded/saved yesterday or today. This can be found on the start menu, all programs, Accessories, system tools, then system restore. I remind u, u can take ur pc back to any date, so if u downloaded something 3 days ago, but u take ur pc back to 2 days ago, the thing u downloaded will still be there. Good luck! = )
Lbrown
2009-02-14 01:07:51 UTC
Can you post the exact error message?

That would help to recommend the proper solution...



For example is it the SYSTEM registry file or hive file that is corrupt



If it was the following procedure would be the proper fix:

SYSTEM is one of your registry files which Windows needs to start.



Your personal folders such as (pictures, documents etc) should be okay as long as you do not reformat the hard-drive and as long as this error is not a hard-drive hardware error.



Worst case you would need to remove the hard-drive and either put in an external usb kit and attach to a second computer or attach as a second drive to a different computer.

This is a safety precaution to ensure that your critical files are safe.



Next depending on the registry file error or other BSOD error do a Google search to determine the appropriate recovery option.



Most likely you will have to reboot from the install disks and get into the recovery console to either run chkdsk or copy backup registry files into their proper location.



Then after reboot do a system restore to get the computer back to a current state.



There is much good documentation out on the web on this but all steps must be done in order and very carefully.



Post back if more assistance is required.
Tony B
2009-02-12 08:27:54 UTC
Can you post the exact error message?

That would help to recommend the proper solution...



For example is it the SYSTEM registry file or hive file that is corrupt



If it was the following procedure would be the proper fix:

SYSTEM is one of your registry files which Windows needs to start.



Your personal folders such as (pictures, documents etc) should be okay as long as you do not reformat the hard-drive and as long as this error is not a hard-drive hardware error.



Worst case you would need to remove the hard-drive and either put in an external usb kit and attach to a second computer or attach as a second drive to a different computer.

This is a safety precaution to ensure that your critical files are safe.



Next depending on the registry file error or other BSOD error do a Google search to determine the appropriate recovery option.



Most likely you will have to reboot from the install disks and get into the recovery console to either run chkdsk or copy backup registry files into their proper location.



Then after reboot do a system restore to get the computer back to a current state.



There is much good documentation out on the web on this but all steps must be done in order and very carefully.



Post back if more assistance is required.
brianthesnail123
2009-02-12 08:38:31 UTC
hi laura

this is a common problem and the blue screen (blue screen of death) indicates a specific problem with your pc or the software installed on it

however your screen information points towards a problem with the n.t.f.s file system,to be more specific "This Stop error indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to drives formatted with the NTFS file system. (A similar Stop message, 0x00000023, exists for the file allocation table [FAT16 or FAT32)] file systems.)

to resolve this problem try this :

Interpret the error message. The stop error is followed by four parameters defined in order of appearance:

Source file and line number.

Optionally contains the address of the exception record.

Optionally contains the address of the context record.

Optionally contains the address where the original exception occurred.

All stop errors due to problems with NTFS or FAT have encoded in their first parameter the source file and the line number within the source file that generated the stop error. The high 16 bits (the first four hexadecimal digits after 0x) identify the source file number, and the lower 16 bits (the last four hexadecimal digits of the parameter) identify the source line in the file where the stop occurred.

Check Event Viewer for error messages from SCSI, FASTFAT (the System Log), or Autochk (the Application Log) that might help determine the device or driver that is causing the error.

Try disabling any virus scanning programs, backup programs, or disk defragmenter tools that constantly monitor your computer, and if possible, run hardware diagnostics tools supplied by your computer manufacturer.

Run chkdsk /r to detect and resolve any file system structural damage.

Depletion of non-paged pool memory can cause this issue. If you create a Services for Macintosh (SFM) volume on a large partition (7 gigabytes or larger) with a large number of files (at least 100,000) while the AppleTalk driver Apf.sys is running, the indexing routine consumes a large amount of non-paged pool memory. If the non-paged pool memory is completely depleted, this error can cause your computer to stop responding (hang). However, if the amount of available non-paged pool memory is very low during the indexing process, another kernel-mode driver requiring non-paged pool memory can also cause this issue. To resolve this issue, increase the amount of installed RAM to increase the quantity of non-paged pool memory available to the kernel, or reduce the number of files on the SFM volume.

however if your pc is using the fat32.fat(file allocation table) file system you need to do the following :

Make sure the drive that contains the corrupted NTFS volume is disconnected, and then start Windows by using Safe mode.

Rename the %SystemRoot%\System32\Drivers\Ntfs.sys file to Ntfs.old, and then shut down the computer (this action prevents the Ntfs.sys driver from loading).

Reconnect the drive that contains the corrupted NTFS volume.

Restart the computer, and then run the following command on the corrupted NTFS volume:

chkdsk driveletter: /f

NOTE: The Chkdsk tool has built-in support for NTFS and does not require the Ntfs.sys driver to make repairs.

After you use the Chkdsk tool to repair the corrupted NTFS volume, rename %SystemRoot%\System32\Drivers\Ntfs.old to Ntfs.sys, and then shut down and restart the computer.

give these a go and if you experience any problems let me know,there may be another solution to this

good luck laura !
steve_loir
2009-02-12 08:15:21 UTC
Yeah, try in Safe Mode and a System Restore.

If that doesn't work then boot with the XP (or Vista) CD and choose Repair.



Next time!

Do not switch your PC off with the power button. Wait!

Once it has settled down then see if you can do a proper Shutdown. Try and pick Shutdown and Turnoff.



If you power down your PC while it is writing to the hard disk it will often mess up the hard disk so it won't boot.
swirly s
2009-02-12 08:05:18 UTC
What the hell does leaving the cord out for 8 hours do? And don't buy a Mac cause some fanboy tells you to. Try everything else he said, minus the 8 hours stuff. Also try the option to start with last known good configurations.
2009-02-12 07:59:42 UTC
start windows normally. If it does, end of story. If it doesn't, come back for further advice.



start in safe mode then. If it starts, end of story. if it doesn't, come back for further advice.



Could be anything depending on the text on the blue screen, but reinstall windows is a possible solution. You do have a backup of your data don't you?
GÅÑDÅLƒ
2009-02-12 08:13:54 UTC
0x00000024 is usually caused by a corrupt registry entry try booting from last known good configuration



i have no idea what upluging the pc for 8 hours would achieve that's a new one on me...
2009-02-12 08:01:26 UTC
unplug the power cord and leave it for about 8 hours or so and then try rebooting and loging in

if that doesn't work then try running in safemode and using system restore to the day before everything happened

if that doesn't work then try removing that circular battery on your motherboard after unplugging your pc and then leaving it for about 8 hours again and replacing the battery and rebooting

if that doesn't work call a computer tech and buy a mac =/
2009-02-12 08:01:00 UTC
I have never experienced this before with any computer, you should have been able to switch users, and login to your own account.



START WINDOWS NORMALLY IF IT DOSENT WORK, THEN I THINK YOUR ONLY SOLUTION WOULD BE TO RESTALL WINDOWS XP
?
2009-02-12 08:10:37 UTC
just choose the start windows normally option.

and next time, take a little more time and care when logging in to your account. good luck
bonneville
2009-02-12 07:58:36 UTC
start windows normally
Surfing Smurf
2009-02-12 08:43:36 UTC
Thats why i have an iMAC.


This content was originally posted on Y! Answers, a Q&A website that shut down in 2021.
Loading...