- Joined
- May 13, 2010
- Messages
- 5,926 (1.14/day)
| System Name | RemixedBeast-NX |
|---|---|
| Processor | Intel Xeon E5-2690 @ 2.9Ghz (8C/16T) |
| Motherboard | Dell Inc. 08HPGT (CPU 1) |
| Cooling | Dell Standard |
| Memory | 24GB ECC |
| Video Card(s) | Gigabyte Nvidia RTX2060 6GB |
| Storage | 2TB Samsung 860 EVO SSD//2TB WD Black HDD |
| Display(s) | Samsung SyncMaster P2350 23in @ 1920x1080 + Dell E2013H 20 in @1600x900 |
| Case | Dell Precision T3600 Chassis |
| Audio Device(s) | Beyerdynamic DT770 Pro 80 // Fiio E7 Amp/DAC |
| Power Supply | 630w Dell T3600 PSU |
| Mouse | Logitech G700s/G502 |
| Keyboard | Logitech K740 |
| Software | Linux Mint 20 |
| Benchmark Scores | Network: APs: Cisco Meraki MR32, Ubiquiti Unifi AP-AC-LR and Lite Router/Sw:Meraki MX64 MS220-8P |
Crowdstrike needs to spend more on QA and testing and less on marketing.
Too many companies spend tons of money on marketing these days and barely anything on QA and it shows
Today's example is the crowdstrike windows incident. Millions of critical systems were taken offline because Crowdstrike (wierd name huh?) decided to do a content update that bricked a ton of people's computers and servers.
Tons of images showing blue screens of death and unable to boot into windows.
All down to one file that got corrupted. C-00000291*.sys that the only way to fix this is to boot into recovery mode and navigate to the specified directory and delete that file (c:\windows\system32\drivers\crowdstrike\C-00000291*.sys) and then reboot.
but doing this on millions of systems one by one is going to be all the circles of hell!
WHY DIDN'T CROWDSTRIKE TEST THIS UPDATE BEFORE THEY ROLLED IT OUT?!
BTW I had the same sorta thing happen when webroot anti-virus decided to roll out an update that caused a blue screen and there was a messed up DLL file just like this and I had to boot into recovery mode to delete that file (I'll add it in an edit or reply later for the exact file name cuz I can't remember it off the top of my head.)
Companies need to take QA and testing more seriously and users need to push them harder on this and everyone needs to tear these companies a new hole over this! NOTHING IS GOING TO CHANGE UNLESS WE MAKE THEM DO IT!
Too many companies spend tons of money on marketing these days and barely anything on QA and it shows
Today's example is the crowdstrike windows incident. Millions of critical systems were taken offline because Crowdstrike (wierd name huh?) decided to do a content update that bricked a ton of people's computers and servers.
Tons of images showing blue screens of death and unable to boot into windows.
All down to one file that got corrupted. C-00000291*.sys that the only way to fix this is to boot into recovery mode and navigate to the specified directory and delete that file (c:\windows\system32\drivers\crowdstrike\C-00000291*.sys) and then reboot.
but doing this on millions of systems one by one is going to be all the circles of hell!
WHY DIDN'T CROWDSTRIKE TEST THIS UPDATE BEFORE THEY ROLLED IT OUT?!
BTW I had the same sorta thing happen when webroot anti-virus decided to roll out an update that caused a blue screen and there was a messed up DLL file just like this and I had to boot into recovery mode to delete that file (I'll add it in an edit or reply later for the exact file name cuz I can't remember it off the top of my head.)
Companies need to take QA and testing more seriously and users need to push them harder on this and everyone needs to tear these companies a new hole over this! NOTHING IS GOING TO CHANGE UNLESS WE MAKE THEM DO IT!
