BSOD at random times, mostly when playing. Various error codes

rogeriop · 01 Sep 2015

Well, I will let the thread open and run the test individually in each slot, just so we discover the real issue.

rogeriop · 05 Sep 2015

Can you help me analyze this dump?

I was testing the memory into the first and third slot and got a BSOD, but with a new message, "Memory Management"! So my suspicion about the first two slots might be right.

Here it is!

Attachment 35894

I have contacted the insurance and they asked me to send the motherboard back, I am probably going to that!

essenbe · 05 Sep 2015

Roger, have we run sfc /scannow and the DISM command? Have we run tests on your hard drive? This is what your dump files say.

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 1A, {3f, 38d9, 5176cd09, 1176cd09}
Probably caused by : memory_corruption ( nt!MiValidatePagefilePageHash+285 )
Followup: MachineOwner

What I think is, data is written to memory. The memory then writes the data to the hard drive. It may be that the data read from the page file is not the same as the data written to memory. Just a guess here. So, I would like to make sure the hard drive is not showing errors by running the short and long test with Seatools http://www.sevenforums.com/tutorials...s-how-use.html And that there are no corrupted system files.

rogeriop · 20 Nov 2015

Ok, sorry for the long period of waiting, but it TOOK SOME SERIOUS time.

Here is what happened:
Magically one of the pins of my motherboard's cpu's scoket had broken, probably the pin that had some communication with the ram stick, hence the bugging with ram slots 1 and 2. When I shipped the motherboard, it arrived with more pins broken (bad luck?) so the insurance did not cover that, but the company called me and after some chat, they recommended me a third party to fix my motherboard for a much more reasonable price than buying a new one. Ok, done that, they shipped me back (free of charges at least, here in Brazil that is a great achievement) and I just assembled the computer back on and BYE BYE PROBLEM.

So, at the end of the day, the bug was a pin broken in the motherboard's cpu's socket that had some communication with my memory slots 1 and 2.

Assembled the computer back on last sunday, played the hell out of it this week with the new Fallout 4 (vacation), with memories at slot 2 and 4, and no more BSOD's.

Anyway, thanks for the attention, care and patience!

I am marking it as solved, finally, and I highly recommend people with similar problems to see this thread, such a trivial defect generated a huge commotion.

Cheers.

essenbe · 20 Nov 2015

That is great news. Very well done. That is one of the things there is no test for. You did great and thanks a lot for letting us know the final outcome. Congratulations for figuring it out.