UBCD4Win Forums > NTOSKRNL.EXE" not found

distro

Mar 10 2008, 10:27 PM

Warning: File "C:\002-BootCD\UBCD4Win\BartPE\I386\SYSTEM32\NTOSKRNL.EXE" not found

I've read previous posts, but none seems to apply *exactly*.
I'm using an XP Pro CD with Service Pack 2 included.
I copied my XP Pro CD to my system HD.
My system runs XP Pro + Service Pack 2.
I run the builder, it creates an ISO file, but with the above warning.
I burned the ISO to disk, but when I try to boot the system from it, as a test,
the boot gets to the first menu, and after I select boot UBCD4WIN,
the system locks up in a blue screen error message.

NTOSKRNL.EXE is visible on the original XP Pro with Service Pack 2 CD.
NTOSKRNL.EXE is visible in C:\002-BootCD\XPCD, the file folder on the system HD.
I turned off my Internet connection.
I turned of Sysmantec Anti-Virus.

I've been wrestling with this for two days. Any help would be greatly appreciated.
I can post the builder log, if that would help.

Thanks, distro

rdsok

Mar 10 2008, 10:31 PM

Try building in SAFE MODE ...

distro

Mar 11 2008, 04:48 PM

QUOTE (rdsok @ Mar 10 2008, 10:31 PM)

Try building in SAFE MODE ...

I saw the references to running in Safe Mode, but I didn't understand why Normal Mode would cause a problem.
I went ahead and booted into Safe Mode, ran the builder, and got exactly the same result:
Warning: File "C:\002-BootCD\UBCD4Win\BartPE\I386\SYSTEM32\NTOSKRNL.EXE" not found

The following processes are running while in Safe Mode:
taskmgr.exe
igfxsrvc.exe
explorer.exe
svchost.exe
svchost.exe
lsass.exe
services.exe
winlogon.exe
csrss.exe
smss.exe
System
System Idle Processes

Which of these is supposed to be the problem child?
It goes without saying that there are a lot more processes running in Normal Mode.

Thanks for the help, distro

rdsok

Mar 11 2008, 04:58 PM

The reason to use Safe mode is to ensure that your protection software is not getting in the way... Symantec is known to cause issues and doesn't tell the user that it blocked access to files etc.

distro

Mar 11 2008, 05:06 PM

QUOTE (rdsok @ Mar 11 2008, 04:58 PM)

The reason to use Safe mode is to ensure that your protection software is not getting in the way... Symantec is known to cause issues and doesn't tell the user that it blocked access to files etc.

I didn't see the Symantec icon in the System Tray when I ran in Safe Mode, so I didn't actually confirm that Symantec was not running.
Do you recognize the process, of the ones I listed, that is for the anti-virus?

Thanks again, distro

P.S. I went to http://www.processlibrary.com/directory/ and checked, it turns out that DefWatch.exe is a/the Symantec process.
It was *not* running while I was in Safe Mode.

...distro

cdob

Mar 11 2008, 05:38 PM

A bad slipstreamed XP SP2 may cause error NTOSKRNL.EXE.

Do you use OEM windows source files?

Try slipstream SP2 again.

distro

Mar 11 2008, 08:13 PM

>

QUOTE (cdob @ Mar 11 2008, 05:38 PM)

>A bad slipstreamed XP SP2 may cause error NTOSKRNL.EXE.
Why only ntoskrnl.exe?
If the slipstreamed copy of XP wasn't done right, wouldn't there be a plethora of errors?
Additionally, ntoskrnl.exe is present, in the folder, on the HD.
The builder message is that it can't be found, and it *is* there.

>Do you use OEM windows source files?
I'm using a copy of a VAR CD from MS.

>Try slipstream SP2 again.
>

Before I try a bunch of random solutions,
I would like to get a response from someone that has experienced this *exact* problem,
knows what happened, and knows the solution to it.

Thanks for the response, distro

pcuser

Mar 11 2008, 09:34 PM

QUOTE

Before I try a bunch of random solutions

