Question Windows 10 Boot Error - Kmode Exception Not Handled

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Jul 3, 2022
12
0
10
Hello,

some time ago, I purchased a used gaming laptop which unfortunately has quite a few issues. Currently I'm struggling with the most recent one, resulting in a startup error (perhaps due to a failed update).

Windows 10 system on the SSD refuses to boot, showing a KMODE EXCEPTION NOT HANDLED error. The same happens when I try to boot from a Windows 10 USB drive. Windows Recovery and Windows Safe Mode are inaccessible, with the same bluescreen error. Recently, I somehow managed to get to a "Recovery" screen: "Your PC/Device needs to be repaired | A required device isn't connected or can't be accessed | Error Code: 0xc0000178 | You'll need to use recovery tools ..."
More interestingly, I still can boot from a Windows 10 DVD, but I can't make any changes to the system (repair or reset options don't work).

Meanwhile, the laptop boots to an Ubuntu 22.04 USB drive without any issues, and I have full access to the files on the SSD.

System specs:

15.6", Full-HD, 60Hz, non-glare, IPS
Intel Core i7-7700HQ, 4x 2,80GHz
16GB DDR4-2400 RAM
1TB HDD + 250GB SSD
NVIDIA GeForce GTX 1070
Windows 10 Home 64-bit

If any logs are needed in order to further investigate the problem, please tell me where to find them.
I do have access to an another system with Windows 10, so if any drivers or startup files are damaged, I could copypaste them to the faulty system (if it somehow helps resolve the problem).

Thanks so much for any help!

Best regards
Geralt H
 
Jul 3, 2022
12
0
10
Win 10 will reactivate itself when installed. The details of that PC + a copy of the licence key are saved on Microsoft servers. When you reinstall win 10 and get to part of install asking for a key, you click "I don't have one" and win 10 will continue to install and once you reach desktop, will contact servers and check activation. And if it finds it, reactivate. You don't have to do anything.

Okay, does it then require the hardware configuration (including the HDD) of the laptop to remain the same when reactivating?
And could it somehow impact my plan to install the Windows 10 Pro on the 2.5" SSD? Could the Microsoft servers maybe recognize it as the same hardware configuration and then use the Windows 10 Home license to activate the new Win 10 install? Do I then need to have the new Windows 10 Pro key ready to enter when Windows asks for one in order to avoid getting in conflict with the original Windows 10 install? And is it possible to have two Windows 10 licenses to be associated with the same hardware (only different target drive)? Many questions at once, I know, I'm just trying to think through all potential traps and how to circumvent them in advance, so that I don't get stuck halfway through the process and have to start over again...

Nope. Linux installs its own boot (GRUB). It should (once in a while it misses) add already present Windows installations to the GRUB menu.
I just need some kind of OS selection screen when I turn the laptop on, I'm largely indifferent as to how it looks and whether it's based on Windows or Linux. But thanks for confirming that installing Linux after Windows should work.
 
Last edited:

Karadjgne

Titan
Ambassador
Windows 10 is free, just download a copy, install it, skip the registration then add any extra drivers after completing any updates. Best to do this before resale, that way the buyer needs to purchase his own registration key and doesn't walk away with one of yours. What's on the drive now is registered to someone else, in some fashion.

Doing it that way deletes any prior info of yours when windows partitions the drive. Only then reinstall any other drives, so Win10 remains seperate.

Win7 is standalone, doesn't spread to include other drives. Win10 isn't. If you have more than a single drive present, Win10 will incorporate the extra drives into an extended C drive, even if it has a different label. If you remove a dependant drive, Windows gets bricked. So if you intend to install 3 OS on 3 seperate drives (doesn't matter if physical or logical or virtual, a partition counts as a drive) remove all other drives to install 10 by itself.
 

Colif

Win 11 Master
Moderator
If you have more than a single drive present, Win10 will incorporate the extra drives into an extended C drive, even if it has a different label.
not that I have ever seen.

What it does is it might put other partitions on any empty space it finds. Sure, that extra partition could be the boot partition but it never makes the drives appear to be one big C drive.

So if you intend to install 3 OS on 3 seperate drives (doesn't matter if physical or logical or virtual, a partition counts as a drive) remove all other drives to install 10 by itself.

NO, you install 7 on 1 drive, leave it in PC
then install win 10 on another drive and it will add itself to the boot info that win 7 created.
then install linux and it will make grub and do its own thing.

if you install 10 by itself it has no idea the other ones exist. you do it all in a process to get them to see each other right.
 
Jul 3, 2022
12
0
10
Sorry for the lack of updates lately, I had very little time to continue working with the laptop.

Yesterday, I temporarily removed the 250 GB M.2 SSD with the broken Windows 10 in order to test whether I could boot from the Win10 USB now. After removing the SSD, I started the laptop once into the BIOS and then shut it down (I suppose, this was the suggested UEFI mode boot?). And indeed, I seem to be able to boot from the Win10 USB - I got to the language selection menu and then to the 'Install Windows 10' screen, so I think I could proceed with installing Windows 10 Pro. I stopped there for now.

Next, I tried to boot from the Windows 7 USB in order to set up the intended triple boot - unfortunately, with the same result as always (as posted in #15: https://forums.tomshardware.com/thr...-exception-not-handled.3768755/#post-22736340 ). I made a clean new bootable USB drive in order to rule out any hardware problems with the one I had used before, but the result remains the same.

My procedure for creating the Windows 7 bootable USB:
  1. Make ISO of a Dell Windows 7 Pro x64 SP1 DVD
  2. Create a bootable Windows 7 USB drive with Rufus
  3. Use the Gigabyte Windows Installation tool to add USB3, NVMe drivers & packages (like here):
1493745406_6_gigabyte_windows_installation_tool.png


As I had previously written in this thread, I could intiate the boot process from the source Windows 7 DVD in an external DVD drive (USB connection). At some point though (when the 'starting Windows' screen with the Win7 logo appears), the connection to the DVD seems to stop, and then the laptop freezes, with no visible progress (at least not within ~30 minutes). But this is still the furthest I got with trying to boot Windows 7; USB has never worked.
I even tried once to start the Windows 7 installation (from DVD) from the running Windows 10 system, and while it would copy the files and initiates the required system restart, the result would still be the same - the 'starting Windows' screen with the logo appears, and then it's frozen for all eternity. And I've been stuck with a broken "Windows Setup" in the boot selection menu in the first position since, so whenever I was not paying attention to actively select Windows 10 instead, I would enter the broken setup again. I couldn't remove the broken entry at all - it's still on the 250 GB SSD with the non-functional Win 10.
Strangely enough, the issue with booting from a DVD also occured when I first tried to install Windows 10 from a DVD: I could boot into the menu, select the target drive to install Windows 10, even create the target partition (this is where I noticed that Windows 10 always creates 2-3 additional, smaller partitions next to the target one), but when I hit install, an error prompt would tell that the connection to the source medium is not found.


Any ideas on what might still cause this issue? What should I try, test or change next in order to proceed? Did I do the suggested UEFI mode boot correctly, or did I overlook something?
And is there maybe a clean, trusted Windows 7 Pro x64 image from a safe source that I could try instead of mine? I know that Microsoft stopped supporting Windows 7 a long time ago, but I recon there should be a mirror somewhere...
 
Last edited: