Jump to content











Photo
- - - - -

Stop error 0xc0000098 in ntoskrnl.exe on booting


  • Please log in to reply
4 replies to this topic

#1 kvarkk

kvarkk

    Newbie

  • Members
  • 24 posts
  •  
    Russian Federation

Posted 03 August 2010 - 06:55 AM

Hi all,
I've made a VistaPE bootable flash drive using WinBuilder and VistaPE Core v.12 (RC1).
Vista SP2 x86 Enterprise was used as a source.
The project was built OK and I made a bootable USB pendrive using Grub4DOS.
I tried this pendrive on several computers and on each of them the result was the same: VistaPE starts booting, the desktop wallpaper is displayed for a moment and then the system crashes into a BSOD 0xc0000098 stating that the file ntoskrnl.exe is missing or corrupted.
I checked the vistape.wim file - it contains ntoskrnl.exe and the file is identical to one packed in boot.wim from the source.

Can anybody help me?

#2 theclam

theclam
  • Members
  • 4 posts
  •  
    United States

Posted 05 August 2010 - 06:27 AM

I have the same problem. If I use WAIK as a source, the problem goes away, but I miss all the goodies that need the Vista disc.

#3 kvarkk

kvarkk

    Newbie

  • Members
  • 24 posts
  •  
    Russian Federation

Posted 05 August 2010 - 06:52 AM

I have analyzed the compiled vistape.wim file and discovered that some system files in this package are outdated. Many of them are critical for OS - for example, halacpi.dll, halmacpi.dll, acpi.sys and ataport.sys. All these file were created in 2006 whereas in Vista SP2 source package the mentioned files are dated as of 2009.
The conclusion is: one of the project scripts copies system files from WAIK wimpe.wim archive instead of boot.wim.

#4 kvarkk

kvarkk

    Newbie

  • Members
  • 24 posts
  •  
    Russian Federation

Posted 05 August 2010 - 09:41 AM

In a hit-and-miss fashion I have discovered that the script "04-additional.script" overwrites original system files copied from Vista DVD source with older versions. Disabling this script caused my VistaPE to boot without any BSOD's.
But without additional files VistaPE doesn't work properly: PEnetCfg doesn't start due to a missing file, removable drives are not mounted and etc.

I can't understand where does the script 04-additional.script takes those outdated system files. I have replaced original C:\Program Files\Windows AIK\Tools\PETools\x86\WINPE.WIM file from Vista WAIK with a newer one from Windows 7 WAIK. The result was the same.

#5 kvarkk

kvarkk

    Newbie

  • Members
  • 24 posts
  •  
    Russian Federation

Posted 05 August 2010 - 11:45 AM

As it turned out the reason was simple: I just used and old project server - vistape.net/project.
I have selected the up-to-date project - vistape.winbuilder.net and built VistaPE with it. It boots fine now.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users