Results 61 to 70 of 120
-
08-18-2020 04:17 PM #61
- Join Date
- Jun 2020
- Reputation
- 10
- Posts
- 22
Memory issues are 80-90% resolved with 0704 bios for me at least. You can get it for any mobo from the first post of this thread: https://rog.asus.com/forum/showthrea...sus-Z490-stuff
I get random resets overnight every once in a while, but rarely see them during daily use. Annoying but I can wait a little longer for a better fix.
-
08-19-2020 03:58 AM #62
- Join Date
- Jun 2020
- Reputation
- 10
- Posts
- 9
its pretty idiot proof.. i put the wrong beta file on mine at first and it tells you wrong file when you go to write it..
just put on usb stick and reboot to cmos, then go to bios update..
dont expect afix... some people have claimed this beta 704 bios file fixed most of their problems.. but it has done nothing for me at all..
still running 1 16gb in dimm 1 only... goes into boot loop if i put the pair in... and it happens to all three ram sets i have for it (all on QVL list)
im at my witts end... i love ASUS but need to fix this so going with another brand reluctantly
-
08-19-2020 06:33 AM #63
- Join Date
- Jun 2020
- Reputation
- 10
- Posts
- 22
ya if you're worried just rename the file to a string with no spaces like asusbios0704.CAP, I think all the renamer does is remove funny characters and spaces. Or you can just load the bios using the ai suite tools if you have them installed while inside windows...
-
08-21-2020 01:09 AM #64
- Join Date
- Jul 2020
- Reputation
- 10
- Posts
- 9
https://www.youtube.com/watch?v=TS-gxtgZ7DU&t=1800s
Hope this help, the suggestion in the video make minor improvement of stability, mine enable XMP 3600 don't freeze after loaded into window, but still cannot run any stress test. And my 10700 also have the same high voltage after enable XMP.
I hope anyone from ASUS can let us know what happened.
-
08-24-2020 09:54 PM #65
- Join Date
- Aug 2020
- Reputation
- 10
- Posts
- 8
Asus
I am in the same boat as the rest of you guys but I did go the route of switching to another brand, starts with M and ends with I and the board is not as good as this one. Luckily, I purchased my ASUS from Amazon, found out the issue existed but thought it was the RAM, also from Amazon and so replaced RAM and then got the other brands board and realised how crap it was and found this thread. So I went back and got the ASUS board and decided to live with it until a fix arrives as it is superior to the M*I board.
My experience of the other board is below.
1. The ASUS has better VRM cooling compared to both the MSI and Gigabyte. The MSI has a fan just as the ASUS but it is a high velocity fan which generates a lot of noise but does a poor job of cooling the VRM's compared to the ASUS VRM fan which does a good job of cooling and is silent, Gigabyte lacks a fan completely (MSI allows full control over the fan in the BIOS and ASUS does not).
2. All the fan headers on the ASUS board are PWM headers, the MSI's chassis header is DC 3 pin.
3. RGB/LED headers are on opposite sides of the board on the ASUS and there are two in total, the MSI has one and it is a 3 pin.
4. The ASUS has an illuminated ROG symbol on the NVMe heatsink which is a nice touch and not overpowering, the light is subtle and easy to control, the MSI has nothing of the sort.
5. The ASUS has both NVMe slots on the top side of the board and both are teamed up with individual heatsinks unlike MSI who have one NVMe port on the top side and one of the bottom side of the board which is a pain if something goes wrong and there is no heatsink for that bottom one due to space constraints.
6. ASUS has far superior fan controls within the BIOS and the software within the OS is very good, gives much better control compared to MSI Dragon Centre software.
7. ASUS can control the LED's on my Hyper-X Fury RAM and enable 'Smart' lighting which is set to change colour in a certain temperature range (0 degrees to 50 green light, 50 to 70 degrees yellow light and 70 to 100 red light). but the MSI cannot control the RAM LED's at all, even though it is compatible and stated in the list on MSI's website.
-
09-06-2020 02:13 AM #66
- Join Date
- Feb 2017
- Reputation
- 10
- Posts
- 7
I have both boards. I can confirm that swapping board solved my problem. I contacted certain individuals @ asus and notified them of the problem. I'm not sure if they fixed or or if it can be fixed as I'm not sure its a board or bios issue. The only thing I can confirm is it was not an IMC/memory/cpu issue. I am aware that they released a new public bios. If someone can confirm it solved there problem let me know and I will retest my board.
-
09-06-2020 03:28 PM #67
- Join Date
- Aug 2020
- Reputation
- 10
- Posts
- 8
-
09-07-2020 07:14 AM #68
- Join Date
- Jun 2020
- Reputation
- 10
- Posts
- 21
0704 or 0707 has solved nothing for me. Tried both with XMP I/II and both gives me freezes.
Only thing helped me is setting VCCIO and SA voltages to 1.1V which is suggested by morello1n (thanks a lot) with this post:
https://rog.asus.com/forum/showthrea...ge4#post809920
I was using 0704 with VCCIO and SA voltages manually set to 1.1V and I've got no freezes or hangs for a month until I flashed 0707 yesterday. Using 0707 with XMP and VCCIO and SA voltages set to auto, STILL gives me random freezing. I will try with 1.1V VCCIO and SA voltages today and report back.
-
09-08-2020 05:05 AM #69
- Join Date
- Feb 2017
- Reputation
- 10
- Posts
- 7
There's 2 ways to quickly identify if you have the problem one much quicker than the other. Run blender benchmark with scene victor. It will crash in warmup/loading scene.
The even quicker way is to install XTU run avx 512 for most of the time 5 mins is enough and more often than not it will hardlock in less than 20 seconds.
2x16bg will aggravate this problem more. 2x8gb will alleviate the problem to an extent as ii could prime stable i could aida i could hci memtest I could game but i couldn't XTU avx 512 for 5 minutes or blender victor scene and pass ever. I've held out hopes that it was all bios but as the reports trickled in that people rma'd board or bought multiples then finally 3 boards later there problems magically disappeared and or used another brand and no more problems and since i've verified it was not my memory or just a bad cpu or bad imc in my cpu i'm really just leaning towards there are some faulty boards causing everyone these problems.
Vccio/vccsa alleviated but did not make the problem go away it just bought me maybe 5-10 minutes runtime in XTU sometimes. Setting tfaw to 16 in my testing seems to really magnify the problem and any decent set of samsung Bdie memory can do 16 TFAW just fine so it's not the memory causing this issue.
Higher speed memory also makes the problem worse. I tested 3600 3400 3200 2933 and lower. The only time I ever could pass was defaults loaded.
The same 2x16gb memory/cpu can do 4000 16-16-16 in another brand ITX board HCI stable, Prime stable, aida64 stable, tm5 anta777@extreme stable and XTU stable so that rules out the bad memory or weak IMC possibility.
The vccio/vccsa in all vendors boards is overkill. For like 2x16gb 3600 memory you should really only need 1.15 SA 1.10 IO and then it scales up from there so like 3800 memory 1.20 SA 1.15 IO and 4000 1.25 SA and 1.20 IO you can probably start with similar scaling with 2x8gb but i would try 1.10 SA 1.05 IO for 3600 and scale up from there as 2x8gb should require less.Last edited by chew**; 09-08-2020 at 05:26 AM.
-
09-08-2020 03:26 PM #70
esarhaddon PC Specs Motherboard ROG STRIX Z390-e Gaming Processor i7 8700K Memory (part number) CRM5522 Monitor VA1912wb CPU Cooler Hyper 212
- Join Date
- Nov 2018
- Reputation
- 10
- Posts
- 8
ASUS NEVER AGAIN, Won't even run 3600 RIpjaws with 0707
I can run 32 gig, 2X16 but have to run them at 3200. TEH thinking of the Engineers is quite good and innovative, but their follow-through is terrible. THey have no Idea how to implement their edeas in the real world. ASUS CS is the worse. I thought MalwareBytes was bad but these guys lie and tell you stuff they know nothing about. I asked about why it wasn't letting me adjust the vccio and even after he assured he really knew the BIOS on my Z490e all he could say was "We don't recommend doing that". Why the heck even make these setting in the BIOS if they don't want you to use them. I did figure it out that ASUS engineers ' changed canoes in the middle of the stream from using the drop-down windows to +/- leys to make the adjustments. I even wrote the CEO's office ( just another cubicle) to get help and they tried to tell me all kinds of things about my RMA on My Z390e MoBo first saying it never arrived, but FedEx had a signature and Satellite tracking on the delivery truck. Then he claimed I sent to the wrong address, which they supplied the shipping label, then said it was damaged, but no photos of the damage or description of said damage, so I told them why not have documentation like I did when I worked CS desk? Then he said well if we see damage on a shipped box we reject it. SO that implies I shipped a damaged item in a good box. Funny I showed it to the FedEx guy to prove it was intact, in pristine condition and he double boxed it to assure safe delivery. They were only trying their lil hearts out to find some reason to void my warranty. After 2 weeks of arguing they will be replacing my MoBo with someone else's junker that has probably been ridden hard and put away wet.
ASUS NEVER AGAIN. Unless ASUS can format a MUCH better Business plan.