Sin Stalker

So a single stick of ram from the other machine gave me a post without issue. Does this mean BOTH sticks of my Corsair Vengeance RGB Pro are bad? It seems highly unlikely both went bad. My thought is perhaps WHATEVER is wrong with my system (power delivery, motherboard controls, whatever) has killed the ram over this time. I think this because I have a hdd that went bad due to this instability. Something would cause one hdd to ramp up and down. It would disconnect and reconnect randomly. If I removed that HDD, the other HDD would immediately begin ramping up and down, and disconnect/reconnect. It is why I'd have to have only my NVMe and sata SSDs. No HDDs. I guess the next test is to stick both sticks of my good ram into the machine and see if there is any instability?

Yes. I have another kit in the family media pc / vr machine. I'll pull that. I am still going through with each slot and each stick to see if it'll post with a single stick of either ram. So far one stick will not result in a post in any of the 4 slots. Switching to the other stick now. Then I'll pull from the other machine and try a single stick from there.

Was way ahead of you. Noticed when I tried to run memtest again, while looking up the recommended configuration for one stick of ram with my motherboard, that it wouldn't post at all now. No splash, no bios, no memtest. I removed the ram and left in the one stick in the correct location. No post. Swapped it with the other ram stick, no post. My system will not post now. All lights come on, but no display. The Q-Code reads "8 ", as in the first number is 8 and the second number is blank. I checked the manual and there isn't a code for that. https://www.asus.com/Motherboards/ROG-CROSSHAIR-VI-HERO-WI-FI-AC/HelpDesk_Manual/ I put both sticks back in and got a post. I'm thinking crashing mid-memtest messed something up. Going to retry one stick again.

So I think the system crashed while running memtest. It was more than halfway done with no errors. I was working on some HW and when I looked up, I noticed both screens were black.. It has been awhile since I used memtest86 and I don't think that's how it looks when it finishes.

GPU was already swapped. A GTX 1070 was used, a 1080ti, a 1080 FE and a 1080 zotac mini. The problem is 100% not the GPU. No other cards. I have memtest on a usb. I'll run it now.

Ruled out the SSD, I think. Now that the crashing is occurring again, I ran apex when using the nvme and crashed. I then removed it and booted with my 1tb sata ssd and crashed in apex again.

I've had this PSU since the life of the system. Going back when this was originally a 1700x and an ASUS B350-F motherboard.

And it would void my warranty. So I'll just wait for the replacement. The system just crashed again while I was an hour and a half into my class. Just had a zoom meeting going for that time, nothing else happening. There was also no noise. Nothing is hitting the fan. I verified that.

It isn't a buzz. It sounds like grinding type noise. Like a card in a bike wheel. Sometime it sounds like grinding. The PSU I have is under warranty, so a replacement is on its way. The fan sound was enough to trigger an RMA. So is your thinking the problem is either PSU, NVMe drive or...? I figure if I swap the psu, try a sata ssd to boot from and if nothing changes then the problem has to be mobo?

Ive had a lot of homework and finally got back to this now. Apologies for the slow reply. At first, after turned everything back on to run unigine valley, the noise on my power supply was gone. Everything seemed fine. Even booting up a game. But I continued with UV and ran the benchmark. Halfway through, all of a sudden there was a single artifact/white box for a moment and the sound on the PSU returned. Benchmark finished and I got a score: 5276 with FPS:126.1. Ran the benchmark again with the noise occurring from the beginning and got Score:5261 and FPS: 125.7. For good measure, I turned on Apex. I was able to run a single PVE mission without it crashing. This is something that would not happen before. I would crash either as soon as the mission loaded or halfway through. The noise of the PSU was there but went quiet after a few minutes into the mission. Before the noise was constant as long as the computer was on. Given that I normally play with a headset on all the time, it could be the noise has always been there was instability in the system occurs and I never realized it. But as far as I can confirm, the noise started after 1pm last week and my system was fully unstable. I will install windows on a separate ssd and see what happens with UV and apex.

You mean do a fresh install of windows on my current drive or are you saying fresh windows on another draft, as in it may be my m.2 that is causing the problem??

"The system has rebooted without cleanly shutting down first." It is because I shut down my computer, but after 5+ minutes of it having that blue screen and the words "shutting down..." in the center, I held down the power button. Then a few minutes later realized I forgot to upload them here and went back in. My system often won't shut down and I have to do it manually. Although I hit shut down this time, after logging back on to check what the error was and it shut down quick and easy this time. /shrug

