search

Mattiwatti / EfiGuard

Disable PatchGuard and Driver Signature Enforcement at boot time
GNU General Public License v3.0
1.78k stars 337 forks source link

Booting causes BSOD #72

Closed devingDev closed 1 year ago

devingDev commented 1 year ago

Trying to boot with the 1.2.1 it fails and causes a BSOD with some thread exception or whatever on the bsod it also displays four hex codes on the top left.

SystemBootEnvironmentInformation:

SystemModuleInformation:

SystemCodeIntegrityInformation:

SystemKernelDebuggerInformation:

SystemKernelDebuggerInformationEx:

SharedUserData->KdDebuggerEnabled: 0x00

SystemKernelDebuggerFlags: 0x00

SystemCodeIntegrityPolicyInformation:

stevefan1999-personal commented 1 year ago

Seems like some Windows internal structures are changed...

Mattiwatti commented 1 year ago

Hi,

Thanks for creating an issue, but if you want me to fix a blue screen I'm going to need something more to go on than

a BSOD with some thread exception or whatever

and

it also displays four hex codes on the top left

Preferably I need a crash dump (a 'kernel' or 'automatic' dump will do), but at the very least I need to know the bugcheck code. What does the screen actually say? That includes the four hex codes since they are the bugcheck parameters. Still, without a crash dump it's not likely I will be able to fix this unless the issue is very obvious. So, need more information.

Mattiwatti commented 1 year ago

Backpedaling because I missed this:

IntegrityOptions: 0x2001

I'm assuming you are on Windows 11, or else 10 with VBS enabled. Try bcdedit /set hypervisorlaunchtype off followed by a reboot. If that's not it, see previous message.

Mattiwatti commented 1 year ago

I'm assuming this is the same BSOD as #57, which has been fixed.

If that is incorrect and the BSOD still occurs with 2f4a666, feel free to reopen.