Grimm Spector

I have a temperature monitor program running that loads on boot, so I see it. If I just hop into the BIOS and wait for it to level out it is in the idle range around 50 degrees I mentioned in the post. I don't believe it's throttling during boot, but the highest it'll go at 100% usage across all cores is 4.3 out of the advertised 4.5 GHz. Right now if I give it something heavy to play, like Star Citizen it saturates my cores and doesn't appear to be hitting 91 anymore, it's sticking at about 87 degrees. Still isn't passing 4.3 GHz though.

Recently upgraded to a 5800X3D, replaced the stock AMD cooler from my old processor with a NH-U9S, but the thing booted at 90 degrees C, so obviously it appears insufficient. Swapped it out for a Deepcool 240EX AIO, which should in theory provide more than enough cooling, but it still boots in the high 70s to low 80s. And when I try stress testing it, it throttles at 91 degrees at about 4.2 GHz, not hitting the theoretical 4.5 it's capable of and running at maximum temperature, it takes a minute or so to saturate at best. It idles around 48 degrees C after being allowed to sit, and I can't make the room it's in any cooler. I've got the AIO on the front, only place it'll fit my case, drawing in cool air, and two exhausts, one on the back and one on the front. I've set all the BIOS settings to favour "Turbo" fan speeds for all fans, and as far as I can tell they're operating normally, I even replaced on when I put in the AIO just in case it wasn't. I've tried reseating the AIO, not that I figure I badly mounted both the Noctua air cooler and the AIO, one of them maybe. No change. Is this a defective chip? A bad bond to it's IHS maybe? Should I be trying to get this swapped out? Is there anything else I could reasonably try? I've never had such heat issues with a CPU, and in the past AIOs have licked issues where air coolers have failed me.

I recently picked up a new TV and attached it to my PC. Previously I attached a different SDR TV using the same HDMI cable, and it worked fine no issues, except it wouldn't register as HDR with Windows. I picked up another cable, a monoprice cable rated for HDMI 2.1. HDR works, screen works, but I am now often getting this weird rainbow colored static over the top of what I'm looking at, mostly on the lower half of the screen. It happens often on white background pages and screens, much less on other screens. Sometimes when I scroll through a page the upper edge of the artifact will stay on the same spot on the page (i.e. it moves up with the content). I want to know if this is perhaps related to the cable? Or if it's an issue with the screen itself? Not sure what to do to resolve it. Video of the effect attached. IMG_6010.MOV

About a year, was new for this system. The lack of a system event makes me think power supply too. Makes me wish for more integration between PSU and motherboard signalling. Sucks to have to replace, but a heck of a lot better than other options! I'll have to see if I can get a loaner, and reproduce the shut down somehow.

Had a couple weird power offs recently while the machine has been in use and once while idle. Nothing in the system event logs that I can find correlates at all. The system is on a UPS so no power surge. It just turns off as if the power was cut, but the RGB on the motherboard remains on. System will not respond to the power button until the power supply is cycled by turning it off on the back and turning it back on. System appears to start normally immediately after this. Any ideas what it could be? I'm thinking power supply, maybe the supply thinks it's overheating which seems impossible.

Hey I just did a Windows (10) reinstall on a working PC that was having some weird issues, install seemed fine. Components are pretty new, specs below. Ever since the reinstall all other issues are gone, but I'm having this weird stutter or maybe latency, in the audio. It sounds distorted or sometimes slow, briefly, it's not constant, but often every few seconds. It seems to happen on all interfaces, be it the HDMI ports on the graphics card, the optical SPDIF out on the motherboard, of the front panel connector for 3.5 mm audio to the internal audio header. Videos played in MPC and other apps also seems to lag somewhat, though streaming through PLEX and YouTube seem fine for video, but the audio issue persists. The audio issue also happens with just windows sound effects, or anything, local, or remote. I've tried disabling the NIC on the motherboard to see if that was the issue but it wasn't. The reinstall occurred due to a blue screen caused by an errant 10 Gb NIC that the driver just didn't seem to play nice. After it was uninstalled the weirdness began, so the reinstall was done. That card is not and has not been in the system since before the reinstallation of Windows 10. I've tried manually by hand updating all the drivers on the system that weren't as up to date as I could find, I've tried changing the sampling rates, I've tried changing the bit rates, I've tried everything I can think of to fix this and it is driving me nuts. I just want to get back to enjoying content and playing games with my system. The main audio is run into a surround system which I've never had issue with and worked fine on previous PCs and this one up until this point. There are no spikes in CPU usage, disk usage or memory usage that seem to accompany any of the issues. And when I run the DPC audio latency analyzer it tells me that the system should have no problem with real time audio, though oddly it is yellow and cites audio latency as high as 1000 microseconds average, max 1400, which seems awfully high to me. I also don't see any particular spikes in the latency reading during the playback of any audio or windows sounds. Temperatures on GPU and CPU are fine, idle low in the 30s typically, no overheating issues. All audio effects/enhancements are off. Anyone got any suggestions? Specs: AMD Ryzen 7 2700 (not overclocked) CPU ASUS ROG STRIX X470-F GAMING Motherboard 32 GB Corsair Vengeance 3000 MHz, not overclocked, no XMP etc. Main drive is an NVMe SSD with over 100 GB free EVGA GeForce 1060 3GB SSC video card Running in the background typically, Dropbox OneDrive GoogleDrive Steam OculusTrayTool GeForce Experience I hope someone has some idea, as this is driving me absolutely nuts!

