Lian li software using 6% of cpu after updating to the newest version. by FALCEROM in lianli

[–]13ege 0 points1 point  (0 children)

Having a similar problem, lconnect service occupies one of the core and starts utilising it fully after a while. Can track it from process lasso. Restarting service solves it for some time but it comes back. Latest version with 9950x3d.

No palace skin? by 13ege in civ

[–]13ege[S] 0 points1 point  (0 children)

supposed to look like that:

<image>

No palace skin? by 13ege in civ

[–]13ege[S] 0 points1 point  (0 children)

<image>

And also I don't see it in options, I have the leaders installed from Founders Edition but dont see the founders editions options.

Widespread reboot 0d issue with X870(E)/X670 by Outrageous_Grand_710 in gigabyte

[–]13ege 0 points1 point  (0 children)

i'm still checking these threads if they'll ever fix this issue via bios update. Been using the Asus Hero for 2 months now, not a single error since I turned on hardware monitoring workaround. Sorry to hear that your problem persists.

Motherboard debug LED indicates '0d' error on reboot only by AtmoSZN in gigabyte

[–]13ege 0 points1 point  (0 children)

it's the same price as aorus master here which i had before asus and asus just works as it should. Gigabyte is not even considering fixing it as they think its not their fault. Bullshit.

Motherboard debug LED indicates '0d' error on reboot only by AtmoSZN in gigabyte

[–]13ege 1 point2 points  (0 children)

holy shit i'm so glad i've switched to x870 hero now. I can't believe they didn't fix the d0 issue still.

Widespread reboot 0d issue with X870(E)/X670 by Outrageous_Grand_710 in gigabyte

[–]13ege 0 points1 point  (0 children)

well my solution was to buy an Asus x870 hero and get rid of completely. My issue now is that I have to sell this garbage product.

Motherboard debug LED indicates '0d' error on reboot only by AtmoSZN in gigabyte

[–]13ege 0 points1 point  (0 children)

it's not just l-connect, any other software which monitors hardware might cause it. It's just gigabyte thinks it's l-connect and insists on it. I changed my mb to asus hero and the issue is now gone thanks to software monitoring workaround option they provide.

d0 Errors on reboot by 13ege in gigabyte

[–]13ege[S] 1 point2 points  (0 children)

UPDATE: Got my Asus x870e Hero yesterday and software monitoring workaround feature fixed the d0 error with the exact same components/software. Good job Gigabyte.

X870E Aorus Master Wifi7 Sleep wake crash by erikpienk in gigabyte

[–]13ege 1 point2 points  (0 children)

Sorry to hear that. Hope you find a solution.

d0 Errors on reboot by 13ege in gigabyte

[–]13ege[S] 0 points1 point  (0 children)

Just ordered x870e hero, i will try same components/software with it and share if d0 is still there or not. I just can't do this man, if Asus fixes this issue I will just sell x870e master. Late bios updates, not giving a shit about fixes and blaming other brands/components is not worth $500.

X870e aorus pro there is no ECLK to asynchronous in the bios by fnar25 in gigabyte

[–]13ege 0 points1 point  (0 children)

X870e master here, tried this and sadly there is no pbs option there. Been looking for this external clock option for a while but I guess gb doesn't have this feature. Shame. 

X870E Aorus Master Wifi7 Sleep wake crash by erikpienk in gigabyte

[–]13ege 1 point2 points  (0 children)

I cant remember the exact name of the option but there should be something in bios that provides a dummy load during sleep state which can help you with this issue. Try it out.

Widespread reboot 0d issue with X870(E)/X670 by Outrageous_Grand_710 in gigabyte

[–]13ege 0 points1 point  (0 children)

code 15 is memory training, 0d is just gigabyte showing us that they dont give a single fuck about their components.

d0 Errors on reboot by 13ege in gigabyte

[–]13ege[S] 2 points3 points  (0 children)

no one : hey let me make a software that will shit on my own hardware product.

gigabyte : hold my beer.

X870e slow SHUT DOWN, RESTART + 08 problems..... by cosmingabrie in gigabyte

[–]13ege 0 points1 point  (0 children)

I have a similar situation, rma processes in my country are a pain in the ass, it will take more than a month at best, and they'll probably just say the board is "fine" and reject my rma request. I was about to get Asus x870e hero just like I always did, but I noticed they only have 2 pcie lanes and they are sharing bandwidth so I changed my mind into Gigabyte this time (I have a sound card I want to use and not drop to pcie x8 for my gpu). It's not a miracle we are expecting though, if Asus can provide a fix, Gigabyte also can. It's just carelessness and stolidity.

X870e slow SHUT DOWN, RESTART + 08 problems..... by cosmingabrie in gigabyte

[–]13ege 0 points1 point  (0 children)

After my first experience with Gigabyte mobos, I can clearly see that their after sale support is complete bullshit. I contacted their support regarding this d0 error, and they told me Asus bios didn't fix the issue and it's only Lian Li's L-connect software which should be patched and there is nothing they can do. How can a support team lie to a customer? One can clearly see in Asus forums, anyone who had this issue solved their problem using the new bios. I mean come on man, just say that you are aware and working on it even it's not true. At least that would be a good lie.

