ntoskrnl HELP Reboot is out.

L

lambert

Hi. This is Lambert from Rome. I'm sorry for my English
language.

I need your help.

I have a computer with Pentium 4 3,06Mhz with Hyper-
Threading and I didn't know that I couldn't use the
booteditor program for bootscreens (that I've erased
immediately) because it didn't figure. When I saw that
the computer could start and finish in the right way, but
it couldn't do the reboot anymore, I've deleted or
replaced some files and the computer was blocked-up
definitely.

I've reinstalled XP from CdRom only with option "r" =ok
to don't lose my files, then upgrade= ok, patch Q811493
(5.1.2600.1151) =ok, sfc /scannow (sometimes it has red
the cd-rom) =ok,

...so everything's ok, but the restart (reboot) loops.


Support from Microsoft isn't possible: Windows registered
OEM

Support from the company that sold me the computer isn't
possible, cause it there isn't anymore.

I don't know no one that helps me. My friends advise me
to format and reinstalling everything, but I wouldn't do
it.

Now, my files-situation is:

ntoskrnl c:\i386 1998 Kbyte version file:
5.1.2600.1106 original name:
ntoskrnl !?!? (righ-click and property)

ntoskrnl c:\windows\system32 1852Kbyte version file:
5.1.2600.1151 original name: ntkrnlmp

ntoskrnl c:\wind..\driver cache\i386 1885Kb vers.files
5.1.2600.1151 original name: ntoskrnl


ntkrnlpa c:\i386 1879 Kbyte version file:
5.1.2600.1106 original name: ntkrpamp

ntkrnlpa c:\windows\system32 1880Kbyte version file:
5.1.2600.1151 original name: ntkrpamp

ntkrnlpa c:\windows\driver cache\i386 1908Kb vers.file:
5.1.2600.1151


ntkrnlmp c:\windows\driver cache\i386 1852Kb vers.file:
5.1.2600.1151


ntkrpamp c:\windows\driver cache\i386 1880Kb vers.file:
5.1.2600.1151


Version operating system: 5.1.2600.1106 (sp1)

Upgrade Q811493: ok

Contents di c:\i386\sp1.cab
Ntoskrnl 1998 Kbyte version file: 5.1.2600.1106
Ntkrnlpa 1906 Kbyte version file: 5.1.2600.1106
Ntkrnlmp 1851 Kbyte version file: 5.1.2600.1106
Ntkrpamp 1879 Kbyte version file: 5.1.2600.1106

Contents di c:\windows\driver cache\i386\sp1.cab
Ntoskrnl 1998 Kbyte version file: 5.1.2600.1106
Ntkrnlpa 1906 Kbyte version file: 5.1.2600.1106
Ntkrnlmp 1851 Kbyte version file: 5.1.2600.1106
Ntkrpamp 1879 Kbyte version file: 5.1.2600.1106

Folders summary:
c:\i386 = ntoskrnl , ntkrnlpa and ntkrnlmp (File EX_
creation:today)
c:\windows\system32 = ntoskrnl and ntkrnlpa
c:\windows\driver cache\i386 = idem + ntkrnlmp e ntkrpamp

I really don't know! Can you help me or tell me where I
can ask for some advises? Or the problem is into the
windows-register?

I seen in web the "cumulative 820128 patchs"

Thank's for your patient and for your disponibility. I'm
waiting for your answer.

Italy GMT+1
Hi All
 
R

Rich Barry

Lambert, did the Repair Install work and then you added some winupdates
and after that you have a reboot loop?
 
L

lambert

also.
1)install and use programm
2)reboot loop
3)certainly my wrong action (replace and/or delete files)
4)system down. no start
5)reinstalling xp and updates
6)start system ok,
reboot loop again and always
 
A

Alex Nichol

lambert said:
Now, my files-situation is:

ntoskrnl c:\i386 1998 Kbyte version file:
5.1.2600.1106 original name:
ntoskrnl !?!? (righ-click and property)

ntoskrnl c:\windows\system32 1852Kbyte version file:
5.1.2600.1151 original name: ntkrnlmp

Set the BIOS to boot CD before Hard Disk. Boot the XP CD and, instead
of Setup, take the immediate R for Repair. (Borrow an XP CD if
necessary) Assume any password requested is blank, and TAB over. Give

Copy c:\i386\ntoskrnl.exe c:\windows\system32\ntoskrnl.exe

to replace the one that is there. This happened to someone else the
other day - the upgraded version 1151 from Q811493 caused this looping,
and going back to 1106 cured it. That patch is only important to
corporate networks concerned about a possible disaffected employee
prompting himself into full control of systems


A query: Is this machine a dual processor one? Or one that uses a
Pentium 4 recent version 'with hyperthreading'? That 'original name
ntkrnlmp indicates that it is, and I would like to know if the problem
has been an incorrect installation of the patch
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top