I'm cruisin' along perfectly happily with a 5.5 year old laptop and a 10 year old lab computer, both on Windows 7, and I never get bluescreens. It's not the age specifically that's the issue....
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:
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/ ).
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
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.