Several different BSOD errors

Page 1 of 8 123 ... LastLast

  1. Posts : 38
    Windows 10
       #1

    Several different BSOD errors


    Just built my first PC with Windows 10, and I have had several BSODs, either while gaming or even just in google chrome. I am not sure what these errors are for, but I'm hoping that it's not a hardware issue.
      My Computer


  2. Arc
    Posts : 1,626
    Microsoft Windows 10 Home
       #2

    I notice two things there, mainly.

    First, windows is not up-to-date.
    Code:
    Windows 10 Kernel Version 10240 MP (4 procs) Free x64
    Update it to the latest. It is necessary.

    Second, two different bugcheck codes are pointing to memory corruption.
    Code:
    BugCheck 1000007E, {ffffffffc0000005, fffff80082a9556a, ffffd000799ab0f8, ffffd000799aa910}
    
    Probably caused by : memory_corruption ( nt!MiDemoteCombinedPte+3e )
    
    Followup:     MachineOwner
    ---------
    Code:
    BugCheck 50, {ffffe00045823010, 0, fffff80216f7b6b7, 2}
    
    
    Could not read faulting driver name
    Probably caused by : memory_corruption ( nt!MiFindEmptyAddressRangeInTree+107 )
    
    Followup:     MachineOwner
    ---------
    So the first place to start will be to test the RAM. Follow it: MemTest86+ - Test RAM - Windows 10 Forums

    Run this test for at least 8 consecutive passes. If it starts to show errors or red lines, stop testing there.

    Take a camera snap of the memtest86+ window before closing the program and let us see it.
      My Computer


  3. Posts : 38
    Windows 10
    Thread Starter
       #3

    Arc said:
    I notice two things there, mainly.

    First, windows is not up-to-date.
    Code:
    Windows 10 Kernel Version 10240 MP (4 procs) Free x64
    Update it to the latest. It is necessary.

    Second, two different bugcheck codes are pointing to memory corruption.
    Code:
    BugCheck 1000007E, {ffffffffc0000005, fffff80082a9556a, ffffd000799ab0f8, ffffd000799aa910}
    
    Probably caused by : memory_corruption ( nt!MiDemoteCombinedPte+3e )
    
    Followup:     MachineOwner
    ---------
    Code:
    BugCheck 50, {ffffe00045823010, 0, fffff80216f7b6b7, 2}
    
    
    Could not read faulting driver name
    Probably caused by : memory_corruption ( nt!MiFindEmptyAddressRangeInTree+107 )
    
    Followup:     MachineOwner
    ---------
    So the first place to start will be to test the RAM. Follow it: MemTest86+ - Test RAM - Windows 10 Forums

    Run this test for at least 8 consecutive passes. If it starts to show errors or red lines, stop testing there.

    Take a camera snap of the memtest86+ window before closing the program and let us see it.

    I did the Memtest86+, and found no errors after 12 passes. What's my next course of action?
      My Computer


  4. Arc
    Posts : 1,626
    Microsoft Windows 10 Home
       #4

    Have you updated windows?
      My Computer


  5. Posts : 38
    Windows 10
    Thread Starter
       #5

    Arc said:
    Have you updated windows?

    I have updated windows to the latest edition. My graphics drivers are up to date according to AMD, so I'm not sure why I keep getting crashes. I'm attaching a new set of dumps. If it still points to memory, could it mean my r390 is a lemon?
    Last edited by greenburrito; 21 Mar 2016 at 21:11. Reason: added zip
      My Computer


  6. Arc
    Posts : 1,626
    Microsoft Windows 10 Home
       #6

    greenburrito said:
    I did the Memtest86+, and found no errors after 12 passes. What's my next course of action?
    Assuming this is a valid statement, the next thing that you will need to do is to enable Driver Verifier.Run DV for 24 hours or the occurrence of the next BSOD, whichever is earlier. Try to replicate the BSODs with DV on. Let us see the resulting BSOD logs.
      My Computer


  7. Posts : 38
    Windows 10
    Thread Starter
       #7

    I wasn't able to get the BSOD to go until now, and it's a different error (faulty_hardware_corrupted_page)
      My Computer


  8. Arc
    Posts : 1,626
    Microsoft Windows 10 Home
       #8

    Well, this is a driver verifier enabled crash dump.
    Code:
    SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    And it says ......
    FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
    This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error.
    Arguments:
    Before going any further I would like to see a camera snap of Memtest86+, completed 8 passes.
      My Computer


  9. Posts : 38
    Windows 10
    Thread Starter
       #9

    Arc said:
    Well, this is a driver verifier enabled crash dump.
    Code:
    SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    And it says ......
    Before going any further I would like to see a camera snap of Memtest86+, completed 8 passes.
    https://i.imgur.com/X0ksHhW.jpg
      My Computer


  10. Arc
    Posts : 1,626
    Microsoft Windows 10 Home
       #10

    Well and good.
    Now let us test two other important hardware, one by one.

    Stress test the Graphics Card using Furmark.Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

    Stress test the CPU.It saves the result as a .txt file in the prime95's folder. Upload the file for us.

    Let us see how these two goes.
      My Computer


 

  Related Discussions
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 01:33.
Find Us




Windows 10 Forums