Windows 10: Repeated BSOD on Windows 10, mostly ntoskrnl.exe

Discus and support Repeated BSOD on Windows 10, mostly ntoskrnl.exe in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi everyone, My Windows 10 computer has suddenly started producing BSODs lately. It's a Lenovo T440s. The error produced is MEMORY_MANAGEMENT.... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by jam6789, Mar 17, 2017.

  1. jam6789 Win User

    Repeated BSOD on Windows 10, mostly ntoskrnl.exe


    Hi everyone,

    My Windows 10 computer has suddenly started producing BSODs lately. It's a Lenovo T440s. The error produced is MEMORY_MANAGEMENT.

    BlueScreenView shows it's mainly caused by address ntoskrnl.exe+142970.

    I tried Driver Verifier, but then Windows wouldn't boot at all (it keeps showing BSOD of IRQL_NOT_LESS_THAN_OR_EQUAL). I used system restore to boot normally again.

    I've updated all the drivers through Lenovo's software update tool, except the BIOS. No new devices lately. Nothing seems noteworthy in Windows Update either.

    The computer used to be Windows 8.1, and I got the free upgrade to 10. It's been working fine up until the last month or so.

    Memtest86+ and SSDLife show that it's not RAM or SSD.

    Any help is appreciated!

    Attachment 125560

    :)
     
    jam6789, Mar 17, 2017
    #1
  2. ar300500 Win User
    ar300500, Mar 17, 2017
    #2
  3. ar300500 Win User
    Constant BSOD (Mostly Ntoskrnl.exe)

    Constant BSOD mostly caused by Ntoskrnl.exe.

    I have tried every single trouble shooting technique including:

    Memtest86+ 10 passes 35 hours no errors

    New power supply

    New memory

    Bios updates

    SSD firmware updates

    Updates in general

    windows 10 in place upgrade (Repair Install Windows 10 with an In-place Upgrade)

    Driver verifier (Crashes on boot)

    Tried using poolmon (Confusing and didn't help me)

    sfc scannow

    dism health repair

    Last 2 Minidumps:

    https://drive.google.com/file/d/1u-B4GfCoqDMxwZwu_17AP25esQnOmrcD/view?usp=sharing

    System:

    Windows 10 pro

    i7 4790k

    MSI Z97 gaming 5 motherboard

    32gb hyperx fury ddr3

    GTX 780

    EVGA GQ 750w PSU

    Samsung 850 evo 500gb

    Samsung 850 evo 250gb

    2x 2tb Toshiba HDD

    If you need anything else for analysis please ask

    Thank you
     
    ar300500, Mar 17, 2017
    #3
  4. JLAF5150 Win User

    Repeated BSOD on Windows 10, mostly ntoskrnl.exe

    Well just some initial looking around, It appears you only have 4GB of Memory.. IT could be not enough memory for what you are asking it too do.. I do believe you need more memory..

    Are you running a new program within the last month?? The minimum Windows specs is 2GB Ram for Win 10 on 64bit.. that only leaves you 2GB for other applications.. I think that is your initial problem..
     
    JLAF5150, Mar 17, 2017
    #4
  5. axe0 New Member
    4GB is enough to run Windows 10 properly, there are many who do.


    SSDLife, is only able to read the SMART of the SSD so far the screenshots of their website show. Meaning that it doesn't do anything with the file system of Windows itself.
    There are multiple event logs about the file system having issues, my suggestions:
    1. Cleanup the partitions, you need to have have at least 10-15% free space
    2. Run in an admin command prompt the following command
    Code: chkdsk C: /r&chkdsk D: /r[/quote] The free space is required, else chkdsk will get issues and Windows won't be able to do background things like maintenance.
    Next, the chkdsk command can only run when the system reboots, because chkdsk needs to unmount the partition to check it. In the case of the OS partition it is only possible when the system is offline.
    When chkdsk asks you to schedule it on the next reboot, press Y and reboot.
     
  6. Ztruker Win User
    @axeo, noticed he is at build 10586 which is pretty old for Windows 10. Needs to update to the current 14393.953 build.
     
    Ztruker, Mar 17, 2017
    #6
  7. axe0 New Member
    That could be a next step, after the free space issue & file system issue.
     
  8. jam6789 Win User

    Repeated BSOD on Windows 10, mostly ntoskrnl.exe

    Thanks all for the help. Here is the chkdsk log:
    Code: Checking file system on C: The type of the file system is NTFS. Volume label is Windows8_OS. A disk check has been scheduled. Windows will now check the disk. Stage 1: Examining basic file system structure ... 458752 file records processed. File verification completed. 16093 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... The file reference 0xab000000015fdb of index entry 6B9CA31C5DE4CE8D701FAD3DA1BE894122C7E604 of index $I30 with parent 0x1a140 is not the same as 0xa8000000015fdb. Deleting index entry 6B9CA31C5DE4CE8D701FAD3DA1BE894122C7E604 in index $I30 of file 106816. The file reference 0xab000000015fdb of index entry 6B9CA3~1 of index $I30 with parent 0x1a140 is not the same as 0xa8000000015fdb. Deleting index entry 6B9CA3~1 in index $I30 of file 106816. The file reference 0x123000000015fda of index entry AAD91963EE6F778FD67AF8C4384E5214505774C3 of index $I30 with parent 0x1a140 is not the same as 0x120000000015fda. Deleting index entry AAD91963EE6F778FD67AF8C4384E5214505774C3 in index $I30 of file 106816. The file reference 0x123000000015fda of index entry AAD919~1 of index $I30 with parent 0x1a140 is not the same as 0x120000000015fda. Deleting index entry AAD919~1 in index $I30 of file 106816. 569436 index entries processed. Index verification completed. CHKDSK is scanning unindexed files for reconnect to their original directory. Recovering orphaned file A7D538~1 (90074) into directory file 106816. Recovering orphaned file A7D538BA17CC43106DA0872A1F09EAFDBB1D4BCD (90074) into directory file 106816. 2 unindexed files scanned. Recovering orphaned file DD4E4F~1 (90075) into directory file 106816. Recovering orphaned file DD4E4FD7BA3A44565F8E6B37609EB3E0372BF471 (90075) into directory file 106816. 2 unindexed files recovered to original directory. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Cleaning up 171 unused index entries from index $SII of file 0x9. Cleaning up 171 unused index entries from index $SDH of file 0x9. Cleaning up 171 unused security descriptors. Security descriptor verification completed. 55343 data files processed. CHKDSK is verifying Usn Journal... Usn Journal verification completed. Stage 4: Looking for bad clusters in user file data ... 458736 files processed. File data verification completed. Stage 5: Looking for bad, free clusters ... 1757209 free clusters processed. Free space verification is complete. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. No further action is required. 62337020 KB total disk space. 54567404 KB in 319579 files. 204268 KB in 55344 indexes. 0 KB in bad sectors. 536512 KB in use by the system. 65536 KB occupied by the log file. 7028836 KB available on disk. 4096 bytes in each allocation unit. 15584255 total allocation units on disk. 1757209 allocation units available on disk. Internal Info: 00 00 07 00 cb b7 05 00 8b af 0a 00 00 00 00 00 ................ 10 03 00 00 07 93 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.[/quote] It looks like Windows fixed something? D seems ok. I'll keep running the computer and see if it's fixed. Anything else I should try?
     
    jam6789, Mar 20, 2017
    #8
  9. jam6789 Win User
    Another BSOD, looked exactly the same as most of the rest. The dump file is attached. I'll try running Windows Update. It says there's a "Feature update to Windows 10, version 1607" available? And I I realized that I forgot to upgrade the RAM after I bought the computer. Maybe I'll upgrade it if that might help.

    Attachment 125973
     
    jam6789, Mar 20, 2017
    #9
  10. axe0 New Member
    I hope you're aware about RAM and laptops? That you cannot just install any kind you'd want?

    As @Ztruker mentioned, update to the latest Windows 10 is the next step to go. This, however, requires at least 30GB of free space on the OS partition.
     
  11. jam6789 Win User
    Yes, I'm aware about how to upgrade RAM. Is having only 4GB RAM likely to be causing these BSODs, though? If so, I'll try to upgrade sooner rather than later.

    And, I'll try to make my C partition bigger. But can an older Windows 10 version really be the cause of the BSODs all of a sudden?

    If it's any help, the BSOD's only seem to happen while Firefox (fully updated) is running. Relevant?
     
    jam6789, Mar 21, 2017
    #11
  12. axe0 New Member
  13. jam6789 Win User

    Repeated BSOD on Windows 10, mostly ntoskrnl.exe

    Thanks axe0 for the tips. I will work on getting the Windows partition more space and updating the installation.

    I've also already disabled hardware acceleration in Firefox, as it has been slow lately and I tried that to make it faster. Doesn't seem to have had any effect on the BSOD. However, avoiding running Firefox seems to help.

    I'll post back once I've updated Windows with any results.
     
    jam6789, Apr 5, 2018
    #13
Thema:

Repeated BSOD on Windows 10, mostly ntoskrnl.exe

Loading...
  1. Repeated BSOD on Windows 10, mostly ntoskrnl.exe - Similar Threads - Repeated BSOD mostly

  2. Ntoskrnl BSOD

    in Windows 10 BSOD Crashes and Debugging
    Ntoskrnl BSOD: Hello, Any ideas how I can stop ntoskrnl.exe of causing blue screens? It happens every few days while I am playing games on steam Here are my dumps: https://drive.google.com/file/d/1E7Kwdh1341_R2psC5NVUoETVBtqC_QlP/view?usp=sharing...
  3. Ntoskrnl BSOD

    in Windows 10 Ask Insider
    Ntoskrnl BSOD: Hello, Any ideas how I can stop ntoskrnl.exe of causing blue screens? It happens every few days while I am playing games on steam Here are my dumps: https://drive.google.com/file/d/1E7Kwdh1341_R2psC5NVUoETVBtqC_QlP/view?usp=sharing...
  4. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...
  5. Ntoskrnl BSOD

    in Windows 10 Installation and Upgrade
    Ntoskrnl BSOD: I have had this issue for so long its almost like a part of me. I have uploaded the last 3 minidumps but I don't really understand what is going on. But I know the number one culprit is Ntoskrnl.exe https://1drv.ms/u/s!AgeiZ1AnXkV6esFtCX3uiwaGGuA?e=SlXCUk...
  6. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...
  7. BSOD ntoskrnl

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl: I'm having the same issues. It started 2 days ago, computer is crashing randomly with different BSOD errors. I've tried a new SSD, new RAM and multiple fresh installs of Windows 10. I've run out of ideas, I'm starting to think there is a seriously nasty virus or Microsoft...
  8. BSOD ntoskrnl+ 142480

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl+ 142480: Hi *Smile I have problem with BSOD ntoskrnl+ 142480 . previously I used windows 8.1 and got BSOD ntoskrnl+ 142480, and maybe if I change the OS to Windows 10 the problem will be solved but not . I have update all driver but still got bsod . Please help me *Sad I...
  9. BSOD various ntoskrnl

    in Windows 10 BSOD Crashes and Debugging
    BSOD various ntoskrnl: Hi guys! Made a fresh Win10 install with just basic software (Like whocrashed) I have tried using the Guru3Ds tool to remove all traces of old video card drivers and installed the newest ones without any extra software or bloatware. Have ran Memtest for 24 hours without a...
  10. Bsod ntoskrnl

    in Windows 10 BSOD Crashes and Debugging
    Bsod ntoskrnl: Hi guys, Any help would be massively appreciated. My computer is BSOD at least two times a day. As far as I can tell, all drivers are up to date including Nvidia. Could somebody take a look at the attached and let me know if you find anything? I've ran a system check...
Tags: