Solved BSOD's at random intervals

[scotty2hotty81]

Hi guys,

Apologies if this has been solved already but couldn't find anything similar to my problem so thought it would be best if I started a new thread.

So in the last 6-8 months, I have been encountering a gradual degradation of stability whilst my system is running, both under load and whilst idling. My system is custom-built (Gigabyte 990FXA-UD5 rev3, AMD Phenom II X6 1100t BE CPU, 2 x 4Gb Generic DDR3 1333mhz RAM, EVGA GTX650Ti graphics card, 1 x Samsung EVO 250Gb SSD (running W7 X64 Ultimate) and a WD 2tb mech HDD for internal storage. All powered by an OCZ modxstream 700w PSU.) The system had gradually over the space of 6-8 months become more and more unstable, with random crashes and BSOD's both under load and whilst just idling or using the system under very light system use (browsing the net/watching streaming media.) Come last weekend, when I get the most horrific BSOD and then can't log back into Windows, both in normal and safe mode, due to a missing or corrupted registry file. Anyhow, subsequently, after recovering the system from a backup I had made, I managed to log back into Windows and ran SFC which showed a couple of hundred system files which were damaged and couldn't be repaired. I formatted both the internal drives (to ensure removal of any malware) and have reinstalled my OS onto my SSD. Had a bit of a 'mare trying to get the chipset drivers in and for the system to actually recognise the mb as a Gigabyte board and accept the drivers but all sorted now, drivers are in, system is running.

I am still however getting random BSOD's at random, again whilst under load and whilst idling or using non-system intensive applications such as Google Chrome. The main BSOD I have been having a lot of is "memory_management" although I have seen several others, the most recent one was related to NTFS.sys. I have again, run several passes of the Windows memory diagnostic tool as well as CHKDSK in safe mode, both come up with no errors or bad sectors. SFC however, displays already several file system errors which it states it cannot repair, even after running SFC /SCANNOW 3-4 times with system restarts in between.

I am starting to think that this is more HW related seeing as the exact same fault which caused me to reimage my system has followed me through to a clean install. My mobo is still in warranty also (thank goodness for Gigabyte's three year warranty) so if necessary I could ask them to RMA the board (if I can deduce that the board is at fault.) Any help or advice will be greatly appreciated and rewarded with cake (virtual cake of course!)

 

[Golden]

Additional information is required.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

 

[scotty2hotty81]

Thanks for your assistance Golden; I'll run the DM Log Collector when I get home from work this evening - will this pick up previous bluescreens or will I have to wait until I encounter another BSOD before generating I generate the ZIP file?

 

[scotty2hotty81]

Here is the DM Log Collector zip. Plese note that I have since added a further 4Gb of RAM that I had lying around hence why it now says 12Gb in the MSInfo file. Shouldn't make a difference as I have had the same issue using this RAM as well....

 

[Golden]

Host Name:                 SCOTT-PC
OS Name:                   Microsoft Windows 7 Ultimate 
OS Version:                6.1.7600 N/A Build 7600
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
Registered Owner:          Scott
Registered Organization:   
Product ID:                00426-OEM-8992662-00497
Original Install Date:     26/01/2015, 19:51:28
System Boot Time:          03/02/2015, 18:17:43
System Manufacturer:       Gigabyte Technology Co., Ltd.

Counterfeit installations such as yours contains heavily modified code that causes the installation to behave it unexpected ways. Analysing BSOD's and determining their causes on these sorts of installations is very unreliable.

My recommendation is to start with a clean slate, and install a genuine version of Windows. This will minimise the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a genuine Windows installation, and are still experiencing BSOD's, we will be happy to help you solve them

 

[scotty2hotty81]

No problems, I have managed to resolve the problem by updating the BIOS to the latest build (Fcb) which seems to have resolved the bluescreens so far. I guess long term testing will confirm this 100%.

Thanks for your help!