Crinklewott 💕 @thingywott@awoo.space

@ctrlaltdog@chitter.xyz i think i'm just more generally used to linux, so my first instinct with windows is to "find the logs"

and as much as i use procmon to watch specific processes, it doesn't quite scratch the same itch as strace imo

windows stuff can really be out of my depth tbh

@ctrlaltdog@chitter.xyz maybe! though some are harmless too, like there's an error for wifi disconnecting for some reason (??)

it's worth it to check them out though, because they can really tell you a lot about the little things that eventually build up into instability

@ctrlaltdog@chitter.xyz oh! i actually totally forgot that existed, ahahah

@ctrlaltdog@chitter.xyz hee, me neither! the things i can't actually replace are pretty small overall

i actually use wsl to rsync my home folder to an external drive, and it's not even close to big enough for me to worry about upgrading that any time soon

i know someone who actually clones their entire main hard drive to an external one so they can boot into a working windows version with their stuff if things go south on their main disk

@ctrlaltdog@chitter.xyz also, that event viewer filter is just a nice thing to have in general too. i occasionally check it, because sometime things break in subtle ways--and fixing them can do wonders for system stability

in fact, i don't have many things in my event viewer at all with that view (though i think that reset since my last OS update)

i bring this up because it can save a lot of headache if this ends up being the first place you look if something inexplicable starts happening

@ctrlaltdog@chitter.xyz oof, those ain't cheap either

do you have a way things get backed up every now and then to something else?

@ctrlaltdog@chitter.xyz a couple other possibilities are that your connection to the drive is bad, or things are overheating

at least, that's what i think

@ctrlaltdog@chitter.xyz my line of reasoning is

• long POST means that it had issue with some hardware likely
• you see corrupted stuff appear sometimes on your drive
• there are SMART warnings
• you have inexplicable instability sometimes
• your system jutters every now and then (a side effect of disk access)
• this log entry points to a disk issue right before the unexpected shutdown

so i'm pretty sure a lot of these things would go away with another drive

@ctrlaltdog@chitter.xyz "HardDiskVolume3"

whichever disk that is...might be your culprit

@ctrlaltdog@chitter.xyz hmm, i see volmgr errors...

are there any hints in there..? because that just makes me think it's a disk even more

@ctrlaltdog@chitter.xyz oh heck, your log categories are too powerful...in that case, maybe uncheck the "Applications and Services" logs then?

you can also change the "last hour" to "all time" if you do that

@ctrlaltdog@chitter.xyz oofa. i guess the thing i'd do is to make a custom error and critical log message view in the event viewer (like the screenshot), and then wait for the next time something acts up to check it for hints

if that doesn't give anything useful, then, as much as i hate to suggest it, maybe back up your drives, and then try running your computer without the NVMe for a while to see if that's what's getting you ^^'

@ctrlaltdog@chitter.xyz that was...a good question actually

i know that gsmartcontrol can do it, but i don't actually see anything in CrystalDiskInfo

it seems like speedfan can do it though! (i was just talking about the extended test, but i imagine the in-depth analysis couldn't hurt either) http://www.almico.com/sfdownload.php

i think this data gets uploaded though, so i'm not sure how comfy you are with that idea

@ctrlaltdog@chitter.xyz hm, yeah, nothing really jumps out at me, though i also don't know what the lg service does ^^'

and a long POST huh? maybe some service that interacts with your hardware is doing A Bad? in fact, that actually points back to hard drive stuff a little. can you see if you can run a full SMART test on your drives? i feel like there might be something there that's being missed

that could also explain why a service caused that bluescreen--because if it fails to do I/O, that can happen

@ctrlaltdog@chitter.xyz the main reason that autoruns is better for this is because you can see the image path, so you can more easily tell if it's a service you even want

@ctrlaltdog@chitter.xyz (or better yet! autoruns in sysinternals! https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns)

@ctrlaltdog@chitter.xyz oh!! looking at that, it looks like a service is probably what's doing this to you!

services.msc is a good place to see if anything seems sketchy

@ctrlaltdog@chitter.xyz ah, sfc found things?

sometimes this actually happens normally because of updates--though the stuttering is something else entirely ^^'

does the event viewer have anything helpful in it? and does watching the resource monitor give any hints about what's causing the stuttering?

if you really want to dig into certain things, process explorer and procmon in sysinternals can also be handy