let me hear your voice tonight (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
alexseanchai) wrote2017-01-04 06:20 pm
alexseanchai) wrote2017-01-04 06:20 pm
(no subject)
BLUESCREEN FUCK
stop code: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
what failed: FLTMGR.SYS
I don't know what this means except it's different from previous bluescreens
...I feel like my whole public-facing journal lately, and no small amount of locked, is technical issues. /o\
stop code: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
what failed: FLTMGR.SYS
I don't know what this means except it's different from previous bluescreens
...I feel like my whole public-facing journal lately, and no small amount of locked, is technical issues. /o\
no subject
This might be helpful. Usually this is a temporary problem you don't need to worry about much, though.
no subject
Honestly what I need to do is suck it up and buy a new desktop, probably. This one's five-six years old and been bluescreening variously for a while. This is a different bluescreen error, is all.
Hopefully you're right and it's a temporary problem, though...
no subject
But yeah, with a 6-year old desktop temper tantrums are just part of the battle. 8')
no subject
*nod*
Thanks :)
no subject
fltmgr.sys is the file system filter driver, typically invoked by things like virus scanners. A thread failure in that driver seems spurious. If this is a one-off I'd ignore it. However if I know more about the other sorts of bluescreens you're getting I might be able to help establish a pattern.
When lots of random bluescreens happen, signs point to bad RAM, motherboard, or CPU. Fortunately RAM is the easy one to check:
http://www.memtest.org/#downiso
There's a link to a program that can create a bootable USB key (marked *NEW!*) or you can download the "Pre-Compiled Bootable ISO (.zip)" and burn that to a CD-ROM instead. (If you need a disk burning program, I highly recommend http://imgburn.com/ ).
Here's the FAQ: http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting
but I can summarize it like this: boot it, run it overnight (it'll keep running until you stop it), look for any errors in the morning. "No errors are acceptable." As the FAQ says, a failure doesn't necessarily indicate bad RAM (it could be bad chips on the motherboard, the motherboard itself, or a bad CPU) but it's an indication that the fault is with your hardware, not Windows itself.
no subject
Thank you!