Windows 10 with P67 Extreme6 RevB2 - BSODs

I've had limited success with rolling back the video driver that Windows Update wants to install. However still see a BSOD now and then. I've had no luck trying to update the bios version as it won't recognize the file I have on my flash drive. It sees the flash drive but won't recognize the file.

Sorry my control of English language is not good
Hi I also just registered to let you know.
ASRock p67 pro3 B2 (with fail in sata port)
Bios 2.0.2L custom.
The same problem: bsod in Windows version superior to 1909.
1909 working well.
Next I installed Windows system to superior at 1909 and update bios to the last beta 3.40 work well stable system about 48 hours on, but ¡In bios I lost 2 socket of ram! The total of 12gb= 2x4gb and 2x2gb only appears 2x4gb in slot A1 and B1, I can choose between 1066 or 1333, in other program as cpu-z appear 12gb, in system and games only 8gb.

The next step to test downgraded bios 2.40beta to 2.30stable = the pc don't work... press button on 1 second restart, 3 second... restart restart restart...

In the past in all versions of Windows 10 this pc have CPU 100% fake in task manager.

If you need download a specified version of Windows 1909 there to ways:
Universal MediaCreationTool wrapper for all MCT Windows 10 versions from 1507 to 21H1 with business (Enterprise) edition support
https://gist.github.com/AveYo/c74dc774a8fb81a332b5d65613187b15
Or
https://uupdump.net/known.php?q=1909

And global information:
https://answers.microsoft.com/es-es/windows/forum/windows_10-update/c%C3%B3mo-volver-a-una-versi%C3%B3n-anterior-de/0e1b4386-a228-43dc-9592-3ac2b278aae1

Guide to flash bios external
https://www.bios-mods.com/forum/Thread-GUIDE-Flash-BIOS-with-CH341A-programmer


By other hand I contact with support of ASRock via mail about what is the correct version to update bios and the answer was:
Hello,
sorry no Spanish speaking. I reply in English.
You can ??based on serial number
Purchase Date:
20 Feb, 2011
Serial Number:
11MOX1052811
??only go to BIOS 2.xx ??because of B2 stepping of chipset.
BIOS 3.xx is only for B3 stepping chipset mainboards.
In answer to shop other main board to test
We do not have this mainboard anymore on stock (since many years).
You might find it on platforms like eBay, Amazon or local used part platforms?
best regards,
ASRock Support
ASRock Europe B.V.
Bijsterhuizen 1111
6546 AR Nijmegen
The Netherlands
www.asrock.com
From: noreply@asrockamerica.com [mailto:noreply@asrockamerica.com]
Sent: 30 July 2021 23:41
To: support@asrock.nl
Subject: #P67 Pro3# Dudas de compatibilidad (Spain)


Thanks by this forum, member, and answer.

MichelvH wrote: I have the exact same thing and haven't found the solution yet. Seems to be an issue with one of the drivers. In this case I think it's the Intel chipset driver set, but there is no newer version than the one I have installed. I think it's time to sunset this motherboard and go look for a new one...

Hi MichelvH, The fake 100% CPU load, was this on 1903 or 1909?

aqq wrote: Just registered on forum to let you know that I figured it out on my P67 Pro3 B3 and i5-2500K. Also had values like 3879465GHz in task manager. I've installed latest BETA BIOS for motherboard. It looks like it was intended for this purpose because it's flashable through UEFI Instant Flash, not from Windows OS where you get BSOD's and probably you won't be able to successfully flash. Now the values in task manager are normal and I don't get any BSOD's

Unfortunately there's no "Instant Flash" or "CPU monocode update" for the p67 Extreme6.

Hi,

I havent such a BSOD issue with my AsusTek board. Neither do I see CPU at 100%, and CPU speed looks correct on my side.

But I get high system interupt usage + CPU at 14% after cold boot. I need a further warm boot to get things Ok.

That box was initially running Win8, then was updated to 10 (up to the most recent version). It worked fine until last summer, then after a Windows update, interrupts went high...

I assume I have a driver issue, but didn't find which one, or how I could tweak that box. So I'm booting (cold initial), then rebooting (warm boot) to solve that interrupt usage issue.

My HW is ASUSTeK COMPUTER INC. P8P67-M (RAID) plus i7-2600K. It may be a rev 3.0 mother board (I would need to open the box to check this). With a BIOS of 16/07/2013.

I have a similar problem, and will attempt to detail as much as possible here:

HARDWARE
P67 Extreme4 - P1.60
i5-2500K
Samsung 850 EVO (original, still running Win10 1909)
Samsung 860 EVO (new, attempting clean install of Win10 20H2)
Corsair Vengeance Blue 16GB (2x8 GB) DDR3 1600MHz (PC3 12800) (CMZ16GX3M2A1600C10B)
GTX 960
Corsair TX750 PSU

SOFTWARE
Windows 10 Pro version 1909 (10.0.18363) (This is what I'm currently using that doesn't bluescreen)
BIOS settings: Drives in IDE mode on 1909, attempted AHCI on 20H2 (explained below), no overclocks, mostly or entirely default config.

HISTORY
Originally built in the summer of 2011 with a disk instead of SSD. Upgraded to 850 EVO SSD originally and eventually upgraded to Windows 10, but remained on IDE mode because of problems switching to AHCI mode (may have been my own misconfiguration in the past).

For the past few years in Win10 I have had the CPU utilization bug (pictured):



In 2020, I decided to purchase a new SSD (860 EVO) and attempt AHCI again, this time with a clean install of Win10. However, I would get unpredictable reboots and/or bluescreens on the system after installing and logging in. Can't remember the error anymore. Ditched this attempt for awhile and remained on Win10 1909 with my previous configuration (850 EVO), which is stable and doesn't bluescreen on me.

In 2021, I repeated this previous attempt at a clean install on the 860 EVO with AHCI, this time using Win10 20H2. After the initial install process, after the first reboot while configuring the system, windows bluescreens with the dreaded KMODE_EXCEPTION_NOT_HANDLED. However, after that it somehow manages to boot and I am able to log in. Once in it's only a matter of time before it bluescreens on the same error again, though (the longest I've seen it go is about 15 minutes).

If I'm quick enough, I can reconfigure windows to boot into safe mode, which seems able to run indefinitely. However, parsing the memory dumps as suggested in various other forums has turned up nothing specific - no particular driver is identified as the problem, it's always one of two kernel executables.

There was one thread, somewhere (maybe MScommunity help), where a user indicated that they updated their BIOS to fix this problem - however at the moment I cannot find it.

If I dig up any promising resources on this problem or make any progress I will share it here.