zwclose

I ran it on bare metal Windows 10 22H2 64 bit.

>BugChecker is not so well tested on bare metal Oh, that's sad. Local debugging is a very important advantage, it would be nice to have it. >because the BugChecker main...

Hi Vito, I managed to start the driver before the storm but it didn't help, interrupts have started consuming CPU time ~1-2 minute after system start. I made one more...

No, I didn't even try to break in. Frame buffer autodetect doesn't work though I see that NativeUtil detects memory resources correctly (at least they match Device manager's info). And...

Hi Vito, Got a lot of progress with BugChecker. What I did: 1. Disabled video drivers, set framebuffer parameters to: 640 * 480, address from resources.txt, stride = 0 2....

>just start the BugChecker driver with "some" framebuffer info, correct or incorrect doesn't matter. Awesome! I played with the framebuffer trying different resolutions and strides. Noticed that: 1. NativeUtil sometimes...

Looks one of the problems is that EnumDisplaySettingsA returns incorrect results when video drivers are unloaded. On my bare metal Windows it does not return the actual resolution but the...

I tried stride 0 too, no UI, just some garbage. >So you are unable to determine your screen resolution when the display drivers are disabled, even with Windows' display properties,...

I have a feeling that calling EnumDisplaySettingsExW with EDS_RAWMODE flags can solve the issue, I will try it later today.

You are about to hear the dumbest root cause ever. You have been warned. 4K resolution returned by EnumDisplaySettings was correct. Stride detected by BugChecker was correct too. What made...