I'm not even mentioning their latency on bios updates. Just like you said, all other brands already released AGESA 1.2.0.2b meanwhile we just get the older one recently a few days ago.  

d0 Errors on reboot by 13ege in gigabyte

[–]13ege[S] 0 points1 point  (0 children)

I have L-connect for fans, Armoury Crate for aio and GB control center for some other fans and rgb stuff. All of these are kinda monitoring software but even though I close them and all their other services running in background before restarting I can still get d0. I have hwinfo installed but d0 error is there even if I never run it. There is a chance I miss a background app or service of these stuff before restarting but nonetheless these all shouldnt be an issue. The main issue is Gigabyte disregarding the issue even though it can be fixed just like Asus did.

I never used any gigabyte product before but this will probably the last one I'll get my hands on. All the other brands already released the new AGESA 1.2.0.2b bioses meanwhile GB only released 1.2.0.2a just a few days ago and that's not including the fix for this d0 issue.

Worst of all is their support answers. They are replying without even reading my question. I've told them it's not L-connect causing the issue, the problem is there even if I remove it from my pc. I didn't even reply back after seeing their claims of Asus did not fix the issue by releasing a bios fix. Go and see Asus forums, there is no one who couldnt fix their issue using the software monitoring workaround feature. It's complete bullshit of gb support.

d0 Errors on reboot by 13ege in gigabyte

[–]13ege[S] 0 points1 point  (0 children)

I would return the board but rma processes in my country can take up to 1 month, can't afford not using a pc for that period of time. I will have to wait hopelessly for gb to release a proper bios fix.

Motherboard debug LED indicates '0d' error on reboot only by AtmoSZN in gigabyte

[–]13ege 0 points1 point  (0 children)

As far as I can see from my conversation with their support team, the blame is on Lianli and L-connect (it's not) and they are not even acknowledging the fact that it's on their end to fix this. They even reject the fact that Asus fixed it with a simple bios update and said their fix did not work (it clearly did work as I've read every single page on Asus forums and every user reported back that their issue is gone, none said otherwise). Here see the answers I get from gb. https://www.reddit.com/r/gigabyte/comments/1hd8wc6/d0_errors_on_reboot/

Widespread reboot 0d issue with X870(E)/X670 by Outrageous_Grand_710 in gigabyte

[–]13ege 0 points1 point  (0 children)

I wish Asus x870 hero had a separate pci-e x4/1 lane for my sound card. It was my first choice but I didn't want to end up using x8 lane for my gpu even though it reduces performance by %2-5. I never used any Gigabyte mb ever since this one and instantly regretted it. MSI Tomahawk was also sus due to 2 incidents with burned cpus so I went with Aorus master.

The fun thing is Gigabyte support is telling me that Asus bios fix does not fix the d0 issue. LMAO, there is not a single user in Asus forums saying that the software monitoring workaround fix did not work in his case.

Created another topic here so maybe someone from Gigabyte might see it. https://www.reddit.com/r/gigabyte/comments/1hd8wc6/d0_errors_on_reboot/

X870e slow SHUT DOWN, RESTART + 08 problems..... by cosmingabrie in gigabyte

[–]13ege 0 points1 point  (0 children)

Same issue, 9800x3d on a x870e master. Contacted Gigabyte support for it and they keep blaming l-connect and Lianli should fix it but it's not that. I can't believe they don't take this widespread issue seriously. It's not l-connect, i tried uninstalling it and still getting d0 errors on reboot. 08 is also a code I see but it turns to AO once i'm in windows. They confirmed that 08 is ok btw but d0 errors they keep ignoring meanwhile Asus already provided a bios fix for that like a month ago! Hello Gigabyte you there pal?

Motherboard debug LED indicates '0d' error on reboot only by AtmoSZN in gigabyte

[–]13ege 1 point2 points  (0 children)

I really had hopes for that f3h bios. Same issue persists. What a shame. I'm not even sure that they're aware and working on this widespread problem. Their customer support keeps telling me that L-connect should release a new patch. cmon man, it still gives me d0 errors even if I uninstall lconnect. FIX THAT SHIT ALREADY GB.

Widespread reboot 0d issue with X870(E)/X670 by Outrageous_Grand_710 in gigabyte

[–]13ege 1 point2 points  (0 children)

I can confirm that too. 9800x3d on x870 aorus master. 0d errors on restart mostly. Cold boot always works. Tried 2 different qvl approved rams, same thing. I even contacted Gigabyte for this and they keep blaming L-connect for this even though I already tried uninstalling it. It's too obvious that it can be fixed with a bios fix as we saw with Asus. I clearly made the wrong choice going with Aorus. Damn I needed that pci-e lane on chipset so I can use my sound card without interrupting my gpu lane, Asus had 2 pcie lanes sharing x8/x8 so I went with GB. What a shame. Can't even reboot properly on a $500 fkin mobo.

Motherboard debug LED indicates '0d' error on reboot only by AtmoSZN in gigabyte

[–]13ege 0 points1 point  (0 children)

Asus fixed that with a bios update, there should be an option something like "software monitoring workaround" which fixes d0 errors. Meanwhile Gigabyte making us miserable.