[SOLVED] BSOD if I try to activate Core Isolation - cause is hswultpep.sys driver ?

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Sep 11, 2022
14
1
15
I'm using Windows 11.
Now I try to activate the CORE ISOLATION.
If I restart after activation, I get a BSOD (Blue Screen of Death) und it shows me, that there is a problem with driver hswultpep.sys.
My PC has an INTEL-Board with Intel Core i3-8100 processor.
The properties of the hswultpep.sys driver are:

  • Filedescription: Intel Engine Power Plug-in driver
  • Fileversion: 6.2.9200.16384
  • Productname: Intel(R) Core(TM) 4xxxU and 4xxxxYProcessor Line Power Engin Plug-in
  • Productversion: 6.2.9200.16384
  • Copyright: Intel Corporation
  • Changingdate: 08.02.2013
It seems me that this driver is very old.
How can I solve this problem?
I tried to find corresponding information in the WEB, but unfortunately did not find anything.

Kindly regards

Samson
 
Solution
Today I downloaded the new Windows version and wanted to run a repair installation (according to the instructions).
did you mean the link I showed? a repair install as you were meant to use the same version of windows as was installed
The Windows 11 installation media (ISO or USB) must be the same edition, same version, and same or higher build as the currently installed Windows 11.
so that could be why it didn't work.
Your installed Version is 21H2, the ISO is 22H2 now.

Did you try installing the update normally instead?
although running it from within...
Yes, I really did the installation with the 22H2 - Sorry.
However, the same problem also occurs when I perform the repair installation with version 22H1.
So I have no choice but to try a clean installation with version 22H2 as you suggested.
So at least I can quickly see if it's possibly due to the hardware.
Thank you very much for your great support!!! 👍👍👍
 
The error was found and the source of it was also identified.
I had a lot of time yesterday and worked through the device manager device by device until I found the device that uses the driver HSWULTPEP.SYS.
There I was offered to reset to an older driver.
Here the driver INTELPEP.SYS was used.
The driver HSWULTPEP.SYS is from 31.1.2013, the INTELPEP.SYS from 20.6.2022, thus clearly more current.
This error also occurred with the latest Windows version 22H2.
As cause I could locate the program "DRIVER UPDATER", which wanted to exchange the current, against the ancient driver.
When I first used DA, I made the mistake of replacing all drivers marked as old.
In the future I will check every driver for this problem and only replace the one that really needs to be changed.
I would like to take this opportunity to thank everyone who gave up their time to help me.
The core isolation is now running smoothly!!!

With kind regards
 
  • Like
Reactions: Colif