m$ fucking W10 again

**stj** · 06-24-2020, 01:44 PM

https://www.zdnet.com/article/window...ering-reboots/

**RJARRRPCGP** · 07-12-2020, 07:09 PM

For me, the March, 2020 update was bad.

**ivtec** · 07-14-2020, 12:23 PM

Depend on the Hardware you have. if you have older PC Stay away from 2004 win 10 version,some apps don't work ,1909 version is
ok.

**BigTroll** · 07-14-2020, 04:22 PM

I updated to version 2004 on my asrock deskmini a300, and I did have problems, notably it would be a blank screen coming out of sleep, so I ended up removing the graphics drivers and installed a beta amd one, yes radeon drivers still suck but I don't know weather to blame them or windows 10.

**RJARRRPCGP** · 07-14-2020, 04:54 PM

Quote:

Originally Posted by BigTroll

notably it would be a blank screen coming out of sleep

Sounds like when Windows 98 SE kept crashing, won't wake up if I installed the third party monitor driver said to be from Phillips for the 107S CRT, which it turned out I didn't even need for going to 85 Hz on my cheap Phillips 107S CRT.

Of course, the early-2000s was also a time where the BIOS for AMD systems, seemed a lot more buggy! Soyo was possibly the worst for this!
It would keep crashing at low load and usually found the PC crashed, if I walked away! So, they had a BIOS that was said to be from April, 2001, which fixed that.

But there was a work around for the Soyo SY-K7VTA-B motherboard: (KT133)
Lower Vcore by -0.025V, IIRC.

**Per Hansson** · 07-15-2020, 10:31 AM

That is quite interesting.
My Server 2016 machine had its first ever BSOD a few days ago.
Maybe it is related to M$ fuckups then and not memory corruption as I feared.
I did run Memtest86+ and there where no errors found...

Bugcheck code was: 0x00000109
https://docs.microsoft.com/en-us/win...ure-corruption

**Topcat** · 07-15-2020, 10:49 AM

Quote:

Originally Posted by Per Hansson

That is quite interesting.
My Server 2016 machine had its first ever BSOD a few days ago.
Maybe it is related to M$ fuckups then and not memory corruption as I feared.
I did run Memtest86+ and there where no errors found...

Bugcheck code was: 0x00000109
https://docs.microsoft.com/en-us/win...ure-corruption

Yikes.... I just started test bedding S2K16 on a system....I haven't had this yet, but thanks for the heads-up.

After a round of updates on S2K12, Starcraft1 and AoE don't run anymore. Spit out an error on startup, no idea what's causing it.

**ivtec** · 07-15-2020, 01:18 PM

Quote:

Originally Posted by BigTroll

I updated to version 2004 on my asrock deskmini a300, and I did have problems, notably it would be a blank screen coming out of sleep, so I ended up removing the graphics drivers and installed a beta amd one, yes radeon drivers still suck but I don't know weather to blame them or windows 10.

I just did not try to find out why some apps did not work on 2024,i just reverted to older version 1909 and all was good ,and as they say if it works good don't change.

06-24-2020, 01:44 PM	#1
stj Great Sage 齊天大聖 Join Date: Dec 2009 City & State: Europe My Country: some shithole run by Israeli agents I'm a: Professional Tech Posts: 23,156	m$ fucking W10 again https://www.zdnet.com/article/window...ering-reboots/

07-12-2020, 07:09 PM	#2
RJARRRPCGP Badcaps Veteran Join Date: Jul 2004 City & State: North Springfield, Vermont My Country: USA Line Voltage: 118-127V 59-63.5 Hz-> actualizo: pérdido de voltaje I'm a: Knowledge Seeker Posts: 5,297	Re: m$ fucking W10 again For me, the March, 2020 update was bad. __________________ MSI B450 Tomahawk Ryzen 7 "Matisse" 3700X 16 GB Corsair Vengeance LPX DDR4 SDRAM XFX Radeon RX 580 8 GB eVGA Supernova G3 750W "There's nothing more unattractive than a chick smoking a cigarette" -Topcat "Don't eat yellow snow!" -Salem "did I see a chair fly? I think I did! Time for popcorn!" -ratdude747

07-14-2020, 12:23 PM	#3
ivtec ivtec Join Date: Dec 2008 City & State: Fall River, Mas, My Country: USA Line Voltage: 120-60hz I'm a: Hobbyist Tech Posts: 1,464	Re: m$ fucking W10 again Depend on the Hardware you have. if you have older PC Stay away from 2004 win 10 version,some apps don't work ,1909 version is ok.

07-14-2020, 04:22 PM	#4
BigTroll Badcaps Veteran Join Date: Sep 2010 City & State: Jefferson My Country: LAMBDA SOND Line Voltage: 120VAC 60Hz I'm a: Hardcore Geek Posts: 1,072	Re: m$ fucking W10 again I updated to version 2004 on my asrock deskmini a300, and I did have problems, notably it would be a blank screen coming out of sleep, so I ended up removing the graphics drivers and installed a beta amd one, yes radeon drivers still suck but I don't know weather to blame them or windows 10. __________________ My Computer: AMD Ryzen 7 2700X, Asrock X370 Killer SLI/AC, 16GB Geil EVO X DDR4 3000, 500GB WD Black NVME and 2TB Toshiba HD,EVGA GTX 1080 SC, In-Win 303 White, EVGA SuperNova 750 G3, Windows 10 Pro

07-15-2020, 10:31 AM	#6
Per Hansson Super Moderator Join Date: Jul 2005 City & State: ---- My Country: Sweden Line Voltage: 230v 50Hz I'm a: Knowledge Seeker Posts: 4,552	Re: m$ fucking W10 again That is quite interesting. My Server 2016 machine had its first ever BSOD a few days ago. Maybe it is related to M$ fuckups then and not memory corruption as I feared. I did run Memtest86+ and there where no errors found... Bugcheck code was: 0x00000109 https://docs.microsoft.com/en-us/win...ure-corruption __________________ "The one who says it cannot be done should never interrupt the one who is doing it."

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode