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

[Samson_DE]

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

 

[Colif]

updating chipset drivers might help.
try running this to see if it offers any new drivers - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

Have you turned on virtualisation in the BIOS?
You mainly use Core Isolation for Virtual Machines.

Driver dates might be fine, if it hasn't changed in 8 years, no reason to release a new version. Intel have clearly sent it to Microsoft for testing with WIn 11 or it wouldn't be running at all now. I sometimes see older drivers. Age doesn't necessarily mean its a problem. You won't see them but some drivers dates are in the future to stop them being overwritten by accident.

 

[Samson_DE]

Hi Colif,
many thanks for your answer.

I have installed the Intel-driver-support-assistent.
Unfortunately, the result was "Your Intel® drivers and software are up to date."😳
That doesn't help me either.
Does anyone still have an idea to solve the problem?

Regards

Samson

 

[Colif]

I see one other person with error and Microsoft in their wisdom just told user to roll back to previous version of windows. That doesn't work on 11. Seems it causes Green screen errors as well.

• 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

File version & Product version both tell me that driver came as part of windows itself.
which makes me curious why its playing up

right click start button
Choose Windows Terminal (admin)
If it doesn't open as Powershell, select the drop down list in the title header and choose it
copy/paste this command into window:
Repair-WindowsImage -Online -RestoreHealth
and press enter
Then type SFC /scannow
and press enter
Restart PC if SFC fixes any files as some fixes require a restart to be implemented
First command repairs the files SFC uses to clean files, and SFC fixes system files
SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11

 

[Samson_DE]

Hi Colif,
many thanks.
It seems that I am "stumbling" over the next problem. When I start the Powershell,
I see the blinking cursor, but I can't make any input from the keyboard.
I can insert the command string with copy and paste,
but the shell does not respond to the Enter key.
If I start SFC /scannow as SYSTEM (via PSEXE) I get the Message "Windows Resource Protection did not find any integrity violations.".
What to do?

Regards

Samson

 

[Colif]

does command prompt open? if so, open as admin
type
DISM /Online /Cleanup-Image /RestoreHealth
and press enter.
spacing needs to match or you get errors.

its the same command as the Powershell one.

I wonder why your keyboard doesn't work in powershell (or was that in Windows Terminal?)

 

[Colif]

You may experience an issue with Windows Terminal where keyboard input does not work. By and large, we've determined that this is caused by the "Touch Keyboard and Handwriting Service" being disabled.


If you're hitting this issue, make sure that the "Touch Keyboard and Handwriting Service" is not disabled. Certain "de-bloating" software (and apparently MSI Afterburner) likes to disable it or suppress it in the name of making your machine less understandable and "faster".


If you're experiencing an input issue that is not helped by exiting MSI Afterburner or re-enabling the "Touch Keyboard and Handwriting Service", please file a new issue.

https://github.com/microsoft/terminal/issues/4448

 

[Samson_DE]

Great,
the hint to "Touch Keyboard and Handwriting Service helps me to find the command "sc config TabletInputService start= demand".
Now I can use my keyboard in Windows Terminal and Powershell again
One problem solved.👍👍
Unfortunately, the problem described in the 1st post is not yet solved.
I worked through the scripts and Windows didn't find any errors.🤢

Best regards and many thanks

 

[Colif]

have you checked windows update this week?

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

can you try to enable it again, I am curious if I can see any drivers that might be getting in the way. Parts of windows generally don't cause bsod but could be pushed.

Dumps would tell me some but what are specs of the PC?

 

[Samson_DE]

Pls. have a look at the zip-file https://1drv.ms/u/s!AnSrtkIVr_2enqwOcqANNeb-fM5Dcw?e=39MFK1
Here you can see, that the dump is activatet.
Every time I start Windows, the BSOD -Screen appears,
but I can't find the subfolder "c:\Windows\Minidump".
Where is the problem?

 

[Colif]

i won't pretend to understand the update log. Question was mainly if you were up to date or not. Win 11 22H2 might be out in the next week, it could fix this by replacing windows completely.

I have to say I am getting tired of computers that won't create minidumps. It makes it hard to figure out their problems if they won't show us anything to work from.

how big is your memory.dmp file? it shows in root directory of C. Might need to show hidden files.

Does the bsod occur before logon or after?

what make/model drives do you have in PC?

can you share a screenshot of the system information application?

 

[Samson_DE]

The BSOD comes before LogIn.
I did not find the file memory.dmp on drive c: - I'm sorry 😳
Some informations about systemconfiguration you can find in this ZIP-file:
https://1drv.ms/u/s!AnSrtkIVr_2enqwTVlI7_E1jt85QXw?e=98ckVg

Ifyou need any more informations, I will send them on sunday, until then, I will take a few days of vacation.

I wish you a nice weekend.

 

[Colif]

Have a good break

oh, its a Medion/Lenovo (they own Medion)
I wonder what motherboard it has- Guess I can wait a few days

 

[Samson_DE]

It's a Z370H4-EM (Akoya P42000) Mainboard.
I didn't find a description for this board.

 

[Colif]

bios update page - don't use, just collecting links - http://www1.medion.de/downloads/?op...ram=Z370H4-EM&imageField.x=37&imageField.y=10

see if you can find any BSOD using this - https://www.thewindowsclub.com/find-and-view-bsod-log-files-in-windows-10-event-viewer (it would be same in 11)

