2ot

Unfortunately, I've tried upping the voltage. I swapped my slots and now the PC boots into safe boot after failing to POST three times in a row. I have the luxury to return the mobo and CPU to see if that fixes things.

Seems like it was not the cooler at all, I tried with my big ole heatsink just chilling on the cpu (same RAM slots) and I think I figured it out after some time. I think I have a dud CPU because my memory runs perfectly fine at 3600Mhz but when I up FLCK to match it (1800Mhz), my system does not boot at all. The highest I've been able to take flck is 1500Mhz on 1.1V SOC. I think I will return the CPU to Microcenter and try my luck with a new 3600. I don't think I am overreacting by doing this either. It's pretty ridiculous that I can't even run 3200Mhz memory. Could this be anything but the CPU if it only crashes on higher FLCK?

Seems like it was not the cooler at all, I tried with my big ole heatsink just chilling on the cpu and I figured it out after some time. I think I have a dud CPU because my memory runs perfectly fine at 3600Mhz but when I up FLCK to match it, my system does not boot at all. The highest I've been able to take flck is 1500Mhz on 1.1V SOC. I think I will return the CPU to Microcenter and try my luck with a new 3600. I don't think I am overreacting by doing this either. It's pretty ridiculous that I can't even run 3200Mhz memory. Could this be anything but the CPU if it only crashes on higher FLCK?

Hey there, I would've done some more troubleshooting before posting here if I had the time but I have to drive back to college tomorrow and won't be back home within 15 days to return any components to Microcenter if needed. System: Ryzen 5 3600 ASUS B550-F Gaming (WiFi) Crucial Ballistix Gaming 3600Mhz (2x16GB) Inland Premium 2TB NVME SSD Nvidia GTX 1080ti EVGA GA 750W The issue I am getting is that the system is booting in non-DOCP (2666Mhz) mode with two sticks perfectly but then if I try changing to DOCP, the ASUS default settings result in the next boot cycle getting stuck on the amber RAM LED. The only way to get the system to boot again is if I take out the CMOS battery (is there a faster way to reset BIOS?). I have updated chipset and BIOS to the latest version. I also encountered an error on the built in memtest for Ryzen DRAM Calculator, with MEMbench: Memtest. I'm assuming this knowledge doesn't narrow it down much? I have not tried different slots yet, I'm going to try loosening the CPU cooler a bit and trying to boot in DOCP, if that doesn't work then I will have to play with it a bit more tomorrow. Should I try single slot 3600Mhz? My cooler is massive and my PC is mounted on my wall so maintenance sucks.

I'm getting the same issue with a Ryzen 5 3600, ASUS B550-F Gaming (WiFi), and 32 gb 3600mhz Crucial Sticks. I have updated chipset and BIOS to the latest version and everytime I try to boot with DOCP the boot gets stuck on RAM and I have to reset CMOS. I also encountered an error on the built in memtest for Ryzen DRAM Calculator, with MEMbench: Memtest. Is this a faulty RAM kit or is that not certain? I have not tried different slots yet, I'm going to try loosening the CPU cooler a bit and trying to boot again, if that doesn't work then I will have to play with it a bit more tomorrow.

Yeah, I contacted crucial and they said it should work if set on xmp and their statistics show it was a popular combo, albeit with a low return rate, (probably because of the microcenter deals) but I'm surprised after searching for hours I can only see me having this problem. The crucial support guy also said it might be the 3600 specifically as others have chosen different cpus for this combo. Still gonna wait the estimated 3 days for gigabyte support lol. I'll keep this post updated.

Xmp is not helping to boot both sticks but it is making the systems seem faster to boot and less jittery on single stick. One system is running newest bios (N4) and the other is running the older but still ryzen 3000 compatible bios (F40) and no luck. The bios settings are not always saving, could this mean that xmp would help but the bios is fucked?

Just tested on my friends system with the same exact specs and the same problem occurred... No way it is 2 duds in a row?

Yeah, I tested and the system is most stable on xmp and will even push to 3200 mhz on a single stick but does not even post on two. Is this a compatibility issue?

Sorry for the late response, I am about to test them more thoroughly but both sticks do work individually.

