Unexplained system crashes

Jcstrickland89

Commendable
Aug 27, 2016
10
0
1,510
Let me start off by saying that I custom built this computer in June with all compatible parts.
Since June, I've been experiencing crashes. Three different professionals have had my PC in shop to diagnose and fix. Each diagnosis and "fix" did not solve the issue.

It's a modest build: AMD 4300 CPU, GeForce 950, MSI board, ddr3 ram, two case fans plus the CPU fan (all functional), HDD and SSD. Windows 7 professional 64 bit OS.

The motherboard has been replaced with a brand new one, the ram had been replaced 4 times, HDD has been replaced, psu and video card have all been tested, and Windows has been clean installed several times using several instillation discs.

Not, this last fix after the HDD had been replaced seemed to work for fine for 4 days while updating Windows. Then within the past two days, I've received stop errors 0x50, 0xFE, 0x1E, and 0x1A.

I haven't ran memtest again (for the hundredth time), but I did run chkdsk, malwarbytes, scannow, and Windows diagnostic. All came back clean. All drivers are up to date, including chipset. I have one Windows update that won't update regardless of how I try. Not sure if that's related.

I'm at a loss here. If anyone might have any insight, please do assist.

Thanks,
Jonathan S.
 
Solution
BIOS tend to screw up the memory timings on your g.skill 8 gb memory stick.
it has a documented 2 clock cycle command rate. Many BIOS versions will set it at one clock cycle. So if it fails be sure to check the BIOS secondary timings for the command rate. (should be set to 2T or 2N)



looks like you have a updated bios but you did not update the motherboard drivers from the motherboard vendor.
also, it looks like you have mixed memory modules, the second one requires 2n command rate. This timings would most likely to be set manually.
You need to confirm your memory timings are set correctly by running memtest with no errors.
bugchecks with a error code of 00000000c0000005 (0xc0000005) are often caused by memory timing errors.

9-9-9-24-2N at 1.5v would likely be the correct values for the BIOS setting of both ram sticks to work together.
often a bios will default to a 1N command rate.



------------
remove overclocking driver:
\C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Thu Apr 05 02:23:37 2012
remove second overclocking driver:
\C:\Program Files (x86)\MSI\Super-Charger\NTIOLib_X64.sys Thu Oct 25 03:27:58 2012

update old xbox driver
\SystemRoot\system32\DRIVERS\xusb21.sys Wed Apr 08 07:28:44 2009
to xusb22.sys version (dated in 2012)

machine info:
BIOS Version V25.1
BIOS Release Date 04/20/2015
Manufacturer MSI
Product Name MS-7641
Product 760GMA-P34(FX) (MS-7641)
Version 5.0
Processor Version AMD FX(tm)-4300 Quad-Core Processor
Processor Voltage 8eh - 1.4V
External Clock 200MHz
Max Speed 3800MHz
Current Speed 3800MHz

memory
bank0 4GB Corsair CMX4GX3M1A1333C9 at 1333MHZ
bank 1 8GB F3-1600C9-8GXM0000 at 1333MHz




 
BIOS tend to screw up the memory timings on your g.skill 8 gb memory stick.
it has a documented 2 clock cycle command rate. Many BIOS versions will set it at one clock cycle. So if it fails be sure to check the BIOS secondary timings for the command rate. (should be set to 2T or 2N)



 
Solution
looks like you put a link to the files on your google docs account rather than the actual memory .dmp files.
it just tries to link back to your machine which we would not have access to.

try and just copy the memory .dmp files and paste them to your google docs directory.



 
last bugcheck was a bugcheck while running your virus scanner, a bad memory address was again uesd but it looks good.
you would just have to remove your overclocking drivers:
C:\Program Files (x86)\MSI\Super-Charger\NTIOLib_X64.sys Thu Oct 25 03:27:58 2012
\C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Thu Apr 5 02:23:37 2012

it is just not a good idea to debug systems with overclocking drivers installed. You just end up with too many timings problems where the hardware electronics miss a signal and just wait for signals that will never come. Or the windows tries to reset the card to get it going again. (puts in nasty delays that mess up timings)

---------------
the second bugcheck was while steam was running. something passed a bad memory address to the kernel, it kind of looks like a good memroy address so it could just be a timing problem cause by the overclock driver that is installed.
C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Thu Apr 5 02:23:37 2012

this should be removed.
normally I see steam crashes associated with old network drivers or overclocking. you network driver looked pretty current.

-------------
or this graphic failure I would suspect your motherboard sound driver is conflicting with the GPU sound driver.
see below for the update.

system was running NvBackend.exe
it look like the system tried to run code at a bad memory address (zero)

when I look up your BIOS I see the vendor has the most current bios dated 04/20/2014
but yours has a version dated 04/20/2015 (one year newer)

here is the link I looked at:
https://us.msi.com/Motherboard/support/760GMA-P34-FX.html#down-bios
you will want to make sure you installed all of the updated motherboard windows 7 drivers.

for example I see you have
\SystemRoot\system32\DRIVERS\usbfilter.sys Mon Nov 29 01:50:21 2010 installed but should have been updated or removed.
your motherboard sound driver is from 2012 while the website has one from 2016
\SystemRoot\system32\drivers\RTKVHD64.sys Tue Jun 12 03:02:32 2012
(bad sound drivers cause graphics drivers to crash)

you also have a old xbox driver with known bugs installed.
\SystemRoot\system32\DRIVERS\xusb21.sys
you should remove this driver and install the updated version xusb22.sys just so it does not mess up your USB ports.




 

TRENDING THREADS