BSOD at least twice a month - uncertain cause

Page 8 of 8 FirstFirst ... 678

  1. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #71

    @philc43

    At this time I have only used Slots #1 and #3

    I was having MEMORY_MANAGEMENT errors with DIMMs #1 and #3, but no such errors with DIMMs #2 and #4 in the same slots

    This leads me to believe that the issue lies within the RAM, not the mobo

    Therefore, is it reasonable to try to isolate whether it is DIMM #1 vs #3 by pairing one of these up with an established working DIMM (e.g., DIMM #2) using the same slots that have always been in play (i.e., #1 and #3)
      My ComputerSystem Spec


  2. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #72

    Just swapped out DIMM -- currently testing #3 (which had previous caused BSOD when combined with #1) and #4 (which did not cause BSOD when combined with #2)

    Will report any BSOD (which would likely be due to #3 if they occur)

    Slots unchanged (always #1 and #3)
      My ComputerSystem Spec

  3. philc43's Avatar
    Posts : 4,095
    64bit Win 10 Pro ver 1809 Build 17763.503 and W10 Insider Build 18362 and 18895
       #73

    Great progress!
      My ComputersSystem Spec


  4. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #74

    Got a BSOD 5 days after testing DIMMS #3 and #4

    MEMORY_MANAGEMENT

    MEMORY.ZIP: Dropbox - MEMORY.zip - Simplify your life

    This is the 2nd time that #3 was tested and the 2nd time that it failed - I will reach out to G.Skill re: warranty

    Will start testing #1 (which previously failed in very first test) and #2 (which passed)
    BSOD at least twice a month - uncertain cause Attached Files
      My ComputerSystem Spec


  5. Posts : 25,429
    windows 10 professional version 1607 build 14393.969 64 bit
       #75

    The memory.dmp debugging didn't display any misbehaving drivers.

    Continue testing hardware.
      My ComputerSystem Spec


  6. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #76

    Got a BSOD 3 days after testing DIMMS #1 and #2

    MEMORY_MANAGEMENT again - coming out of sleep

    MEMORY.ZIP:
    https://www.dropbox.com/s/4u7cebganu9dhtv/MEMORY.zip?dl=0

    Failing DIMM combos:
    • #1 and #3
    • #3 and #4
    • #1 and #2


    Passing DIMM combos (i.e., no MEMORY_MANAGEMENT BSOD since I put them in on 12-26-18 and took them out 4-11-19):
    • #2 and #4


    Always tested on MoBo slots #1 and #3

    What should I do next?
    BSOD at least twice a month - uncertain cause Attached Files
      My ComputerSystem Spec

  7. philc43's Avatar
    Posts : 4,095
    64bit Win 10 Pro ver 1809 Build 17763.503 and W10 Insider Build 18362 and 18895
       #77

    Sorry for the late reply. I think you have proved that memory modules #1 and #3 are faulty and should be returned/replaced.
      My ComputersSystem Spec


  8. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #78

    No worries about late reply

    I wonder if modules #1 and #3 are truly faulty (and whether #2 and #4 were a fluke and would have BSOD'd soon enough) -- the reason is that #1 and #3 were purchased as part of two separate sets a number of years apart

    Before sending them in to G.skill, I will try out the modules in slots #2 and #4 (for the first time) in order to exclude a faulty slot #1 or #3
      My ComputerSystem Spec


  9. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #79

    I set up DIMMS #1 and #2 for testing on slots #2 and #4 on 4/24.

    I just experienced a BSOD right now ~20 days later

    The message was FAULTY_HARDWARE_CORRUPTED_PAGE

    MEMORY.ZIP Link: Dropbox - MEMORY.zip - Simplify your life

    Is the error also linked to RAM? If so, I was going to try the two good sticks #2 and #4 in slots #2 and #4 just to confirm (and send #1 and #3 to GSkill)
    BSOD at least twice a month - uncertain cause Attached Files
      My ComputerSystem Spec

  10. philc43's Avatar
    Posts : 4,095
    64bit Win 10 Pro ver 1809 Build 17763.503 and W10 Insider Build 18362 and 18895
       #80

    Yes, this latest error looks like a memory related error.

    Code:
    FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
    This bugcheck indicates that a single bit error was found in this page.  This is a hardware memory error.
    I think you have enough evidence to return modules 1 and 3 under warranty, putting modules 2 and 4 into slots 2 and 4 should give you a good working system.
      My ComputersSystem Spec


 
Page 8 of 8 FirstFirst ... 678

Related Threads
Random BSOD for the last month in BSOD Crashes and Debugging
Hey Guys, My PC keeps randomly BSODing mainly from DRIVER_IRQL_NOT_LESS_OR_EQUAL 00000000`00000000. Have tried different GPU & RAM. Have even done a fresh install to no avail any help would be much appreciated. Thanks in advance.
4 BSOD's on 2-month old PC in BSOD Crashes and Debugging
Recently built a new PC, and it works excellently well however over the last 3 weeks I've had 4 BSOD's all with the same bugcheck error code from Event Log I don't know how it starts or what triggers it. It simply runs into the issue every few...
3rd BSOD in a month in BSOD Crashes and Debugging
Hello. Last night I received my 3rd blue screen error in about a month. That one and the previous one said "system service exception (netio.sys)." I forget if the first time this happened the error listed the same. Anyway, here's my log file...
Multiple bsod's in last month in BSOD Crashes and Debugging
Hello, I have had multiple bsod's in the last month. they seem to occur when pc is not doing anything. When im working on it it bsod's sometimes, but when i walk away it will in a matter of minutes. 61517 i hope someone can tell me what is...
Keep getting BSOD for the pass 2 month in BSOD Crashes and Debugging
BlueScreenView says that its ntoskrnl.exe driver error.
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 00:12.
Find Us