Windows 10: Getting Unexpected Kernel Mode Trap fail on attempted repair-installs

I have an older 32-bit desktop that is having problems -- when I try to create Macrium Reflect rescue media, or install the WinPE boot, the PC blue-screens with "Unexpected Kernel Mode Trap" error.

So, I tried to do a repair-install. It starts the process, gets to around 30%, and then blue-screens with the same error.

I have tried different media approaches, using a mounted ISO, a USB stick, and a DVD -- and all fail the same way, at the same point.

I've run memory tests and they pass with no problems.

I've run "sfc /scannow" and it passes with no problems.

I've run chkdsk and done surface tests, and they pass with no problems.

My BIOS does not have a setting for memory caching, so I can not disable that.

I'm NOT able to do a clean-install, as I've already tried that using a separate disk and the older Win-7 games do not carry over successfully -- and this is a BIG issue to the person using the desktop.

I've run the DM Log collector and will upload the .Zip file here.

NOTE: The file will say Win7 in the PC name, but it's actually running Win10 Home 32-bit.

:)

 

received KERNAL MODE TRAP blue screen error

I keep getting the unexpected kernel mode trap blue screen errors.

Any fix for this?

Original Title: KERNAL MODE TRAP

 

how to solve"UNEXPECTED KERNEL MODE TRAP"

How to solve unexpected kernel mode trap

 

Quick suggestion before looking at the dumps.

Clean install then install Windows 7 games for Windows 10 Anniversary Update and above. That's what I do after each Windows 10 clean install.

 

No dumps in the zip file, will make it hard to debug this problem.

Doesn't look like the specs listed in My Computer match what are in teh zi p file you uploaded.
Can you provide the specs to match the zip please?

Looks like 4GB of RAM with Win 10 Fall Creators Update 32 bit.
60GB partition with about 30GB of free space for the boot drive.

Please post a screen shot of an expanded Disk Management window (where all information is visible).

 

Not one of these games, thanks.

 

Specs of the system with the problem:
Computer Type: PC/Desktop
System Manufacturer/Model Number: Self-built using Gigabyte motherboard
OS: Windows 7 32-bit, Windows 10 32-bit
CPU: AMD FX4100 64-bit 4-core
Motherboard: Gigabyte GA-78LMT-S2P
Memory: 4GB PC3-10700
Graphics Card: onboard ATI Radeon 3000
Sound Card: Onboard Realtek ALC888
Monitor(s) Displays: Samsung 23"
Screen Resolution: 2048x1152
Keyboard: Logitech wired
Mouse: Logitech wireless
Hard Drives: Kingston 240GB SSD, Seagate 500GB HD
Browser: IE v11, Edge

I created a jpg file of the screenshot of diskmgmt:

 

So it's a dual boot Win 7 / Win 10 system?

Uninstall Macrium Reflect.
Download and create a DVD or flash drive of Windows 10 Recovery Tools - Bootable Rescue Disk from KYHI. It includes Macrium Reflect Portable. Boot the Rescue DVD/flash drive then run Macrium to create a backup of the existing 250 GB SSD drive.

Next, disconnect the 500GB hard drive so only the SSD is accessible
Disconnect everything not absolutely required to boot the system, including all external connection other than mouse and keyboard. You can even disconnect the Ethernet cable until the Repair completes then reconnect it and do a Windows Update.
Uninstall Norton Anti-virus. Use the built-in Windows Defender for now. You can reinstall Norton after the repair if you feel the need.

Please make sure your PC is configured for small dump files: How to Configure Windows 10 to Create Dump Files on BSOD

Mount the Win 10 ISO image again and run setup from it.

Is any kind of disk cleanup program being run on the system that might be deleting mini dumps? If so, stop using it until we're done here.

 

Ztrucker:

Thanks much for getting back.

UPDATE: Well, I though that was going to work, at least, it looked like it was. It got all the way through installation, put up the message about the PC restarting -- and then redisplayed the desktop, with a single popup window that had the text "Windows 10 Installation has failed".

No BSOD, no minidump files, no error message.