BSOD, random time, different warning

[Valmighty]

Hi, i experience BSOD frequently now, about twice a week, at random time (but never when i play games, so far).

I suspected RAM since i just bought a new RAM, but i scanned the RAM with memtest86+ and it had no error.

This has become a nuisance now because my hard drive (F:, 3TB) runs very slowly now and i need to check disk it, but the last time my PC crashed into BSOD when i check disk the F after about 9 hours.

Help please, thank you.

 

[Arc]

All different errors, but all of them are pointing to Memory corruption. How many passes did you run memtest86+? It needs to run for 8 complete passes at least. If you havent completed 8 passes, you are suggested to do so. And a screenshot/camera snap after completing 8 passes would be good for documentation.

Also, as an attempt, you may try to update the BIOS to Version 3602 from ASUSTeK Computer Inc. -Support- Drivers and Download P8P67 PRO (REV 3.1)

Also update JMicron RAID from ftp://driver.jmicron.com.tw/SATA_Controller/Windows/ . get the latest WHQL.

Let us know the results.
___________________________________________________________________________________________

BugCheck 3B, {c000001d, fffff800034afab3, fffff88008f81da0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
-------------------------------------------------------------------------------
BugCheck 1A, {41201, fffff680009fbab0, 2c000003ce07025, fffffa80132b89d0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 )

Followup: MachineOwner
--------------------------------------------------------------------------------
BugCheck 50, {fffffa8030e13848, 1, fffff800034afaad, 2}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------------------------------------------------------------------------------
BugCheck 109, {a3a039d8a57385cd, b3b7465ef7f05523, fffff8000342baa9, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

 

[Valmighty]

Thanks, will redo the memtest and everything else

 

[Valmighty]

I switch the new RAM into another socket. It doesnt give me any error until now (7 ongoing passes). Out of curiosity, how do you tell which one is faulty between the RAM and the motherboard (aside from trial and error)?

 

[Arc]

Out of curiosity, how do you tell which one is faulty between the RAM and the motherboard (aside from trial and error)?

No other way than trial and error.

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.

 

[Valmighty]

Attached is the latest test, i continued it until 10 passes. What does the 1930.5MB means? The RAM has 2GB faulty sector?

I'm now using my old RAM to the suspected DIMM. I'll update the result...

 

[Arc]

Do discrepancy in size, but the RAM is faulty.

 

[Valmighty]

Thanks Arc! will RMA the RAM.