Forum Home
Press F1
Thread ID: 147322	2018-11-10 22:05:00	ntoskrnl.exe is corrupt...I cannot fix it	kioti (17360)	Press F1

Post ID	Timestamp	Content	User
1455505	2018-11-10 22:05:00	ntoskrnl.exe missing/corrupt My W7x64 Pro SP1 will not open to Desktop. After going through the POST motions the computer gets to the part where it should open to Desktop and all I get is a monitor screen with a white cursor. I have tried all I know to get it to open up but will just not do it. It was after trying all sorts of things from bootrec /fixmbr...bootrec /fixboot.....bcdboot c: \windows /l en-us.... used Easeus Partition Manager to create a bootable USB drive containing WinPE to get me into the W7 from booting to the WinPE drive and working in there to attempt fixing the problem....all to no avail. Then as the D and E drives were 'locked' because the permissions had been changed and I had to take ownership of them to make them show as a hard drive should when viewed in This PC or My Computer. All they were showing was a Drive letter before I changed permissions. Apart from the CMD Prompts I have tried here are others and they fail...I also say why I think they failed to fix the problem. W7 Installation DVD: Repair computer option fails says cannot use the disk to repair the version of OS installed (probably because installed has SP1) System Repair disk gets me into and allows CMD Prompts, the bootrec /fixmbr says completed...then when I use the bootrec /fixboot command line it was saying 'Element not found' (that was before I realised the D and E Drives were inaccessible and I then performed the change permissions) After gaining access to the D and E drives the CMD Prompts still failed to get the computer to open to Desktop. I used Easeus Home Partition Manager to Rebuild MBR which it showed as Done and still no go go for me. It was not until the very end that it became known to me that ntoskrnl.exe is missing and I cannot get it into the System from any W7 OS/ System Repair Discs that I possess. So, can anyone tell me how I am going to get that system file back into my W7x64 Pro SP1 installation and get it opening to desktop? Will be greatly appreciated as I have had the 'Current' instal on computer for about 4-5years and I'm sure you will understand my reluctance to have to start from Fresh Install of it. How did it all come to happen? I think it was the following that caused it: I decided to get up to date and installed W10 Pro v1709 to a 80GB HDD and that filled rather fast in a couple of weeks. With 13GB Space remaining and lots more programs/apps to install I decided to 'Clone' the W10 to a 1TB Sata HDD I used Easeus Partition Master Tech Edition to Clone the C Drive to the 1TB Unallocated space HDD. (Which was a disaster.... It opened at a snails pace, had only created a 75GB C drive and the remaining 900GB space was unallocated and I couldn't enlarge the C drive into the unallocated space because for some reason the Clone operation had created 2 System Recovery partitions: one at the start and another in-between the 75GB C Partition and the unallocated space (????) So I wiped it and will do fresh install of 1709 version and have it upgrade to the 1803 I have now in the C Drive. It was immediately after I had performed the Clone W7 task that my W7 instal wouldn't open, about 1 week ago. Since then I have been using W10 and getting accustomed to it. I would still like to have the use of my W7 while I get the hang of W10. I ignored the voice of experience in my head telling me to disconnect all internal/external HDD's apart from the Source W7 C Drive and the receiving 1TB unallocated drive before I performed the 'Clone' task. As has happened to me once /twice before a few years ago, I ended up with a screwed MBR on a Drive. That's about it. Any help to get my problem solved much appreciated. A couple of questions..... If I copy the W7 DVD to ISO and then create a new DVD of it with SP1 included will that get the ntoskrnl.exe into the system?..... Can I make a CD from the W7 SP1 ISO I have and use that on its own to get the ntoskrnl.exe back into the system from a CMD Prompt? Thanks in advance. Edit: All OS's are installed on individual HDD's.... no Dual boot etc. Garry edit: I have very little knowledge on changing permissions in Security for hard drives etc but I found 1 good video for it on the web and I add the URL here, it helped me to get the D and E drives accessible. Perhaps it might help someone else. www.youtube.com Gigabyte GA-78LMT S2P... AMD Athlon II x4 630... 8GB DDR 3 Crucial Ballistix Sport PCS 14900... Nvidia GForce GT 710... CoolerMaster RS 550 PCAR-E3... 3xInternal Sata2 HDD+4 external 4TB Drives	kioti (17360)
1455506	2018-11-11 00:02:00	Start again get 1803 if you want Win10, with the mediacreation tool. Use something like rufus to put the ISO on a flash drive. Then boot from it Then if you've got more than 1 hdd disconnect the others first. Make sure you delete all partitions on the hdd you're installing windows on first. Dont install over what's already on it	Speedy Gonzales (78)
1455507	2018-11-11 03:39:00	Start again get 1803 if you want Win10, with the mediacreation tool. Use something like rufus to put the ISO on a flash drive. Then boot from it Then if you've got more than 1 hdd disconnect the others first. Make sure you delete all partitions on the hdd you're installing windows on first. Dont install over what's already on it Speedy Gonzales, thanks. I have the 1TB Hdd ready to instal W10 1709 because that is the ISO that I have of it. It will upgrade to 1803 from Windows update feature as it has done on the 80GB HDD it is on at the mo. I guess I could go to Windows Download and DL the 1803 version of W10. I Dl's the 1809 version from Microsoft One Group but apparently it is buggy, so that can stay in the backroom til a stable version is released. I will look into Dl'ing the 1803 from MS. Yeah, apart from the destination HDD I'll disconnect ALL HDD's when I do the W10 install. Thanks Kioti PS: It is the W7 OS that is the problem with the corrupt ntoskrnl.exe. I'm using W10 1803 now. I would like to have the ole GF W7 still at hand :D...Cheers :D	kioti (17360)
1455508	2018-11-11 03:53:00	I have the 1803 mediacreation tool...I will try that to DL the 1803. Thanks	kioti (17360)
1455509	2018-11-11 06:20:00	If you want 2 OS's do you want to dual boot?? If you do install Win7 first. Leave 2 hdd's connected. Update Win7 after first. Then install Win10 1803 on the other. Next time you want to use either. Turn the computer on and select the OS you want to use If the mobo supports UEFI / has a UEFI BIOS, And if you've configured it for UEFI / Win10 You need 64 bit Windows 7	Speedy Gonzales (78)
1455510	2018-11-11 13:50:00	If you want 2 OS's do you want to dual boot?? If you do install Win7 first. Leave 2 hdd's connected. Update Win7 after first. Then install Win10 1803 on the other. Next time you want to use either. Turn the computer on and select the OS you want to use If the mobo supports UEFI / has a UEFI BIOS, And if you've configured it for UEFI / Win10 You need 64 bit Windows 7 Speedy Gonzales. Hi again. I don't want to dual boot. One OS per HDD. I having difficult time with the downloaded W10 v1803 I used mediacreation tool to obtain. After DL it burned to Blank DVD using Windows image Burner, and than I disconnected all HDD's apart from the intended 1TB Sata HDD I plan to instal the W10 1803 onto. It booted from the DVD and got as far as the Windows 10 blue logo and that was it. Optic drive LED flashing away as disc being read but no LED indication of HDD activity. So after giving it 10 minutes to show some action on screen I figured that the instal isn't going to happen and shut down PC, reconnected the 80GB HDD with the working W10 1803 installed and put the instal disc aside. Before I quit it for the night, I used ImageBurn to check that the DL'd ISO of W10 1803 was bootable and I did the same to the created W10 1803 DVD from the ISO. I Created a copy from the Burned DVD and checked if that was bootable, then I burned a 2nd copy from the ISO I had created. Considering that the DL'd ISO of the W10 1803 appears to have been auto-removed from my PC after the Image had been burned to disc it seemed like a good Idea to have a copy that worked. But does it?? As said so far it hasn't installed from the DVD created from the DL'd ISO and before I hit the hay in a few minutes, I will do the disconnect all HDD's barring the target 1TB HDD and have another go at installing W10 v1803 from the created DVD's........ If it is the same and I do not see a circle of spinning blue dots within 30 seconds of that Windows 10 logo showing onscreen, the discs are destined for the recycle bin and I will use the v1709 I have that I know is working instal DVD. Thanks. edit: I don't have UEFI I have BIOS.	kioti (17360)
1455511	2018-11-11 18:28:00	Use rufus, get 2.18.exe rufus.ie That mobo has a UEFI BIOS as well. So if you want to use UEFI you can change the settings in the BIOS. But if you want to use MBR instead, get rufus put a USB flash drive in a USB port, run rufus select MBR partition add the 1803 ISO you downloaded. Wait for it to finish. Reboot change the bootdisk to the flash drive, save settings. Reboot. Press a key when it says to. When you get to the setup screen delete all partitions then install Win10 It'll just take longer if you dont dual boot, you'll have to go into the BIOS all the time to change from Win7 to 10.	Speedy Gonzales (78)
1455512	2018-11-11 22:18:00	Hi Speedy. I found when I had my W7 working and BIOS set to boot from the HDD that W10 is installed that I would get a screen from which I could choose to boot into W7 or W10. My W7 is inoperable at the moment but still shows in the opening screen from which to choose an OS to boot open.... and both PS's were on their own HDD. Well I managed to instal W10 v1803, after a 3 minute wait the blue spinning circle of dots appeared. I had to instal it to a 160GB Sata HDD because attempting instal to the 1TB HDD popped up a window saying "Cannot instal to the HDD because it is about to fail" or words to that effect. One thing knocks me down about the SIZE of the GB used to instal it! It used 105GB of the available Space leaving only 35GB Free space. The 1803 instal I am using at the moment which as I said before is upgraded to v1803 from the v1709 is on an 80GB HDD and that has AV/and other programs installed yet still has 15.3GB Free space from the HDD's 73.5GB usable Space. Perhaps you could explain to me why the v1803 I installed from the DL'd ISO has used 47GB more space to instal on that 160GB HDD it is on, than the upgraded v1709 to v1803 . (???????)	kioti (17360)
1455513	2018-11-12 00:02:00	One thing knocks me down about the SIZE of the GB used to instal it! It used 105GB of the available Space leaving only 35GB Free space. The 1803 instal I am using at the moment which as I said before is upgraded to v1803 from the v1709 is on an 80GB HDD and that has AV/and other programs installed yet still has 15.3GB Free space from the HDD's 73.5GB usable Space. Perhaps you could explain to me why the v1803 I installed from the DL'd ISO has used 47GB more space to instal on that 160GB HDD it is on, than the upgraded v1709 to v1803 . (???????) Its possible when you installed Windows 10, that you didn't delete all the previous partitions /Data from the original HDD, thus leaving used sections of the drive behind A fresh install of W10, with drivers and all current Updates is approx. 17.3GB BTW: that's Windows 10 1809 but 1803 is similar. Defiantly wouldn't go using 1709, that's over a year out of date, and would only upgrade to the latest anyway. If you do an upgrade from 1709 to 1803 there will be a windows.old folder, that will be approx. 20GB give or take a bit.	wainuitech (129)
1455514	2018-11-12 02:28:00	Its possible when you installed Windows 10, that you didn't delete all the previous partitions /Data from the original HDD, thus leaving used sections of the drive behind A fresh install of W10, with drivers and all current Updates is approx. 17.3GB BTW: that's Windows 10 1809 but 1803 is similar. Defiantly wouldn't go using 1709, that's over a year out of date, and would only upgrade to the latest anyway. If you do an upgrade from 1709 to 1803 there will be a windows.old folder, that will be approx. 20GB give or take a bit. Wainuitech, thanks. it seems that the HDD I installed the V1803 W10 Pro to was NOT unallocated space as it showed in Easeus Partition Master v12.10. Now I am positive that I had deleted the partition and it shows all as unallocated space apart from a partition titled MBR at the very beginning of the displayed drive. I considered deleting that MBR partition but decided not to because of the grief I am having with the ntoskrnl.exe being corrupt in my W7x64 Pro SP1 instal on another HDD. I have just viewed all HDD's in This PC and the L Drive on which the W10 Pro v1803 was installed shows 3 Windows Old Folders using 89.5 GB of space and many other entries going back April 2016. So obviously I screwed up somewhere with the instal of W10 v1803. I presume I can delete all that is not dated 12/11/2018...Here is a link to a pic that shows the contents and folders / files in the L HDD. www.dropbox.com At the end of the day a 160GB HDD is not enough so I will be ordering a new 2TB Sata HDD on which to instal W10 Pro v1803. Same as the inoperable W7 drive that I have.	kioti (17360)
1 2 3