I am not sure what to make of these. I booted up apex to get proper times. System messed up at 10:31 on my phone's clock. Got back into windows at about 10:33. Also, there are lots and lots of warnings being generated constantly. I will refresh the list after a minute or two and itll take up the whole viewing window. This is all with the same PSU, RAM, etc, installed. Wanted to get these listed before class. I'll try single ram sticks in a few hours (after class).

I've tried xmp enabled and disabled, as well as running my 3200 ram at 3000. No change. I've ran 1 stick before with other stability issues going on and it had no effect. But I'll try tomorrow again. Currently the PSU is removed and I'll be RMAing it back due to at least the fan noise. Is system folder in event viewer?

I'll try running with a single ram stick to see if it's the issue. I don't think it is a socket pressure issue, as I have a Ryzen CPU. But I haven't installed anything recently, save for Zoom for a summer math class and then HWinfo64 after the issue began. I just found out about the crash stuff log. Here: I don't understand how to read them. Is there a guide anywhere? No OC. Specs: CPU: Ryzen 2700x Mobo: Asus x370 Crosshair IV Hero AC/wifi Ram: 2x Corsair rgb vengeance pro Main drive: m.2 nvme Samsung 970 Evo ssd. Gpu: GTX 1080 FE (but also have it happening with a 1080 zotac mini). PSU: EVGA g3 850w 80+ gold.

Either some point during a game (early on or immediately upon opening) or sometimes when simply opening an image, my computer's screens go black and shit off. The fans will ramp up to 100% and everything will stay this way until I hit reset or cut power via the PSU. If I do not reset, eventually the post screen comes up and stay up, with an LED stuck on VGA or boot. It started today, around 1pm and no matter what I do (event swapping out the GPU), the problem persists. I've also noticed the fan on my PSU sounds bad. It is loud and harsh.

Any idea what these mean?

I'll open CPUID HWMonitor and eventually notice extremely high frequencies in the max column. Here are some screenshots I took: 5802 MHz 5580 MHz 5580 5441 4784 If these don't look right, could this explain my instability issues I've been having for almost a year?

I am having ongoing issues. Now I keep crashing randomly while I play Apex Legends. I am trying to figure out if information on CPU, GPU and other component's temp are saved at the time of crash, as well as other information? Besides some abnormally high CPU frequencies, I cant see anything out of the ordinary before a crash occurs.

Turns out the problem wasn't solved. So it was just off in settings. Still crashing and other shit...

Thank you. That is what I have now done. https://www.overclock.net/forum/11-amd-motherboards/1624603-rog-crosshair-vi-overclocking-thread.html#/topics/1751252 Also, my board had been saying AA most of the time as well. Although I think it may have said something different several months ago. But either way, turning completely off now is weird...

Oof. I have an Asus X370 Crosshair VI Hero. I've posted about them before. That should cover most of it. Does anyone know if this is a feature that can be activated for other boards like my Asus x370??? I'd love that.

By normally, I mean completing a boot and loading into windows. I ask because after months of struggling with instability of various types, I decided to replace the motherboard. However that mobo was DOA, so I put back in my previous. Instability is better than nothing. Well I got into windows and was then analyzing my cable management when I realized the LED was completely off. This confuses me because for the last year, it has ALWAYS had a code on it. AA, if I remember correctly, would always be displayed. I figured it just leaves the last code displayed. But now I am thinking maybe it is supposed to go off and somehow, reseating 100% of everything may have fixed the issue???? Such a question, probably very obvious to most, is still difficult to Google apparently. So I am here to embarrass myself in order to be probably educated on the subject. Side note, I need an emote such as 'egg on face' for this one, I think.

It won't even post, though. If it refused to load into an OS, that's workable. It also has a relatively fresh OS on it. I fresh install annually.

I have an fx-4300 and motherboard that I used as a media PC for several years. I upgraded that system and listed the cpu, mobo and ram on eBay. The first buyer claimed it wouldn't post and after some time troubleshooting, opened a case to return it as defective. When I got them back I tested it. It posted and loaded into windows without issue. So I assumed either they had a faulty part or took advantage of eBay's buyer protection, sticking me with the shipping bills. Either way it was done. Since it worked fine, I reposted it on eBay and sold it the next day. Now this current buyer claims it's not posting. I've given them suggestions and made sure they werent using the motherboard video ports. Does anyone have any idea why these people are having trouble with this system that boots perfectly for me? Is there a known issue with a solution i can suggest they try that'll fix the issue?