Windows 10 with P67 Extreme6 RevB2 - BSODs

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   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.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
welshypie Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 09 Apr 2021 Status: Offline Points: 15	Post Options Post Reply Quote welshypie Report Post Thanks(0) Quote Reply Posted: 09 Apr 2021 at 1:24am
	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.

pauljva Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 17 Mar 2021 Status: Offline Points: 15	Post Options Post Reply Quote pauljva Report Post Thanks(0) Quote Reply Posted: 17 Mar 2021 at 8:45am
	I had this problem and my minidump showed cfosspeed6.sys was the problem. I uninstalled the Asrock XFast LAN utility and my problem seems to have gone away. Asrock P67 Extreme6 with i7-2600K, bios P1.60 Clean Windows 10 Home x64 install, March 15 2021

Angilas Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 04 Mar 2021 Status: Offline Points: 2	Post Options Post Reply Quote Angilas Report Post Thanks(0) Quote Reply Posted: 04 Mar 2021 at 9:23pm
	I forget to say Windows 20H1 and 20H2 same not work only Bluescreens get

Angilas Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 04 Mar 2021 Status: Offline Points: 2	Post Options Post Reply Quote Angilas Report Post Thanks(0) Quote Reply Posted: 04 Mar 2021 at 9:20pm
	Hello all.. Same Problem here with a Asrock Fatal1ty P67 Professional Windows do not run after 2004 Version only Bluesreens get not usetable I have try all no way. Looks Windows 10 have make here a big Error in the new Core ans much p67 Board get same Problem Windows 10 only works fine to Version 1909 Any have contact ASRock Support or Microsoft ?

smuchen Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 29 Jan 2021 Status: Offline Points: 1	Post Options Post Reply Quote smuchen Report Post Thanks(0) Quote Reply Posted: 29 Jan 2021 at 5:54am
	Looks like same problem happens with all P67 chipsets motherboards. Same issue on my AsRock P67 PRO3 SE and also didn't find a solution. But it all started, when I bought sh*ttiest Zalman VE350 external hard drive. Before that, there was not such a problem, but also something obv broke in my motherboard, cuz it wont start with the CMOS battery now. Could it be actual BIOS problem?
	smuchen

MichelvH Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 Nov 2020 Status: Offline Points: 3	Post Options Post Reply Quote MichelvH Report Post Thanks(0) Quote Reply Posted: 04 Dec 2020 at 9:48pm
	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...

Qwertikator Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 04 Dec 2020 Location: Russia Status: Offline Points: 5	Post Options Post Reply Quote Qwertikator Report Post Thanks(0) Quote Reply Posted: 04 Dec 2020 at 5:23pm
	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...

Qwertikator Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 04 Dec 2020 Location: Russia Status: Offline Points: 5	Post Options Post Reply Quote Qwertikator Report Post Thanks(0) Quote Reply Posted: 04 Dec 2020 at 5:14pm
	Aha! This like! Soooo, as we see, system is idle! [url=https://ibb.co/JF1pbHm][/url]

Qwertikator Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 04 Dec 2020 Location: Russia Status: Offline Points: 5	Post Options Post Reply Quote Qwertikator Report Post Thanks(0) Quote Reply Posted: 04 Dec 2020 at 5:11pm
	Saint cow... how it works!?!? [url=https://ibb.co/Stc1jD0][/url]

Qwertikator Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 04 Dec 2020 Location: Russia Status: Offline Points: 5	Post Options Post Reply Quote Qwertikator Report Post Thanks(0) Quote Reply Posted: 04 Dec 2020 at 5:02pm
	Here is the thread about fake 100% CPU loading: [URL= ]https://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/why-is-windows-10-final-build-showing-100-cpu/493e1afa-8fce-4779-8962-8e21dfe57df9?auth=1&page=1[/URL]