BSOD 0x0000003b ntoskrnl.exe+75b80 mostly on Shutdown

Ok yes, I got the hang again even after formatting. Seems like a driver issue.

I've posted it here.

Please read the entire Driver Verifier article. It will explain what to do in the event that Driver Verifier causes a boot loop, in which case you merely go into Safe Mode (tap F8 before Windows logo) and then disable Driver Verifier from there. If somehow Windows wasn't getting into Safe Mode either, then it means there's a hardware issue that coincidentally popped up, since Driver Verifier does not load on Safe Mode nor most 3rd-party drivers.

You're good with the settings for Hwinfo. It's odd, but it just means either Hwinfo doesn't fully support your motherboard, or your motherboard isn't revealing voltage sensor data. If you haven't already updated your BIOS, that would probably help.

I wouldn't be too sure on the driver thing. There's a good possibility that there's a hardware issue, and whereas it previously triggered a BSOD through corrupting some driver operation, with that driver out of way and the environment altered, it causes a lockup instead.

I've reviewed the other thread. I'll wait and see how the results are with removing that one particular software.

OK, it seems to have solved the problem. It's been a couple of days, I've been running smoothly. So I'm marking both threads as solved.

I'll read the Driver verifier article again for future. If possible, can you link it ? Maybe I've been reading the wrong one.

Still don't know why the voltage sensor data isn't showing. BIOS is up to date. I'll try and find out somehow if I can.

Thanks again to both of you in this thread. I think the reps should be on their way :)

Sure, link to DV article again is here. I admit, the part where it explains what to do when experiencing a boot loop is kinda vague, with this line:

If you can't get into Windows because it crashes too soon, try it in Safe Mode.

Doesn't really explain what to do inside Safe Mode (hint: turn off Driver Verifier). It also goes to explain what to do if Safe Mode doesn't even work, but I think that's superfluous. Driver Verifier only operates in normal Windows mode, so if there's problems accessing Safe Mode, it's coincidental, and is a sign of some other issue, not Driver Verifier.

Glad to hear it was just this rogue software that happened to slip past me, and that it's taken care of.