1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

STOP 0x00000024

Discussion in 'Windows XP' started by Christer, 2005/04/12.

Thread Status:
Not open for further replies.
  1. 2005/04/12
    Christer

    Christer Geek Member Staff Thread Starter

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    Hello all!

    Yesterday, I had my first bluescreen on Windows XP pro at startup. The full error message:

    STOP 0x00000024 (0x001902FE, 0xF52151D8, 0xF5214ED4, 0x805642B7)

    Googling 0x00000024: a MS article discussing a problem with the NTFS file system (Ntfs.sys), possibly in relation to the hardware (HDD).

    Googling 0x001902FE: a discussion on a forum from which I guote:

    I ran IBM Drive Fitness Test on the HDD with the system partition but no sign of anything wrong or any bad blocks.

    No bluescreen since that single occasion and I did nothing but restart but does someone know more about this?

    Thanks for Your time,
    Christer
     
    Last edited: 2005/04/12
    Christer,
    #1
  2. 2005/04/12
    BenMcDonald[MS]

    BenMcDonald[MS] Inactive

    Joined:
    2004/12/14
    Messages:
    228
    Likes Received:
    0
    0x001902fe refers to some problem with your swap file. Converted to dec. this means about 1.6GB of the HDD were marked as bad blocks.
    This information is inaccurate.

    STOP 0x00000024 (0x001902FE, 0xF52151D8, 0xF5214ED4, 0x805642B7)

    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.

    With stop 24s, you have to guess, or get someone from microsoft to crack them.

    In this case, a generic exception occured, you'd need to open the dump in a debugger, .exr param 2 and .cxr param 3. Once you did that, you'd get a completely new stack.

    This specific error code is the generic unexpected exception handler in NTFS. Without the above context, it provides no clues about the cause.
     
    BenMcDonald[MS],
    #2


  3. to hide this advert.

  4. 2005/04/12
    Christer

    Christer Geek Member Staff Thread Starter

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    Hi Ben!

    All this is a bit over my head and under "start and reset ", I have limited it to "64 kb Minidump" ...... :eek: ...... since I wouldn't know what to do with it anyway.

    That's exactly what I know nothing about, I have the Minidump but that might not be enough even if I knew what to do with it.

    More important:

    I suspected that this was bad information and the IBM DFT supported that suspicion and You have confirmed it.

    Thanks,
    Christer
     
    Christer,
    #3
  5. 2005/04/12
    JoeHobart

    JoeHobart Inactive Alumni

    Joined:
    2004/05/19
    Messages:
    919
    Likes Received:
    1
    That's exactly what I know nothing about, I have the Minidump but that might not be enough even if I knew what to do with it.

    Christer, Im confused about your intentions. Did you want a hand with how to pull that data out of the dump. I dont know if it will be in a mini or not, but its not a lot of work to check.

    All you'd have to do is modify the advanced section of the debugwiz to insert this:
    .cxr 0xF5214ED4;.exr 0xF52151D8;

    after the !analyze -v; in the command string.
     
    JoeHobart,
    #4
  6. 2005/04/13
    Christer

    Christer Geek Member Staff Thread Starter

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    Hi Joe!

    My intention was to get a harddisk failure eliminated from the list of suspicions. I had the information, which I quoted, about a big chunk of the harddisk being marked as bad and the result of the IBM DFT which said that nothing was wrong with it. Ben settled that "argumentation ".

    Being a Ghost user, I'm not that good at trouble shooting and learning about the debugwiz has not even begun. It would be interesting to learn more but right now I'm a bit short on time. I'll try to get more autodidactive before asking You (or anyone else) for assistance but thanks for the offer!

    Christer
     
    Christer,
    #5
  7. 2005/04/13
    JoeHobart

    JoeHobart Inactive Alumni

    Joined:
    2004/05/19
    Messages:
    919
    Likes Received:
    1
    to be clear, although 1.5g of your hard disk was not marked bad, there is still a strong chance that you have some sort of disk corruption, possibly a bad sector in an important place.

    Have you run a full platter sector scanning utility?
     
    JoeHobart,
    #6
  8. 2005/04/13
    Christer

    Christer Geek Member Staff Thread Starter

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    Yes, the IBM Drive Fitness Test has a Quick Test and an Advanced Test. The Advanced Test reads every sector on the harddisk and it took almost an hour to scan my 120 GB harddisk.

    The bluescreen recommended, if it was a first time occurence, to just restart the computer which I did and all has been well ever since.

    When it happened, I had only pushed the button and left the computer to boot on its own so, I don't know at what stage of the boot process it went wrong.

    Christer
     
    Christer,
    #7
  9. 2005/05/16
    Christer

    Christer Geek Member Staff Thread Starter

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    Today, I had reason to use Diskeeper Lite to do an analysis of C: (the system partition) to find out which files certain colors represent in the legend. To my surprise, I found that the pagefile was no longer in the spot that it usually is. Restoring a Ghost Image, which I have done dozens of times, puts the pagefile towards the front. Only a chunk of other system files are ahead of it. The pagefile is now in the middle of the partition and the previously occupied space (by the pagefile) is free.

    I remember that Ben said

    but my assumption is that it happened when I had the bluescreen and that there was/is a connection to the pagefile.

    Christer
     
    Christer,
    #8
  10. 2005/05/16
    Christer

    Christer Geek Member Staff Thread Starter

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    I restored the most recent Ghost Image which was created prior to the bluescreen and I was again surprised when the pagefile was restored to the new location with the previous space free ...... :confused: ...... was there something to the "bad blocks" after all ...... :eek: ...... ?

    I defragmented the system partition and files were moved to the space previously occupied by the pagefile.

    I restored the same Ghost Image once more and after that, the pagefile was back in its original location towards the front of the partition.

    I'm now convinced that the bluescreen originated from an error in the pagefile but that it was a software error and not a hardware error.

    Christer
     
    Last edited: 2005/05/16
    Christer,
    #9
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...