Results 101 to 110 of 152
-
12-29-2017 04:13 AM #101
- Join Date
- Nov 2014
- Reputation
- 18
- Posts
- 113
We were able to replicate in PCIEX16_1, but according to reports it happens in any slots. We'll have to look in a different direction. The main difference is PCIEX16_1 and PCIEX8_2 are directly from the CPU, while PCIEX1_1/PCIEX1_2/PCIEX1_3/PCIEX4_3 are from the chipset GPP ports.
Last edited by elmor; 12-29-2017 at 07:54 AM.
-
12-29-2017 09:06 AM #102
- Join Date
- Dec 2017
- Reputation
- 10
- Posts
- 1
Hi,
I have same problems (reboots on start, crashes) with audio card Xonar ST PCI version. Motherboard is ASUS B350 Prime plus and operating system Fedora 27 64-bit. I tried all ports, OC and default settings, nothing helps. Replication is really problem - sometimes it works a few days (my record is seven days) without problem (switching output, changing cards etc.), but in enough time crash will come. On platform AM3 there was no problem. Without audio card everything works OK.
I think Xonar and chipset for Ryzen hate each other.
Robert
-
01-01-2018 10:33 PM #103
- Join Date
- Sep 2015
- Reputation
- 10
- Posts
- 70
Well, if it is happening on other operating systems other than windows we can assume its not driver related.
It has to be something on a hardware level.
if it happens on any of the pci-e ports (the ones controlled by the cpu and the ones controlled by the chipset) perhaps one should be looking on what's common between the 2 (cpu and chipset).
Could it be related to pci-e power delivery? Something detecting the sound card initialization either as a power surge or malfunctioning hardware?
In the AMD Ryzen platform, what controls/checks the power delivery to the pci-e ports?
I am running out of ideas here...
-
01-06-2018 12:18 AM #104
- Join Date
- Jan 2018
- Reputation
- 10
- Posts
- 1
Another two settings
I can report 2 other settings (one work the other sometimes crash).
I have two of the same cards: Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio]
https://www.asus.com/de/Sound-Cards/Essence_STX_II/
on both machines runs Debian stretch with the newest backports kernel 4.14 (btw other kernels make no difference)
my Home Maschine:
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: 970 PRO GAMING/AURA
CPU:
Socket Designation: Socket 942
Version: AMD FX(tm)-8350 Eight-Core Processor
this works!
the club maschine:
Base Board Information
Manufacturer: ASRock
Product Name: AB350 Pro4
CPU:
Socket Designation: AM4
Version: AMD Ryzen 3 1200 Quad-Core Processor
this crashes when I change the Main volume with alsamixer (not always but reproducible by changing wild)
-
01-06-2018 02:45 AM #105
- Join Date
- Sep 2015
- Reputation
- 10
- Posts
- 70
Any news on this?
Thanks
-
01-10-2018 08:59 AM #106
- Join Date
- Nov 2014
- Reputation
- 18
- Posts
- 113
Still waiting for updates ...
-
01-10-2018 10:55 AM #107
- Join Date
- Sep 2015
- Reputation
- 10
- Posts
- 70
-
01-11-2018 07:21 PM #108
- Join Date
- Sep 2017
- Reputation
- 10
- Posts
- 7
Yea im actually a Systems Administrator and honestly can't figure this one out because its very random. It seems to be conflicting with something as for what it is anyone's guess. I had mine working for 6 months not a single reboot then all of a sudden it starts to reboot again then works for X amount of time again. Trying to spot something that is consistent and there really is nothing besides the "switching" sound. I'm not 100% sure on this but seems like the problem is most likely to happen when you hear the switching sound twice and usually crashes on the second switching sound.
So a good question is why somethings when i open up discord or any game you hear a single click (90% of the time) and other times its a double (10% of the time)?
-
01-11-2018 11:10 PM #109
- Join Date
- Nov 2017
- Reputation
- 10
- Posts
- 12
-
01-20-2018 10:52 AM #110
- Join Date
- Sep 2015
- Reputation
- 10
- Posts
- 70
More than 4 months have passed and this issue still hasn't been solved.
Yesterday it rebooted 3 times in a row.
This is very frustrating guys....
Do you guys have any clue of what the issue is?
This is a piece of premium hardware that cost a lot of money...
Can we please have an ETA on when this is going to be fixed?
Can we, at least, have some feedback other than: "we're waiting"?
We shouldn't have to beg for a solution....
Thanks