Read what cdob wrote. It's not just some random idea that he had, it's straight from the pebuilder FAQ

QUOTE

When booting BartPE I get the following the error "File \i386\system32\ntoskrnl.exe could not be loaded. The error code is 14"

You did not slipstream your Service Pack to your Windows XP installation files correctly!
An easy way to check if you have slipstreamed correctly:
If you have slipstreamed Service Pack 2 to your installation files, view the file called drvindex.inf. There should be a line like CabFiles=SP2,driver in the version section.
If you have slipstreamed Service Pack 1 to your installation files, view the file called drvindex.inf. There should be a line like CabFiles=SP1,driver in the version section.
If the line does not have the SPn argument the slipstreaming was not succesfull!

If you have a non-english Windows XP and you have slipstreamed using PE Builder's (v3.1.4 and lower) slipstream option in the main menu you can also get this problem. This will be fixed in next PE Builder public release. For now, please slipstream the files yourself, see FAQ item 21.

cdob has been heavily involved in the PE community for a very long time being active in both development and level1 support on the forums so even if his suggestion happens to not work, it's definately in your best interest to give it a shot before doubting it.

BTW. He aslo asked if you're using OEM source files (which happens to be the only other known cause for this error that I know of).

Tom

rdsok

Mar 11 2008, 09:41 PM

QUOTE (distro @ Mar 11 2008, 08:13 PM)

Before I try a bunch of random solutions,
I would like to get a response from someone that has experienced this *exact* problem,
knows what happened, and knows the solution to it.

Thanks for the response, distro

Then I suggest you use the Forum Search if you are looking for similar issues but know this, that doesn't mean you will find the cause of yours as the cause of what others may have experienced... That is because there is never just one cause of a problem, computer problems are not that simple.

cdob is an expert in this field... there can't be a guarantee in a computer issues and only by you checking the suggestions givin can you find the cause of yours...

distro

Mar 11 2008, 10:16 PM

QUOTE (pcuser @ Mar 11 2008, 09:34 PM)

QUOTE

Before I try a bunch of random solutions

>Read what cdob wrote.It's not just some random idea that he had,it's straight from the pebuilder FAQ
I will read the pebuilder FAQ, more thoroughly. However, see below.

>>

QUOTE

When booting BartPE I get the following the error "File \i386\system32\ntoskrnl.exe could not be loaded. The error code is 14"
>Warning: File "C:\002-BootCD\UBCD4Win\BartPE\I386\SYSTEM32\NTOSKRNL.EXE" not found
The message "ntoskrnl.exe could not be loaded. The error code is 14" is *not * the same as NTOSKRNL.EXE" not found.

>You did not slipstream your Service Pack to your Windows XP installation files correctly!
I will check the disk, again. It currently works properly. What symptom should I see?

An easy way to check if you have slipstreamed correctly:
If you have slipstreamed Service Pack 2 to your installation files, view the file called drvindex.inf.
There should be a line like CabFiles=SP2,driver in the version section.
I will check this.

If you have slipstreamed Service Pack 1 to your installation files, view the file called drvindex.inf.
There should be a line like CabFiles=SP1,driver in the version section.
If the line does not have the SPn argument the slipstreaming was not succesfull!
I don't have SP1.

If you have a non-english Windows XP...
I don't have a non-English CD.

...and you have slipstreamed using PE Builder's (v3.1.4 and lower) slipstream option in the main menu you can also get this problem.
This will be fixed in next PE Builder public release. For now, please slipstream the files yourself, see FAQ item 21.

*I* didn't slipstream SP2, the Win XP CD already had SP2 on it.

>cdob has been heavily involved in the PE community for a very long time being active in both development and level1 support on the forums so even >if his suggestion happens to not work, it's definately in your best interest to give it a shot before doubting it.
I always look forward to assistance. While the word random seems to set off alarms, what it really means is that I'm looking for the answer to a difficult and complicated problem, and I perfer to have a reason for things I undertake. I don't doubt the credentials you have cited for cdod. I am happy to hear what he has to say and suggest. But the learning process means I have to ask why I'm doing something. I already looked at the FAQ's at the BartPE and UBCD4Win Web sites, and read through all the pertinent postings I could find in this forum. That is why I said .."I've read previous posts, but none seems to apply *exactly*.

