[DISCUSSION] Windows 10 1903/9 'FINAL' Build 18362/3.xxx (PC) [19H1/2 Release]

Discussion in 'Windows 10' started by Enthousiast, Mar 20, 2019.

  1. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,638
    Trophy Points:
    450
  2. Master01

    Master01 MDL Novice

    Joined:
    Mar 18, 2015
    Messages:
    40
    Likes Received:
    16
    Trophy Points:
    0
    1) This build have memory leak, video and RAM.
    Nvidia Pascal dedicated videocard, latest driver 419.67, and try WU driver... same result.
    Firefox 67 Beta, with new Webrenderer engine crush after hour or so of watching video from youtube, consume all available RAM
    Chrome seems works fine.

    2) Some people says that many games (Directx 11/12) also crush with memory leak problem.:throw:

    This issues i see earlier on previous builds months ago...
    If Microsoft did not pay their attention on this issues and did not fix this before GA relese...well, 19H1 may have even worse launch than 1809.:eek:
     
  3. farmers

    farmers MDL Member

    Joined:
    Nov 20, 2011
    Messages:
    226
    Likes Received:
    104
    Trophy Points:
    10
    Looks more like a driver issue than anything, which if you read the link in the post immediately above yours you will find these issues are often addressed in the first few weeks.
     
  4. Master01

    Master01 MDL Novice

    Joined:
    Mar 18, 2015
    Messages:
    40
    Likes Received:
    16
    Trophy Points:
    0
    Issue occur and early 19H1 builds and this "RTM".

    Old drivers Pre 400s - 399.24, new drivers - 419.67, new Hotfix - 425.11, and even special WU driver 430.00 all the same - memory leak!

    Revert back to 1809 and all is fine, every tested driver work fine as it should, no memory leak.

    Maybe some new DirectX features or DWM, graphics layers have this memory leak. 1803-1809 work fine.
    Chrome work on this build fine
    Firefox with new Webrender engine not... memory leak and crush... Division 2 (DirectX 12) also crush because memory leak - consume all available RAM and crush.
    Maybe AMD users have not seen this problem... As i have Nvidia Pascal card.
    Hope MS will fix this soon.
     
  5. WhiteDeath1313

    WhiteDeath1313 MDL Member

    Joined:
    Aug 25, 2018
    Messages:
    113
    Likes Received:
    206
    Trophy Points:
    10
    yeah that is true ..is not the drivers gpu
     
  6. SAM-R

    SAM-R MDL Guru

    Joined:
    Mar 21, 2015
    Messages:
    4,836
    Likes Received:
    4,443
    Trophy Points:
    150
    Drivers are up to Hardware Makers Not Microsoft.
     
  7. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,638
    Trophy Points:
    450
    Probably it's 2 way.

    My main system and my test laptop both don't have windows 10 drivers available by the manufacturers but both run fine on the drivers offered on WU and they don't show any of the mentioned problems.
     
  8. DontuZoru

    DontuZoru MDL Member

    Joined:
    Mar 6, 2014
    Messages:
    200
    Likes Received:
    94
    Trophy Points:
    10
    421.65 and 430.00 have memory leak in games. 425.11 is fine.
     
  9. Leopeva64

    Leopeva64 MDL Expert

    Joined:
    Oct 4, 2016
    Messages:
    1,096
    Likes Received:
    927
    Trophy Points:
    60
  10. antonio8909

    antonio8909 MDL Guru

    Joined:
    Feb 16, 2014
    Messages:
    2,939
    Likes Received:
    1,414
    Trophy Points:
    90
    We need to wait until a fix then... I'll turn off the PC every time for now
     
  11. Konstantinos

    Konstantinos MDL Member

    Joined:
    Sep 8, 2012
    Messages:
    182
    Likes Received:
    74
    Trophy Points:
    10
    I haven't seen any of those memory leaks. I have tested latest Firefox Beta, Chromium Edge, League of Legends and Maplestory 2. The drivers I was using were 419.xx and now 430.xx Everything works as it should.
     
  12. TairikuOkami

    TairikuOkami MDL Expert

    Joined:
    Mar 15, 2014
    Messages:
    1,057
    Likes Received:
    926
    Trophy Points:
    60
    There is a new task \Microsoft\OneCore\DirectX\DirectXDatabaseUpdater
     
  13. Leopeva64

    Leopeva64 MDL Expert

    Joined:
    Oct 4, 2016
    Messages:
    1,096
    Likes Received:
    927
    Trophy Points:
    60
  14. cuteee

    cuteee MDL Guru

    Joined:
    Oct 13, 2012
    Messages:
    5,013
    Likes Received:
    775
    Trophy Points:
    180
  15. Enthousiast

    Enthousiast MDL Tester

    Joined:
    Oct 30, 2009
    Messages:
    35,567
    Likes Received:
    59,638
    Trophy Points:
    450
    With the 7GB hdd space preservation enabled:
    Code:
    Capacity Data              : Total: 63 GB , Avail: 44 GB {69,84%} - Approx Values.
    With the 7GB hdd space preservation disabled:
    Code:
    Capacity Data              : Total: 63 GB , Avail: 51 GB {80,95%} - Approx Values.
    Working, exactly 7GB difference between them :D
     
  16. Leopeva64

    Leopeva64 MDL Expert

    Joined:
    Oct 4, 2016
    Messages:
    1,096
    Likes Received:
    927
    Trophy Points:
    60
  17. cuteee

    cuteee MDL Guru

    Joined:
    Oct 13, 2012
    Messages:
    5,013
    Likes Received:
    775
    Trophy Points:
    180
  18. EaglePC

    EaglePC MDL Addicted

    Joined:
    Feb 13, 2012
    Messages:
    624
    Likes Received:
    226
    Trophy Points:
    30
    1.1809 if works all fine and your happy with it stay on build if it not broken don't fix it
    2.1903 if you want a faster OS (MS new kernel) try it out with bugs
    3. Win 10 LTSC if you want a stable OS no MS Apps (vanilla) better then 1809+1903 , I might choose #3
     
  19. spedia

    spedia MDL Senior Member

    Joined:
    Jul 13, 2009
    Messages:
    281
    Likes Received:
    103
    Trophy Points:
    10
    Not a bad choice. IIRC the retpoline patch was ported to LTSC 2019.
     
  20. mabaega

    mabaega MDL Senior Member

    Joined:
    Dec 30, 2010
    Messages:
    284
    Likes Received:
    179
    Trophy Points:
    10
    Any info for vmware workstation problem in this build?