Ask a questionAsk a question
 

AnswerVista SP1 RC1 - dead pc - missing ntoskrnl.exe 0xc0000098

  • Friday, December 28, 2007 11:43 AMGavCol Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,

    I just installed the Vista SP1 RC1 update and on the first reboot I get the missing or corrupt ntoskrnl.exe (0xc0000098)
    The advice given is to run a repair from the Vista disk but that doesn't work as It's unable to see the windows installation.

    Trying to do a System restore doesn't work either as there are no restore points existing even though I created a restore point and then the RC1 update created one before the install.

    I now have a dead machine and would like any advice on restoring my PC back to some normality.

    Cheers

    Gav

Answers

  • Wednesday, January 02, 2008 12:43 AMnlcollings Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

     

    I had the same problem and it is to do with the indexing of the file.

     

    To fix:

     

    Boot to a command prompt (select from F8 menu or use a boot disk) I used the vista install disk then selected Fix my computer then command prompt.

     

    Run chkdsk C: /F (replace C: with your system drive)

     

    My chkdsk found 3 indexing errors and fixed them

     

    Reboot

     

     

    hope this helps

All Replies

  • Saturday, December 29, 2007 8:03 PMGavCol Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Some Extra info:

    I have Vista on 2 different hdds

    I never bothered with having boot manager setup to handle both OS' because it was just as easy to make the selection via bios boot drive options
    Sata hdd: is the main auto boot option
    IDE hdd: redundant OS not used for months, accessible via bios boot-time drive selection options

    I installed RC1 while in the SATA vista but somehow the update has recognised the IDE vista and updated it's bootmgr and clobbered the SATA bootmgr.

    When I boot to the IDE I get 2 vista selection options
    1> Microsoft Windows Vista (Selecting this boots the old IDE Vista)
    2> Windows Vista Ultimate * (selecting this boots the SATA vista sp1 rc1 with the ntoskrnl error)

    (* = unrecovered  or sometimes * = recovered )
    It's been nearly 2 days now and I haven't had a response yet.

    Is there any information that can help me ??

    Cheers

    Gav
  • Sunday, December 30, 2007 6:19 AMi022418 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    I have almost the same problem and I need help. I have two partitions on the same drive (the one created by bitlocker preparation tool) and when I try to repair from Vsta boot DVD, it finds the operating system on the wrong drive. I do not wnat to do a clean installation of Vista but rather revert to a previous stage

     

    Cheers,

     

    Vassilis

  • Sunday, December 30, 2007 10:44 PMmutley69 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    It seems to me that microsoft has a serious problem with Vista SP1-RC1. I even cannot get the dvd to boot. Just after loading the drivers all i get is the sam error you do.
    I used to be able to get the plain vista ok - by disabling the AHCI modus in the bios on the sata-drives. But this doesn't help anymore.

    Vista 64-bit runs better, even installs fine, but gets sometimes realy slow.

    I know it's only a pre-release, but i do hope microsoft will be able to fix this AMD 690-chipset issue before SP1 gets out! AMD
    BE2350 cpu - on a gigabyte GA-MA69GM-S2H - good memory - no bad memtests either!

    (the same system runs extemely stable under linux 0 crashes - and it's relyable without SP1 also 0 crashes - if i don't put the AHCI-modus on the sata on). I could even upgrade to SP1 RC1 without problems at all. But not install with the RC1 32-bits version. The 64-bit version is also not stable enough...

    If somebody could explain to me what may cause this error - i might be able to get a little further...
    (otherwise i'll have to turn to linux & run vista under vmware - that's an alternative - the generated dvd from iso boots fine on another amd-machine, so it's not the dvd. I even upgraded the firmware to the latest rev.).

    kind regards
  • Monday, December 31, 2007 12:35 PMGavCol Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I'm surprised I haven't had a response yet on how to fix this.  I would have thought the title of "dead pc" would have caught some attention from microsoft.  Especially as the RC1 has modified the bootmgr on the wrong drive.  I'm sure there are heaps of people out there with OSs on different drives.

    It's been too long now without a solution and I will have to use my last resort to just blow away the current installation and re-install vista on the sata drive.  What's the point testing betas or RCs if we don't get a response to fix their bugs

    Gav


  • Tuesday, January 01, 2008 8:48 AMchintan modi Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    i am having the same problem... and now i cant boot my sys into vista.....
    try to found the solution but coudnt....


    if any one knows the solution then please post it otherwise i've to reinstall the entire OS!!!!


  • Wednesday, January 02, 2008 12:43 AMnlcollings Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

     

    I had the same problem and it is to do with the indexing of the file.

     

    To fix:

     

    Boot to a command prompt (select from F8 menu or use a boot disk) I used the vista install disk then selected Fix my computer then command prompt.

     

    Run chkdsk C: /F (replace C: with your system drive)

     

    My chkdsk found 3 indexing errors and fixed them

     

    Reboot

     

     

    hope this helps

  • Wednesday, January 02, 2008 2:21 AMGavCol Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks for your suggestion.

    I couldn't wait any longer and have already re-installed Vista.

    I hope your suggestion helps others and as it is the first and only constructive answer I've received I'll just mark it as the correct answer.
    I might try it on my old vista on IDE drive... see what happens.

    Has anyone done any testing to see if gigabit networking has been fixed in sp1 ??

    Gav







  • Thursday, January 03, 2008 5:11 PMCarl D_ Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    For those of you who have done this and the install still fails please do the following:

     

    If you run chkdsk /f on the system drive, the output will go to \bootex.log first.  This file will then be scooped into the application event log under the wininit source, event id 1001

     

    Please send me the text/logs of all errors chkdsk reports

     

    Many thanks,

    Carl D.

    a-cadiet@microsoft.com

    Windows Beta Team

     

     

  • Thursday, January 03, 2008 5:29 PMCarl D_ Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    Oh...and for those of you who haven't done so ( that have access to the MBC tool ) please do file a bug and include these logs as well if they exist:

     

    %windir%\Panther\setupact.log

    %windir%\Panther\setuperr.log

    %windir%\logs\CBS\CBS.log

    %windir%\logs\CBS\CBS.persist

    %windir%\winsxs\poqexec.log

    %windir%\winsxs\pending.xml

     

    Kind regards,

    Carl D.

    a-cadiet@microsoft.com

    Windows Beta Team

  • Wednesday, January 09, 2008 12:32 AMdennyc69 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    okay, well I got the same error, so I ran chkdsk, the results were 5 unindexed files and it failed to transfer logged messages to the event log with status 50.

    My machine is still dead as of this point and  I'd love to get it going again. Since Safe Mode is not an option what can I do to get my machine going again without losing data?

    Running dual core AMD with an NVIDA chipset and a 6600 NVIDA video card (if this info really helps)

    Thanks

    Chris

  • Thursday, January 10, 2008 2:51 AMpeterdoo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer

    On my PC (HP) the error 0xc0000098 occurs each time the disk is filled up more than 70% and some system files required for the system to load are updated. When a file is updated it is written to a new location on the disk. It seems that when files are located close to the end of the disk, the Vista/XP loaders cannot reach the file in the NTFS structure. Vista reports 0xc0000098 and XP reports "A disk read error occurred Press Ctrl+Alt+Del to restart".

     

    It seems that the BIOS translation to disk sector numbers (BIOS is used by loader) is not the same as the translation used by driver when Vista/XP is running already.

     

    In my case it helps connecting the disk with the OS to another PC and defragmenting it there.

     

    Peter

    • Proposed As Answer byBrian Borg Saturday, May 30, 2009 8:26 PM
    •  
  • Thursday, January 10, 2008 4:20 PMdennyc69 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Well, what happened with me was,

    SP 1 wouldn't install. It would always get to 99% and then hang. It did it everytime I tried to install it. I'd deleted the files from Software Distro like others have posted here suggested,and tried again, and nothing would happen. So I gave up. Then when a bunch of new updates showed up on the 8th, I installed them. Low and behold the SP started to install. When the computer restarted that's when I lost my OS with the missing ntoskrnl.exe.

    I ran the Vista repair and of course it can't find anything wrong, but won't boot up. The OS is on an SATA drive and the only other Windows machine I have is my laptop. I did email on of the techs on here and he tells me there's nothing that would fix that untill the next build. Which does me no good.

     What I need to know is, is there a way to do a command prompt uninstall of the last updates from the command prompt window off the OS DVD. I do have another HDD to do a clean install but that would mean calling the activation line again.... and explaining to them what happened and I'm not going to do that, at least no yet.

    If it hadn't been for the fact that I had Ubuntu installed on a smaller drive, I would be out a PC right now.

    I need some postitve feed back Microsoft, to get my $ 159.00 product key that I paid for working because I'm not buying another one. Mine's paid for!

    Regards,
    Chris

    c.denny@insightbb.com
  • Thursday, January 17, 2008 8:40 PMAnotherOne Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,

    I'm having the same problem with a Vista Home Premium HP-Notebook. The installation failed two times at 99%, then it finally installed. (At least I thought so.)
    After a reboot i get a corrupt ntoskrnl.exe error (0xc0000098).

    I've got 2 SATA HDDs. On the first HD I have a 100GB NTFS, about 40GB nothing, 11GB ext3 and a 1GB swap partitition. On the NTFS Vista has been preinstalled by HP. Tomorrow i'll try a Vista Home Premium DVD to repair. But since HP neither distributes OS DVDs nor could I create one (The recovery disk creator script crashes everytime.), i have to lend one from a friend.. Hope that this doesn't matter..

    If there's an "official" or at least working solution for this issue, i'd been interested in.



    PS. Sorry for my English..
  • Friday, January 18, 2008 3:42 AMSideshowBob Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Could have something to do with IDE/SATA corruption problems others are having with dual boot configurations.
  • Friday, January 18, 2008 6:44 PMdennyc69 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    The end result for me was writing 0's to the drive and reinstalling the OS, but now I get
    800F081F from Windows update after the new WU program installed. It will not connect to WU server to download anything.
    Anyone else seen this?

    Chris
  • Saturday, January 19, 2008 5:37 PMSideshowBob Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Yes, twice. This last time installing the Installer update KB938371 alone, without any other updates at all, solved the problem. Of course, you may want to read this if you have any anti-virus or firewall installed. That particular update caused me all kinds of nastiness.
  • Monday, January 21, 2008 8:45 PMdennyc69 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    For me it was never an issue with dual boot, though I do believe it may have something to do with SATA drives
    There was no antivirus installed, only Windows Firewall
  • Tuesday, January 22, 2008 1:02 AMSideshowBob Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Then you should be able to install the installer update by itself. After that I didn't have any trouble with those updates failing anymore.
  • Wednesday, January 23, 2008 3:21 AMdennyc69 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Issued fixed!!!!!

     

    I went here:  http://support.microsoft.com/kb/932494/en-us

     

    downloaded  Download the WindowsUpdateAgent30-x86.exe package now.

     and it fixed my issues. After WU downloaded my updates I unchecked the update to WU and hid it, then installed the rest of my updates. I do have UAC turned off too

     

  • Wednesday, January 23, 2008 4:17 AMBRGROUP Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I had to totally disable my IDE drives by unplugging the power before Vista could find my install on the SATA drive and I could do a startup repair for the BOOTMGR error that SP1 gave me.

  • Tuesday, March 18, 2008 5:29 PMTh3Dr4g0n Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    All the advices here seem to be useless. As always Micro$oft is beta testing live with people' computers without taking in consideration the inconviniance and damage to others.

     

    I am also getting the same missing ntoskrnl.exe 0xc0000098. Except that I am also getting one more error;

    "A files is missing or currupted" The major problem is that it does't seem to know what file(s) is(are) missing or currupted.

    I ran the repair uption and ran:

     

    chkdsk /f C:

     

    To my surprive it went into the Volune System Information folder and rectify all the indexes in side the files pointers. After rebooting one more time and getting the above mention error, I tried to use the BCDedit.exe ustility as mention by Micro$oft, I tried to backup the file just in case I currupt the bootmgr but now I am getting permission denied. So I decided to find out who own those files:

     

    dir /a /q

     

    To my surprice those files are own by TrustedInstaller group and by System I was expecting. Well I was to give up and follow my own advice to run Knoppix  and recover my files and them reinstall. But to test one more theory I decided to try to fix the MBR and see if that works. And here is Micro$oft advice which does not apply to my case. In this case it is a sub article that I will test today and post if this actully fix my issue.

     

    For years I have been a Micro$oft consultant but, after Windows XP and now Vista I am begining to move my customers to either Linux of Unix as it seems to be more stable. Currently I only have one computer running Windows and it is for my school classes.

     

    Bottum line is I am tired to pay for halfve way done products, Windows is taking many features from Linux in that case why stay with Windows when I can run Linux or Unix with less problems, worries, time waste and with less security issues. Always thinking when Micro$oft will deploy the next damaging patch >>

     

    Th3Dr4g0n

     

     

  • Wednesday, March 19, 2008 12:46 AMTh3Dr4g0n Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I am doing a follow up to my previous post as I promise and here is more information:

     

    I tried the resolution from 927392 and as spected it was totally useless. I also tried several other solutions and nothing.

    But I was able to put some information together that perhaps one of the many guru from Micro$oft can put some light in the problem.

     

    While trying to repair the installation I get the following:

     

    Proble Signature.

    Problem Event Name                           StartupRepairV2

    Problem Event Name 01.......................External Media

    Problem Event Name 02.......................Vista Version

    Problem Event Name 03.......................6

    Problem Event Name 04.......................524296

    Problem Event Name 05.......................CurruptFile

    Problem Event Name 06.......................BadDriver

    Problem Event Name 07.......................0

    Problem Event Name 08.......................3

    Problem Event Name 09.......................WrpRepair

    Problem Event Name 10.......................Vista Version

    Locale ID:                                            1033

     

    I kow I sent the logs to Micro$oft while I was performing the Repair, I am trying to find them but It seems to be deleted. If any one knows where the logs are located please let me know.

     

    Th3Dr4g0n

     

  • Wednesday, March 19, 2008 9:59 AMDiGiTaLLiCa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I'm having the SAME EXACT ISSUE right now.

     

    After SP1's install; vista fails to boot and I'm getting missing or corrupt ntoskrnl.exe 0xc0000098

     

    What the hell! I've waited till MS officially releases this update on Windows Update to avoid all beta and RC bugs! Right now my PC IS COMPLETLY DEAD. I've tried everything from inside the repair disk including trying to system restore and chkdsk! can ANYBODY please shed some light on the cause of this issue!

     

    BTW: I only have one OS (which is the now dead vista) installed on my hard disk.

     

  • Wednesday, March 19, 2008 12:27 PMTh3Dr4g0n Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I ran some other utilities in my pc plus, finally find the log which (I think) finally told me what is wrong with my pc. Here is the output of my log.

     

    Startup Repair diagnosis and repair log
    ---------------------------
    Number of repair attempts: 1

    Session details
    ---------------------------
    System Disk = \Device\Harddisk0
    Windows directory =
    AutoChk Run = 0
    Number of root causes = 1

    Test Performed:
    ---------------------------
    Name: Check for updates
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: System disk test
    Result: Completed successfully. Error code =  0x0
    Time taken = 0 ms

    Test Performed:
    ---------------------------
    Name: Disk failure diagnosis
    Result: Completed successfully. Error code =  0x0
    Time taken = 93 ms

    Test Performed:
    ---------------------------
    Name: Disk metadata test
    Result: Completed successfully. Error code =  0x0
    Time taken = 63 ms

    Test Performed:
    ---------------------------
    Name: Target OS test
    Result: Completed successfully. Error code =  0x0
    Time taken = 78 ms

    Root cause found:
    ---------------------------
    No OS files found on disk.

    Repair action: Partition table repair
    Result: Failed. Error code =  0x490
    Time taken = 2938 ms

    ---------------------------
    ---------------------------
     

    As you can see, some way some how the SP1 RC released by Micro$oft damage my partition table and now the pc can't find the location of the sector to boot properly. Wikipedia has a nice small article that can help to place some light in this mess.

     

    If you are at some level computer techie then I will suggst to get a partition utility and try to rebuild the partition table. I will try the same some time today.

     

    BTW: If you have Automatic Updates enable, then this was unavoidable. Personnally I place all of the responsability on MS since they sould of release the SP as "test only" and not as a SP. They should of place the SP1 for Vista in a way that Windows update couldn't find it as a regular release. Iam not sure what king of QA they have but, they really need leave too much to be desire.

  • Thursday, March 20, 2008 5:36 PMDarren Jackson Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I'm getting the exact same problem: After SP1's install; Vista fails to boot and I'm getting missing or corrupt ntoskrnl.exe 0xc0000098.

    I, too, have waited until the official release of SP1 and now find myself with a useless laptop and, after nearly two hours of online troubleshooting with a Microsoft support person, it seems that my only option is to do a complete reinstall!

    I am really annoyed about this. It is now going to take me a long time to reinstall all my apps and data and reconfigre everything. It simply isn't good enough...

    Are Microsoft intent on destroying their OS market share, or something? They seem to be doing a bloody good job of it, anyhow. Linux distros must be delighted...
  • Thursday, March 20, 2008 10:04 PMTh3Dr4g0n Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    There are some utilities available to fixe the partition table. Most of them are commercials. I won't recommend a specifict utility as for personal experience defferenc users prefere deffirent utilities. I haven't have the time to work on my but hopefully I will be doing it soon enought.

     

    As you I have over 100 programs in my comp I don't feel like installing all of them. It very poor how Micro$oft handle their business. Again, if you wan stability move to Linux or Unix.

     

    I will post my results hopefully not later than Satuday.

     

    Th3Dr4g0n

  • Thursday, March 20, 2008 11:42 PMPoorWinUser Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello,

    As you all I have been waiting to download the final version of the SP1, and as many of you I ended with a nice useless Sony Vaio Laptop, and I dont really like the format feature, since I have important data, etc.. I see Micro$oft doesnt really care about us, and neither have published any kind of fix or WORD about this, so I suggest about starting a legal complain as I will do tomorrow. I know some other people got paid for this kind of problem, so I will let this be fixed by my law guy.

    Regards
  • Friday, March 21, 2008 1:41 AMDiGiTaLLiCa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Alright guys, Here's what I did to boot my Windows up again and re-install SP1 (Already confirmed working by other users):

     

    You'll need to manually restore some files again to the version that came with your Windows installation DVD. Use the Windows DVD to boot into repair mode and restore these files using the command prompt:

     

    In your "\Windows\System32\" folder, restore just these files:

    hal.dll

    ntoskrnl.exe (You shouldn't need to replace it because it's not really corrupted.)

    ntkrnlpa.exe (Same as ntoskrnl.exe. Try booting without replacing them first)

     

    And in your "\Windows\System32\Drivers" folder, restore these:

    acpi.sys

    msisadrv.sys

    pci.sys

    volmgr.sys

    volsnap.sys

    disk.sys

     

    Make sure to rename or backup the files you're going to replace (just in case you do something wrong). All the original files you'll need to replace your "corrupted" files with should be found inside the virtually mounted drive (X:\), so they should be in "X:\Windows\System32"\ and "X:\Windows\System32\Drivers\" (you don't need to "expand" any files like the old XP days, you'll just need to use basic "copy" and "rename" commands).

    HINT: If you're not too comfortable using the command prompt, you can use the notepad's file browser to copy and paste files from inside the repair DVD. Just type "notepad.exe" in the command prompt and set the file type to ALL inorder to see non-txt files.(WARNING: It doesn't prompt you when overwriting files and It doesn't show hidden or system files, but you shouldn't need it to anyways)

     

    After it boots successfully you should try to reinstall SP1 again BUT DO NOT USE WINDOWS UPDATE TO REINSTALL IT, DOWNLOAD THE STANDALONE RELEASE. It's highly recommended to reinstall SP1 again because eventhough after you're going to boot, Windows will say that it's removing all SP1 files because the install failed, it actually doestn't replace most of the system files. Your copy is going to be a hybrid between no SP and SP1. When you reinstall SP1, Stage 3 is going to be repeated twice, once before Stage 1 and then again after Stage 2. But that is completely normal.

     

    You should'nt need to restore any other files for you Windows to boot. Don't just replace all the files inside your "System32\Drivers\" folder like what that article said, that will probably do more harm than good. I used the debug boot log file from inside my Windows folder (ntbtlog.txt) to determine which files Windows is using while attempting to boot, and then I checked their file version from inside the repair DVD (right click>properties>details or just leave the mouse pointer on the file for a second); If it was 6.0.6001.18000 (SP1 release version), I replaced it with the old version from my boot DVD.

     

    Good luck guys.

     

     

    IMPORTANT UPDATE:

     

    msisadrv.sys is the correct file name, that was just a typo (edited and corrected). Sorry about that.

     

    Also, I just remembered something; hal.dll did actually give me some trouble because it wasn't in the X: drive. And unfortunatly it's the VERY FIRST file the Windows Loader tries to load at boot so you'll have to get it somehow. You can use the Automatic Repair Method (Posted by "Koben Haven" right below this post) and see if that works for you, but you can also use a USB Flash memory to copy it (make sure it's a pre-SP1 Windows Vista "hal.dll" ) or you can look for it in your Windows folder inside your "winsxs" (ex C:\Windows\Winsxs\) folder (a folder that Vista uses to basicly backup every version of every file ever made for Windows Vista) But it's kinda of tricky because:

    1)The file is deep inside "winsxs" which has TONS of folders and files

    2)The file itself is kinda of tricky to back up because the exact file isn't actually there.

     

    Let me explain:

    If you look inside your "C:\Windows\System32" folder, You will see three files: hal.dll, halacpi.dll, and halmacpi.dll. You will likely see that hal.dll is the same size as one of them. That's because it's exactly the same file just copied and renamed. Basicly if you have a multi-core PC you'll need to use halmacpi.dll and rename it to hal.dll, If you're running a single core PC you need to use halacpi.dll instead. The "winsxs" folder only has these two files and not hal.dll straight up because it kinda depends on the type of processor you're using. So look inside your "winsxs" folder for folders that start with "x86_hal.inf_XXXXXX_6.0.6000.20500_none_XXXXXXX" and you'll find these two files inside along with a "hal.inf" which you won't need to replace (it's inside the "inf" folder in your Windows directory), and then copy whichever one you should use -depending on your processor- to your "C:\Windows\System32\" folder. Now that I think about it, It's probably better if you replace both halacpi.dll and halmacpi.dll inside your System32 folder too (Just to be on the safe side).

    NOTE: You'll probably find two or more folders that start with "x86_hal.inf" in your "winsxs" folder, but make sure:

    1)The folder starts with just "x86_hal.inf" not "x86_hal.inf.resources"

    2)The version number in the folder name is NOT "6.0.6001.18000" because that's SP1 one that causes the problems.

     

     

    Good Luck again!

     

    BTW: This is not a partition table problem (atleast it wasn't like that for me). It was merely a F"d up SP1 install process due to a F"d up installer that shouldn't be trusted to install flash games.
  • Friday, March 21, 2008 7:55 AMKoben Haven Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Big and very big thanks to DiGiTaLLiCa for solution!

    Hey man it did help to boot up my laptop again, but with a few changes.

    First, i missed msiasdrv.sys you mentioned, but i found msisadrv.sys, so i replaced this file instead.
    Second, in my boot DVD did not had a hal.dll file, so i did next:
    1. I did all as you said, to back old files, and then replaced them with new from boot DVD.
    2. For hal.dll i just backed it up by renaming it to hal.dll.bak as i did with all other files in list to copy.
    3. Then restarted Laptop, it did not boot, as hal.dll was missing, but then i run my boot DVD repair option and it did fixed issue - got from somewhere new hal.dll.

    After that, my laptop lastly booted up and began this cursed servicepack install stage 1 of 3 ...

    PS. if you try to run startup repair, after renaiming hal.dll, the repair did not work, i had to restart to laptop to found that hal.dll missing and then the startup repair worked and fixed the "root cause".

    Anyway man big thanks!!! I have a lot valuable information as this is my work laptop, and it would take weeks to restore everything, now thinking to backup everything, before anything else screw my laptop to pieces.
  • Friday, March 21, 2008 8:57 AMDiGiTaLLiCa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     Koben Haven wrote:

    First, i missed msiasdrv.sys you mentioned, but i found msisadrv.sys, so i replaced this file instead.
    Second, in my boot DVD did not had a hal.dll file, so i did next:
    1. I did all as you said, to back old files, and then replaced them with new from boot DVD.
    2. For hal.dll i just backed it up by renaming it to hal.dll.bak as i did with all other files in list to copy.
    3. Then restarted Laptop, it did not boot, as hal.dll was missing, but then i run my boot DVD repair option and it did fixed issue - got from somewhere new hal.dll.

     

    Yes, msisadrv.sys is the correct file name, that was just a typo. Sorry about that.

     

    And also yes; hal.dll did actually give me some trouble because it wasn't in the X: drive (I remember now, Sorry again :-D) . And unfortunatly it's the VERY FIRST file the Windows Loader tries to load at boot so you'll have to get it somehow. You can use the Automatic Repair method if that works for you, but you can also use a USB Flash memory to copy it (make sure it's a pre-SP1 Windows Vista hal.dll) or you can look for it in your Windows folder inside your "winsxs" (ex C:\Windows\Winsxs\) folder (a folder that Vista uses to basicly backup every version of every file ever made for Windows Vista) But it's kinda of tricky because:

    1)The file is deep inside "winsxs" which has TONS of folders and files

    2)The file itself is kinda of tricky to back up because the exact file isn't actually there.

     

    Let me explain:

    If you look inside your "C:\Windows\System32" folder, You will see three files: hal.dll, halacpi.dll, and halmacpi.dll. You will likely see that hal.dll is the same size as one of them. That's because it's exactly the same file just copied and renamed. Basicly if you have a multi-core PC you'll need to use halmacpi.dll and rename it to hal.dll, If you're running a single core PC you need to use halacpi.dll instead. The "winsxs" folder only has these two files and not hal.dll straight up because it kinda depends on the type of processor you're using. So look inside your "winsxs" folder for folders that start with "x86_hal.inf_XXXXXX_6.0.6000.20500_none_XXXXXXX" and you'll find these two files inside along with a "hal.inf" which you won't need to replace (it's inside the "inf" folder in your Windows directory), and then copy whichever one you should use -depending on your processor- to your "C:\Windows\System32\" folder. Now that I think about it, It's probably better if you replace both halacpi.dll and halmacpi.dll inside your system32 folder too.

    NOTE: You'll probably find two or more folders that start with "x86_hal.inf" in your "winsxs" folder, but make sure:

    1)The folder starts with just "x86_hal.inf" not "x86_hal.inf.resources"

    2)The version number in the folder name is NOT "6.0.6001.18000" because that's SP1 one that causes the problems.

     

    I'll edit my previous post and update the info, Thanks for the heads up!

     

     

     

     

     

  • Sunday, March 23, 2008 12:56 AMlabznet Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    But what if i don't have the vista DVD?

    My Windows Vista Home Premium (32-bit) came with my HP Pavilion tx1000 and they don't issue the DVD.

    My whole problem started when an automatic windows update told me to update something.

    i did, and then i had the "configuring updates - stage 3 of 3 - 0% complete"

    so i looked through many forums and tried several things.

    one of which is to dl the standalone SP package (x86) and install it.

    At this point of time, whenever i shutdown my laptop, the service pack installs. 100%.

    and then when i boot it up, it goes into startup repair. and then it finds a corrupt ntoskrnl.exe and repairs this by system restore to a restore point just before the service pack installation.

    then it restarts and shows the message "installing service pack - stage 3 of 3 - 0% complete"

    and then it logs on.

    works fine.

    but when i shutdown, it repeats the cycle. (i.e the service pack installs 100%)

    i need help. I can't be waiting for so long just to shutdown and boot up twice just to get into windows.

    thanks in advance..
  • Sunday, March 23, 2008 2:39 PMgstelmack Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Thanks for this info, I may have to try it soon. My first SP1 install from Windows Update corrupted acpi.sys; restoring from winsxs got me booting, but every time I rebooted it wanted to finish installing SP1. After that went on all day and through about 4 reboots, I downloaded the full SP1 installer and ran it, and got bit with the ntoskrnl.exe issue. After manually replacing all the files it complained about as I kept rebooting (ntoskrnl.exe, PSHED.DLL, tcpip.sys, ntfs.sys), it now bluescreens on boot (if I boot into safe mode, it gets as far as crcdisk.sys and then decides to just reboot). No system restore point, and Microsoft Support tried to get the registry restored but that did not help.

     

    I'm waiting for another callback from support tomorrow (I'm being elevated for the second time), but I'll keep this post in my back pocket in case they can't fix it.

     

    If only the Vista DVD would let me install the OS again like XP would, but that process complains that in order to use the same product key that's already on the hard drive, I'd have to re-run install from within Windows, which of course I can't get to right now...

     

  • Sunday, March 23, 2008 7:29 PMDharun Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I have the same problem with the blue screen.  This occured after I replaced ntoskrnl.exe, PSHED.DLL, tcpip.sys, ntfs.sys.  I think the problem is that some of the files are from sp1 and the one's I replaced are not.  I would appreciate any help on this.
  • Sunday, March 23, 2008 10:32 PMDiGiTaLLiCa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    Guys, if you're getting the same error just replace the files I listed in my previous posts and follow the same steps, hopefully this will get you up and running again.
  • Monday, March 24, 2008 3:26 PMDharun Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I followed those instruction however they did not work.  I managed to do a system restore but only back to the point where SP1 was installed.  As soon as I restart, it attempts to configure updates and then the bootup fails again.
  • Tuesday, March 25, 2008 12:33 AMgstelmack Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Did not work for me either. Still bluescreening on a normal reboot, still just rebooting after it hits crcdisk.sys on a safemode boot. I'm going to keep playing around with it to see if I can get it going again.

  • Tuesday, March 25, 2008 8:05 AMKiM tech Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Dear all,

     

    On my friends PC with vista X64 AMD 5600+ 

    1.) i run chkdsk /f (by using command prompt of Vista DvD)

    2.) I followed process posted by "DiGiTaLLiCa "  in the manner of "Koben Haven " (skiping hal.dll)

    3.) restarted pc & it told me "ataport.sys" missing.

    4.) restored it from c:\WINDOWS\LAST GOOD\SYSTEM32\DRIVERS TO C:\windows\system32\drivers\

    5.) restarted pc

    6.) Re installation of SP Stage 1 of  3 started ....

    7.) stage 2 of 3 completed, pc restarted & again this error came "missing ntoskrnl.exe 0xc0000098"... bull *** vista SP1

     

     

     

     

     

     

     

  • Tuesday, March 25, 2008 5:43 PMAdz3 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Guys, after having the same problem I rang microsoft and if you are thinking about doing the same. Dont bother they have no idea what is going on with this issue.

     

    I have surcome to the fact I am in data recovery, reformat and roll back to XP mode. This is a shame as I have been a fan of Vista until now. I thought SPs where to enlighted the experience not crash it???

     

  • Wednesday, March 26, 2008 3:40 AMseattlemark Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    The same  missing ntoskrnl.exe problem happened to me. So I was going to try  the fine suggestions given above by DiGiTaLLiCa.  I got lucky though. When I booted with the Vista DVD, and chose to do a Startup Repair, it completely fixed my problem.  (Startup Repair Instructons can be found at: http://windowshelp.microsoft.com/Windows/en-US/help/5c59f8c1-b0d1-4f1a-af55-74f3922f3f351033.mspx#ESG )

     

    I haven't been brave enough to try another attempt at SP1 yet.   I first want to back some more stuff up from my Vista partition. (Fortunately almost all of my data is already on another partition shared by my XP multi-boots.)

     

     

     

     

  • Wednesday, March 26, 2008 8:34 AMDiGiTaLLiCa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
     seattlemark wrote:

    The same  missing ntoskrnl.exe problem happened to me. So I was going to try  the fine suggestions given above by DiGiTaLLiCa.  I got lucky though. When I booted with the Vista DVD, and chose to do a Startup Repair, it completely fixed my problem.  (Startup Repair Instructons can be found at: http://windowshelp.microsoft.com/Windows/en-US/help/5c59f8c1-b0d1-4f1a-af55-74f3922f3f351033.mspx#ESG )

     

     

    For some reason, not only did startup repair refuse to fix my problem (completely useless if you ask me) but it also managed to delete all my pre SP1 restore points and my partition shadow clones. I am 100% sure that I had multiple restore points before starting the SP1 installation process AND a new restore point was automatically created at the begining of the installation.

     

    For people who still have restore points created, don't do a system restore; try restoring your windows partitions' shadow copy to Pre SP1. It's the repair tool right under system restore (called "Full System Restore" or something). Running system restore will not prevent Windows from trying to continue the installation eventhough some of the files were restored. But if you restore the whole partition it'll probably forget the whole installation ever happened. Other than that follow the instructions I posted here earlier and hope for the best.

     

    And for those who get bluescreens at crcdisk.sys, you didn't restore all the files I mentioned properly. I had the same bluescreen because I skipped restoring a couple of files from that list at first (eventhough they didn't give me an error at boot). You must replace all SP1 files that load at boot, regardless of weather they give you an error or not.

  • Wednesday, March 26, 2008 12:13 PMgstelmack Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
     DiGiTaLLiCa wrote:
    And for those who get bluescreens at crcdisk.sys, you didn't restore all the files I mentioned properly. I had the same bluescreen because I skipped restoring a couple of files from that list at first (eventhough they didn't give me an error at boot). You must replace all SP1 files that load at boot, regardless of weather they give you an error or not.

     

    Well, I followed it step-by-step, including double-checking which hal.dll to use. I replaced them all.

  • Friday, April 04, 2008 1:49 PMJames D 1001 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Have just installed SP1 on a Vista Ultimate config, same error.
    1 200Gb drive, single partition. PC restarted after SP1 had finished configuring and suess what... CRASH!!!!
    Now about to start the "fix".
    Begs the question of why doesnt the system sun a chkdsk after install by default?

    (Have about 30 Dell Vista Business pc's and laptops to update, 2 successful updates on Dell  PC's with the MSDN version of SP1, now to try a laptop with the version on Update Centre...3/1 on it gets corrupted)
  • Friday, April 04, 2008 8:45 PMbcallens Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    had the problem too: missing ntoskrnl.exe

    Followed DiGiTaLLiCa 's remedy with limited success: I could boot again, but SP1 was not installed and an attempt to execute the installation again with the downloaded version reverted to the 'ntoskrnl.exe' problem...

    So:
    1. I uninstalled Bitdefender and some other potentially sensitive applications.
    2. I checked the cbs.log file. I could see an often recurring issue:

    2008-04-03 23:51:57, Info                  CSI    000000fe Expected resource missing during POQ execution:
        ID1: [l:180{90}]"\Registry\Machine\SYSTEM\CurrentControlSet\Services\RemoteAccess\Parameters\AccountLockout"
        ID2: [6"(null)"

    3. Some reading convinced me to attempt tampering with that same Registry setting. I changed
    MaxDenials from a default null setting to 3.

    Result:
    • Started reinstall of SP1 again - success !
    • Check of the registry shows that the 'AccountLockout' entry has disappeared totally
    • I only needed to reinstall Bitdefender. While doing that, it gives me that Bitdefender v10 is not supported - Bitdefendres website confirms this: need to upgrade to Bitdefender 2008 (free upgrade - thanks)... smoking gun?
    Many thanks for all the posters and particularly DiGiTaLLiCa !
  • Sunday, April 27, 2008 6:45 AMRextter Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I had this problem too.  The patch would appear to install, even display the "successful" message, but when the computer rebooted the ntoskrnl.exe program would be missing or corrupted.  The only way back for me was to insert my Vista DVD and choose to repair.  Back to square one.

     

    My problem seemed to be rooted in Bit Defender antivirus version 10 still.  I uninstalled it, which was harder than I thought it would be because even though it was no longer installed, Vista still used 2 components of it as the firewall and a virus screen.  These had to be stopped too as they prevented the SP1 installation.  The way I did it was not to go into SafeMode but to have Windows Defender show me which BitDefender files were still running and then fire up Task Manager to stop them.

     

    Once BitDefender was gone I used a download of the SP1 to install for about the 8th time and this time it worked.  The computer rebooted, took 30 mins to install the 3 stages and now has the SP1 installed and working.  Also, BitDefender has been upgraded to 2008, which they kindly offer for free.

     

     

  • Friday, May 23, 2008 2:54 PMLPTInformatica Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi to everyone !!!

     

    First...sorry my english...

     

    I resolve the problem runing de DVD, then i run the command line and CHKDSK C: /F /R....restart and boot again with DVD and select repair computer....restart and i boot correctly.

     

    I hope this resolve your problem too.

     

    Regards,

    Luis Pinto

  • Friday, June 06, 2008 1:35 PMxatomic Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi everyone

    It looks like disaster has struck again on this issue..having innocently installed the SP1 after automatic update and woila..my computer cannot boot up. All this coming from the 'latest, so called more reliable and secured new O/S from Microsoft..." The worst thing is its coming frm themselves instead of a 3rd party vendor..

    sigh..

    Initially I tried the steps replacing the selected files suggested by Digitallica and it worked, although the same stupid SP1 tried to install again and i managed to skip that and can use my computer. The main problem is that my audio has failed to work, even i reinstall the driver (built-in Mobo, Realtek).

    The first thing I wanna do is is to get rid of this SP1 but i cant. Its not even in Installed Updates. And the automatic update keep downloading the SP1 and saying its installed (when its not). So I downloaded the standalone SP1 and tried to install, but it failed. So now I can't take it out nor install it. wtf


    And when i restarted my computer again, it prompt the same error again. I repeated all the steps previously but it failed. Then i tried replacing the ntoskrnl.exe file and then Pshed.ddl, tcpip.sys and ntfs.sys. Then the blue screen of death came.

    So anyone has a new solution so far? And since this is so common, does Microsoft has an official solution yet to this issue? I really don't want to go the path of doing a clean install..need my data..
    or anyone has a tip or two on how to do a vista reinstall without losing the data?


  • Tuesday, June 10, 2008 1:08 AMckistnerq Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    So, thank you for all of your knowledge on how to fix their problem.  It still however does not work for me.  The system will still not boot up with the boot disc (32 bit), hence I do not have access to the files I need to replace.  Do you know of any other way to boot to repair mode?  Any help would be great.  Thanks again. 

  • Thursday, June 12, 2008 12:39 AMHyphyBayBoy Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Edit: IMPORTANT UPDATES!!!! (Wednesday, June 12, 2008, 6:22PM PT)
    Xatomic!
    Many thanks for pointing this out. I have edited my previous post, but left the steps I did to get Vista back up. Digitallica's Fix only helped the solution by allowing me to boot into Vista and back up all of my files before they were gone for good. I knew that something would come back later to bite me in the butt. And it surely did. After another restart of Vista i found that my Realtek Audio sound driver were missing. Even after a reinstall of updated drivers, nothing seemed to be working. There were a forums online discussing the problem of missing audio drivers after a SP1 update, so it wasn't just me. It was really a widespread problem and there didn't seem to be a fix (some of you may have experienced this problem.
    And in the end, I chose to clean reinstall Vista to avoid any possible leftover SP1 residue. It worked out better that way and I was able to play my DX10 games again. Only this time, I would be careful and deliberate about what updates Windows would install (Changed option to No Downloads and No Install Updates Unless I SAY SO, lol).

    Keep in mind that I did NOT yet try to install the standalone sp1 update after a clean install of vista. I have been scared to do so because I do not want to go through all of this again. I want confirmation that it wont corrupt my files.

    Beat yeah, thats it in a nutshell. Surely Micro$oft will have to face the repurcussions of this, as it has caused many to suffer and panic.

    For anyone who happened read my previous post, I apologize for sounding the victory trumpets too soon. My mistake. It wasn't a "miracle solution" it was just a temporary fix. Xatomic, thanks again, and I hope you won't come across any more problems of this sort. If something does come up, make sure to come back to this thread to share your experience.
    It will be a great help to everyone.

    -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    I cannot express enough gratitude for you solution, Digitallica!
    And many thanks to Koben Haven as well!

    Let me say first that I have been WRACKING my mind all week with this "ntoskrl.exe missing or corrupt" nonsense.
    And yes, the origin of the problem was definitely a botched Vista SP1 update. (For shame, Micro$oft)

    When I saw that error message pop up after automatically updating, I panicked.
    However, I was fortunate enough to have previously installed a dual-boot OS of Vista 64 and XP,
    so when I found out that my Vista was corrupted and I couldn't get back on at all,
    thank god at least I had the dependable and reliable XP to fall back on.
    But I still wanted my Vista to play DX10 games on.

    So I looked online and in forums for a solution to this problem. Like many, I did not want to clean install Vista with so much data lost. There were many threads about this topic but none of them were any help to allieviating this problem. Nothing seemed to be helping and I was about to give up all hope.

    I don't know how many times I read over and over these instructions from Digitallica. But they finally make sense to me.

    This is exactly what I did to get my Vista back up and working:

    1. I followed Digitallica's above instructions and used my Vista Boot DVD to enter the command prompt.
    2. In the command prompt I typed in notepad.exe to bring up Notepad.
    3. From Notepad, I went to Open and was able to see my files again in icon form. This was easier for me than working in command prompt.
    4. From there I went to My Computer/C:\drive/Windows32.
    5. I backed up all of the files listed from the System32 and System32/Drivers folder,
    6. Then I went into the X:\ drive from the Vista DVD and got inside its Windows System32 folder.
    7. I copied the files that needed to be replaced from the list with one difference.
    I found out from a restart that I needed to replace ataport.sys as well.
    (This may not apply to everyone, it did for me though)
    8. So after backing up the existing files and replacing them with the old ones from the X:\ drive of the Vista DVD.
    I rebooted.
    9. And VOILA! Vista was back and running.

    The first thing up was the the last stages of that blasted SP1 update.

    In the end, this was an invaluable asset in deed and helped my computer back on its feet rather than leaving it dead in the cold.

    Again, I advise anyone who is able to boot up again into Vista to back up ALL their data and do a clean install of Vista, avoiding the SP1 Auto Update (I turned my auto updates off). It's just for the better and you won't regret it.

    Many thanks to everyone who contributed to this thread. We need to get this out to as many people as possible. I will already be going on other forums and posting the link to this thread in hopes of saving as many people from this as possible. It's not too late to help out others in need. That's the importance of help forums, they should never be outdated as there is always constant need, even for the oldest of problems.

    I hope that you all may find this advice helpful and that you will finally be able to get over this problem. If anyone needs help, feel free to contact me at hyphybayboy@hotmail.com. I will do my best to help you.

    GOOD LUCK TO ALL!

    Peace, I'm out!


    "Most of the important things in the world have been accomplished by people who have kept on trying when there seemed to be no hope at all..."



  • Thursday, June 12, 2008 8:14 AMxatomic Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    HyphyBayBoy, the problem might come again coz it is not cleaned up yet. That was what happened to me. Better backup all your data first coz it might screw up anytime.

    I gave up finding solutions to this. Coz of this I have to go out and buy the SATA-to-USB connector to transfer my data to my laptop first before i reinstall vista...then first thing after a clean install, i install the SP1 standalone. It works fine like this

    The blardy SP1 installation takes even longer than a clean Vista install..

    i m having issues wt the application fonts being blur..no idea is it the graphic driver or vista..

  • Friday, June 13, 2008 1:49 AMHyphyBayBoy Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello again, Xatomic.

    I know what you mean about the SP1 installation taking longer than a clean Vista install, its true.

    I still haven't yet updated to SP1 (even the standalone) for fear of repeating the same problems. Can you confirm that it is working correctly and without problems?

    For now I am trusting my gut instinct and professional help online and sticking to a non-SP1 vista.
    I'd rather have a stable working Vista OS with no SP1, since I only use it to install and play games.
    I am running a dual-boot os with XP as my MAIN operating system. And I am glad to have this to fall back on otherwise I would only have a non-working Vista. I know this does not apply to everyone since almost all new computers and laptops come with vista already installed..

    For those who haven't, I highly recommend setting up a dual-boot os with Vista/XP. It will save you in emergencies like this when Vista goes down. Easy to back up stuff if the hard drive(s) are partitioned correctly.

    Also on an important note, a clean install of vista backs up all old data from your old vista install into a folder called Windows.Old. You won't be able to boot into it, but the files will be there (sometimes I thought that was a pretty genius add-on from Vista.

    As for the application fonts being blurry... I'm not so sure what could be causing that. If you suspect its the graphics driver, make sure to update it if you haven't already. If it's Vista, then.... Vista is just being Vista. Lol, no but really keep looking online for help, surely something will come up. I never got that problem. But with the all its problems and incompatibility issues aside, Vista can look beautiful. I especially like the translucent black menu theme and DreamScene background! Also that quick 3d window changer (windows+tab) is pretty nifty.

    Here's an acronym joke I saw somewhere on the internet.

    V - Viruses
     I - Intruders
    S - Spyware
    T - Trojans
    A - Adware

    i know its not true, but I thought it was funny when I saw it. (Don't hunt me down, Micro$oft )

    Good Luck Everyone!

    Peace!

    "Never give up. Never surrender. That, is Spartan law..."

    **MeGaTrOn**
    EVGA 780i SLI Motherboard
    Intel Core 2 Extreme QX9650 3 Ghz
    EVGA Nvidia 8800GT 512MB
    4 GB OCZ Sli-Ready Ram
    150GB 10,000rpm Western Digital Raptor X Hard Drive
    Sony DVD/CD Drive, etc. etc.
    Dualboot: Vista 64-bit Ultimate/XP Pro

  • Friday, June 13, 2008 2:56 AMxatomic Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Have fixed the blur font issue...its coz i use higher DPI and u have to select the 'use custom DPI with windows xp scaling' option or something like tat..

    Yup, that was what happened to me...no sound on my Realtek after that, then i tried to install the standalone sp1 and it got screwed up.

    Anyway after i did a clean install, the first thing i did is install the standalone sp1. And so far, it works fine and the SP1 word is stamped on the version of Vista i m using now Smile

    Good luck buddy

  • Friday, June 20, 2008 7:06 AMJakeLepeg Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Wow again, thank God for people like you. I will try this tonight, I had just about given up and was going to re-format tonight.

     

    John

     

  • Friday, June 20, 2008 7:28 AMGavCol Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Jeez....... I am still surprised so many people were having this problem for so long.  I started the thread in Dec and people are still having so many variations of causes ending in the same problem even after SP1 was released

    Glad so many people were eventually able to find a solution.

    What a messy problem to fix.

    Gavin
  • Sunday, June 22, 2008 1:44 PMsorin_m Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    hi

     

    I have the same problem with that missing file ntoskrnl.exe, but i'm afraid that I can't run Repair Computer because when I bought the notebook (hp pavillion) I didn`t received any CD with the Windows. But I heard from someone that may exist a hidden partition where is a Windows copy. Does anyone know how can I acces that partition without a CD to repair my notebook ? Or where could find that kind of CD ? I mention that I already have a licensed Windows Vista Home Basic.


     

    Thank you !

  • Monday, June 23, 2008 7:13 AMDeseas Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I also have the same problem


    Is the
    Windows DVD The full Windows Vista Business CD or is it the Syatem Recovery DVD?... because when I bought my laptop.. it only comes with the System Recovery DVD as my laptop has already been preinstalled with Windows Vista Business...
  • Monday, June 23, 2008 4:18 PMsorin_m Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    you can Repair the computer only with the Recovery Disk CD. But I didn't received any of them (OS CD or Recovery Disk CD) but I don't know how could I Repair the Computer from my Recovery Disk partition, without having a CD. 

  • Monday, June 23, 2008 4:50 PMJohn Gray [MSFT]4 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Sorin:

     

    Please contact Microsoft Customer Support for the missing ntoskrnl and/or stop 0xC0000098 error messages. They can help with restoring the system.  We still do not konw the cause of this, we suspect that it has something to do with dual-boot systems and/or with something holding a file lock on the kernel during restart.  We had a small batch of these reported in March and early April when the Vista SP1 was first released, but have had almost no support calls on this issue since then, so the suspicion is that it's something unique to enthusiasts who are likely to be the first ones to install the SP directly from the WU sites. 

     

     

    From Anthony's original posting:

     

    Windows Vista customers are entitled to no-fee support for issues that relate to the SP1 update from Microsoft Help & Support until March 18, 2009. Microsoft Help & Support provides you with email, chat, or telephone support where you can talk to a Microsoft Support Agent to assist in troubleshooting your installation issue. 

     

    Please click on this link and open up a case with our product support services teams:

    https://support.microsoft.com/oas/default.aspx?prid=11274.

     

    Thank you for taking the time and we look forward to hearing from you.
    If you have a problem accessing the above link, please:

    1. Click on the “Contact a Support Professional” link on the left side.
    2. Click to choose Windows Vista Service Pack 1 (All Languages).
    3. Now you should be at the Support Page that fits your IE Language settings.

     

  • Monday, June 23, 2008 8:11 PMDiGiTaLLiCa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
     John Gray [MSFT] wrote:

    Sorin:

     

    Please contact Microsoft Customer Support for the missing ntoskrnl and/or stop 0xC0000098 error messages. They can help with restoring the system.  We still do not konw the cause of this, we suspect that it has something to do with dual-boot systems and/or with something holding a file lock on the kernel during restart.  We had a small batch of these reported in March and early April when the Vista SP1 was first released, but have had almost no support calls on this issue since then, so the suspicion is that it's something unique to enthusiasts who are likely to be the first ones to install the SP directly from the WU sites. 

     

     

    From Anthony's original posting:

     

    Windows Vista customers are entitled to no-fee support for issues that relate to the SP1 update from Microsoft Help & Support until March 18, 2009. Microsoft Help & Support provides you with email, chat, or telephone support where you can talk to a Microsoft Support Agent to assist in troubleshooting your installation issue. 

     

    Please click on this link and open up a case with our product support services teams:

    https://support.microsoft.com/oas/default.aspx?prid=11274.

     

    Thank you for taking the time and we look forward to hearing from you.
    If you have a problem accessing the above link, please:

    1. Click on the “Contact a Support Professional” link on the left side.
    2. Click to choose Windows Vista Service Pack 1 (All Languages).
    3. Now you should be at the Support Page that fits your IE Language settings.

     

     

     

    First of all, going to the "no-fee" support is a complete waste of time. When I first had this issue they were of no help at all. I'm not saying that they didn't want to help, I'm saying that they were NOT able to help. All their suggested solutions were useless because they had no clue what so ever about what caused the issue. Also, the guy handling my issue kept telling me to hold on for a minute while he looks for a possible solution, then all of a sudden the support session would end and I would be kicked out. So much for support.

     

    Secondly, So far I've not found any other working solutions except for the ones found in this thread and the other one I started. So you're definatly going to need a Windows Vista installation DVD to go through with the repair steps. It doesn't have to be the one you used for the install, any installation DVD will do because you're just going to use the repair tools. So anyone missing their own DVD can borrow one from a friend or something.

     

    Finally, IT IS NOT A DUAL BOOT PROBLEM, and It's definatly not the user's fault IN ANY POSSIBLE WAY. I didn't have a dual boot configuration when my PC failed to boot. The problem is due to a faulty install process due to a crappy SP1 installer. MS can deny that all they want, but there was nothing wrong with my system before installing SP1.

     

  • Tuesday, August 19, 2008 8:08 AMkamal555 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    i would like to congratulate all at microsooft for once again developing an operating system that is no better than the last one. please bring back windows 98 as it seems to be the only stable operating system that has stood the test of time. i have had this problem with ntoskrnl as well and all efforst to fix have failed, i have had to remove my hard drive and copy all files to another computer hard drive, and start formatting the computer. oh by the way i have not re-installed vista but LINUX instead. thank you for your non-support!!

    Kamal
  • Wednesday, September 17, 2008 12:27 AMimute247 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    It's a good thing i formated my dad's C drive before seeing this.....
  • Saturday, October 18, 2008 11:44 AMSHADOW-13 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
  • Friday, October 31, 2008 7:31 PMBarstool Pundit Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I am also working on this issue.

    I followed digitallica's steps which got me past the ntoskrnl.exe error, but moved me on to the ataport.sys error instead.

    Others in this thread have restored ataport.sys from this point and been able to boot. This is not working for me. I have restored the file and it still boots with the same error. As a result, I think it is not ataport.sys itself that is corrupt, but some other file it is trying to load.

    Does anyone know what other files I should try to restore to get ataport.sys to load properly?

  • Friday, October 31, 2008 9:11 PMBarstool Pundit Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
     frumpus wrote:
    I am also working on this issue.

    I followed digitallica's steps which got me past the ntoskrnl.exe error, but moved me on to the ataport.sys error instead.

    Others in this thread have restored ataport.sys from this point and been able to boot. This is not working for me. I have restored the file and it still boots with the same error. As a result, I think it is not ataport.sys itself that is corrupt, but some other file it is trying to load.

    Does anyone know what other files I should try to restore to get ataport.sys to load properly?



    tried a few other files that i found elsewhere. after restoring all of these files i moved past the ataport.sys file to now the same error on acpi.sys.

    acpi.sys
    atapi.sys
    ataport.sys
    battc.sys
    compbatt.sys
    disk.sys
    intelide.sys
    msisadrv.sys
    pci.sys
    pciidex.sys
    volmgr.sys
    volsnap.sys
    wmiacpi.sys

    not knowing what files could still be the problem i did the following out of pure desparation. basically backing up and restoring every .sys file in the drivers folder.

    Boot to Vista DVD and go to the command prompt from the repair menu.

    c:
    cd windows\system32\drivers
    md sysbackup
    copy *.sys .\sysbackup
    x:
    cd windows\system32\drivers
    copy *.sys c:\windows\system32\drivers
    A

    (the A just tells it to overwrite all files.)

    surely that would fix it

    WRONG

    Still the 0xc0000098 error on ACPI.SYS

    Why is this thread marked 'answered' when it clearly is not?

    Also not recommending the free microsoft support. They will waste 2 or 3 hours of your time making you try things you have already tried and in the end they tell you to reinstall Vista.

    If I have to reinstall an operating system you can bet it won't be Vista.
  • Wednesday, December 03, 2008 2:32 AMoutthink Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    "We had a small batch of these reported in March and early April when the Vista SP1 was first released, but have had almost no support calls on this issue since then, so the suspicion is that it's something unique to enthusiasts who are likely to be the first ones to install the SP directly from the WU sites. "

     

    Sorry to disillusion you, but you have a problem with SP1.  Mine was an install done with automatic updates. I just recently took the time to reinstall Vista on the PC in question after the OS died last April.  Then low and behold, after all the trouble of doing the fresh install, installing all the drivers an automatic update of SP1 killed the PC again.

     

    I am once again spending an evening restoring the Operating System instead of spending time with my family.

  • Sunday, December 07, 2008 6:46 PMJeremy_germ9 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I'm running vista home premium x64 on my self-assembled system.  Automatic updates screwed me up the same way everyone here has already experienced way back in spring 08'.  I used DVD to repair the existing Vista installation, and promptly turned OFF automatic updates... the helpfull (annoying) balloon reminding me everyday that i had turned off auto-update was tolerrable... but alas, the day has come that SP1 is required to continue.   GTA IV won't run on vista without SP1. 

    I'm currently trying to get sp1 installed without the ntoskrnl.exe missing error bullcrap. 

    1.  Install SP1 standalone (not auto update), although I can't be sure that this will make THE difference
    2.  Error ntoskrnl.exe
    3.  repair vista using DVD
    4.  run cmd from vista with admin privileges
    5.  run chkdsk on system drive... found 5 files not indexed
    6.  try installing sp1 standalone again....

    I'll post my success when, and if, that happens.

  • Monday, December 08, 2008 6:02 AMJeremy_germ9 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    failure.

    I think I managed to get really close though... but I really have no idea.

    I spent 3 hours online chat with microsoft support.  Even had the MS support agent take control of my computer and do some stuff..  Eventually he ended up elevating my case and scheduling a call back.

    I followed DiGiTaLLiCa's instructions, but I'm not sure that they apply for my because I'm running x64 version, and I don't see the two
    halacpi.dll, and halmacpi.dll in my system32 folder. 

    I also ran into the ataport.sys file needing to be replaced.

    This is how the process has been going for me.  I can't boot to command prompt after attempting to install sp1.  Even using the DVD to boot, because I don't have that option for Repair.  Fortunattly I can repair my Vista installation using the DVD and it seems to work everytime, only It does a system restore back to the point right before sp1 installation, back to square one.  I happen to have Fedora installed on a second drive, so what I've done is copy the files that DiGiTaLLiCa listed as needing to be replaced.  Then I'll install the sp1 and when the installer reboots the system, I'll boot with Fedora, copy the old files into the system32 and system32\drivers folders and reboot, allowing the installer to pick up where it left off.  The installer will first "Configure updates step 1" to "step2" to 100%, then reboot ( and I do the move copy the old files inbetween)... Windows VIsta will start (!! Awsome!! that didtn' happen before! Thanks DiGiTaLLiCa!) .. and the installer will continue with step 3 and go to 100%... Then it starts "Installing Service Pack 1 step 1" to "step 2" to 100%, but wants to restart again before step 3.  I do the same thing as before.. copy the old files "hal.dll, ntoskrnl.exe, acpi.sys... etc" EXCEPT this time I get a new corrupted file:  PSHED.dll.!

    Has anyone had to replace PSHED.dll?  Well... this process is consuming sooo much time.  Everytime I discover that I need to use one of the "old" files that because of sp1 installer has become corrupted, I need to let the DVD repair Vista (restore) which can take anywhere from 10-45min. 
     
    I'm thinking that I should make copies of all the entire windows folder, so that I can move some "old" copies into the "new sp1" vista when ever the boot up says that the file is either missing or corrupted.

    I'll try that tomorrow... hopefully it will work and I won't have to let the call back from Microsoft take over and go throught their troubleshooting routines that so far only prove that the Service Pack 1 installer doesn't work for me... which IS NOT COOL.  Or maybe they'll call back with a quick fix!  I'll keep my fingers crossed.


    • Proposed As Answer byJeremy_germ9 Friday, December 12, 2008 1:24 PM
    •  
  • Friday, December 12, 2008 1:35 PMJeremy_germ9 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    I guess I'm the only one that is still having this problem. 

    Fortunatly, its fixed!

    MS Support was very helpful, they get a bad wrap sometimes I think.

    Using my windows DVD I 'updated' my existing Vista install... which is like doing a fresh install over the top of vista I guess, nice thing is I didn't have to reinstall any software (except some minor driver issues afterwards.)

    I also updated my BIOS... which was a little nervewreaking.  I downloaded the latest .bin file from Asus that was listed as the most recent BIOS for my model.  Using the, pretty but useless, GUI update through windows was a waste.  So I tried EZ Flash via the bios menu.  The switch seemed to work fine untill the reboot came.  Nothing.  Blank monitor.  no boot.  jeeezuus!  my hole keeps getting deeper here!  So I unplug the power cord, and pop out the little Mobo hearing aid battery... an put it back.. and then it boots.. "oh thank the gods".  The wild thing is, I go to check my bios version and its the updated one!.. what the heck.  I thought cutting the power reverts the eeprom back to factory defaults.. and onlly some of the the time at that!  I knew I was lucky.. but that lucky?

    Windows boots up, and I try to install SP1 via the standalone download (After installing all previous updates).  It works!  holy ____.  Thanks Nora!
    • Proposed As Answer byJeremy_germ9 Friday, December 12, 2008 1:36 PM
    •  
  • Sunday, December 28, 2008 12:53 AMhbvic Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    wont start after install...0xc0000098
  • Tuesday, January 13, 2009 3:49 AMspind0c Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Good God!!

    When you "updated" your install, did just do it like you were doing a "clean" install or were you given the option of "repairing" the existing install like you could in XP.

    Just a bit nervous, as the installer says that it will wipe out everything and put the old info in a windows.old dir.

    Although, like DiGiTaLLiCa! I miss my DX10 games, I have my XP install (SP2 thank you, until I get Vista back up) and a MAC to keep me going.  I'm really trying to avoid a fresh install as most of my software is in storage.  Besides I like a challenge!

    As a side note,  I work on PC's for a living and this is the first SP1 issue I have ever had (out of more than 100 installs).......figures it would be on my own PC  :+)
  • Wednesday, March 11, 2009 11:53 AMtumblez Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I know I'm a little late to offer this person a fix, it is 3/11/2009, but I offer it in hopes that those other unfortunate souls who have delayed installing SP1 until just now like I have, will now have a solution to their problem.  I like my solution as it did not require me to reinstall my OS, which not only risks losing personal data, but is guaranteed to wipe out all my settings to date, and force me to reload all my programs that I have installed over the past couple of years.  Yuck!  Don't want to do that.

    I successfully overcame this problem on my laptop which is a dual boot with Windows Ultimate (32 bit) and XP Professional.

    Up front, I first tried calling MS, but because I have an OEM version of Windows Ultimate, they were going to charge me for support.  Forget that.

    Then I called Gateway since my laptop was under warranty.  The connection to India or Pakistan was horrible, and the advice they gave me was even more horrible, restore my laptop from scratch.  Forget that!

    What I did was the following:

    1) You DON'T want to use Windows Update to reinstall SP1, but instead download the standalone release:   http://www.microsoft.com/downloads/details.aspx?FamilyId=B0C7136D-5EBB-413B-89C9-CB3D06D12674&displaylang=en

    2) Disabled my AntiVirus software, and shut down any other windows that need not be running.  Also, disconnected all unneeded USB connections.

    3) Executed the file I downloaded from the MS url in step 1).  It gets past installing stage 2 of 3. 
     
    4)  When it asks to restart the laptop, I instead chose to shutdown.

    5) Laptop shut down without going through the SP1 step installs.  Very good.

    6)  Power back up, press F8 and choose to go into safemode.

    7)  At this time, the SP1 install displays it is in stage 3 of 3.  Very slow at this point, I went to bed because it seemed to be locked on 38% complete and was going nowhere in a hurry.

    8) Got some much needed sleep for me.  :)

    9) Awoke in the morning and found my PC up and running.

    10) Looked at my Windows Updates, did not find the SP1 still showing as needing to update.  Very good sign I had this problem licked.

    11) Shutdown my PC and it didn't go through the SP1 install anymore.  Another good sign.

    12) Started up my PC and it booted up, just fine.  Problem resolved!!!

    13) Checked my BigFix program, and where I had nearly 53 prior problems, all of them were now resolved.  This was a bonus for me.
  • Friday, April 17, 2009 12:10 PMcleverman Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello,

    peterdoo solved it for me. The BIOS translation explanation sounded like it was just the kind of thing that can go wrong and the solution was easy to try (I thought) assuming Chkdsk and the defrag program is on a recovery CD. My hard disc was only 55% filled (127Gb used out of 232Gb) though.

    By the way, I had the ntoskrnl.exe 0xc0000098 error after a routine Micorosft Update install not some big SP install<. You can imagine the frustration! With a dead machine I went down the route of recovery CD which I don't have so I eventually found this useful snippet by Long Zheng http://www.istartedsomething.com/20080324/recover-create-a-recovery-disc-vista-sp1-rtm/

    But be aware that the creation of the recovery CD needs to see your VISTA installation CD to proceed so that was in fact a dead end for me at the moment.

    In the end I installed the hard disk with the broken Vista in another system which was running XP. I tried chkdsk /F and whilst that did fix some problems the disk still wouldn't boot back in its correct system. So I then defragged it back on the XP machine. I figured this was low risk as it is just working at NTFS level moving files around. It took about 6 hours for 127Gb used space but did pack things well. Previously data was spread across about the first 75% of the space but after it was nicely packed to about the 50% mark.

    The defragged hard disc booted fine back on the Vista machine. PHEW! If this BIOS addressing is really the issue then with a packed disc any updated files will probably get located on the end of the space and I'll get this issue again and again so hence the interest to get a recovery CD working.

    Thanks all