Weird BSOD problem

Page 2 of 2 FirstFirst 12

  1. Posts : 9
    Windows 10 Pro
    Thread Starter
       #11

    Another BSOD after clean reinstall


    Hi Arc,

    The Windows was an upgrade.

    So I've installed a clean install of the Windows 10 on another newly formatted partition, so I have now dual-boot Windows 10(one upgrade and one clean install). Clean install OS is by default to boot.

    I did not installed any drivers, only via Windows updates.

    Here is another BSOD today, same behavior.

    Thank you
      My Computer


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

    Code:
    BugCheck A, {fffff6e800f80738, 2, 0, fffff8015eabf5b3}
    
    Probably caused by : memory_corruption ( nt!MiReplenishBitMap+a3 )
    
    Followup:     MachineOwner
    ---------
    Two things may cause memory corruptions. One is meory hardware (RAM, DIMM slot, or memory controller) and the other thing is the drivers passing bad information to the memory.

    Apparently the second possibility is completely nullified by now, as it occurs in multiple complete different situations on the same hardware.
    So we have to search for the causes of the BSOD in the hardware environment.

    Previously (18 May 2015) you posted ......
    Tested RAM with memtest86+: run for about 17h45m. 16 passes. 0 errors.
    Which apparently nullifies the possibility of a problematic RAM.
    The RAMs run at 800MHz.
    Code:
      Speed                         800MHz
    Much lower, but supported by the motherboard.
    Attachment 68517
    The BIOS s old, but the latest version.
    Code:
    BiosVersion = 0404   
    BiosReleaseDate = 03/05/2010
    Now, we have very limited things left to do. Let us do these one by one.

    First, let us check that the components are properly seated.
    Dismantle the computer. Clean the inside (make it free from any dust accumulation). Remove the components like SATA ports, RAM and graphics card. Clean them all. Clean the edges of the RAM stick with clean cotton cloth.
    Now seat those back.
    Does it change anything there? Let us know.

    If not, we will step forward to the next possible step.
      My Computer


  3. Posts : 9
    Windows 10 Pro
    Thread Starter
       #13

    Hi,

    I did all the steps you said:
    Clean the inside (make it free from any dust accumulation). Remove the components like SATA ports, RAM and graphics card. Clean them all. Clean the edges of the RAM stick with clean cotton cloth.
    Now seat those back.
    + I disconnected ODD, as I don't remember when last time I used it.

    Started PC> BSOD> but it did not left a minidump, only a file called C:\DUMP1e36.tmp
      My Computer


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

    That means the dump was not recorded.
    Next time take a camera snap of the BSOD screen and let us see it? Expecting that the onscreen codes will give at least some information.
      My Computer


  5. Posts : 9
    Windows 10 Pro
    Thread Starter
       #15

    new


    hi, please find attached. thank you
      My Computer


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

    Code:
    BugCheck 1000007E, {ffffffffc0000005, fffff803bd7d0c37, ffffd0018afafb98, ffffd0018afaf3b0}
    
    Probably caused by : NTFS.sys ( NTFS!NtfsCommonRead+298 )
    
    Followup:     MachineOwner
    ---------
    No more useful information is there in the crash dump. So, taking a look at the probable causes .....
    Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
    ► 1. Disk space. It is ....
    Drive C:
    Size 90.88 GB (97,585,893,376 bytes)
    Free Space 72.93 GB (78,312,951,808 bytes)

    ► 2. Device Driver: We havent got any trace of a failing device driver there. Even in the deepest search.

    ► 3. Video Card: Same, no trace of a failing video card. But you still can stress test the Graphics Card using Furmark to determine if there is a failure from graphics.
    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.

    ► 4. BIOS: It is old enough.
    BIOS_VERSION: 0404
    BIOS_DATE: 03/05/2010
    I think it might be a cause of the BSOD, but it is the latest version.

    ► 5. As it was the same with Windows 7 too, it may not be really related to the hardware incompatibility; though ASUS does not list anything for this board that is compatible with windows 10.

    ► 6. System service errors should not be there even after a clean reinstall.

    ► 7. Memory: We havent got any memory related errors in memtest86+

    So, my best possible inference is, it is a motherboard/BIOS level corruption.
      My Computer


  7. Posts : 9
    Windows 10 Pro
    Thread Starter
       #17

    Did the Furmark test for an hour, stable at 66 degree Celsius, fan at 76%. No artifacts.

    So I suppose this is fine also...
    Last edited by Senarium; 05 Jun 2016 at 06:08.
      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 05:24.
Find Us




Windows 10 Forums