Hey dumping specs at the beginning, everything is new: B450 Aorus Pro Wifi Updated to newest N4 BIOS Crucial 32GB BLS2K16G4D32AESB Radeon Rx 5700xt Inland Professional HF2E Pcie m.2 ssd Powerspec 750BSM Ryzen 3600 Now the problem... The PC is already setup with windows and updated... With one stick of RAM. I was able to boot with a single stick even at 3200 mhz. When I try to insert both sticks, even at 2400 mhz, the motherboard's LEDs indicate that the system is stuck on DRAM and occasionally flickers back to CPU. This was the problem on the older BIOS update as well and all slots have been tested and work. Important to note, the PC takes a longer time to boot, sitting on the DRAM light, after going back to one stick or after turning off the power supply. Not expecting any for sure solutions because the 3600 is new but thanks in advance!

League of Legends has a very handy network log analyzer, in that I have random spikes in packet loss but nothing insanely high (4-5%). Enough to be noticeable in-game however. It also shows me that my jitter is at best 8ms and at worst 14ms. One of the latest tests I did, with just the modem, showed a small period where the jitter and packet loss were both at zero for maybe 1 minute. Could this be a puma 6 chipset issue and I just swapped a bad modem for bad?

Just tested with all the conditions, the network logs for League look the same and the test results are the same, the only difference is that the resolver issue from the Netalyzr test goes away without the router, understandably. I am starting to think that this modem swap might be a hoax because I swapped a shitty modem for a puma 6 modem which is notorious for latency, jitter, and packet loss.

I can see the resource usage on my router and everything is as expected really. Nothing that looks like it's bogging down the network just some wireless usage, less than 4 gigs on the day and the downloads I did today. None the less i'll run some virus cleaners through everyone's devices and try a period where no devices are connected to make sure. I'll double check the cable thing, only time I can think this might happen is to my room where my main pc is located. I also don't use wireless to game. Could this be a problem with my router just not efficiently handling packets or something along the sort? Would new firmware like openwrt solve a problem like that?

I've been experiencing some weird jitter and packet loss on my network for quite some time now. Last month it got bad to the point where it was frustrating to play most online games. I thought it was the modem, replaced it with the netgear cm700 and the problem got better but wasn't fixed. Now I'm looking funny at my asus rt-ac66u because I think I have extensively tested everything else. ALL cables have been checked using a network cable tester, modem replaced, Comcast has great results with other customers in my area, AND I just installed a fresh copy of Windows 10. I am running out of options and really don't want to spend more money. I think maybe this Berkeley Netalyzr test might help me solve the problem, but I am quite inexperienced with networking so it makes little sense to me. ANY help would be appreciated, if you need any more information / results from the test I would be glad to post them, I just posted the ones that were flagged for reasons that weren't predicted to be a security measure. Network performance (?): Latency: 33 ms, Loss: 0.0% + TCP connection setup latency (?): 36ms + The time it takes your computer to set up a TCP connection with our server is 36 ms, which is good. TCP connection setup latency (?): 36ms + Background measurement of network health (?): no transient outages + During most of Netalyzr's execution, the client continuously measures the state of the network in the background, looking for short outages. During testing, the client observed no such outages. Background measurement of network health (?): no transient outages + Network bandwidth (?): Upload 8.6 Mbit/s, Download >20 Mbit/s + Your Uplink: We measured your uplink's sending bandwidth at 8.6 Mbit/s. This level of bandwidth works well for many users. During this test, the client observed 62 reordered packets. Your Downlink: We measured your downlink's receiving bandwidth at >20 Mbit/s. This level of bandwidth works well for many users. Network bandwidth (?): Upload 8.6 Mbit/s, Download >20 Mbit/s + Network buffer measurements (?): Uplink 120 ms, Downlink 50 ms + We estimate your uplink as having 120 ms of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic. We were not able to produce enough traffic to load the downlink buffer, or the downlink buffer is particularly small. You probably have excellent behavior when downloading files and attempting to do other tasks. Network buffer measurements (?): Uplink 120 ms, Downlink is good + Certain TCP protocols are blocked in outbound traffic Not all DNS types were correctly processed Certain TCP protocols are blocked in outbound traffic The path between our system and your network does not appear to handle fragmented IPv6 traffic properly Your system is configured to use 1 DNS resolver(s). The resolver at 192.168.1.1 could not process the following tested types: Large (~3000B) TXT records fetched with EDNS0 Requests from this resolver come from 69.252.244.129. This resolver requires 75 ms to fetch a result from our server and 0 ms to return a result from its cache. It validates DNSSEC. It provides DNSSEC records upon request. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties.Show them. IPv6 Path MTU (?): Warning – Your system can send and receive fragmented traffic with IPv6. The path between our system and your network does not appear to handle fragmented IPv6 traffic properly.