BTW. He aslo asked if you're using OEM source files (which happens to be the only other known cause for this error that I know of).
See below.

Tom

>>Do you use OEM windows source files?
>I'm using a copy of a VAR CD from MS.

Thanks for the help, distro

pcuser

Mar 11 2008, 11:18 PM

If you're looking for a solution to your problem then I suggest trying what's already been recommended to you. If you're looking for a reason "why" then I suggest setting the debug switches in txtsetup.sif and hooking up another computer running a kernel debugger via a null-modem serial cable so you can hopefully trace the events that led up to the crash.

rdsok

Mar 11 2008, 11:44 PM

At this point... it sounds like your more likely cause is a corrupted file... this is also why cdob suggested that re-slipstreaming may be a solution in the event that it was corrupted during that process... if you didn't slipstream it, then there is some other cause of the corruption.

distro

Mar 12 2008, 03:39 PM

QUOTE (rdsok @ Mar 11 2008, 11:44 PM)

At this point... it sounds like your more likely cause is a corrupted file... this is also why cdob suggested that re-slipstreaming may be a solution in the event that it was corrupted during that process... if you didn't slipstream it, then there is some other cause of the corruption.

Yeah, I'm going to double check on my source CD. As I said, my understanding is that my guy, (the VAR), made a copy of his MS supplied original of XP Pro with SP2 already included. I'll know later in the day if that is correct. The only problem with the corruption diagnosis is that the file, with the proper name, exists, and is in the proper folder. Does the builder do some kind of file evaluation that eliminates corrupted files from use? If so, why the message about not being able to *locate*?

If my VAR used an original disk, then I'll try using the original disk, instead of my copy.
If my CD burner is funky, I overcame the copy errors manually, by copying the missing files from my Desktop system.
Originally I had 6 Errors and 1 Warning. I've already indicated the Warning.
The Error file were:
usbehci.sys
usbehci.sy
mstedit.dll
c_28603.nls
msctfime.ime
hccoin.dll
After supplying the missing files, and running the builder again, I'm down to the NT Kernel problem.

They are 37 background processes running while in Normal/Standard Mode, versus 12 in Safe Mode.
Having tried the builder in Safe Mode I was hoping that one of those I listed would turn out to be a well known culprit.

I'll know more later tonight.

Thanks for all the feedback, distro

stidyup

Mar 12 2008, 05:12 PM

Just because the file exists and you can see it doesn't mean that everything is OK.

I've installed MS Office at work and the copy I've got has a dodgy cab file which needs replacing nearly 90% of time, sometimes it copies to the hdd fine and installs but more often than not the Office installer can't find it and asks where it is. Once I overwrite it with another copy of the file the installer continues and everything is fine.

distro

Mar 28 2008, 03:59 PM

QUOTE (rdsok @ Mar 11 2008, 11:44 PM)

At this point... it sounds like your more likely cause is a corrupted file... this is also why cdob suggested that re-slipstreaming may be a solution in the event that it was corrupted during that process... if you didn't slipstream it, then there is some other cause of the corruption.

I've been working on getting resolution to this problem since your last post. The delay was in getting my VAR to provide the disks I used.
The 1st disk I used was a 3rd generation copy (and as it turns out, a bad copy).
We then moved up to a 2nd generation copy and it also was bad (too many scratches).
We then created a new 2nd generation copy fron the original MS disk.
I ran the builder (in SafeMode) with the newest disk, and Wham, Bam, Thank-You-Mam, I got a good build, no warnings and no errors. I booted with the new burn, and works-fine, lasts-a-long-time.
So, there you go. I burned a copy for my VAR (and he is very pleased) and a copy for myself. Cool.
Bottom line: I had a corrupted / bad / incomplete copy of Win XP SP2 when I started.
Using a complete / good copy made the process painless.

Thanks for all the help, distro (still learning the ropes)