locked
Stop Error: 0x00000024 not able to get past windows loading screen RRS feed

  • Question

  • I recently got hit with the bluescreen with error message 0x00000024 (0x00190203). i cannot get past the windows loading screen on my windows XP desktop before it gets this blue screen. nothing i do gets me past, like running the last working config and all that. it gets to the windows loading screen then i get hit with the blue screen. it doesn't even have the countdown to restart and i have to keep pressing in the power button to get my desktop to turn off. any idea how to fix this?
    Thursday, September 27, 2012 8:17 PM

All replies

  • Bug Check 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.

    Parameters

    The following parameters are displayed on the blue screen.

    Parameter Description
    1 Specifies source file and line number information. The high 16 bits (the first four hexadecimal digits after the "0x") identify the source file by its identifier number. The low 16 bits identify the source line in the file where the bug check occurred.
    2 If NtfsExceptionFilter is on the stack, this parameter specifies the address of the exception record.
    3 If NtfsExceptionFilter is on the stack, this parameter specifies the address of the context record.
    4 Reserved

    Cause

    One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

    Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

    Resolving the Problem

    To debug this problem: Use the .cxr (Display Context Record) command with Parameter 3, and then use kb (Display Stack Backtrace).

    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.


    --
    .
    --
    "Samantha s" wrote in message news:dc6786bc-13fe-4d28-8f51-d5ba1dbd9961...
    I recently got hit with the bluescreen with error message 0x00000024 (0x00190203). i cannot get past the windows loading screen on my windows XP desktop before it gets this blue screen. nothing i do gets me past, like running the last working config and all that. it gets to the windows loading screen then i get hit with the blue screen. it doesn't even have the countdown to restart and i have to keep pressing in the power button to get my desktop to turn off. any idea how to fix this?
    Thursday, September 27, 2012 8:53 PM
  • i try to run windows with debug and the command prompt, but it doesnt work either, still bluescreen. means i cannot disable virus scanners or anything. how would i be able to do this otherwise?
    Thursday, September 27, 2012 9:07 PM
  • You need to get a Windows (Vista or later) CD/DVD and boot from it to a command prompt and run
     
    chkdsk c: /r

    XP has slightly different procedure. Search Recovery Console.
     
    Have to go to work now.
    --
    .
    --
    "Samantha s" wrote in message news:77327c0d-485d-48af-b663-3299b56a2401...
    i try to run windows with debug and the command prompt, but it doesnt work either, still bluescreen. means i cannot disable virus scanners or anything. how would i be able to do this otherwise?
    Thursday, September 27, 2012 9:31 PM
  • Drive letters change when booting from DVD so it won't be C:, morelikely D:.

    --
    .
    --
    "DavidMCandy" wrote in message news:70c3917d-1b76-45f0-bd5d-1c42bdfc5fba...
    You need to get a Windows (Vista or later) CD/DVD and boot from it to a command prompt and run
     
    chkdsk c: /r

    XP has slightly different procedure. Search Recovery Console.
     
    Have to go to work now.
    --

    --
    "Samantha s" wrote in message news:77327c0d-485d-48af-b663-3299b56a2401...
    i try to run windows with debug and the command prompt, but it doesnt work either, still bluescreen. means i cannot disable virus scanners or anything. how would i be able to do this otherwise?
    Thursday, September 27, 2012 9:34 PM