So this is kind of a long-run problem. My computer experiences program crashes of all sorts and BSODs. It's gone through several reinstalls but somehow always ends up the same way.

I don't know what to try anymore, so I'm posting my BlueScreenView and DxDiag data + warnings and errors from the Event Viewer from just yesterday (I exported it in English but it doesn't seem to be quite perfect).

Also, here are the components (it's possible that some of them are just not compatible well enough, I don't know):

  • AMD Vishera FX-4300
  • CORSAIR CX Builder Series Modular
  • 600W Seagate Desktop HDD - 1TB
  • MSI N760 TF 2GD5/OC Gaming Evolveo
  • Zeppelin GOLD 8GB DDR3 1333

I'd appreciate any help you can think of.

PS: I believe I already did MemTest on this machine, but I admit it might not be trustworthy enough of an information, considering it was some time ago.

PPS: I recently RMA'd the motherboard and they returned it as functional

UPDATE: I just got the RAM back from RMA. They returned it, saying it's not faulty. Can the CPU be the cause, since the MBD and RAM were both found OK? Or is their statement just not trustworthy? (They said they ran memtest on the RAM that showed no errors. I'm gonna run memtest again later to confirm or disprove what their results.)

UPDATE 28/7/16: I gave the whole setup to the shop, after they told me they would check the whole thing and RMA what's faulty (for free). So I did it and they finally gave it back (perhaps a week ago) with a CPU replacement. The user of the PC reported having a BSOD a day after but didn't complain since. Will recheck everything and maybe reinstall system, to rule out possible aftermath-software problems.

  • Please edit and include the diagnostic data in the question. Questions need to be standalone and not rely on external links that may not be available in the future. – DavidPostill May 21 '16 at 10:41
  • But I can't upload files (?) Hence two problems: The text files are long and one of the files is not plain-text at all. So how do I go about it? – Keashi May 21 '16 at 14:12
  • modern CPUs have the memory controller on the CPU, maybe this controller is damaged – magicandre1981 Jul 23 '16 at 8:22

From the txt file I can see that you get the Bug Check 0x1A: MEMORY_MANAGEMENT

Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00005003

According to the MSDN page, the error code 5003 in parameter 1 means you have some hardware issue:


The working set free list is corrupt. This is probably a hardware error.

Run memtest86+ for each RAM module and look if you get errors. If the RAM is time, run CPU-Z and look in the memory and SPD tab and look if the RAM timings are applied correctly.

Also if the Command Rate (CR) is set to 1, change it to 2.

enter image description here

|improve this answer|||||
  • Running Memtest and already got 136 errors... wow. Is it safe to assume that the RAM is faulty or is there any chance the mbd slot is at fault (to confirm I'd run the Memtest again in a different slot - I only have one memory stick). – Keashi May 21 '16 at 15:13
  • Replace the memory. – Moab May 21 '16 at 21:32
  • 1
    yeah the RAM is damaged. Test each RAM module on its own of you have more than 1 RAM module installed to see which one is damaged. Remove this damaged RAM module – magicandre1981 May 22 '16 at 6:26

Since you write of RMA-ing the components individually, I assume you spec'ed and assembled this PC yourself. In light of your update saying someone else tested the memory and claims it is ok, I'm going to focus on this part of your question:

here are the components (it's possible that some of them are just not compatible well enough, I don't know)

Yes, it is possible for components to be incompatible. With the CPU, there are sometimes BIOS updates needed to avoid glitches. As for RAM, well not all RAM is created equal. The Gigabyte support page for that motherboard has links for "CPU support list" and "Memory support list" that I suggest you download and read. It isn't necessary to stick with the QVL when building your own PC, but it helps avoid compatibility problems.

You may have to futz with memory timing settings to get your RAM to work. Go into the BIOS/UEFI and look for memory timings. The motherboard reads the SPD values from the memory module to make it easier, but if more than one set of timing values is offered, choose the ones that match the timing numbers printed on the memory module itself, the packaging, or the product info when you bought it. Don't go for the faster timings (lower numbers) because that gets into overclocking territory; you need a stable known-good system before you think about overclocking.

Also, don't overlook the physical stuff. Check that you're using the right memory slot(s) according to the motherboard manual, use some compressed air to make sure there's no dust in there, make sure the modules are fully seated and the latches closed with a solid click, etc.

|improve this answer|||||

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.