8akesale

radio astronomer

you cannot keep me off zhe telescopes
late 20s
agender
ΘΔ, you know how it is wizh spaghetti

atriarch of research
director of zhe Cohost Enclave Space Agency
pfp: meeee
banner: @softtummybitch

kobold60.comi'm a scientistshorter zhan average
longsnake

BEHOLD, ZA CRITTERS

💜@genderdruidflygon
mynoheart@mynotaurusdratini
💚@minecraft & @dragongirlcloacacosmog
💕@bytebatjolteon
🩷@Gyroumbreon
💞@yaodemazoroark
=============
🧡@Seven-Cute-Fishscolipede
=============
♥️@precarioussoulbotporygon
💙@leahpleasebraixen
🩵@saccharinekatlitten
💖@ehksidianlatias
----------------
🤍@dragongirlafrobrionne
🖤@charmytearchen

Reedrill
@Reedrill

hey i know cohost is a not-terrible pc troubleshooting knowledge base, does anyone know what exactly i can do to look into this bluescreen and whats causing it?

This has only ever cropped up within the past few days but has really intensified tonight. Seeing some talk that its storage related but unsure what is True nowadays


SomeEgrets
@SomeEgrets

honestly i use windows seriously so little these days that im not really confident taking a guess at this

Here's what the windows technical docs have to say about this stop code, but it doesnt give many actionable steps for an end-user

gotta be someone with more relevant & contemporary knowledge out there

Edit: i dont think Reed will see reshares of reshares of reshares (etc...) so probably best to drop info in OP comments


8akesale
@8akesale
Check the System Log in Event Viewer for other error messages to help pinpoint the device or driver that's causing the error. To open Event Viewer, select the keyboard shortcut Win+R, enter eventvwr.msc and press the ENTER key. Look for critical errors in the system log that occurred in the same time frame as the blue screen.

Try that and lemme know what you see

You must log in to comment.

in reply to @Reedrill's post:

in reply to @8akesale's post:

oh yeah this is the step that looked most useful on there - it's definitely in the kernel so probably not some userspace thing causing it, narrowing the search down with logs is smart

(this seems to have copied or embedded real hard to read though - dark grey text on black background, probably a light/dark mode mixup or something?)

Edit: oh yeah it's just a light/dark thing, inverting the colours fixes it so nbd