Linux functions correctly, Windows fails, need assistance!
Linux functions correctly, Windows fails, need assistance!
There are roughly 30 of these issues. At times it seems so "intense" that it won't even complete the blue screen. For example, it might display something like "Your pc ran into a prob," which is it. It simply halts right at that point, without finishing. More often I've noticed irql_not_less_or_equal, acpi.sys and around 20 other entries.
I misunderstood that section initially. It seems like a UEFI BIOS problem at first. From what I understand, Surface BIOS updates are sent via Windows Update, so the issue might have occurred during the update process. It would be best to contact Microsoft for assistance unless there are other suggestions.
At the installer start button, select "Repair your computer" and open cmd. In cmd, enter SFC /SCANNOW. If no errors appear, you may proceed; otherwise, run Dism /Online /Cleanup-Image /RestoreHealth from the same window. You can also launch a WinPE interface and use CMD there, ensuring you navigate to the internal SSD first. EDIT: Verify your location on the SSD before running SFC /SCANNOW.
It seems the system might have been updated, but after rebooting it went into BSOD and recovery wasn't possible. You were trying to fix it using Linux.
You aren't following me. I can't get to the installer bit. It will BSOD before the installer opens up. Here is the process. Surface is off, I put the flash drive in, I press the power button. Surface logo comes on, surface logo goes away, windows logo comes on. Windows circle dots spinning and then BSOD. There is no way to get to a command prompt, a repair option, a restore option etc. It's a bsod way way before any of those options.
I recommend utilizing a WinPE disk for executing commands like Hirens BootCD. Activate one of the "mini windows" configurations.
I mentioned earlier that I also used WinPE, but it behaves identically. WinPE, Windows, anything related to Windows will trigger a BSOD before an installer or command prompt appears. The only exception is Linux, which seems quite unusual in this context.
You could potentially update the BIOS yourself, which might resolve the issue. It could also stem from a hardware malfunction related to an IRQ error, though the unpredictable nature of these errors suggests various problems might be addressed. There’s a chance it works, but I’m unsure about the steps or feasibility.