Windows 10 with P67 Extreme6 RevB2 - BSODs

A proud owner of AsRock P67 Extreme6 Rev. B2, serial no# 0CM0X3053908

Purchased in 2011 and still going strong with Windows 7 64bit, except for the 4 SATA2 ports that no longer work. Wasn't aware of the rev B2 SATA2 port decay issue, missed the recall announcement/period altogether, had to find out the hard way when I thought some my HDDs have suddenly died 5-6 years ago. I have since installed 2 PCIe to SATA cards to cater for the HDDs.

So the problem arises when I tried to fresh install Windows 10 (tried both 2004 and 20H2, and each Windows version with all scenarios below) on a SSD (Samsung 850 EVO 500GB), tried on SATA port P0 and/or P1. I get constant BSODs, spontaneously, after booting into Windows.

TL;DR version
#1 - Would updating the BIOS get me out of the BSOD nightmare?
#2 - Has anyone who own the same motherboard and similar setup had any luck updating to Windows 10, successfully?
#3 - What is the mysterious device or driver that's causing all these BSOD?

Current setup:
Note: Everything running at stock, no O/C, stock BIOS v1.10
CPU: i5-2500K
RAM: 4 x 4GB G.Skill Ripjaws F3-12800CL 1600MHz
(Running @ 1333MHz, cannot boot past POST/BIOS with 1600)
GPU: Gigabyte GTX 1060 Mini ITX OC 6GB
PSU: Corsair HX750
PCIe#1 - ASM106X - 4 Ports SATA3
PCIe#2 - ASM1166 - 6 Ports SATA3

For the Windows 10 installation, there's only the ONE 500GB SSD connected to either P0 or P1 at any one time. All other SDDs and HDDs are disconnected. The 2 x PCIe to SATA cards were also disconnected. To rule out the chance of a faulty SSD, I've inserted this SSD (with Windows installed) onto another PC (Lenovo Tiny m93p), and it booted fine, no BSOD observed in 2 hours. Put this SSD back into AsRock P67 Extreme6, the constant BSODs came back. Then I tried with a brand new Crucial MX500 2TB in two of the iterations in those scenarios, got the same results - constant BSODs.

The long version
After installation of Windows 10, I get constant spontaneous BSODs when I get into Windows, giving the error "Kmode exception not handled", on all 3 scenarios below. And every time after booting into Windows, it won't last more than 30 minutes before it gets a BSOD.

Scenario #1 - Let Windows Update install all the required drivers.
     * Case#1 - Windows 10 ver 2004 on P0
     * Case#2 - Windows 10 ver 20H2 on P1
     * Case#3 - Windows 10 ver 2004 on P0
     * Case#4 - Windows 10 ver 20H2 on P1

Scenario #2 - Manually install the following Windows 10 drivers (with no Internet Connection)
     * AsRock P67 Extreme6 website:
        - Intel ME 11.0.0.1156
        - INF driver 10.1.1.8
        - 3TB+ Unlocker utility ver:1.1.1
     * 3rd Party:
        - Etron EJ168 USB 3.0 ver_0.119
        - Marvell SATA3_mv91xx_1.2.0.1049
        - Realtek LAN_Win10_10045_10232020
        - Realtek Audio R2.81
        - Nvidia Drivers 457.09, released 2020.10.29, for Win 10 64-bit

Scenario #3 - Connect to the internet after Scenario #2, and let Windows Update does its things. I noticed the following was updated,
     * Intel ME 11.0.0.1156 updated to 11.0.0.1157
     * INF driver 10.1.1.8 updated to 10.1.1.38

Also mentioned before, if I boot with Windows 7, everything is hunky dory.

Checking the Event Viewer, these event IDs are constantly popping up in a group, quite consistently:
     * Event 1001: Bugcheck...
     * Event 41: Kernel-Power
     * Event 56: Application Popup, with the following PCI codes
        - PCI 01000000684CE00000
        - PCI 010101010101010100

I've also run Windows Memory Diagnostics, no issues found.

Tried unplugging mouse and keyboard and leave the PC alone - still end up with BSOD.

Device Manager hasn't shown any drivers issues.

Then I was desperate enough to run "Verifier.exe".
1st round - No unsigned drivers have been found
2nd round - No drivers built for older versions of Windows have been found
3rd round - Verifying ALL drivers gave rise to a whole new problem, the dreaded "DRIVER VERIFIER DETECTED VIOLATION" reboot loop. I had to google on how to break the boot loop.
Then, event viewer shows a new Event ID 5, Kernel-General.

Having tried all the above, I think I have narrowed it down to 2 possible causes,
1.     A mysterious device or driver
2.     BIOS.

Since I have no luck discovering what this mysterious device or drive is, I turned my area of research to the BIOS, then I found this thread:
[URL=http://forum.asrock.com/forum_posts.asp?TID=3922&title=help-needed-p67-extreme6-b2-revision-bios-problem]AsRock Forum Thread[/URL]

From what I understand, I should NOT need to update the BIOS if I?™m on Sandy-bridge, the update is only required if you are using Ivy-Bridge. Difference between B2 and B3 revisions are the SATA2 ports issues are fixed. The OP in the forum also recommends BIOS v1.80, rather than the v2.10.

So the question now is, do I need to update the BIOS so that I can have a stable Windows 10 installation? If yes which BIOS version should I get?

Would the BIOS update perhaps enable the board to run the RAM at 1600MHz?

I've already looked up in eBay and found this seller: bios-store.
[URL=https://www.ebay.com.au/itm/BIOS-CHIP-ASRock-P67-Pro3-SE-Pro-P67-Extreme6-Extreme4-Gen3-Q77M-vPro/131609241687?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2060353.m1438.l2649]eBay Link[/URL]

Hi MichelvH, still no joy from my end I'm afraid. The other thing I've tried after posting this is installing Intel RST (Win 7 version downloaded from Asrock website). No notable improvements -- still getting constant BSOD.

I've already given up to be honest. I'll just stick to Windows 7 on this machine.

Did you have 1903 or 1909 before 20H2?

I might try with 1909 or 1903.

Long time using Win 7 x64 Ult on Asrock P67 Extreme4 revB2 with no problems.
Few days also ago tried to install Win 10 x64 Pro 20H2 and... constant BSOD KMODE_EXCEPTION_NOT_HANDLED!!!
Tried different 20H2 install source (official, non-official) - same BSOD.
Tried 2004 version - same BSOD.
"Out-Of-The-Box"! Constant BSOD! BTW, in safe mode (and it's very strange) OS works stable.
I've searched many forums, even MS site. Then in some thread on MS forum I've found message with information that last versions of Win10 can't be installed on older hardware configurations and decided to try lesser version.
Then I've tried to install 1909 version and it works! No BSOD. But ))
There is some strange thing... CPU load showing always 100% for all 4 cores (i have i5-2500k on MB) and CPU clock showing insane values, like 43567890 GHz, while system mainly is responsive.

Saint cow... how it works!?!?
[url=https://ibb.co/Stc1jD0][/url]

So the Windows 10 installation problem on P67 chipset can be resolved with earlier versions - 1909 and earlier.
But fake 100% CPU load... for example, i have latest BIOS 2.10 for my M/B P67 Extreme4 revB2 and problem is still there...