Windows 10: Constant BSODs caused by ntoskrnl.exe

Discus and support Constant BSODs caused by ntoskrnl.exe in Windows 10 BSOD Crashes and Debugging to solve the problem; So I got to build a new pc. It al went well until I suddenly started to get some BSODs. I searched online and got to the conclusion that it was... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by cemarv25, Aug 2, 2017.

  1. cemarv25 Win User

    Constant BSODs caused by ntoskrnl.exe


    So I got to build a new pc. It al went well until I suddenly started to get some BSODs. I searched online and got to the conclusion that it was something wrong with the drivers, so I went and updated them all manually, but that didn't solve the problem. I then ran chkdsk /f /r with the Windows 10 installing drive, and the results said everything was fine. At that point I decided to make a clean install of Windows 10 again to see If it would solve the problem. After I installed it, I updated the drivers again, and a few days later, I started to get the BSODs again. Then, I went and downloaded BlueScreenView to see what was causing the problem, and in every single BSOD there was this ntoskrnl.exe marked as the cause (there usually was another file that was blamed during the actual BSOD, like volsnap.sys, tcpip.sys, etc.)
    It usually just resets and get no other BSOD until I turn it off and turn it on manually.

    With basically no other option, I come here to you guys to see if I can get some help. Also, my RAM is actually two kits of 2x8GB, so I have 32GB. Is there any way that having two kits of the same RAM causing these problems?

    :)
     
    cemarv25, Aug 2, 2017
    #1
  2. wadeb Win User

    Windows 10 Blue Screening on me. DRIVER_CORRUPTED_EXPOOL

    Caused by Driver: ntoskrnl.exe

    Caused by Address: ntoskrnl.exe+146440

    Above is from my dump file using BlueScreenView. Not sure what driver is causing the BSOD, how can I determine the driver?
     
    wadeb, Aug 2, 2017
    #2
  3. BSOD APC_INDEX_MISMATCH ntoskrnl.exe+142940

    I had a BSOD. Bug Check String APC_INDEX_MISMATCH , cause by driver ntoskrnl.exe caused by address ntoskrnl.exe+142940. Adive on the fix for this. XPS 15 9950 RUNNING Windows 10 Pro.
     
    SanilPrakashan, Aug 2, 2017
    #3
  4. Constant BSODs caused by ntoskrnl.exe

    There are many different bugchecks in the dumpfiles.

    The cause for different error codes are usually hardware and lower level problems.

    U should begin with:




    Constant BSODs caused by ntoskrnl.exe [​IMG]
    Diagnostic Test
    Constant BSODs caused by ntoskrnl.exe [​IMG]
    RAM TEST

    Constant BSODs caused by ntoskrnl.exe [​IMG]
    Run MemTest86+ - Test RAM - Windows 10 Forums


    Constant BSODs caused by ntoskrnl.exe [​IMG]



    Constant BSODs caused by ntoskrnl.exe [​IMG]
    Note MemTest86+ V5.01 needs to be run for at least 8 complete 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.

    More Info here: https://answers.microsoft.com/en-us/...f-ecc7b7ff6461


    Make a photo of the result and post it.
     
    BSODHunter, Aug 2, 2017
    #4
  5. Please test only two RAM sticks at once (2x 8 GB). When 8 passes are done test the other two RAM modules
     
    BSODHunter, Aug 2, 2017
    #5
  6. cemarv25 Win User
    Ok, I ran it today in the morning with all the sticks for 4 hours (the non-UEFI version), then shut it down with no errors, gonna run it overnight today.
     
    cemarv25, Aug 3, 2017
    #6
  7. Its important to run it 8 passes long in one piece without interruption. With 32 GB RAM (four modules) it could take up to 100 hours. Running it over night will not be enough my friend *Smile

    Thats why I wrote u should test only 2 sticks at once. You should plan two days for it.


    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.
     
    BSODHunter, Aug 3, 2017
    #7
  8. cemarv25 Win User

    Constant BSODs caused by ntoskrnl.exe

    Ok so here is the 8 passes on the first 2x8gb kit. Couldn't run the 8 passes in a single run because there was a storm after the first 3, so i did the other 5 later. I'm running the test on the other kit, with 5 passes as of posting this.
     
    cemarv25, Aug 5, 2017
    #8
  9. Wrong Version of Memtest. Please run V5.01.
     
    BSODHunter, Aug 5, 2017
    #9
  10. cemarv25 Win User
    Are the versions of memtest really that different? It's just so much time to run it again on both of the kits :/
     
    cemarv25, Aug 5, 2017
    #10
  11. zbook New Member
    If you use software to test hardware you will want the most up to date software.
    In addition the method of testing is important.
    For memory testing it has been found that the results can be misleading if improper testing is performed.
    For example if less than 8 passes are performed there is a high incidence of false negatives.
    A false negative is getting a test result of pass and finding later that the RAM was malfunctioning.
    So in order to reduce the false negatives a minimum of 8 passes is required and the more passes the better.

    https://answers.microsoft.com/en-us/...f-ecc7b7ff6461
    MemTest86+ - Test RAM Windows 10 BSOD Tutorials
     
    zbook, Aug 5, 2017
    #11
  12. cemarv25 Win User
    Well, here is the 8 passes on one of the kits (with the correct version of memtest now xD).
     
    cemarv25, Aug 6, 2017
    #12
  13. zbook New Member

    Constant BSODs caused by ntoskrnl.exe

    The memtest 6+ displays 16 GB
    Is it possible to test the othe 16GB?
    Approximately how long did it take to complete the 16 GB testing?

    Code: ffffc181`5fbc6880 ffffac08`40de0088 ffffc181`5fbc6888 fffff802`dad0cde1 dxgkrnl!ADAPTER_RENDER:Constant BSODs caused by ntoskrnl.exe :DdiSubmitCommandVirtual+0x181 ffffc181`5fbc6890 fffff802`dc305b13Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_24ddebfb518b5a55\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0xc5b13[/quote] The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.


    The computer manufacturer's web site is preferred. Enter the computer's serial or product number and the operating system to view available drivers.


    If you use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.


    Official Display Driver Uninstaller DDU Download


    Display Driver Uninstaller Download version 17.0.7.2


    Display Driver Uninstaller: How to use - Windows 7 Help Forums[2]=Hardware%20and%20Drivers


    NVIDIA
     
    zbook, Aug 6, 2017
    #13
  14. cemarv25 Win User
    Yes, I am testing the other 16G kit, I just did it separately because it would take forever to test 4x8G 8 times xD.
    About the display driver, I just did it, and checked the "clean install" box, so that should be fine now.
     
    cemarv25, Aug 6, 2017
    #14
  15. cemarv25 Win User
    Here is the 8 passes from the test on the other 2x8G kit
     
    cemarv25, Aug 7, 2017
    #15
Thema:

Constant BSODs caused by ntoskrnl.exe

Loading...
  1. Constant BSODs caused by ntoskrnl.exe - Similar Threads - Constant BSODs caused

  2. ntoskrnl bsod

    in Windows 10 Software and Apps
    ntoskrnl bsod: My pc has been bsod-ing for 2-3 years now and i recently decided to try and fix it. I use bluescreen view and always see that the bsods are always caused by ntoskrnl.exe. heres all of the stuff ive to try and fix it.Used 1 8gb ram stick at a timeused different ram slotsused...
  3. ntoskrnl BSOD

    in Windows 10 Software and Apps
    ntoskrnl BSOD: Hello, I have quite a persistent problem here.I often get BSOD or straight out system restarts the latter don't have any trace in minidump. In the past few days, they were too recurrent and got to a point where I had to reinstall Windows because my laptop actually got slowed...
  4. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: KUKutter_UKFirstly, I would like to say that I am posting this again because after having an instant reply from an 'Andrew', and posting my dmp files as requested on July 24th I haven't heard anything back since! I have responded a couple of times but nothing is happening to...
  5. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: Hi there, My new machine around 8 months old now runs perfectly most of the time. Uptime 3 - 6 weeks at a time. NO issues at all - I am a heavy PC user: Gaming, Audio Work and some 3D modelling, so my machine goes through its paces.Every now and then on boot, I get the error...
  6. 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...
  7. 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...
  8. BSOD caused by ntoskrnl exceptions

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by ntoskrnl exceptions: Hello to anyone that is willing to help my name is Glenn, My pc was assembled by professionals but it got really hot so a month ago I took my cpu cooler off and noticed that they left the plastic on the cpu cooling block, So I fixed that issue after emailing the people...
  9. 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...
  10. BSOD - Bad Pool Header caused by NTOSKRNL

    in Windows 10 BSOD Crashes and Debugging
    BSOD - Bad Pool Header caused by NTOSKRNL: Hello, I've been having an issue this past week whenever my computer restarts (seems to be from Windows Updates) I come back to a Bad Pool Header BSOD. I was able to get it stopped by uninstalling Avast and doing a Clean Boot. After about 2 hours of restarting and just adding...
Tags: