BSOD recurring both in Safe Mode and Normal

[Sejian]

Recurring BSOD with or without GPU installed, in and out of Safe Mode, whether it's idle or in use. MemTest86 failed with both RAM modules installed, but completed 11 and 8 passes respectively on each module separately. Currently only using 1 module.

I've read through a few other threads and have attempted to collect as much logs/info as possible. System specs on my profile. The motherboard is old and may be faulty, my ASUS recently failed and a friend lent it to me. The BSOD started after about 2 days of use. I'm of the opinion it's either the mobo or the RAM.

My apologies for the short description, but I've BSOD while trying to type this.

Thanks for any assistance.

 

[Arc]

Hi Sejian.

My opinion goes with you, after checking the crash dumps. So many different BSODs in a small period, which indicates to memory failure, mostly.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

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 results.
________________________

BugCheck 4E, {8d, 5b01b, 1c25d, 81}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+96c )

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

BugCheck A, {fffffa7fffd02fd0, 2, 1, fffff8000328e4ec}

Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e )

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

BugCheck A, {fffffa7fffdd4fe0, 2, 1, fffff80003251ac1}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )

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

BugCheck 50, {ffffffffffffffff, 0, fffff800024c1630, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4518f )

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

BugCheck 7F, {8, 80050031, 6f8, fffff800024da205}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

 

[Sejian]

Thanks for the quick response. The memtest I mentioned was done last night into this morning actually. After 2 consecutive BSOD last night the PC wouldn't boot and started beeping. I reinserted the modules, ran MemTest86+, and got multiple errors by the third test. Rebooted with one module and it ran for 5 hours 30 minutes with 11 successful passes, then the second module, 8 successful passes in 4 hours 30 minutes.

Just noticed though my MemTest86+ is outdated, version 4.60 (or .20?). I don't mind running the test again with the newer version if it would make any difference.

Edit: After reading the "How to" I must say what I didn't do was test the various slots. Both modules were tested in the third slot, they failed in the third and fourth slots when tested together.

 

[Arc]

I think the version of memtest is not very important, if it is not the latest haswell CPU.

Thanks for the quick response. The memtest I mentioned was done last night into this morning actually. After 2 consecutive BSOD last night the PC wouldn't boot and started beeping. I reinserted the modules, ran MemTest86+, and got multiple errors by the third test. Rebooted with one module and it ran for 5 hours 30 minutes with 11 successful passes, then the second module, 8 successful passes in 4 hours 30 minutes.

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.

 

[Sejian]

Understood, will make an update when I've got more results. Thanks!

 

[Sejian]

Thus far I've completed 6 memtests ranging between 8-12 passes on each RAM module individually in slots 1, 2 and 3, with a couple hiccups.

First and foremost, the PC wouldn't boot when I installed both modules in slots 1 and 2. It did with slots 1 and 3, but BSOD soon after loading windows. Then I started testing, both modules A and B (which I shall refer to them as from this point on) had 8 successful passes in slot 1. Initial test in slot 2 saw the pc freeze on the 3rd test with B, no memory errors, just froze and had to restart. Swapped B for A, 8 passes, swapped A for B again, 12 passes. Slot 3 saw 8 passes for both modules, at which point I decided to try booting with A in 1 and B in 2, which had failed numerous times before I began testing but worked this time. That was between 8-10AM yesterday (10th). The PC worked (with one reboot to reconnect my secondary drive) through many hours of gaming (Ghost Recon: Future Soldier, Splinter Cell: Conviction and Splinter Cell: Blacklist), watching movies, downloading, defragging, etc. then BSOD while playing music some time between 4-6AM this morning. I believe it was the page fault error. The BSOD froze midway, and I had just woken up, so I was frustrated and groggy and had one of those IDGAF moments and didn't pay attention.

I've come to the conclusion my Corsair RAM is just too sexy for this motherboard and I shall attempt to procure a new motherboard ASAP because my equally sexy OCZ Vector will not work with this BS anymore, I've already seen a decrease in it's Life Left (via Defraggler, I do not defrag my SSD) by 1, dropping me to 97. Theatrics aside, the mobo is compatible with 1600Mhz (OC) but it may be due to whatever fault my friend mentioned might exist. I do not believe my RAM is faulty, but I'll find out after I get a new mobo.

P.S. The same friend has a 4GB 1333Mhz RAM module, providing I'm able to pay him a visit, I shall try to swap my 2x2GB kit for his 4GB module and see if it works. That would also confirm if my RAM is faulty if he starts getting BSOD.

 

[Sejian]

Swapped the modules with my friend for about 5 hours of testing. My 2x2GB kit worked fine on his motherboard, his 4GB module worked on "mine", also tried a 2x1GB kit and it worked. The joys of owning a PC.

 

[Arc]

May be some compatibility issue.

Get the same RAM as your friend has.