11th gen Prestige 15 +others and Razer core x chroma issues

Dadudeondacouch

New member
Joined
Oct 19, 2021
Messages
7
Asking here as a last resort, I recently got an msi prestige 15 and hooked it up to my core x chroma and have had nothing but problems. I’m familiar with egpu’s but it seems this laptop and the summit e15 have the same issue.

The egpu will work fine when you set it up but once you restart the machine with it unplugged (clearing the os kernel from ram) you will then get a bsod at boot (acpi_bios_error) the bsod will affect normal boot, recovery and even trying to boot from a usb windows installer so you effectively have a brick.

ec reset (hole in bottom) and bios reset (holding power) do not resolve the bsod the only way to resolve it is to flash the bios and after doing so it reboots a few times and then starts normally but once you plug the core x in it will happen again. Core x works fine on other laptops with identical setup.

bios, drivers, software, os etc all up to date so not sure what the next step is as it appears to be a bios issue but talking to msi support is less than helpful.
 

drek4

Active member
PRIVATE FIRST CLASS
Joined
Feb 18, 2018
Messages
814
Asking here as a last resort, I recently got an msi prestige 15 and hooked it up to my core x chroma and have had nothing but problems. I’m familiar with egpu’s but it seems this laptop and the summit e15 have the same issue.

The egpu will work fine when you set it up but once you restart the machine with it unplugged (clearing the os kernel from ram) you will then get a bsod at boot (acpi_bios_error) the bsod will affect normal boot, recovery and even trying to boot from a usb windows installer so you effectively have a brick.

ec reset (hole in bottom) and bios reset (holding power) do not resolve the bsod the only way to resolve it is to flash the bios and after doing so it reboots a few times and then starts normally but once you plug the core x in it will happen again. Core x works fine on other laptops with identical setup.

bios, drivers, software, os etc all up to date so not sure what the next step is as it appears to be a bios issue but talking to msi support is less than helpful.
What video card are you using in your chroma?
 

Dadudeondacouch

New member
Joined
Oct 19, 2021
Messages
7
With the prestige there’s no security on thunderbolt so no having to set always connect etc. and there’s no firmware downloads on the site for the a11scx model which is very new in aus.

I’ve had it on over a weekend playing games without issue rebooted and shutdown ok I thought awesome I got it sorted and then I unplug it and take the laptop to work and the error comes back. It’s like something gets flagged in the bios that causes this as the only way to resolve the bsod is to flash the firmware again which I obviously can’t keep doing.

This is the closest I have found to someone with the same issue (half way down the issue is explained) https://insider.razer.com/index.php?threads/rbs-core-bsod-on-every-boot.30471/
 

drek4

Active member
PRIVATE FIRST CLASS
Joined
Feb 18, 2018
Messages
814
With the prestige there’s no security on thunderbolt so no having to set always connect etc. and there’s no firmware downloads on the site for the a11scx model which is very new in aus.
ThunderBolt Driver 1.41.987.0


MSI Center

 
Last edited:

Dadudeondacouch

New member
Joined
Oct 19, 2021
Messages
7
Oh sorry I have tried that driver and also the version slightly higher that windows downloads. There’s no firmware updates for the thunderbolt from what I have been reading msi bundles them into the bios updates.
 

Dadudeondacouch

New member
Joined
Oct 19, 2021
Messages
7
So far this is what I have...
Starting the pc with the Razer Core X Chroma plugged in causes no issues at all.
I have to disconnect the device using the app in the taskbar which disables the gpu in device manager and then unplug the gpu before shutting down or the bsod will occur next boot. This is the whole issue.

My current workaround is to do the above when shutting down and I used gpedit.msc to add a user login script (powershell) to detect if the device is connected and re-enable it if it is.

Code:
If (Get-PnpDevice -PresentOnly "PCI\VEN_10DE&DEV_1F08&SUBSYS_868E1043&REV_A1\6&71e7989&0&00080038") {
pnputil /enable-device "PCI\VEN_10DE&DEV_1F08&SUBSYS_868E1043&REV_A1\6&71e7989&0&00080038"
} Else {
Exit # Device Not Found
}
 
Top