Lenovo Y50-70: recurring MEMORY_MANAGEMENT BSOD

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 10 Pro x64
       #1

    Lenovo Y50-70: recurring MEMORY_MANAGEMENT BSOD


    Hello everyone! :) Iíve been experiencing daily recurring BSOD for quite some time now and no matter what Iíve tried in order to resolve the issue, Iíve not been able to track down the root cause of the problem. Those BSOD are almost always due to memory corruption (bugcheck code: 0x1A) and the crash takes place in the Windows kernel (ntoskrnl.exe and ntkrnlmp.exe).

    Let me get in details:

    • I own a Lenovo Y50- 70 non-touch laptop (1080p, w/ GTX 860M).
    • I am currently running Windows 10 Pro x64; thatís a fresh installation.
    • I have updated my BIOS to the latest version available.
    • Iíve installed all the latest drivers, which are listed on the Lenovo website; Iíve hidden every single (generic) driver, that Windows Update keeps forcing me to install.
    • I have formatted my drive (and reinstalled Windows) way too many times; a virus causing these BSOD is highly unlikely.
    • I do have tested my RAM modules with MemTest86 (8 passes, several times- will rerun it tonight) and Windows Memory Diagnostic tool; both found no errors at all.
    • Iíve enabled Driver Verified; an archive (.7z) containing five minidumps and their corresponding complete memory dumps can be downloaded here [Dropbox link].

    I am looking forward for your help. Thanks for your time!
    Last edited by nicholasM; 26 Oct 2015 at 12:14.
      My Computer

  2. axe0's Avatar
    Posts : 14,787
    Windows 10 Pro
       #2

    Hi nicholasM,

    Welcome to the 10forums.

    How many passes were completed with MemTest86+?

    Please read BSOD Posting Instructions.
      My Computers


  3. Posts : 6
    Windows 10 Pro x64
    Thread Starter
       #3

    axe0 said:
    Hi nicholasM,

    Welcome to the 10forums.

    How many passes were completed with MemTest86+?

    Please read BSOD Posting Instructions.
    Hi, thanks for your quick response.

    I've completed 8 passes with MemTest86 (not MemTest86+) in the past, with no errors at all. Yesterday, I left it running for the night and did 9 passes; found no errors either. I have been messing around with the drivers a lot recently, so I'll go ahead, reinstall Windows, enable Driver Verifier and wait for a couple of blue screens to occur; the file produced by the DM Log Collector Tool will probably be uploaded the day after tomorrow.

    Thanks.
      My Computer

  4. axe0's Avatar
    Posts : 14,787
    Windows 10 Pro
       #4

    Please run MemTest86+ and do not enable driver verifier yet.




    Diagnostic Test

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
      My Computers


  5. Posts : 6
    Windows 10 Pro x64
    Thread Starter
       #5

    axe0 said:
    Please run MemTest86+ and do not enable driver verifier yet.




    Diagnostic Test

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
    I had tried to boot Memtest86+ on a UEFI system in the past with no luck; for future reference, switching from UEFI to legacy (BIOS) support boot mode did it. Once again, not a single error was reported; I let it run for approximately 27 hours and it completed 16 passes.

      My Computer

  6. axe0's Avatar
    Posts : 14,787
    Windows 10 Pro
       #6





    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computers


  7. Posts : 6
    Windows 10 Pro x64
    Thread Starter
       #7

    I'll enable it and report back in a day or two. Thanks! :)
      My Computer


  8. Posts : 6
    Windows 10 Pro x64
    Thread Starter
       #8

    Just a quick update: I've been very busy lately, but found some free time to reinstall Windows 10 yesterday; and thus, right now, my laptop's running on the latest Lenovo-provided drivers. I will enable Driver Verifier later today, but already got a BSOD, so here's the archive created by the DM Log Collector Tool.
      My Computer

  9. axe0's Avatar
    Posts : 14,787
    Windows 10 Pro
       #9

    No driver has been flagged, I'll wait for the verifier results.
      My Computers


  10. Posts : 6
    Windows 10 Pro x64
    Thread Starter
       #10

    axe0 said:
    No driver has been flagged, I'll wait for the verifier results.
    I've had 10 more BSOD; Driver Verifier's been running since yesterday, but no BSOD points to driver failure.


    On Mon 2/11/2015 10:56:22 πμ GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110215-7468-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
    Bugcheck code: 0x1A (0x41792, 0xFFFFF6805B88D6F0, 0x200000000000, 0x0)
    Error: MEMORY_MANAGEMENT

    On Mon 2/11/2015 10:56:22 πμ GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x1A (0x41792, 0xFFFFF6805B88D6F0, 0x200000000000, 0x0)
    Error: MEMORY_MANAGEMENT

    On Mon 2/11/2015 10:28:52 πμ GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110215-8078-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
    Bugcheck code: 0x1A (0x41793, 0xFFFFF68049C03670, 0x2, 0x1)
    Error: MEMORY_MANAGEMENT

    On Mon 2/11/2015 8:22:46 πμ GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110215-8843-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
    Bugcheck code: 0x1A (0x41793, 0xFFFFF6805473CA70, 0x14F, 0x14E)
    Error: MEMORY_MANAGEMENT

    On Mon 2/11/2015 7:41:02 πμ GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110215-7109-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
    Bugcheck code: 0x1A (0x41792, 0xFFFFF6800004F670, 0x200000000000, 0x0)
    Error: MEMORY_MANAGEMENT

    On Sun 1/11/2015 4:29:23 μμ GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110115-7078-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
    Bugcheck code: 0x1A (0x41793, 0xFFFFF6800084B670, 0x2F, 0x2E)
    Error: MEMORY_MANAGEMENT

    On Sun 1/11/2015 3:59:11 μμ GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110115-7515-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
    Bugcheck code: 0x1A (0x41793, 0xFFFFF680000346F0, 0x1F, 0x1E)
    Error: MEMORY_MANAGEMENT

    On Sun 1/11/2015 3:50:46 μμ GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110115-6468-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
    Bugcheck code: 0x1A (0x41793, 0xFFFFF6806EDF46F0, 0x2, 0x1)
    Error: MEMORY_MANAGEMENT

    On Sun 1/11/2015 3:33:47 μμ GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110115-6906-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
    Bugcheck code: 0x1A (0x41793, 0xFFFFF6800004F6F0, 0xF, 0xE)
    Error: MEMORY_MANAGEMENT

    On Sun 1/11/2015 3:07:57 μμ GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110115-7312-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
    Bugcheck code: 0x1A (0x41792, 0xFFFFF68000313670, 0x200000000000, 0x0)
    Error: MEMORY_MANAGEMENT
      My Computer


 
Page 1 of 2 12 LastLast

  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 17:46.
Find Us




Windows 10 Forums