Windows 10

IT WORKED!!!!!! :cool::cool::cool::cool::cool:

Clipboard02.jpg


Hours upon hours of trying to fix these damn BSOD's, and a very sleepless night where I could've lost everything ( *** YOU MICROSOFT ). It turns out the reason why it's BSOD'ing is because Windows 20H2 updates the Intel Management Engine interface automatically which doesn't support certain Z97 chipset motherboard Bios's. The MSI and some EVGA boards. The only way to fix it, is to flash to the latest BIOS and then re do the update! Basically the Interface is talking to the wrong code of the system hence BSOD every time when Windows thinks it knows best! I would never have known this if I hadn't typed the name of my motherboard and this update version!

What a minute... Z97, what year is the new BIOS from? This don't add up. I have another system with an i7 3770K and Z77 Asrock Extreme 6 from 2012. The BIOS I've got installed is from 2015 yet 20H2 never tripped up on it. There is a newer from 2018 with Microcode updates but I've never bothered with it.

Why would it trip up certain Z97 boards?
 
To be fair there are a million and one things like this which could trip up updates - sure many of them individually are simple to test but that is a lot of testing collectively.

(It doesn't help MS have massive reduced down their internal testing and only listen to what they want to hear from external testers/"insiders").

Which is why you don't use an updates approach like they are using in Windows 10 it is just idiotic.

Security updates need to be quicker and easier to apply and entirely separated. Hardware updates should never be pushed through automatically but notified if there are critical security, performance or compatibility issues, feature updates should be left to the end user's leisure. Anything else is utterly pants on head.

My best memories in trust with Microsoft were from the XP days. 2001 to 2007 when Vista hit. I rarely ever remember worrying about updates from Microsoft borking things. There was a decline with Vista testing then Microsoft ramped it up when 7 launched. 7 was as solid mostly as XP from their testing and launch of updates.
 
My best memories in trust with Microsoft were from the XP days. 2001 to 2007 when Vista hit. I rarely ever remember worrying about updates from Microsoft borking things. There was a decline with Vista testing then Microsoft ramped it up when 7 launched. 7 was as solid mostly as XP from their testing and launch of updates.

Windows 7 is pretty flawed as an updates implementation/experience goes - but you could at least take full control over it so that it didn't disrupt your experience of using the OS - Windows 10 though...

XeLd1rM.png

No OS should by its own admission be disruptive.
 
Lesson learnt, don't run DEV builds it always results in a problem causing certain games not to work. I should have knew this since last time it ko'd my Windows install but thought I'd give it another try, to be expected with DEV builds really.
 
Reports of the latest Patch Tuesday security update (KB5001330) causing all sorts of issues, BSOD, performance problems etc... etc..., luckily, im having no issues.
 
Reports of the latest Patch Tuesday security update (KB5001330) causing all sorts of issues, BSOD, performance problems etc... etc..., luckily, im having no issues.

That is interesting. I had heard a lot of complaints but I haven't seen anything out of the ordinary between the two updated systems.
 
Back
Top Bottom