Ryzen 3000: Asus opens up PCIe 4.0 support for selected X470 and B450 boards

As I wrote. Take for example 2700X (105W) TDP chip. Set limit in BIOS to 65W and it will not exceed it. (As long as BIOS has this option since RM on runtime allows minimum of 70W for given chip.)
And since people operated 2700X on those boards, it is really not that bad. But you can cook many boards by having no fans in case. I have seen test of HW Unboxed where they tested different boards and one of tests was case w/o running fans... ~120°C on VRMs, then one fan and something like 60~80°C.

Surely it can handle itself running chip that will not exceed desired limit for average power.

 

Well, just ordered a 3800X for my mATX Tuf Pro-Gaming.
Not going to be using PCIe4 at all, but have the latest Bios installed (1607) that apparently enables it.

Hope the VRM waterblocks arrive this week....

 

Ive read today that on X370 mobos (atleast Asus ones) if you put Ryzen3000 you get the option of Gen4 pciex. I will try that, but don't have new Ryzen. Maybe tomorrow if i buy one

 

buy your chips, but i'd hold off on installing them till this/next weeks bios updates for agesa 1003

 

I can confirm that PCIE 4.0 does indeed work on the Crosshair 7 Hero Wifi

 

I'd test before, in case that is the bios that eliminates the PCIe 4 speed in "other than X570" chipsets.
Just in case.

 

Check your event logs (Microsoft > Windows > Kernel-WHEA) to see if you're getting hit with WHEA errors, these are slowing down system performance and its now being reported to occur with AMD gpu's as well as Nvidia.

Also if you're a destiny 2 player, you need 1.0.0.3 anyway

 

the WHEA also happens with PCiE SSDs. My ASrock B450 can't run for more than 5 minutes with my 3700X installed. I'm getting errors for my GTX 1070 my Samsung 970 Evo Plus SSD and a mysterious 5700 XT that isn't in my computer.

 

im pretty confident that 1.0.0.3 agesa will fix this.

 

No WHEA errors but I have had this persistant dcom error for months and nothing works to fix it.


Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 7/17/2019 9:01:34 AM
Event ID: 10016
Task Category: None
Level: Warning
Keywords: Classic
User: DESKTOP-TJTR3MP\mtrai
Computer: DESKTOP-TJTR3MP
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-TJTR3MP\mtrai SID (S-1-5-21-2953073109-2949042936-1328495743-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2019-07-17T14:01:34.908716400Z" />
<EventRecordID>25535</EventRecordID>
<Correlation ActivityID="{99729336-7a29-4289-bdc1-f9366ea08d86}" />
<Execution ProcessID="1068" ThreadID="9168" />
<Channel>System</Channel>
<Computer>DESKTOP-TJTR3MP</Computer>
<Security UserID="S-1-5-21-2953073109-2949042936-1328495743-1001" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}</Data>
<Data Name="param5">{15C20B67-12E7-4BB6-92BB-7AFF07997402}</Data>
<Data Name="param6">DESKTOP-TJTR3MP</Data>
<Data Name="param7">mtrai</Data>
<Data Name="param8">S-1-5-21-2953073109-2949042936-1328495743-1001</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Unavailable</Data>
<Data Name="param11">Unavailable</Data>
</EventData>
</Event>

 

Thats fixed by https://www.kapilarya.com/fix-event...ant-local-activation-permission-in-windows-10

but its an otherwise harmless thing.