Home » Questions » Computers [ Ask a new question ]

Windows 7 likes to crash on me about every week

Windows 7 likes to crash on me about every week

I have Windows 7 Pro 64-bit edition and it seems like every week I get a blue screen since it crashed for some reason.

Asked by: Guest | Views: 335
Total answers/comments: 4
Guest [Entry]

"Going by the symptoms you listed: clicking noise and BSODs with ntfs.sys; this would most likely point to a hard drive going bad. That of course is assuming the clicking noise is coming from your hard drive. I'm not sure of anything else that has a clicking noise in a computer that isn't a fan or hard drive, but you may want to try throwing in something like Ultimate Boot CD and running a full check disk on the hard drive. Barring any of these not fixing the issue, you can do the following, in recommended order:

Reinstall the operating system
Try each memory stick separately, in each memory slot.
Replace the hard drive
If you have spare memory, try those
Sacrifice a goat

These are the cheapest solutions to try. After this you start getting into the really expensive components like the motherboard or the processor."
Guest [Entry]

Try http://www.resplendence.com/whocrashed It will give you more information about the BSOD. Also try switching your power profiles to High Performance. I had similar BSOD to you and that solved my problem. It can't seem to handle changing clock speeds.
Guest [Entry]

"You should install WinDbg Tools from Microsoft (it's free): http://www.microsoft.com/whdc/devtools/debugging/default.mspx

It's very easy to use to dig some information out of a crash. Just install it, start it (actually, right click on it and select ""Run as administrator"" otherwise you won't be able to have it open the minidump file), and go to menu File -> Open crash dump, then browse to C:\Windows\Minidump, and pick the latest file in there. When the file finishes loading, click on the link '!analyze -v' (or type that yourself in the bottom of the window and hit enter). You'll see lots of information swing by. Look for clues there as to what may have been the cause. Typically, you'll see where the crashing process was (and which process it was, accessing what module etc). If you dig through the help of WinDbg, you can even look at the state of your machine right before the crash pretty extensively.

The nice thing with this, is that you can take any friend's minidump (or full kernel dump) and take a peek at what may have caused their crash too... This is actually the tool Microsoft itself uses to hunt down problems (your minidump gets sent to them if you hit the ""Send problem report to microsoft"" thingie). If you are very interested in this, there's even a blog here (by MS employees) with plenty of hints about this tool: http://blogs.msdn.com/ntdebugging/default.aspx"
Guest [Entry]

Completely remove your overclock and see if this continues. I get the hunch that it won't. It may not be related to the CPU, but the PSU may be failing and the extra power-draw from the OC may be causing the instability.