E!

[E! @Egbebiyi]

@iam_7even Are we mutuals

[E! @Egbebiyi]

@tkb417 This is normal it’s due to the North Korea actors and because of alot of people shipping their jobs abroad or giving it out or North Korea actors taking up jobs in the US.

[E! @Egbebiyi]

Cancer sucks..

[E! @Egbebiyi]

@Ssaasquatch Lmfao. This took me out

[E! @Egbebiyi]

@iam_7even Too early bruv

[E! @Egbebiyi]

@MrEluaka @AbRaheemmuhd @Olufunmi_17 Let’s keep things private as it should be. Please reach out.

[E! @Egbebiyi]

@sendwaveapp can you kindly fix your issues. I have been waiting more than 4 days. This is very terrible

[E! @Egbebiyi]

@ebiatawodi Go Ebi!

[E! @Egbebiyi]

Thank you Uncle Joe!

[E! @Egbebiyi]

@iam_7even You never know anything

[E! @Egbebiyi]

@iam_7even Who?

[E! @Egbebiyi]

Dip in dip..

[E! @Egbebiyi]

@iam_7even I had to go check also. It’s well

[Arpit Bhayani @arpit_bhayani]

I saw many engineers blaming the outage on Microsoft 🤦‍♂️ SWEs blaming without knowing the root cause is concerning.

It is not Microsoft, it is Crowdstrike who released an update for Windows that had a bug. The patch runs in Kernel mode to monitor system activity at a low level.

Because it was running in Kernel mode, the buggy code was trying to access an invalid memory location that triggered a panic and which showed Blue Screen of Death.

The name of the driver file that had the buggy update is "C-00000291.sys", deleting it fixes the issue and unfortunately this needs to be done manually.

Microsoft has nothing to do with it.

[E! @Egbebiyi]

Fun and long Friday. CS BSOD is totally fun.

[E! @Egbebiyi]

@MyFCMB kindly do check your DM and respond accordingly.

[E! @Egbebiyi]

@iam_7even You too dey meet woman oh.

[E! @Egbebiyi]

@iam_7even Before them use “follow” carry you go

[E! @Egbebiyi]

@iam_7even I beg let’s talk this weekend bruv