Elektroda.pl
Elektroda.pl
X
Proszę, dodaj wyjątek dla www.elektroda.pl do Adblock.
Dzięki temu, że oglądasz reklamy, wspierasz portal i użytkowników.

Lenovo Thinkpad L480 - Ciągłe resety i błędy BSOD z powodu ntoskrnl.exe

03 Kwi 2020 09:38 168 7
  • Poziom 11  
    Mam od 2 miesięcy nowy komputer Lenovo Thinkpad L480, praktycznie od samego początku samoczynnie się resetuje i wyskakuje ekran BSOD i główny powód z plików dump to ntoskrnl.exe.

    Sprawdzałem dyski, ramy MemTestem, zaktualizowałem wszelkie sterowniki, zaktualizowałem BIOS - nic to nie dało.
    Później ściągnąłem czysty obraz po numerze seryjnym ze strony Lenovo - wgrałem na czysto - nadal to samo.

    Czy można jakoś bardziej po logach dojść co powoduje ten błąd ?

    Co mogę jeszcze sprawdzić przed wysłaniem na serwis ?

    Już nie mam pomysłu.

    Wyciąg z programu WhoCrashed:

    Cytat:

    Crash Dump Analysis

    Crash dumps are enabled on your computer.

    Crash dump directories:
    C:\WINDOWS
    C:\WINDOWS\Minidump

    On Thu 26.03.2020 11:47:09 your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\032620-12328-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2360)
    Bugcheck code: 0x1A (0x41790, 0xFFFF970007765770, 0x9, 0xA)
    Error: MEMORY_MANAGEMENT
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: MicrosoftŽ WindowsŽ Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred. A page table page has been corrupted.
    This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 26.03.2020 11:47:09 your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\MEMORY.DMP
    This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x630B8)
    Bugcheck code: 0x1A (0x41790, 0xFFFF970007765770, 0x9, 0xA)
    Error: MEMORY_MANAGEMENT
    Bug check description: This indicates that a severe memory management error occurred. A page table page has been corrupted.
    This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 26.03.2020 10:27:56 your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\032620-11734-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2360)
    Bugcheck code: 0x13A (0x12, 0xFFFFAD8969A02100, 0xFFFFAD897C869000, 0x0)
    Error: KERNEL_MODE_HEAP_CORRUPTION
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: MicrosoftŽ WindowsŽ Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Wed 25.03.2020 15:56:06 your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\032520-11359-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2360)
    Bugcheck code: 0x18 (0xFFFFAD8FF73247A0, 0xFFFFAD81084AA4F0, 0x3, 0x1)
    Error: REFERENCE_BY_POINTER
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: MicrosoftŽ WindowsŽ Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Tue 24.03.2020 20:14:18 your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\032420-11203-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
    Bugcheck code: 0x189 (0xFFFFAF879C9C9CB0, 0x0, 0x0, 0x0)
    Error: BAD_OBJECT_HEADER
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: MicrosoftŽ WindowsŽ Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that The OBJECT_HEADER of a kernel object has been corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Tue 24.03.2020 10:36:14 your computer crashed or a problem was reported
    crash dump file: C:\WINDOWS\Minidump\032420-11593-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
    Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF8006F9237A0)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: MicrosoftŽ WindowsŽ Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  • Poziom 43  
    Nie podałeś jaki to windows.
    Zamieść SMART (SSD?) z SSD-Z.
    W trybie awaryjnym błąd występuje?

    Jakim dokładnie memtestem testowałeś RAM?

    Jakaś "grubsza sprawa". Bawi mnie jak podobne tematy nie odnotowały rozwiązań:
    https://answers.microsoft.com/en-us/windows/f...e/73055535-78e0-417e-9b64-d9c91bc7997b?page=2
    https://answers.microsoft.com/en-us/windows/f...skrnlexe/05a3efe0-4c8c-420a-b94e-16f71cf07498
  • Poziom 11  
    safbot1st napisał:
    Nie podałeś jaki to windows.
    Zamieść SMART (SSD?) z SSD-Z.
    W trybie awaryjnym błąd występuje?

    Jakim dokładnie memtestem testowałeś RAM?

    Jakaś "grubsza sprawa". Bawi mnie jak podobne tematy nie odnotowały rozwiązań:
    https://answers.microsoft.com/en-us/windows/f...e/73055535-78e0-417e-9b64-d9c91bc7997b?page=2
    https://answers.microsoft.com/en-us/windows/f...skrnlexe/05a3efe0-4c8c-420a-b94e-16f71cf07498


    Nie wiem dlaczego, ale na żadnym programie nie wyświetla mi się SMART...
    System Windows 10.
    MemTest86 z bootowalnego pendrive.

    Generalnie sprawdziłem sporo rzeczy i szukam jeszcze zanim odeślę do serwisu, bo może leży błąd po mojej stronie... już sam nie wiem.
  • Poziom 43  
    _kamel_ napisał:
    Nie wiem dlaczego, ale na żadnym programie nie wyświetla mi się SMART...

    Ciekawe. To podaj model chociaż.
  • Poziom 11  
    Wychodzi SPCC M.2 PCIe NVMe, nie mam pojęcia co za dysk mi wsadzili.
  • Poziom 1  
  • Poziom 11  
    OK, wysyłam na gwarancję.

    Tak, komunikat za każdym razem inny niestety.
  • Poziom 1