Solved Random BSODs nolonger generating dump files

[richlaf]

Computer stopped generating minidumps but have had numerous BSODs. I have followed the instructions on this site to make sure that PC is configured for minidumps. I have also run chkdsk command with repair and SFC /scannow. I have also run Kaperskys and malwarebytes rootkit virus detectors. Both came back clean. Most pressing need is to be able to generate dump files so that someone help to determine what is causing BSODs. I have attached the file from the dmg collector and also the results from a SFC /scannow. Any help would be appreciated.

 

[axe0]

Please make sure your pc is configured for small dump files How to configure minidump | Windows 7 tutorial

We need at least a picture of the BSOD to see what kind we're dealing with, please make sure you get some pictures of the BSODs and post them.

 

[Arc]

The 16 GB Micron RAM ... was it there from the beginning, or you added it latter?

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us see a camera snap of the Memtest86+ screen before closing the program.

 

[richlaf]

Minidump settings

I have attached screenshot of minidump settings. I believe these have always been the settings on my PC.View attachment 386189

 

[richlaf]

My PC originally had 8GB of memory. I added the additional memory about 2 years ago. I will run the memtest86+ tonight. Thanks.

 

[axe0]

Until the problem of no dump is solved, please uncheck 'Automatically restart' so you have enough time to get a photo and see if any problem occurs while the dump is being created + saved.

 

[Arc]

Dump is not being recorded, most probably because of it.

2/24/2016 2:20 PM
Windows Error Reporting Fault bucket BAD_DUMPFILE,
type 0

Event Name: BlueScreen

But when the last known BSODs are

• 2/24/2016 2:20 PM Windows Error Reporting Fault bucket X64_0x3B
• 2/24/2016 2:19 PM Windows Error Reporting Fault bucket X64_0x24

I see no good reason to not perform the RAM test.

 

[richlaf]

View attachment 386277
Here is a camera shot of the memtest86 that I ran last night. Clearly some type of RAM problem. Not sure of what to do next. I do have the original RAM sticks that came with the PC.

 

[axe0]

Here is what to do.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

[Arc]

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

If it is a bad RAM, you need to change the RAM. Take the other existing (good) RAM to the shop and get one of the exactly same specification. The best is, get a totally new RAM KIT.

If it is a bad slot, it is a motherboard issue. But changing the motherboard needs a preparation for most of us; so dont populate that slot for the time being.

 

[richlaf]

Thanks for the advice. I may be trying to save some time here, but if 1 RAM sticks tests fine in all 4 slots doesn't that tell me that not only is the RAM stick good, but so are all 4 slots? If so, then couldn't I just test the other 3 RAM sticks, one at a time, in just one slot?

 

[Arc]

Nice point! Carry it on!

 

[richlaf]

Thanks, solved

Hi Arc, I just wanted to say thanks for your help. After I replaced the bad memory Stick, about 3 weeks ago, I have had no issues.

 

[richlaf]

Thanks

Hi Axe0, I just wanted to say thanks for the help. I replaced the bad memory stick and now my PC seems fine.

 

[Arc]

The BSOD team of your forum greets you with a for a great job well done.