XPS 9560 Always Blue Screens on Feature Updates

After spending countless hours over the last year trying to remedy this without a clean install on an otherwise smooth running computer, I finally bit the bullet and did a complete clean install of Windows. The problem started with update 1709 (2017 Fall Creators Update).

When I did the clean install in the spring, everything went well and the computer updated to 1803. Now it's time for the fall update 1809 and what do you know? The exact same "memory management" blue screen. I'm pretty confident that there are no memory issues. Googling around reinforces that but I have no clue what to do now. Is there some driver that I always have that is in conflict with feature updates? Software? I have no issue with any other updates.

What would you suggest I do aside from just hiding the update as a temporary fix?

 

If a clean install fixed your issue with going to 1709 and now you're having an issue going to 1809, my guess is that it's something that is getting installed. I didn't have any issues going to 1709 or 1803 on my 9560. You can always use AIDA64 to test your memory just in case. Perhaps putting the exact error here could help us figure out what may be causing the issue. Also listing your system specs to include drive manufacturer would help too.

 

Hey Custom. Thanks a lot for your reply. I'm not familiar with AIDA64 but I did run memory tests (whatever google suggested as well as Dell's own/BIOS etc) and they were all fine. I agree that the only thing that seems logical is that something I use creates some kind of weird conflict. Like taking two medicines in a rare combination such that it isn't well known, I'm fearful that it's hopeless because the errors I get seem generic and hard to pinpoint since I don't get the sense this is a common issue.

"Installation Failure: Windows failed to install the following update with error 0xC1900101: Feature update to Windows 10, version 1809."

My event log has a lot of error's like this: "
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
and APPID"

I assume that's just because I don't use an admin account for every day use. I am sure I tried to update via the admin account in the past and it didn't help anything. I should also mention I tried to update all my drivers on numerous occasions which changed nothing. I haven't done that very recently but only mentioning that in case that is a default suggestion.

Not sure how to list all system specs (let me know if there is something specific to look for) but here is what I find:
OS Name Microsoft Windows 10 Home
Version 10.0.17134 Build 17134
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer Dell Inc.
System Model XPS 15 9560
System Type x64-based PC
System SKU 07BE
Processor Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz, 2801 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Dell Inc. 1.9.4, 4/23/2018
SMBIOS Version 3.0
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Dell Inc.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Mobile
Secure Boot State Off
PCR7 Configuration Elevation Required to View
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume2
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 8.79 GB
Total Virtual Memory 18.4 GB
Available Virtual Memory 7.36 GB
Page File Space 2.50 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes

 

I don't have a ton of time to search right now, but a quick google search shows a few laptop users having to disable Intel virtualization technology in bios to get their updates to work. Perhaps try that?

 

Thanks for the suggestion. Before trying something like that, is there any risk/downside to doing this?

 

No risks or downsides that I can see. You can turn it back on after the installation. Intel VT is typically used if your going to run virtual machines, chances are if you're not sure what it does then you wouldn't use it in the first place.