Announcement

Collapse
No announcement yet.

How to recover from BSOD -- ntoskrnl.exe corrupt

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • How to recover from BSOD -- ntoskrnl.exe corrupt

    Hello Everyone,

    We have a problem that we encountered few days ago.
    The server after a scheduled reboot throws a BSOD with a corrupt ntoskrnl.exe msg.

    This happens to be a Windows 2000 Adv Server with SP4.
    We tried replacing the file from the recovery console, the result was that the BSOD msg successfully dissappeared but the server froze just before the Windows Splash screen.

    Is there any option that I can try to reover this server apart from re-building the server.

    Do let me know your opinion.

    Regards..

  • #2
    Re: How to recover from BSOD -- ntoskrnl.exe corrupt

    Do you have an ERD?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: How to recover from BSOD -- ntoskrnl.exe corrupt

      Unfortunately No! .. We do not have an ERD

      Comment


      • #4
        Re: How to recover from BSOD -- ntoskrnl.exe corrupt

        Rebuild it is then.

        Do you have good backups???

        Comment


        • #5
          Re: How to recover from BSOD -- ntoskrnl.exe corrupt

          Can't you just replace it with the file from the installation CD? "expand Cd drive:\i386\Ntoskrnl.EX_ C:\windows\system32 " seems to be the command. You'll need your RAID drivers if you have a RAID set that you're trying to access. It would be the standard "press F6 for drivers" action when you boot from the installation media. lionking, have a look at this article and see if any of it helps you. Wouldn't it be loverly if it was as simple as a bad keyboard?
          Wesley David
          LinkedIn | Careers 2.0
          -------------------------------
          Microsoft Certifications: MCSE 2003 | MCSA:Messaging 2003 | MCITP:EA, SA, EST | MCTS: a'plenty | MCDST
          Vendor Neutral Certifications: CWNA
          Blog: www.TheNubbyAdmin.com || Twitter: @Nonapeptide || GTalk, Reader and Google+: [email protected] || Skype: Wesley.Nonapeptide
          Goofy kitten avatar photo from Troy Snow: flickr.com/photos/troysnow/

          Comment


          • #6
            Re: How to recover from BSOD -- ntoskrnl.exe corrupt

            Originally posted by lionking View Post
            We tried replacing the file from the recovery console, the result was that the BSOD msg successfully dissappeared but the server froze just before the Windows Splash screen.
            @ Nonapeptide

            Already been tried bud.

            @OP

            When you replcaed the file did you replace it with one from the same service pack level that the machine was at??

            Comment


            • #7
              Re: How to recover from BSOD -- ntoskrnl.exe corrupt

              Originally posted by wullieb1 View Post
              @ Nonapeptide

              Already been tried bud.
              I'm just makin' sure everyone is paying attention. *cough*
              Wesley David
              LinkedIn | Careers 2.0
              -------------------------------
              Microsoft Certifications: MCSE 2003 | MCSA:Messaging 2003 | MCITP:EA, SA, EST | MCTS: a'plenty | MCDST
              Vendor Neutral Certifications: CWNA
              Blog: www.TheNubbyAdmin.com || Twitter: @Nonapeptide || GTalk, Reader and Google+: [email protected] || Skype: Wesley.Nonapeptide
              Goofy kitten avatar photo from Troy Snow: flickr.com/photos/troysnow/

              Comment


              • #8
                Re: How to recover from BSOD -- ntoskrnl.exe corrupt

                Yeah..

                Tried replacing the file from another box with the same OS & SP level.
                It dint work...

                Regards..

                Comment

                Working...
                X