I can't read it, do you know what model Medion you have? That probably speed identification up.

you can run Crystaldiskinfo (blue icons) on drives to check health. It will automatically run, no need to do anything

 

[Samson_DE]

There I am again 😉
Today I made drive-diagnosis with Crystaldiskinfo, but all drives "OK" (look at zip-file).
Then I provoked the BSOD again.
First comes the MEDION mark, then the BSOD, then the PC starts again with the partition-selection.
The Logfiles from eventviewer you can find in the zip-file.
https://1drv.ms/u/s!AnSrtkIVr_2enqwfwUbSzr_Q0AUhfw?e=0uxU5g
Regards

 

[Colif]

You could run seatools for windows on the 1st 2 drives (3tb & 2tb) https://www.seagate.com/au/en/support/downloads/seatools/ - but they both seem fine.
3rd drive is a Crucial MX 500

I had to read thread again as we wandered a long way from fixing that file name.
I assume you have not changed the size or location of page file?

the events don't seem to help me.

what BSOD are you getting? there are about 300 but I only normally see a few of them.

wonder if checking ram would help
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

 

[Samson_DE]

The result of memtest is error = 0!!! (see zip-file).
The short-test with seatools gaves me OK for booth seagate-drives.
From BSOD I take a photo (see zip-file).

https://1drv.ms/u/s!AnSrtkIVr_2enqwiKpOc4PDAarXkJg?e=9Lb8ZH

 

[Colif]

Well, its not ram or storage stopping you getting dumps... I guess the process does run on the CPU.

I am unsure which version of the motherboard you have. I am thinking it could be your BIOS version at fault. Its possible a change was made in the last few versions.

its not easy to tell as the bios versions on the website don't seem to match up with your PC info
http://www1.medion.de/downloads/?op...ram=Z370H4-EM&imageField.x=37&imageField.y=10

Your PC shows 370H4WOX.201 which could be bios version 2.01 and latest for version 2 of the motherboard is 2.05

Its unlikely to be version 1 of board as its latest BIOS is 1.09

I think I would contact Medion to confirm it. There aren't many results searching for bios number.

Another thought is Version22H2 on Win 11 should be out soon, you could clean install when its out and see if this is just a bug of your current install.

 

[Samson_DE]

I checked my board with CPU-Z and got the following result:
https://1drv.ms/b/s!AnSrtkIVr_2enqwmtC1GNk5J_GiUVg?e=lRuURQ

I think your right with the bios-version.

But is the first time, that I have to make a bios-update.
Is there any possibility to save the actual bios-settings and how can I restore them after bios-update?

 

[Colif]

I don't appreciate the last notice on the update

+++Installation+++
1. Unzip the downloaded file into a created folder on your harddisk.

2. Run the file Flash64.bat.

3. Please be aware to restore the original bios settings after the update.

4. Rebooted the system for the changes to become effective.

Please note:
To extract all files press the "Extract"-Button. The files will be extracted to the folder specified in the "Folder"-Field. This folder will be created, if it does not exist.

Important notice:
For any errors, caused by the execution of this update, we don´ t accept any responsibility for damage or lost of data. The customer agrees with that fact by executing the update.


I would be tempted to contact Medion before running it and ask if they know of this error with the file name, and also if the update process works on windows 11. Since they won't take the blame, it might help to know that before you do it.

I would also ask them about settings, if you haven't changed anything in there, you probably don't need to do anything at step 3, but I am not sure.

Don't update bios if there is a storm around or if you might have a power outage. It can end badly.

 

[Samson_DE]

I installed the MEDION service app and there I was offered the update of the BIOS.
I then had this done.
However, the error continues to occur.
An additional request to the MEDION service regarding the BSOD was answered in such a way, that my PC is no longer in the warranty period and I was offered a paid repair.
My question about the BSOD was not answered. 😡
I will therefore have to wait until the new Windows version is available.
Regards

 

[Colif]

if the new version doesn't come out this month, you could try this - https://www.elevenforum.com/t/repair-install-windows-11-with-an-in-place-upgrade.418/
As it might fix the BSOD since its caused by a windows driver.

The repair install method works, I did it myself a month or so ago. took 20 minutes to be back on desktop as if nothing had happened. All it touches is windows, you just need to install one cumulative update and other patches.

 

[Samson_DE]

Today I downloaded the new Windows version and wanted to run a repair installation (according to the instructions).
I removed the AV software (Bitdefender) with the uninstall tool before.
Unfortunately, this installation aborted shortly after startup without further hints.
The repair-update was started at 12:09:52 2022.09.21
I once collected some LOG files and saved them in the zip file.
https://1drv.ms/u/s!AnSrtkIVr_2enqw9b4gRhskCnWjwjw?e=a0wAKh
If you need any more LOG files, please let me know.
Regards

 

[Colif]

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.

Repair Install Windows 11 with an In-place Upgrade Tutorial

This tutorial will show you how to do a repair install of Windows 11 by performing an in-place upgrade without losing anything. If you need to repair or create a new recovery partition or having problems with the Windows 11 operating system on your PC, and the usual solutions will not fix it...

www.elevenforum.com

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 File explorer is essentially same thing as a repair install.. hmm

I will read the update files later, i didn't get much sleep in last 24 hours.
it could be you need to do a clean install. Or are missing something.

I got it earlier today but ran into another problem. It installed but now updates won't.