-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Operating System and Recovery
- KMODE_EXCEPTION_NOT_HANDLED Fresh install of Windows 10

Create an account on the HP Community to personalize your profile and ask a question
07-11-2017 08:11 AM
I am performing a clean installation of Windows 10 on a Elitebook 840 G1 using a company image. The installation proceeds normally up to the initial setup screen where it asks if I want to customize or use express settings. I choose express settings and immediately receive a Stop error (BSOD) with the error KMODE_EXCEPTION_NOT_HANDLED. There is no driver or software listed after to indicate what caused the stop.
The system reboots and begins a loop BSOD, reboot, BSOD, reboot. After two reboots it will boot to the Advanced Setup screen. I can get to Safe Mode, but there is no administrator account created. Account name is DefaultUser0. And Windows doesn't seem to be fully installed or set up yet.
Believing this to be a problem with the company image (setting or software) I created a bootable USB from the MediaCreationTool with the latest version of Windows 10 and attempted an installation from that. It has the same KMODE EXCEPTION. I attempted to revert to Windows 8.1, installing from a DVD. This gives the same KMODE EXCEPTION.
Please advise. I think it might be a driver problem but there is no indication in the error what driver.
07-11-2017 08:52 AM - edited 07-11-2017 08:54 AM
Hi,
There could be a hardware problem. I am thinking hard drive, memory or CPU. Can you try running HP diagnostics on the hardware and see if any problems are encountered?
https://support.hp.com/lt-en/document/c03467259
Another thought, is the computer connected to the internet during the installation (cable). Try installing without the computer being able to connect.
Let me know,
David
07-11-2017 09:28 AM
> There could be a hardware problem. I am thinking hard drive, memory or CPU.
Yes, but you did not mention the "other" major hardware components: the motherboard, and the optical drive, that are required to be functioning "perfectly" during an installation of Windows.
If the motherboard has a fault, that will create a problem.
If the optical drive is misreading from the media, that will create a problem.
If the media is a DVD-R, it could be scratched/damaged -- obtain another copy of the media from your company.
It's always good to post *ALL* the possibilities.
07-11-2017 09:35 AM
@mdklassen
If you make a list of the whole computer I am sure you will find the problem:smileyvery-happy:
When I say I am thinking it does not automatically exclude all other options. I am talking from experience and the problem at hand.
You are talking about DVD setup when the Member used USB drive and DVD drive with same error. So I guess we can exclude the DVD drive (maybe you think otherwise). Please share your wisdom. Do you read the actual questions?
All the best,
David
07-11-2017 09:45 AM
> If you make a list of the whole computer I am sure you will find the problem.
If you do NOT make a list of all the hardware, then I am sure that you may not find the problem.
If the DVD is the problem, and the USB is a direct copy of the DVD, then it follows that the USB will have the same problem.
That's why I suggested to get a "fresh" copy of the "company image" from the source.
Do you read the actual questions?
07-11-2017 09:47 AM
@mdklassen
Once again your wisdom is witout limits.
If you read the question you will see that first the Member tried with company image and then downloaded Windows 10 from Microsoft (media creation tool) and created a bootable USB drive. Both gave the same problem.
Waiting for your wisdom in the next reply.
David
07-11-2017 09:50 AM
Mem Test and Disk Check both come back clean. I also tried a different hard drive in this case, and the same drive in another G1. Both produce the same error.
Installation has also happened both on and off network.
07-11-2017 10:02 AM
> I also tried a different hard drive in this case, and the same drive in another G1. Both produce the same error.
Did you try a different copy of the "company image"?
Your testing seems to rule out either of the 2 hard drives as being the cause of the symptoms.
It is very worrisome that two different computers (motherboards, CPU, RAM) cause the same symptoms.
Can you try the "company image" on some "non-G1" computer, just to verify that the image is OK?