- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have been using DSA and the Intel update installers for years without any problems.
Since the update “Intel® 7th-10th Gen Processor Graphics - Windows, gfx_win_101.2130.exe” from September 2024, the Intel installers for “Intel® 7th-10th Gen Processor Graphics” and “Intel® Killer™ Performance Suite” cause bluescreens (BSOD) during installation.
Definitely applies to the installation and the respective update from one version to the next for:
KillerPerformanceSuite_36.24.10111_Win10-11x64
KillerPerformanceSuite_36.24.12162_Win10-11x64
gfx_win_101.2130
gfx_win_101.2134
Only the updates of “Intel® Wireless Bluetooth” are still running without problems.
The installers for “Intel® 7th-10th Gen Processor Graphics” (versions 31.0.101.2134 and 31.0.101.2130) cause the first bluescreen already at startup and initialization, before anything is installed at all.
The updates, both “Intel® 7th-10th Gen Processor Graphics” and “Intel® Killer™ Performance Suite”, could finally be installed after the corresponding installers were simply run again 3-4 times after each bluescrenn/restart and they then progressed incrementally.
The bluescreens (BSOD) only occur during the installation or update with just this installers! Nothing else causes bluescreens and once the drivers are painfully installed, everything runs perfectly - there are no problems, crashes, bluescreens - even under full load when gaming or using graphics studio applications.
Has anyone experienced the same/similar problem, is it known and is there a solution?
Please refrain from recommending further attempts with DISM/sfc, DDU, etc. and Windows reinstallation - I've already done all that.
Everything up to date, virgin reinstalled Windows, current configuration:
Microsoft Windows 11 Home (64-Bit), Version (Build) 24H2 (10.0.26100)
Intel® Core™ i9-9980HK CPU @ 2.40GHz
Intel® UHD Graphics 630, 31.0.101.2134
NVIDIA GeForce RTX 2080 with Max-Q Design, 32.0.15.7216
Killer® Wi-Fi 6 AX1650w 160MHz Wireless Network Adapter (200D2W), 23.110.0.5
Killer E3000 2.5 Gigabit Ethernet Controller, 1125.21.903.2024
Intel® Killer™ Performance Suite, 36.24.12162
Intel® Wireless Bluetooth, 23.100.0.4
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi MF_,
Thank you for posting in the Community!
I would like to clarify more about the issue you're encountering.
What is the error code of the BSOD you have encountered?
Please provide an application event viewer log from your system. Below are the steps to generate the logs
- Right Click on the Start Button
- Click on Event Viewer
- Click on the chevron of the Windows Logs
- Right Click on the Application and select Save All Events As
- Save the file and send us a copy (make sure to indicate the timestamp of the crash)
Please provide an System event viewer log from your system. Below are the steps to generate the logs
- Right Click on the Start Button
- Click on Event Viewer
- Click on the chevron of the Windows Logs
- Right Click on the System and select Save All Events As
- Save the file and send us a copy (make sure to indicate the timestamp of the crash)
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Dean
Many thanks for your reply. I highly appreciate you taking the time to take a closer look at the matter.
05.02.2025 19:58-19:07:16 - "Intel Killer Performance Suite" installation/update attempts by using "KillerPerformanceSuite_36.24.12162_Win10-11x64.exe" with finally successfull installation (as administrator):
Event Log shows several BlueScreens for the installation attempts: c0000005
Reliability History shows: 0x0000003b (0x00000000c0000005, 0xfffff8051e14ee5e, 0xfffffb02bdca6590, 0x0000000000000000)
2025-02-05T19:07:16 Installation Killer Performance Driver Suite UWD successfull
28.12.2024 09:21-09:44 - "Intel 7th-10th Gen Processor Graphics" installation/update attempts by using DSA with no success (picture attached)
28.12.2024 19:13-19:21 - "Intel 7th-10th Gen Processor Graphics" installation/update attempts by using "gfx_win_101.2134.exe" with finally successfull installation (as administrator and clean install checked):
Event Log shows several BlueScreens for the installation attempts: c0000005
Reliability History data for this period is no longer available on the system
Some additional system information: Memory-Integrity OFF, VBS and Hyper-V inactive, NO overclocking (neither CPU nor GPU)
I attached "EventLogsSystem.evtx", "EventLogsAllApplications.evtx", "DSA Screenshot 2025-02-12 141555.png", "AdministrativeEvents.evtx", "ssu.txt"
Best regards
Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Dean
Thank you very much. I really appreciate you taking the time to investigate the matter in more detail!
05.02.2025 19:58-19:07:16 - "Intel Killer Performance Suite" installation/update attempts by using "KillerPerformanceSuite_36.24.12162_Win10-11x64.exe" with finally successfull, incremental installation (as administrator)
Event Log shows several BlueScreens for the installation attempts: c0000005
Reliability History shows: 0x0000003b (0x00000000c0000005, 0xfffff8051e14ee5e, 0xfffffb02bdca6590, 0x0000000000000000)
2025-02-05T19:07:16 Installation “Killer Performance Driver Suite UWD” successful
28.12.2024 09:21-09:44 - "Intel 7th-10th Gen Processor Graphics" installation/update attempts by using DSA with no success (picture attached)
28.12.2024 19:13-19:21 - "Intel 7th-10th Gen Processor Graphics" installation/update attempts by using "gfx_win_101.2134.exe" with finally successfull, incremental installation (as administrator, clean install checked)
Event Log shows several BlueScreens for the installation attempts: c0000005
Reliability History data for this period is no longer available on the system
Some additional system information: Memory-Integrity OFF, VBS and Hyper-V INACTIVE, NO Overclocking (neither CPU nor GPU)
I attached: "EventLogsAllApplications.zip", "EventLogsSystem.zip", "AdministrativeEvents.zip", "DSA Screenshot 2025-02-12 141555.png", "ssu.txt"
Best regards
Martin
PS: To upload 3MB to Intel takes 20 minutes and I had to rewrite my answer and upload the attachments trice, till that most simple reply to forum worked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Dean
Thank you very much. I really appreciate you taking the time to investigate the matter in more detail!
05.02.2025 19:58-19:07:16 - "Intel Killer Performance Suite" installation/update attempts by using "KillerPerformanceSuite_36.24.12162_Win10-11x64.exe" with finally successfull, incremental installation (as administrator)
Event Log shows several BlueScreens for the installation attempts: c0000005
Reliability History shows: 0x0000003b (0x00000000c0000005, 0xfffff8051e14ee5e, 0xfffffb02bdca6590, 0x0000000000000000)
2025-02-05T19:07:16 Installation “Killer Performance Driver Suite UWD” successful
28.12.2024 09:21-09:44 - "Intel 7th-10th Gen Processor Graphics" installation/update attempts by using DSA with no success (picture attached)
28.12.2024 19:13-19:21 - "Intel 7th-10th Gen Processor Graphics" installation/update attempts by using "gfx_win_101.2134.exe" with finally successfull, incremental installation (as administrator, clean install checked)
Event Log shows several BlueScreens for the installation attempts: c0000005
Reliability History data for this period is no longer available on the system
Some additional system information: Memory-Integrity OFF, VBS and Hyper-V INACTIVE, NO Overclocking (neither CPU nor GPU)
I attached: "EventLogsAllApplications.zip", "EventLogsSystem.zip", "AdministrativeEvents.zip", "DSA Screenshot 2025-02-12 141555.png", "ssu.txt"
Best regards
Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The message you are trying to access is not available.
..is all I get and see after I had replied, included the desired attachments to Deans post...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Dean
I replied already three times including the desired attachments - but unfortunately, I can not see any of my answers. Guess everything is beeing blocked for whatever reason.
I'm already wasting three hours with this as uploading a 3MB file takes 20 minutes!
What can I do to make sure that you get my answer?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Dean
Thank you very much. I really appreciate you taking the time to investigate the matter in more detail!
05.02.2025 19:58-19:07:16 - "Intel Killer Performance Suite" installation/update attempts by using "KillerPerformanceSuite_36.24.12162_Win10-11x64.exe" with finally successfull, incremental installation (as administrator)
Event Log shows several BlueScreens for the installation attempts: c0000005
Reliability History shows: 0x0000003b (0x00000000c0000005, 0xfffff8051e14ee5e, 0xfffffb02bdca6590, 0x0000000000000000)
2025-02-05T19:07:16 Installation “Killer Performance Driver Suite UWD” successful
28.12.2024 09:21-09:44 - "Intel 7th-10th Gen Processor Graphics" installation/update attempts by using DSA with no success (picture attached)
28.12.2024 19:13-19:21 - "Intel 7th-10th Gen Processor Graphics" installation/update attempts by using "gfx_win_101.2134.exe" with finally successfull, incremental installation (as administrator, clean install checked)
Event Log shows several BlueScreens for the installation attempts: c0000005
Reliability History data for this period is no longer available on the system
Some additional system information: Memory-Integrity OFF, VBS and Hyper-V INACTIVE, NO Overclocking (neither CPU nor GPU)
I attached: "EventLogsAllApplications.zip", "EventLogsSystem.zip", "AdministrativeEvents.zip", "DSA Screenshot 2025-02-12 141555.png", "ssu.txt"
Best regards
Martin
PS: This is the fourth attempt to answer you, as up so far all of my post are being blocked by your spam filter. To attach and upload a tiny 3MB file to Intel takes 20 minutes!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi MF_,
Thank you for providing this information and before I look into this further, I would like to know if you already tried updating the BIOS to the latest and let me know if the issue still persists after that. You may find the latest BIOS version here: Support for Alienware M17 R2 | Drivers & Downloads | Dell St. Kitts and Nevis
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Dean
Thanks for your reply.
Yes, of course. V 1.25.0 as you can see in ssu.txt.
Best regards
Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi MF_,
This is noted, I will look into this further internally and will reach back to you once I have the information you need.
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi MF_,
I wanted to explain the difference between OEM and generic drivers to help you better understand their impact on your system.
OEM Drivers: These drivers are provided by the Original Equipment Manufacturer (OEM) and are specifically designed and tested for your particular computer model. They often include customizations and optimizations that ensure the best performance and compatibility with your hardware.
Generic Drivers: These drivers are provided by Intel and are designed to work with a wide range of devices. While they can be useful, they may not include the specific customizations needed for your particular system, which can sometimes lead to issues.
To further isolate the issue, I recommend trying the OEM drivers for your system. Here are the relevant links:
Intel UHD Graphics Driver: Intel UHD Graphics Driver | Driver Details | Dell St. Kitts and Nevis
Killer Wireless 1750/1690/1675/1650 Wi-Fi Driver: Killer Wireless 1750/1690/1675/1650 Wi-Fi Driver | Driver Details | Dell St. Kitts and Nevis
Additionally, have you reported this issue to DELL? If so, what feedback have you received? Also, could you provide the specific BSOD error you are encountering?
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Dean
Thank you very much for your feedback.
I have since used the time to identify the cause of the problem and solved it.
To do this, I have created a generic process flow that may also help other users with the same or similar problems. Especially in case of crashes or bluescreens in connection with graphics or network drivers after their PC has been updated to 24H2.
PC manufacturers love their customers the moment they have received the payment for a new PC. Until the end of the warranty period, customers are tolerated and thereafter they are ignored.
This is why manufacturers stop providing updated drivers after a short time.
However, both the Windows upgrades 21Hn to 24H2 and the evolving requirements of the software used also make it necessary to constantly update the drivers. This applies in particular to the graphics drivers. Current graphics studio applications and gaming require the latest, up-to-date graphics drivers - there is no choice.
For this reason, Intel laudably provides up-to-date driver packages and the Driver and Support Assistant (DSA) tool on a regular basis.
Which I have been using very gladly and successfully for years on various PCs from different manufacturers. Thanks, at this point to Intel for this service.
Nevertheless, the Intel Smart-Installers should be checked and possibly made a little more robust and fault-tolerant.
It doesn't make a particularly smart impression if the smart installer causes a bluescreen on its welcome screen, before the user has even been able to move the mouse to the start button.
Remedy Process
1. Introduction & Background Information
The headache with drivers is that a driver is not ONE driver, but a collection of driver files that have to be installed correctly and hierarchically. The .inf files provide the necessary information for this.
If the PC manufacturer has customized a driver for a specific device, the driver package to be installed contains additional extensions or modified driver files. These, respectively some of them, must be retained during an update so that the device continues to function properly. This applies in particular when updating a device-specific OEM driver package to the generic, current Intel driver package.
Therefore, when updating the OEM driver to the Intel generic driver, the Clean Install checkbox must not be selected. This means that the new driver is installed over the old one and some of the oem.inf files are retained or are subsequently installed or supplemented by Windows.
“Clean Install” is only to be used in special troubleshooting scenarios (...and otherwise leads to the well-known loop that Windows Update instantly overwrites your new installation of the graphics driver with the old, manufacturer-specific driver specified by the manufacturer).
Apparently, after Windows had updated to 24H2, the graphics driver package was corrupted. Only a tiny bit, so that there were no noticeable problems during operation, but further use of the Intel driver updates led to repetitive bluescreens.
When upgrading to 24H2 or reinstalling Windows, Windows takes over the existing drivers. Unless there is an OEM-specific driver predetermined for a device (i.e. graphics card), which is then forcibly installed - if the existing driver was not already the original OEM driver, in this case it leaves it as it was and takes over everything (this will be the solution to the problem).
So usually the up-to-date, generic Intel driver is then simply reinstalled over it (clean install unchecked).
This also worked perfectly this time on the other PCs, but not on this one.
Since a subsequent complete, clean reinstallation of Windows 24H2 also led to the same result, it became clear that Windows 24H2 is not able to install the OEM driver for the Intel graphics on this PC 100% correctly (not self-employed).
In Addition - during a new installation of Windows 24H2 (re-installation), Windows activates VBS and Hyper-V by default. However, a simple deactivation option via the Control Panel is not offered. During an in-place upgrade from 23Hn to 24H2, VBS and Hyper-V are not necessarily activated - it remains as it was before.
Of course, this is not very helpful when it comes to driver troubles and does not improve system stability, prevents the execution of e.g. Intel XTU and does not necessarily enhance the gaming experience.
In the solution process described below, I have taken this point into account in order to exclude the negative influence of virtualization on the installation of the driver packages.
2. Being on 24H2 and facing issues (crashes, bluescreens) regarding the installation of Intel generic drivers - this is what solved it
(Anything else should be in order and up-to-date as well as BIOS)
2.1 Install the possibly (very) old but latest, official OEM driver packages of the computer manufacturer for:
1. Intel Graphics (in my case, Intel UHD 630 from 2021!) - Restart
2. NVIDIA Graphics (if there is one) - Restart
3. Network (Ethernet and WiFi) - Restart
Note the sequence.
(The nice thing about old driver installers is that they are not smart and crash-prone, but brute-force and reliable. Just apply them - uninstallation and re-installation should not be necessary and is not recommended.)
2.2 Reset the PC via the Control Panel and the Recovery Options. Windows will be reinstalled:
Select Keep Settings (and you may keep your data as well). Windows will not change these three OEM driver installations but adopt them (respectively not trying to install them from its own pool - as long as the previously installed driver really are the latest official OEM ones).
2.3 After the reinstallation of Windows 24H2 - disable VBS and Hyper-V (if activated or running and you want to disable it):
1. Turn off Core-Isolation Memory-Integrity (Memory-Integrity only) - Restart
2. Reg-Key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\EnableVirtualizationBasedSecurity" -> 0
3. Reg-Key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\WindowsHello\Enabled" -> 0
Restart and resetting Windows-Hello PIN (Windows prompts for it) - and that's it.
(As of 24H4, Windows now virtualizes Windows Hello. The Registry Key only switches the virtualization of Hello on or off - not Windows Hello itself. If the virtualization of Windows Hello is not switched off, VBS remains in Running status and the hypervisor for Hello remains active. To check use msinfo32.)
Restart again.
2.4 Install the latest Intel generic driver packages suitable for your device now:
(It is best to use DSA to be sure that you are downloading the correct and suitable ones. In the context of this remedy process, however, do not let DSA install the drivers, but run the installation programs yourself while the browser and others remain closed).
Note the sequence and leave the Clean Install checkbox UNCHECKED! (...otherwise everything up to now was for nothing).
1. Intel Graphics (in my case, gfx_win_101.2134.exe) - Restart
2. Network (Ethernet and WiFi) (in my case, KillerPerformanceSuite_36.24.12162_Win10-11x64.exe) - Restart
3. Install the NVIDIA App (not the driver - let the NVIDIA App install the latest and suitable driver package in the next step) - Restart
4. Open the NVIDIA App and let it install the latest driver for your hardware (it should already show that driver package) - Restart
That's it.
Best regards
Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi MF_,
Thank you for sharing your workflow on how to resolve the issue. I'm glad to hear that my previous recommendation to use OEM drivers has helped!
I appreciate your feedback regarding our drivers and will take it into consideration. If you're still okay with it, could you please provide the Kernel dump of your system when the issue occurred? This will help me further investigate the problem.
Best regards,
Dean R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Dean
As I reinstalled Windows during the recovery process, the dumps did not survive this - they no longer exist. Unfortunately I just backed up the the files I have already sent to you.
During the installation of the Intel drivers afterwards, no more errors occurred - so far there are not yet even a crashdump and/or minidump directory or a memory.dmp under C:/Windows present on the system.
Thanks and best regards
Martin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi MF_,
Thank you for getting back to me and I appreciate your response for this. I suggest contacting Dell further regarding driver updates since our generic drivers may not contain the customizations of the device needs. Also, I'm glad to hear that your laptop is working now! If you don't have any other inquiries regarding to your laptop, I will proceed to close this inquiry.
Best regards,
Dean R.
Intel Customer Support Technician

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page