Z390 aorus master

[Naxian]

Hello am new here. I just set un account to tell you my problem. First i want to say i watch almost aĺl videos of ltt. Now i have bought a z390 aorus master a set of 2 sticks of ram f4- 3200c16d gtzsw i7 9700k processor. Dark rock pro4 cooler and Samsung evo 970 plus m2 ssd. When i first put them all together and started the pc without windows i tried to set xmp but with no luck. Every time it came back with a screen said something wnt wrong or something i dont remember exactly. Well I thought it's maybe the bios so i continued to set windows. Next bad and worse was that it could even setup windows. It just stayed there and nothing. First was working for 5 or 10 seconds and nothing. I tried with usb or dvd every time same result. Im desperate and dnt know what to do. Sorry for my bad english Im Greek. 

[Princess Luna]

Do you believe you might have tighten the cooler too much? Excessive pressure from the cooler onto the CPU might cause damages to the IMC (before anything else) which hurts it's performance and/or stability, not long ago I helped someone with a 212 Evo too tight that was killing dual channel for him.

[Kitsan]

What code is your debug led array giving you?

 

Code Description
10 PEI Core is started.
11 Pre-memory CPU initialization is started.
12~14 Reserved.
15 Pre-memory North-Bridge initializations is started.
16~18 Reserved.
19 Pre-memory South-Bridge initializations is started.
1A~2A Reserved.
2B~2F Memory initialization.
31 Memory installed.
32~36 CPU PEI initialization.
37~3A IOH PEI initialization.
3B~3E PCH PEI initialization.
3F~4F Reserved.
60 DXE Core is started.
61 NVRAM initialization.
62 Installation of the PCH runtime services.
63~67 CPU DXE initialization is started.
68 PCI host bridge initialization is started.
69 IOH DXE initialization.
6A IOH SMM initialization.
6B~6F Reserved.
70 PCH DXE initialization.
71 PCH SMM initialization.
72 PCH devices initialization.
73~77 PCH DXE initialization (PCH module specific).
78 ACPI Core initialization.
79 CSM initialization is started.
7A~7F Reserved for AMI use.
80~8F Reserved for OEM use (OEM DXE initialization codes).
90 Phase transfer to BDS (Boot Device Selection) from DXE.
91 Issue event to connect drivers.
Regular Boot
Code Description
92 PCI Bus initialization is started.
93 PCI Bus hot plug initialization.
94 PCI Bus enumeration for detecting how many resources are requested.
95 Check PCI device requested resources.
96 Assign PCI device resources.
97 Console Output devices connect (ex. Monitor is lighted).
98 Console input devices connect (ex. PS2/USB keyboard/mouse are activated)
99 Super IO initialization.
9A USB initialization is started.
9B Issue reset during USB initialization process.
9C Detect and install all currently connected USB devices.
9D Activated all currently connected USB devices.
9E~9F Reserved.
A0 IDE initialization is started.
A1 Issue reset during IDE initialization process.
A2 Detect and install all currently connected IDE devices.
A3 Activated all currently connected IDE devices.
A4 SCSI initialization is started.
A5 Issue reset during SCSI initialization process.
A6 Detect and install all currently connected SCSI devices.
A7 Activated all currently connected SCSI devices.
A8 Verify password if needed.
A9 BIOS Setup is started.
AA Reserved.
AB Wait user command in BIOS Setup.
AC Reserved.
AD Issue Ready To Boot event for OS Boot.
AE Boot to Legacy OS.
AF Exit Boot Services.
B0 Runtime AP installation begins.
B1 Runtime AP installation ends.
B2 Legacy Option ROM initialization.
B3 System reset if needed.
B4 USB device hot plug-in.
B5 PCI device hot plug.
B6 Clean-up of NVRAM.
B7 Reconfigure NVRAM settings.
B8~BF Reserved.
C0~CF Reserved.
E0 S3 Resume is started (called from DXE IPL).
E1 Fill boot script data for S3 resume.
E2 Initializes VGA for S3 resume.
E3 OS S3 wake vector call.
S3 Resume
Code Description
F0 Recovery mode will be triggered due to invalid firmware volume detection.
F1 Recovery mode will be triggered by user decision.
F2 Recovery is started.
F3 Recovery firmware image is found.
F4 Recovery firmware image is loaded.
F5~F7 Reserved for future AMI progress codes.
Recovery
Code Description
50~55 Memory initialization error occurs.
56 Invalid CPU type or speed.
57 CPU mismatch.
58 CPU self test failed or possible CPU cache error.
59 CPU micro-code is not found or micro-code update is failed.
5A Internal CPU error.
5B Reset PPI is failed.
5C~5F Reserved.
D0 CPU initialization error.
D1 IOH initialization error.
Error
Code Description
D2 PCH initialization error.
D3 Some of the Architectural Protocols are not available.
D4 PCI resource allocation error. Out of Resources.
D5 No Space for Legacy Option ROM initialization.
D6 No Console Output Devices are found.
D7 No Console Input Devices are found.
D8 It is an invalid password.
D9~DA Can't load Boot Option.
DB Flash update is failed.
DC Reset protocol is failed.
DE~DF Reserved.
E8 S3 resume is failed.
E9 S3 Resume PPI is not found.
EA S3 Resume Boot Script is invalid.
EB S3 OS Wake call is failed.
EC~EF Reserved.
F8 Recovery PPI is invalid.
F9 Recovery capsule is not found.
FA Invalid recovery capsule.
FB~FF Reserved.
 

[Naxian]

First thank you all for your quick reply. 

Now the odd thing is that there is no funny code. Even when it stacks on win installation its AO.  And to tell you the truth i dont think i tightened too much the cooler. Its not my first time bulding a pc.

[Naxian]

On 8/3/2019 at 2:28 AM, Princess Luna said:

Do you believe you might have tighten the cooler too much? Excessive pressure from the cooler onto the CPU might cause damages to the IMC (before anything else) which hurts it's performance and/or stability, not long ago I helped someone with a 212 Evo too tight that was killing dual channel for him.

I dont think tightening is the issue. From what iam reading on internet these days its probably a ram compatibility issue. I zend it back and i ordered onother set ti check. I will post again for update

[Naxian]

Finally i managed to fix it. It was not motherboard ram or cpu issue though. Everything works perfect now i have not trid any ocing i only enabled xmp. Iam realy so happy. I will post a video on youtube on how i fixed it

 

[jerkwagon]

On 8/9/2019 at 12:53 AM, Naxian said:

Finally i managed to fix it. It was not motherboard ram or cpu issue though. Everything works perfect now i have not trid any ocing i only enabled xmp. Iam realy so happy. I will post a video on youtube on how i fixed it

 

i love how you say you fixed it and only said what the problem wasnt.. any insight would of been helpful.