The Dreaded Blue Screen

[mojo12012]

Over the last couple of days I've started to get random blue screens. This has happened running different programmes, not just TS2013/14. The notification screen goes too quickly before I can note down the error code at the bottom.

System specs:

AMD FX-8150 stable @ 4.20 GHz (well it is still stable as far as I know) With Arctic Freezer Cooler
Gigabyte FXA-UD3 motherboard
16 Gb DD3 13300 Hz memory
Windows 7 64 bit Home Premium installed on separate 256 Gb SSD
EVGA GTX 660 Ti GPU
Steam folder on separate 128 Gb SSD
Asus Xonar sound card
Windows Experience Index gives it 7.8 for what it's worth.
Corsair 750W PSU
Neither the CPU or the GPU are running hot, (the CPU rarely goes above 32C), and the blue screen happens in less demanding programmes, e.g. playing a cd. I've checked the seating of the various components, turned down the FX-8150 to stock speed. Nothing else has been overclocked. The FX8150 has been running fine for the last 18 months at the higher speed, although I suspect this is the obvious candidate. I'm presuming it's not caused by a new programme or driver as I haven't installed anything recently, and it happens in different programmes. System is regularly checked with Malwarebytes and AVG. A recent scan showed no nasty additions. The C: drive has over 100 GB free to use.
So, can anyone point me to a systematic way of working my way through the possibilities in order to narrow down what's going wrong? I know Windows writes a crash dump file, but where is it, and would it tell me anything useful, if I could find it? As I've said, I've tried various things as listed above, but I'm quite happy to go through it step by step again, to make sure I don't miss anything.
Many thanks.

[arizonachris]

In XPeeeee there used to be a setting to tell Windows to stop and display the "STOP:xxxxxxxxxxxx" message rather than just restart, but darned if I can find it in Win 7.

You can check performance logs in Control Panel> Performance Info and Tools> Advanced Tools> Event Log.

Also, if that's an early version of the Bulldozer CPU, you may need this: http://www.abithelp.com/nvidia/topic1612.html

[mojo12012]

Thanks Chris. I'm pretty sure I followed this suggestion when you made it the first time around, but I'll check it again. Very frustrating.

[Ericmopar]

This is how to stop the auto restart in Win 7.

http://pcsupport.about.com/od/windows7/ ... dows-7.htm

[mojo12012]

Thanks Eric. Now I won't have to frantically scribble down the message. Not that it makes a lot of sense anyway. Good old Google.

[mojo12012]

Well, I bit the bullet and went for the clean install of Win 7 on a fresh SSD. 7 hours plus and not a sign of a BOSD, so it is either the old SSD or the particular software configuration I had. At least it appears I can discount the GPU, CPU and memory as being the culprits. Not sure how to clarify whether the SSD is faulty. Running disc checking software indicates it's okay. I'll try Crucial and see if they can enlighten me as to how to check its status.

[mojo12012]

Just to let you know that my Crucial SSD needed a firmware update as the particular model has problems once it got to 5184 hours in service. Given it is nearly 2 years old then it's easy to see that happening. The other SSD with Steam on is only a few months younger, so that needed updating as well. Suffice to say the updates have gone fine, with no further issues. Crucial also recommend running the SSDs powered up, but not connected to the motherboard in order to let the inbuilt "garbage" system run. Nice clean Win 7 system back up and running.

[mojo12012]

Last post re this subject, hopefully. Ran the "garbage" episode last night, things working okay now, and copies safely stowed elsewhere.

[JWStilwell]

Last post re this subject, hopefully. Ran the "garbage" episode last night, things working okay now, and copies safely stowed elsewhere.

What is the garbage episode?

[mojo12012]

Best, JW, if I just quote Crucial's e mail to me:

"After updating the firmware, the behaviour you are describing is also
consistent with deleted cells not being cleaned from your drive. This can
result in reduced performance or even complete lack of response from the
SSD.

There is a feature built into our SSDs called Active Garbage Collection.
Letting Active Garbage Collection run on the drive for an extended period
will clean these cells and restore the SSD to a healthy state.

To do this on your PC or Laptop, you will need to let the SSD idle for 6 to
8 hours.

In a PC, simply disconnect the SATA cable from your SSD and only leave the
power cable connected. After switching your PC on, the SSD will be in an
idle state but still have power so Garbage Collection can function. Leave
the PC powered for the 6-8 hours.

In a laptop, power on with the SSD installed and enter your system BIOS
(please refer to your system manufacturer’s documentation on how to access
the BIOS.) Leave the laptop in the BIOS menu for the 6-8 hours.

Following this process, your drives functionality and performance should be
restored.

To prevent the SSD performance degrading again, you can make adjustments to
your power settings:

- Go to Control Panel
- Go to Hardware and Sound
- Go to Power Options
- Select Change Plan Settings
- Select Change Advanced Settings
- Make sure the 'hard disk' field is set to ‘never’ (Laptop users select
'battery and power adapter')."

That's it. I presume other SSD's have a similar procedure built in?