[coreboot] New Defects reported by Coverity Scan for coreboot

Hi, Please find the latest report on new defect(s) introduced to coreboot found with Coverity Scan. 2 new defect(s) introduced to coreboot found with Coverity Scan. 1 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent build analyzed by Coverity Scan. New defect(s) Re

[coreboot] Re: Debugging Windows 10 BSOD

> Stoney has the same issue, pretty sure it's related to a memory address range being incorrectly marked or something similar (based on the DWORD output of the BSOD), but never bothered to troubleshoot How did you come to that conclusion? > Highly possible you don't need to connect live sessions

[coreboot] Re: Debugging Windows 10 BSOD

Hi Raul, The installer behaves differently than the installed Windows OS, so I'd only try on an already installed OS at first. If you need to do some in-depth debugging, I'd also recommend using a checked build that has debug symbols available. Beware that the installed version is very picky

[coreboot] Re: Debugging Windows 10 BSOD

Forgot to add that to find out what the cause is the easiest way is probably having the installed image configured in a way that it'll write full kernel memory dumps to disk and then use !analyze -v in WinDbg on that generated kernel dump. At least that's what I remember from more than 1.5 year