Fixed with Build 25247.1000
BSOD. Stop code SYSTEM SERVICE EXCEPTION. What failed win32kfull.sys. Build 25227.1000 OOBE clean install from USB media.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
Has anybody seen this problem trying to do a OOBE clean install with Build 25227?
Both the MS official ISO 25227 and the one downloaded from UUP-DUMP have this new issue causing a BSOD during OOBE procedure.
Stop code SYSTEM SERVICE EXCEPTION
What failed win32kfull.sys
I could repeat the same problem on a desktop and a laptop. This is a new bug with latest Build 25227.
Same procedure works fine with previous ISO 25217 or any older Dev one.
Easy to reproduce every time with Shift +F10 and regedit just trying to modify any registry.
Windows Insider program | Windows Insider preview | Install, activate, and Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
52 answers
Sort by: Newest
-
Anonymous
2022-11-22T03:08:32+00:00 -
Anonymous
2022-11-04T04:03:18+00:00 Hi fg,
On a clean install of 25236, as previously established, there's no error unless clicking the scroll bar.
Correct.
The other case I had was when using Shift + F10 to change the registry and I could not do it.
The same situation for me with 25236, cannot do regedit after Shift + F10, gets the same error.
-
Anonymous
2022-11-04T03:55:45+00:00 Hi fg,
On a clean install of 25236, as previously established, there's no error unless clicking the scroll bar.
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2022-11-03T02:32:24+00:00 Verified that we still have the same bug with Build 25236.
As per Blog, MS still working on that issue. 🤷♂️