last win10 update possibly sucked 10% perf

[toutenglisse]

Me and a friend (same hardware, only difference is 16GB and 1070) had the same experience since yesterday : messing with the bios and benchmarking (realbench 2.56), we saw a performance drop.

I just modified my OC profile at 4.8Ghz, only increasing cache speed (ring ratio) to 4.4Ghz instead of 4.2, and I ended in realbench with a 117000 score instead of 130000 before with 4.2Ghz cache.

My friend made a 5.0Ghz OC profile instead of precedent 4.8Ghz, and he ended with 89000 instead of 95000.

I am very suspicious with last windows update…. the only thing that occured recently…

This is just first sightings but something happened ...

[Gnadentod]

WIN10 = Most complex spyware ever invented, camouflaged as an Operating System. Why does a single update make the systemperformance drop by 10% (!)? "Background" processes? Why was WIN10 totally FREE to update to?

 

Get back to WIN7 and enjoy.

Edited May 10, 2018 by Der Hirte
Grammar typos, english not native language.

[Gearbox]

This a meltdown and/or spectre patch or something else? Those have significant performance penalties for certain things.

 

https://meltdownattack.com/

[Mouse_99]

You could try and roll back your system to just before the last update and run a test again, to verify this. just ensure you are set up the same way with no additional apps running in the background that could affect your score. Don't know of any way you can block any particular update or patch for certain, they always nag you and do it behind your back regardless whether you want it or not.

[streakeagle]

I am dreading the day when I build a new system and have to "upgrade" to Windows 10. I am in the process of replacing all of the Win 7 64-bit computers at work with Windows 10 machines. Between Windows 10 and the software updated to support Windows 10, my work applications are worse than before. Win 7 64-bit gave us an exceptionally stable platform for controlling and monitoring water and waste water plants for over 5 years. We never had to apply any Windows patches or software updates and almost no problems were caused by the OS and/or the software applications updated to support Windows 7 64-bit. Now everything is getting screwed up and will require many hours of work to fix thanks to the "upgrades".

[David OC]

I've had a fairly good run moving to windows 10. I was hesitant as I new win 7 and this was also a new pc build, went like a breeze really and performance has been good with very little mucking around.

 

Work was a little harder tho, needed to jump on teamviewer a few times with some of the software upgrades, so much business software that was only made to run on windows 7. This is intended also I think. See you will now need to upgrade to this new version for it to work on win 10 blah blah blah.

 

We have 150,000 dollar machines that need to be completely upgraded to be on win 10 LOL. Some of these machines are only 10 years old running XP and never missed a beat. I was worried about the old mini PC's in them, cost to replace.....$5000 without install LOL, and still on XP as the drivers for this model cannot be updated. I found and bought 2 of these old mini PC online for $250 and just drive cloned the machine PC twice, swapped them out and they worked perfectly for backups.

[BitMaster]

I am on war with my WIn10, that much to the latest build and overall quality.

 

It plain SUCKS BIG TIME. Too many things change, too many companies have to adopt their drivers, BSOD's that are documented and what not else.

 

Tbh...I just permanently installed Linux Mint on my rig, screw windows for my daily work for now.

 

Got no issues in Mint...wonder wonder...

[wizav]

Unfortunately dcs require windows to run, I wonder what is the minimum version ?

 

 

 

 

Sent from my iPhone using Tapatalk

[cichlidfan]

Unfortunately dcs require windows to run, I wonder what is the minimum version ?

 

I would guess Win 7. I think I ran the original A-10C release on XP, in 2011, but I won't swear to that, and DCS World did not exist then.

[toutenglisse]

I'm still very suspicious it's the last win10 update, probably a "fast-made" spectre/meldown patch. It's not drivers or bios.

After more testing I wanted to rollback win10 version but it looks hazardous

[Johnny_Rico]

still rocking windows 7 64 on a Z370 system with a 8700K

