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.

Windows 2000 Stop

Discussion in 'Legacy Windows' started by jsmith50, 2003/10/23.

Thread Status:
Not open for further replies.
  1. 2003/10/23
    jsmith50

    jsmith50 Inactive Thread Starter

    Joined:
    2002/05/23
    Messages:
    54
    Likes Received:
    0
    Windows 2000 Stop
    0x00000044 (0x81847868,0x00000CCA,0x00000000,0x00000000)
    MULTIPLE_IRP_COMPLETE_REQUESTS


    I applied Windows 2000 SP4 after this error. Of course the "blue screen" came up and said to remove newly installed hardware/software.

    I ran CHKDSK from Norton before applying Windows 2000 SP4 and the problem went away (I was able to reboot).

    Is there something to be concerned about?
     
  2. 2003/10/24
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,687
    Likes Received:
    107

  3. to hide this advert.

  4. 2003/10/24
    jsmith50

    jsmith50 Inactive Thread Starter

    Joined:
    2002/05/23
    Messages:
    54
    Likes Received:
    0
    Hi Arnie,

    Thanks for your quick reply. The status of Windows/2000 Professional was at the time of the problem, SP3.

    I looked for FALSTAFF.SYS today and did not find it.

    I have rebooted a few times since the problem went away and have had no further problems.

    The problem with the STOP code happened when the system was trying to startup. The W/2000 system went into a reboot loop. The only way to stop it was to unplug the power to the computer.

    I changed the BIOS boot priority to boot from a CD. I then booted from a SYMANTEC Norton 2003 Professional CD. I then ran Norton's CHKDSK and ran a virus check.

    This probably took care of the outstanding I/O request.

    Jim
     
  5. 2003/10/24
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,687
    Likes Received:
    107
    OK. It's just good to remember that it is probably a driver problem, should it ever return.

    Did you check your event log to see if more details were available (on the cause of the error)?
     
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.