you haven't really worked in IT until you delete something "unimportant" that was actually very important

[Apollo the Just]

proud to announce i have now officially worked in IT. rip to [redacted]'s workstation but it's fixed now. :^)

in my defense, our device monitoring client reported that it hadn't booted since 2017, so i assumed it had been decommissioned already. further in my defense, it was marked on decommissioned already by the person who was previously working on this project. i simply thought deleting the computer from our directory was pruning dead leaves. cue the "I CAN'T LOG INTO MY COMPUTER" call. whoops.

...anyway the local profiles somehow got **** when we tried to re-add it back to the domain and literally everything possible went wrong and there were several completely inexplicable problems with the local admin account on it, but it's working again now, which is a bit pointless because now that i know it exists and is 5 years off warranty and still on Windows 7, it's going to be replaced entirely next week.

somehow, i really love this job

[Marilink]

BEEN THERE. Thank God for backups

[steeze]

Do you know anything about bsods Apollo?

[Apollo the Just]

^^ As an individual, I absolutely detest the cloud model. I hate it so much. I want to have control over where my data goes and how it is transmitted, as much as I can. I enjoy manually moving things that I want access to on other devices, or setting up certain shares in certain cases. But I absolutely want the primary storage location of my media to be on a local storage device that I own.

But? Working for an organization? Dear god the cloud is so helpful. Deploying computer replacements for users is the easiest **** ever. Back everything up to OneDrive and re-sync. My job is so damn easy now because of it lmao

--

^ i mean, they're bad? they mean something went wrong? bsod's can be a symptom of a lot of stuff and i do not pretend to be a Seasoned IT Expert i literally have the most basic ass cert ever and 1 month on the job, but you are also going to have to be more specific. a bsod just means your computer decided that whatever the heck you were doing, it has had it up to here with your crap and it is Done

[steeze]

I've been in an ongoing battle against the bsod for a month or two. Gotten quite a few of them:

IRQL_NOT_LESS_OR_EQUAL
MEMORY_MANAGEMENT
KMODE_EXCEPTION_NOT_HANDLED
KERNEL_STACK_INPAGE_ERROR
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
PFN_LIST CORRUPY
KERNEL_MODE_EXCEPTION_NOT_HANDLED

These are some I remember.

I've switched my ram sticks around, checked for damage, ran tests on my memory. It's maddening. I cannot figure it out. Usually happens when I boot. Sometimes randomly.

[I am nobody]

Have you reinstalled Windows? Those could be a corrupted kernel/system library as easily as bad memory.

Windows also creates a crash log whenever it crashes, and those contain way more information than what you get on-screen. If you can get a hold of those and/or check Event Viewer for the source of critical errors around the crash, you should get more info.

[steeze]

I have reinstalled it a few different times trying to fix the issue. I've actually stopped getting these after I started powering down the system when I get up for the day. We'll see.