Hey, I've got a Windows Server 2016 system running, using a TYAN7067 board. The board has two mini-SAS connectors that each run 4 SAS2.0 drives at 6Gb/s. I'm attempting to add a new set of drives to the array, but am running into some issues. Currently I have 4 existing SAS2.0 drives on the array, and they work fine, they all work regardless of whether I attach one, some, or all of them to either the same mini-SAS connector, or separate connectors. The new drives are all SAS3.0 12Gb/s, but should in theory be perfectly reverse compatible and just run at 6Gb/s, as far as I am aware. However, when they're connected to either of the mini-SAS ports, with or without the other currently functioning drives, none of them show up in disk management. None of them appear to show up in any functional way for me to use. I currently have the opROM on the LSI SAS2 2308 Mustang card disabled so it passes through data, as I typically pass through the drives to virtualized systems. This way there's no RAID level interference of the drive to the virtualized host. This should obviously have nothing to do with the hypervisor WinServer2k16 seeing the drives, as they're always presented to Windows but are set to offlined so other systems can use them directly. Hoping someone has an idea of why these drives aren't being recognized and what I can do to get them working, thanks!

Strange, I can see the USB to boot, but it won't boot, though it was booting from the linux efi files fine ... So, think it may be a RAM issue? :-\

Yup, that's my thinking too, which explains why I couldn't boot to anything when I installed that UEFI version of Ubuntu server...though just now changing some BIOS options it decided it was going to shut off without any error. So I think either the board is bad, or maybe the RAM? Hope it can be just the RAM because finding a replacement board seems unlikely within my budgetary means... To test the RAM I guess I'll have to get Windows running again and load up memtest or something.

Hmm not sure why, but try Ubuntu without installing doesn't appear to be an option even with this image, though it is the server image, maybe you were suggesting the desktop variety? Thought that just had the GUI and was otherwise similar. This has however shown me that for whatever reason when Windows 2016 Server installed it did so in BIOS legacy mode and not in UEFI mode, which is super weird...I am not sure why. I wonder if it's possible this is a badly installed OS issue? Now that I've got USB working-ish I may try to reinstall windows via USB. Perhaps PXE wasn't able to do installs in UEFI mode.

Well, 4 hours in, did some very minor AIDA64 benchmarks, and it was sitting idle after and it went belly up and turned off like before. So it's not just a power issue. On to the live ubuntu attempt...this is so frustrating. There is no 17 available on the site anymore, only 18 and 16, and it's not clear what allows me to do a live CD image. Edit: I dug up what may be the right version, will let you know how it goes when I know.

Their live build was 18.04 live-server ISO, I'll look for a 17 full CD version, though I've had it on this UPS for about 3.5 hours now with no reboots under minimal loads. So maybe this entire building is terrible and this has just been a power issue the entire time. Will update here soon, going to try some stress tests.

Booting from the USB might be possible, I finally made it do that to do the install, which was nice. Though I was using the "live" distribution, and booting from the USB didn't appear to be an option, the only option was to install it. Maybe I grabbed the wrong version, I'll take another look. Testing with another UPS now to see if it's other power issues...

So... I tried that, and once the ubuntu was installed to another disk, the whole thing won't boot. Server starts, but the boot options are all blank, and I manually add another one in, even has me select what efi file I want to boot from, and the ubuntu install is for some reason the only option...and then it doesn't boot from it, and all the boot entries are blank again when it reboots. I have no idea why, nor how to fix this... Edit: I managed to get around this by disabling the ability in the BIOS for the entire disk controller that disk was on to boot, and suddenly I could boot to windows again, it's like if certain boot options are on, others are entirely impossible to reach which is very ridiculous and frustrating. Of course this hasn't solved the shutting down after being on for a few minutes problem.

Sigh, crap. Turns out I was wrong, not sure why it ran stably for a couple hours yesterday, but now it's back to randomly alarming and shutting down after a short time of running, even while idle. PSU is 700 Watts, well more than the server is drawing at any given time, with a load meter I have not seen it try to draw more than 220 so far in fact, though I haven't had the CPUs at full load yet. I've attached another set of server logs here...though this time I'm even more confused about the cause of the shut down than before. This is driving me nuts. serverfail.rar