BSOD. Stop code SYSTEM SERVICE EXCEPTION. What failed win32kfull.sys. Build 25227.1000 OOBE clean install from USB media.

Hi Sibro,

I just tried with the Home edition only, extracted from the original MS multi-edition ISO.

Used a fully compliant Desktop DELL XPS 8940, booted from the USB and did the same sequence that I tried before, it crashed with the BSOD exactly the same way as the Pro edition. As I try to select a key in the registry it just crashes with the same BSOD as reported earlier.

I also saw a different case getting the same BSOD every time just trying to scroll on the selection for the drive where to install windows.

Note that in my case I can always reproduce the BSOD if I attempt to modify the registry after Shift + F10 and "regedit".

If I just follow the normal install procedure it proceeds normally to completion with either Home or Pro and no errors at all.

That could be the reason why MS did not catch the problem. It seems to require some unusual conditions to hit the bug.

For Johnny and yourself, VM seems to be the variable, in my case it is just the editing of the registry or scrolling on the selection for the drive, but the end result is the same BSOD. 😝🤷‍♂️

I was not expecting a different result with Home versus Pro at this stage, given that is not even installed yet.

The screwup must be in the common setup regardless of which edition I try to install. 😎

Here is the other case, I mentioned above, I get the BSOD reproduced consistently just trying to scroll to select the drive partition where to install.

Note that if I select the drive partition directly without scrolling, the bug does not happen, and I can go on formatting and installing. 🤣

You may not even have the scroll bar in your system if you don't have many disks with multiple partitions. 🤷‍♂️

On the laptop screen that you showed earlier type regedit in the command prompt, then try opening a key.

Looking more and more like a Pro version only bug

This on a VM using UUPdump ISO Home version only, no error.

Hi Sibro,

It is easy for me to try Home Edition only on the same fully compliant machine that is failing with Pro and see if it makes any difference.

I'll extract the Home edition only from the MS ISO and then try again.

I'll let you know when I'm done with the test. 😎

On the laptop screen that you showed earlier type regedit in the command prompt, then try opening a key.

Looking more and more like a Pro version only bug

This on a VM using UUPdump ISO Home version only, no error.

On the laptop screen that you showed earlier type regedit in the command prompt, then try opening a key.

Sorry for the delay, I had visitors and had to stop the test.

Anyway, this is on the laptop from USB media with official ISO

I'm working on a clean install VM with Home version only ISO, stand by...

Apparently, the BSOD can happen in different spots, depending on the environment.

When exactly did you get the error?

BSOD occurred either right away or the furthest I got was to choose what version I wanted to use, picked Pro and it crashed. I was using the full install.wim. I had not converted to install.esd.

Regards,

OK thanks,

I did not convert to .esd either.

In my case I just extracted the single edition install.wim for Pro from the MS original ISO, that way it is smaller the 4GiB when I create the FAT32 installation media.

For the second ISO downloaded from uup-dump it was already a single edition for Pro and no need to change anything.

Anyway, both got the same exact BSOD problem, but apparently at a different point than where you got it.