![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
i think some bios updates might have addressed that, maybe, as mine autos to 1.1 too...
yeah its setup odd. maybe a cmos clearing is in order...
I'm tempted to let Dan comment, since I'm 99.9% positive he had an OCed 5950X on the Godlike - he'll know what is off from stock or not, or fi there's a global setting doing something I forgot about.
I went digging specifically for how to configure my exact sticks with my exact motherboard, and didn't find much, except this page confirming their compatibility. Do the numbers in the specs suggest my BIOS should be configured differently?
All that does is run a chkdsk. It won't hurt, but the times I've seen that help in 20 years can be counted without even taking my shoes off. NTFS is damned good at handling that stuff automatically unless the drive itself actually died.
Fix the core cause, or it'll just come back (and you're likely going to have to reinstall windows anyway afterwards either way).
No. It'll be fine.
It'll run forever at 60+c without even blinking - that's well within thermal design spec. Troubleshooting generally doesn't happen much at this level anymore - it's gotten both complex enough, and simple enough, that you don't tend to have to go digging into interrupt polling/etc as a troubleshooting option. One thing: Turn off the integrated audio in BIOS. That'll show if the audio driver is causing an issue, because the device will go away. If it suddenly goes back to performing well, now we know where to dig. Also disable the HDMI audio device on your video card (under device manager), that'll remove that conflict as a potential cause too.
There's no evidence that the drive is the problem. Chkdsk looks for filesystem inconsistencies and journal issues - it, unfortunately, cannot look ~inside files~ to see if their contents are sane (because it has nothing to compare against). Which means you'd just potentially mirror bad data, wherever that is, if this is the issue. There are various ways to do this - all the ones off top of head are UNIX based in some form, but I'm sure there's a livecd version somewhere too.If we're all out of solutions here, then I need to start considering... the nuclear options
* * *
Would this be possible? -> Getting another NVMe 1TB drive tomorrow, placing it on the motherboard alongside the current one (I haven't looked, but the X570 Tomahawk advertises 2 NVMe slots) and then somehow MIRRORING all the contents of my C drive onto the new drive. If this is somehow doable, would it not be a preferable solution to losing everything and starting over, from a time/workload perspective? I just wouldn't know where to begin mirroring a NVMe windows/c drive. (I assume it involves creating some sort of image (.iso?) and then copying all of that to the new drive?)
This is where I'd normally turn now. But in order, I'd do this:If there are good reasons why this would not work, then re-installing Windows from scratch on the same drive after a full reformat seems to be the final solution. Ugh. I hate my life. What would I have to do here, place the Windows media creator app on a bootable USB stick and letting it do the rest automatically? (And re-entering my Win 7 license key when prompted? I think that's how we did it the first time.)
Whew! Sorry for the novel-sized recap. I'd just hate to go to the nuclear option if there was an easier fix to this all along (like some kind of rollback feature) and wanted to be thorough.
same sluggishness.Yes indeed. Kernel issues like that are likely a RAM issue, before anything else. And more specifically, a RAM configuration/settings issue.
Man I remember that thread. I felt so bad for that guy!
This all sounds like good advice, and I'm real close to feeling brave enough to do itYeah. My money is on crashes from RAM - and you finally corrupted the inside of a file (hence why things are going weird) on a crash. It's rare, but it can happen. PS losing things - the file wasn't closed, and the fall back is probably "create new file" when its trashed.
So, to my prior points -
0. Restore bios defaults. This will clear all the settings your friend did - he did it manually, we don't really do that anymore unless we're REALLY trying to push boundaries on overclocking. You're not, so lets not.
1. Set SoC voltage manually to 1.1. Ignore the auto setting.
2. Enable XMP Profile 1.
3. Reinstall Windows. Try to see if things are stable now. Betcha they are. IF not, set RAM voltage to 1.35 or 1.4v - try again. Windows installs are dead easy these days.
what's the best way to restore BIOS defaults? (When I Google the subject, I get some scary answers involving unplugging the power supply, looking for specific pins, etc.) Surely it's easier than that?
Chkdsk tells you if the filesystem is fine (it is, apparently). The drive itself will throw SMART errors (it isn't) if it's broken - that'll show up all over the place. That leaves file contents, and there's no way to really check those other than checksum against a known-good file of the exact same version (g'luck).
Generally it's under the save/exit page in the BIOS - would be something there that says reset to default. No need to touch batteries or pins anymore!This all sounds like good advice, and I'm real close to feeling brave enough to do it
Sure. That'll try replacing files from teh WIM image on the media. I'm always sketched out about that from WAY too much history to bother - and you'll want a backup anyway, so... might as well reinstall? If it goes wrong, you're reinstalling anyway, so...
Ayup.
It's from the boot media of some kind, yes - haven't had to do that since Server 2012, so I'm rusty.
File ops are REALLY slow - I don't expect bandwidth on small files, but file ops are extremely slow. This is weird. Still fix the ram - otherwise we might be chasing ghosts. That's always my FIRST AMD troubleshooting step for good reason.
But I thought default RAM settings is what lopoetve wants me to reset my BIOS back to. I'm so confused.
Okay, let's recap the facts that seem to have become a little blurry again (apologies if you're sick of them at this point, but maybe some late arrivals to the discussion appreciate the rundown).
It's scary going into this thing for the first time! =)
Right?!
I agree! This was my first VPN experience ever (never tried one before) and 6 months later, I've already decided that I'm switching to the browser extension until my subscription runs out, regardless how this nightmare ends.I agree, I've just been hit with a lot of conflicting advice at once (not only here, but elsewhere as well) and wanted to look into as much of it as I can (for instance the SFC /scannow, resetting to BIOS defaults, and/or running CHKDSK /F from recovery console)... things I was planning to get to eventually. Unfortunately, it's 3am now so I'm done, but I hope to try at least the BIOS reset tomorrow.
thats part of your confusion/problem. we here are all telling you the same thing. we dont know what they are telling you "elsewhere", causing you confusion. so pick a poison and stick to it, i would suggest us, but im biased...
Yes, so we can set them correctly. I have no idea what your friend set - he clearly set parts of it manually, and parts of it on auto, and that isn't a sane path anymore (it used to be, things change).
With Ryzen? Yep, it's a bad thing. Ryzen is picky. Perfectly stable once you set it right, but picky before that.Are you saying the guy who helped me build the rig just set auto-everything? Hmm. Is that really a bad thing, though, if it's displaying all the correct values while set to auto (and has been running flawlessly outside those VPN-related KSCF errors for 6 months)? In other words, what if you guys are right about the Kernel Security Check Errors piling up and eventually breaking something that caused the sluggishness (which wouldn't explain why it began with the CHKDSK/VERIFY) but that it's the VPN software causing these errors, not the RAM? (Maybe I need to shut up with alternate theories since I am way out of my depth here.)
Don't know how the software would handle that. That is the VPN adapter, but lord knows how the software would handle it (I use IPSEC and OpenVPN, but my use case is entirely different than yours). Disabling it won't hurt, but the software may bitch at you or just re-enable it.You suggested disabling Ethernet earlier, to see how performance is affected. I tried it, and it killed my internet (which is normal). Without rebooting (because this takes forever now) I then tried loading Photoshop and it was just as slow as it's been since Thursday. However, when I went back to re-enable it and saw the full list of network adapters, I saw :
- Ethernet
- Wi-Fi
- wintunshark0 <- Surfshark?
- Ethernet 2
- All network adapters
If that middle one is Surfshark, and the crashes have only ever happened while I'm on that connection, wouldn't it be worth disabling THAT (instead of Ethernet) to see what happens? (I don't dare 'til one of you I.T. gods tells me it's safe)
Because that uses a different set of tools than normal operation does
SO much is offloaded to specific silicon bits these days that things show up ~weird~. At first glance, a VPN causing a crash from hardware sounds weird - till you realize that the encryption, encapsulation, pass-off and packet formation are all handled in hardware - and all require things to pass through system RAM multiple times - and goofy kit will cause one of those to fail, and garbled data can cause the OS to panic and pull the ejection handle.No doubt. He just didn't know some of the stupid Ryzen tricks we've all learned the insanely hard way. Trust me, my first X370 system was the same way - there's lots of AMD "tricks" you learn - Intel tends to be more "out of the box" ready, for better or worse.Okay, let's recap the facts that seem to have become a little blurry again (apologies if you're sick of them at this point, but maybe some late arrivals to the discussion appreciate the rundown).
- A friend of mine built this rig in front of me from parts recommended by this channel last summer. While he's more Linux than Windows, he was extra-careful with my rig because we're friends. He didn't just rush through it.
See prior comments on offload/etc.
I've only used the verify command once - a full journal replay on every command would make things sluggish, yes, but you've turned it off - so something is wrong. Chkdsk wouldn't actually do anything, and the reboot part is normal (has to be run on an unmounted filesystem, so it boots windows to ram, runs it, and then finishes loading). Try verify on and then verify off to see if anything changes, but we're pretty much at a reinstall here.
I work in the storage industry - outside of filling the SLC cache or DRAM cache, there shouldn't be anything that Chkdsk does to the underlying media because it's only operating at the NTFS level. Now could it have found something stupid that the controller on the drive can't handle? Sure, but all the reports on google are people with other problems - not actually killing drives, which would be a much more major issue
Possible, but that should show up in task manager/etc, and all we're seeing there is massive amounts of interrupts, which tells me "fucked up system, fix hardware, reinstall".
Normal. You don't have a CA.
Normal, bonjour is a moronic service and local broadcast does weird stuff.
DLL validation could easily be "this file is fucked, and I can't load it properly," or "I loaded this, but the data in RAM is garbage" (see a thread here?). EAP is an auth system - go back to my comments on crypto offload/etc, and we're probably at the SOFTWARE side of the crash, but still searching for the hardware.
See above on crypto offload againDoes this mean we just found the errors causing the KSCF BSODS?
A possible barrage of 18 simultaneous Event 2002's every time I download through my VPN app..?
Yes, but I suspect that it's not the VPN or the parts, but Ryzen being picky and when it does crypto offload, it's, as the old saying goes, "eating a bag o' dicks".
Default bios. Set SoC voltage to 1.1. Enable XMP. Reinstall windows. Betcha it's 100% stable from there on out forever.It's also possible that the problem isn't the SurfShark app itself, but something about my specific Windows configuration that the app doesn't play well with. The end result is the same tho : no more SurfShark app, switching to browser extension once this is over.
Right?!
I will likely try default bios config next (tomorrow).
He did the right thing for pre-Ryzen AMD or even Intel (although it's faster on intel to just whack the XMP button too).
Lots of drivers not loaded, lots of things not running. Makes sense actually. Wish we had a process or something that we could see taking the CPU or a hardware piece generating the interrupts
This isn't uncommon, but is also the one thing windows has for checking the integrity of the files (content wise). Doesn't mean it can check everything though - just some things. This is why we're suggesting the reinstall - all new!
You did this with the network up, right?
Won't hurt, bet it won't find anything real though.
That guy got unbootable system as a result of XMP. Most of the time, it's just not stable in windows
I'd do 10, but I run in an enterprise mindset. 11 ain't ready yet.
Ayup. Although it'll likely still be slow as crap in windows until you reinstall.
I ~think~ I've seen that on normal windows too, but I could be wrong. I'll check in a few.
but the adobe stuff isnt running in the background in safe mode, it may load fine but half its tasks are missing. i didnt say anything about the bios but you do need to reset it to get your setting straight. if you dont take some of the steps we keep suggesting, the help will dry up. its very, very frustrating...
uninstall it, you cant disable everything. you can reinstall later. ive seen it cause goofy shit before, there was an issue with it eating cpu resources only like a year ago.