(even though Microsoft tries to tell you that windows 10 is required for that chipset//CPU combo)

[BitMaster]

The patches I received yesterday seemed to have cured my BSOD's..but it might be too early to say so.

 

With Mint and google's stressapptest I can verify it's not the rig but the OS/Software that's BSOD'ing. I installed Steam and can play F1 2015 and many others to verify integrity of the system. I developed a disbelief in my system which is not good at all. I need Mint to regain trust, so to say.

The other thing with Mint ( Ubuntu derivat ) is, if you overdo with oc, Win may boot and crash badly, this Mint hangs right away and wont even try to boot all the way. It seems much more picky on clean overclocking than windows is. If Mint boots, you are on a good path.

 

 

So..since that update from yesterday KB4103721 no more BSOD's...yet......LoL hate it

[toutenglisse]

OK I think I found it .... I rollbacked to version 1709 (actual is 1803) and my realbench 2.56 scrore is back to normal (I made 132015 with my same classic OC 4.8Ghz + 1080Ti OC)

 

So my previous scores with 1709 previous to 27 April were between 128-132000 points, than we had 2 updates (1803 the 1st May and a cumul. 1803 the 5th May) and my scrores went down between 115-118000. Now that I rolled back to 1709 scores are back to 130000+.

 

The thing is that the last 1803 update is there waiting for a reboot .... THO !!

[toutenglisse]

It's OK, the update was not for 1803 version but for 1709.

So the last update I have is 1709 version update KB4103727 installed the 11 May.

And the realbench scores are OK (3 shots between 127000 and 131000)

 

So it seems that spring update (1803 from the 1st May) takes 10% perf. away from one's rig.

[toutenglisse]

I'm coming back on this issue that me and a friend we have with win10 vers.1803

 

My friend didn't go back to 1709 because he lost his bravery during a win10 update some months ago .... at this time his Microsoft account got bugged during process and he had to re-install everything.

 

With actual uptodate 1803 install (updated from today, correcting SSD compatibility) he still has bad realbench scores (culprits in benchmark are encoding and multitask scores - wich are CPU multicore perfs benchmarks if I don't mistake) while I have normal scores with win10-1709.

But he also has problem with SSD : read speed OK (538mb/s) but write speed no ... (450mb/s instead of 530) - my ssd scores are ok (534mb/s and 513mb/s - similar to theorical scores 530/510 of my model) - I am using win10-1709 from before 1stMay but uptodate.

(using crystaldiskmark 6)

 

So .... actual win10-1803 has problem with CPU perf and also SSD perf (in write)... The thing of course is that, reading the net and this thread/posts ... that we are 2 having troubles ...

 

(it's not really tested but in "heavy gaming" (wildlands) with 1803 I had many fps drops during intensive fight and with 1709 everything back to normal - no fps drop)

[toutenglisse]

Friend fixed the SSD problem by re-installing driver from MSI (sata driver) - I read on web that 1803 had messed up some drivers in some cases so it seems logical.

 

He tried than to re-install motherboard's driver for chipset (in hope to restore CPU perf. for encoding) but no luck...

[nachomaga]

I go back to 1709, poor performance in the last update too. Anyway, I’ll be listening. Good luck to you friend!

[BitMaster]

I keep getting BSOD's with various reasons, hardly any two are the same.

 

It only happens in Windows, most of the time when I am away..... and I just cant nail down the bad guy.

 

Time to change this rig, either a new MB or a complete AMD kit. I am getting fed up with this, also the non working XMP. Since the last Bios came out it all went south. I may need to flash an old one back and check... meeehhh

 

Havent checked performance with the old Build, so cant tell, tho I do believe you are basically right.

[toutenglisse]

Hi and thanks for him nachomaga.

 

Ouch! bad news Bitmaster. Any chance it started after 1803 update ? (cause BSOD at idle could come from driver failure, and 1803 seems to mess up with some).

 

I bet you've tried everything (all MB's drivers check/update, unchecking specific power saving option for network card, ...) and this kind of problem is awefull when you don't know what is culprit ...

[Tripleinside]

For what its worth i’d been pulling my hair out with dcs crashes to desktop, logs showing random errors, along with windows suddenly throwing bsods out of the blue, with various reasons (mainly power management)

 

All of this crap stopped when i removed the automatic memory XMP profile in my msi mobo’s bios. None of the logs pointed to ram, yet Windows AND dcs are now stable... go figure...

[hannibal]

the updates affected every thing in order to combat microcode flaws like spectre

[BitMaster]

running only 2 x 8GB modules in straight XMP profile now.

 

It might be RAM with the last 2 recent Bios's or 1803 with the idle thing as it happens when I am not at the machine.

 

I had it do a full 3.5h max torture stresstest this afternoon, all stable...will see if it's the RAM config with 4 modules.

 

and yes, tried many many things.... to no success

[hansangb]

Man that sucks. Microsoft certainly screwed the pooch on this one. Luckily, I didn't have any issues. But on the Alienware laptop, the update has been blocked, so we'll see. Not in a hurry to update the laptop though.

[gavagai]

Man that sucks. Microsoft certainly screwed the pooch on this one. Luckily, I didn't have any issues. But on the Alienware laptop, the update has been blocked, so we'll see. Not in a hurry to update the laptop though.

 

Microsoft is patching the OS to guard against a security flaw created by Intel.

[hansangb]

Microsoft is patching the OS to guard against a security flaw created by Intel.

 

 

 

 

I'm not criticizing the intent, just the execution.