Solved Intermittent BSOD; 0x1e, 0x7e, 0x3b

[SM125]

Having to type quickly as crashes are random, so apologies for mistakes.

Removed programs commonly related to causing problems, updates graphics driver on APU, cant update wireless drivers as its discontinued (possible culprit?).

Crashes are very random, can be days between or a loop of 5 where I cant boot.

Any help will be greatly appreciated!

Latest .dmp's;

http://1drv.ms/1ugOfad

 

[Arc]

Hi SM125.

Click on the button below ....

​

It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[SM125]

Sorry for not uploading it correctly the first time, was trying to beat the next bluescreen.

View attachment 338977

 

[Arc]

Multiple bugcheck codes, but points to memory corruption.

BugCheck 1E, {ffffffffc0000005, fffff800034a4061, 0, ffffffffffffffff}

[COLOR=Red]Probably caused by : memory_corruption [/COLOR]( nt!MiUnlinkFreeOrZeroedPage+181 )

Followup: MachineOwner
---------

BugCheck 1000007E, {ffffffffc0000005, fffff800034ae061, fffff880009a9828, fffff880009a9080}

[COLOR=Red]Probably caused by : memory_corruption [/COLOR]( nt!MiUnlinkFreeOrZeroedPage+181 )

Followup: MachineOwner
---------

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 know the result.

 

[SM125]

Forgot to add, a couple of days ago I ran Windows Memory Diagnostic with no errors, although I assume this isn't half as good of a test as memtest will be.

Also, just before your response I moved my single stick of RAM (which by the way, has a different brand name to what is labeled in cpu-z) to the only other slot, and it could not boot at all. Maybe a coincedence but I thought id add it just in case.

Will it be ok to run overnight or do I need to attend for any reason?

Thankyou!

 

[SM125]

Downloaded Memtest86+ followed all the instructions but cannot get it to boot from the usb, i've changed the boot priority but its still not happening.

What have I missed?

 

[SM125]

Ran memtest, left for 1 hour and 35 minutes, when I came back was greeted by 3458 errors (& 1 pass).

Figured there was no point continuing the test as there was obviously an issue.

So, does this almost certainly mean that the memory is behind all of the problems or are some of the crashes still caused by other things?

Thankyou very much for your help by the way, was close to losing patience with my pc!

 

[Arc]

Ran memtest, left for 1 hour and 35 minutes, when I came back was greeted by 3458 errors (& 1 pass).



So, does this almost certainly mean that the memory is behind all of the problems or are some of the crashes still caused by other things?

Yes, that is the question. We have to search for the answer to this question.

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.

So let us know the situation. We can decide our next step when the answer to the base question is known.

 

[SM125]

The only problem is, when I bought this PC they only used 1x8GB of memory rather than the more preferable 2x4GB, so i'm stuck on what to do next as I have no spares.

Is there any other way we can test it or will it be down to just hoping it's the memory and buying a new kit?

 

[Arc]

There should be multiple DIMM slots. Test the RAM stick in all the slots.

 

[SM125]

Will do that now.

Also, just had a new crash that I've not seen before in the lifetime of this pc, most commonly they are 0x7e but the one I had just now was 0x34 CACHE_MANAGER.

I'm assuming its just another ram/dimm slot related crash.

 

[Arc]

A failing RAM can cause each and every sort of issue.

So let us concentrate on determining the source of the issue. If still other problems are remaining there, we will properly take care of those ones, too. OK?

 

[SM125]

Alright, sorry for jumping to conclusions i'm just sick of the sight of blue screens haha.

Is there an "acceptable" amount of errors on memtest86+ or is 1 error considered faulty?

I appreciate your help greatly.

 

[Arc]

As said earlier, a single error is enough to determine a fault.

 

[SM125]

Have run memtest86+ again with RAM in the slot closest to the cpu rather than the furthest away (only have 2 dimm slots), the reason I had it furthest away is because the watercooler was very close.

Results after 1 hour was 24 errors this time, rather than the 2700+ I got yesterday in the other slot.

 

[Arc]

Have run memtest86+ again with RAM in the slot closest to the cpu rather than the furthest away (only have 2 dimm slots), the reason I had it furthest away is because the watercooler was very close.

Results after 1 hour was 24 errors this time, rather than the 2700+ I got yesterday in the other slot.

one error is enough to say that the RAM is faulty.

As the RAM stick is throwing errors from multiple slots, we can say that the RAM is faulty itself. Get and apply a replacement RAM there.

Let us know the situation after applying the replacement RAM.

 

[SM125]

Just out of curiosity, is there any chance that both DIMM slots could be faulty as I only recently purchased the motherboard just before the problems started.

Thanks again for your time.

 

[Arc]

Just out of curiosity, is there any chance that both DIMM slots could be faulty as I only recently purchased the motherboard just before the problems started.

Thanks again for your time.

Chance is there, but difficult to determine with a single RAM stick.

 

[SM125]

Crashes are a lot more often now, just had the "failed to start" message about 10 times before it finally booted up for it to then crash again 5 minutes later.

To say how quickly it seems to have deteriorated, does this provide further evidence towards the RAM being the culprit, or is it still 50/50 between RAM and DIMM slots?

Just curious before I dish out a potentially wasteful £70.

Thanks again for your time.

 

[Arc]

I am sorry, but that is all that I can say in the existing situation.

Your issue is determined, only your action can do any further.