Windows 10: Windows 10 fresh install BSOD (ntoskrnl.exe)

Discus and support Windows 10 fresh install BSOD (ntoskrnl.exe) in Windows 10 BSOD Crashes and Debugging to solve the problem; So 5 days ago i installed windows 10 and once a day i get bsod caused by ntoskrnl.exe. First two bsod problems i was able to fixing because they were... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by faeth, Jan 13, 2017.

  1. faeth Win User

    Windows 10 fresh install BSOD (ntoskrnl.exe)

    So 5 days ago i installed windows 10 and once a day i get bsod caused by ntoskrnl.exe. First two bsod problems i was able to fixing because they were related to tcpip and nvidia drivers. But then i got only ntoskrnl bsod with no advanced info which driver causing this problem. All my drivers are updated from manufactory sites and from windows update. I run memtest for 5 hours and got 0 errors. Its strange because when i was using windows 8 before i got like 1 bsod in one and half month so its not related to hw problem im sure. I would be happy if someone helped with this problem because i realy like windows 10.

    faeth, Jan 13, 2017

  2. BSOD error due to ntoskrnl.exr

    I have recently upgraded my hard disk to SSD and did a fresh install of windows 10. I have to get BSOD error "Page Fault in non-paged area" most likely when I was running a torrent.

    Link to the dump file: Dropbox - 102516-6859-01.dmp

    I don't think this would be an issue with hardware/RAM. Could this also be caused by the fact that I have Kaspersky installed as antivirus

    Bug check code: 0x00000050


    Caused by Driver: ntoskrnl.exe

    Caused by Address: ntoskrnl.exe+14a2c0
    AyushChordia, Jan 13, 2017
  3. Vilmondes Win User
    BSOD Windows 10 fresh install - ntoskrnl.exe+c773a

    I've figured this out. The problem was my hard drive disconnecting sometimes and that was triggering the BSOD. I've removed it, cleaned its connectors and plugged it back in.

    I'm be soon replacing that with a SSD.

    Thanks for all your help.
    Vilmondes, Jan 13, 2017
  4. Ztruker Win User

    Windows 10 fresh install BSOD (ntoskrnl.exe)

    The 1/11 dump indicates a problem with nvlddmkm.sys.
    Code: BugCheck D1, {ffff9602c4c71130, 2, 1, fffff80b4f2ca227} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+10a227 )[/quote] This is the driver for your Nvidia 1060 video card. You have the 376.33 driver. There is a
    GeForce Hot Fix driver version 376.48 available.

    Remove and install latest Nvidia drivers:

    I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the hotfix driver for you Nvidia card from link I posted above.

    Then do a custom install of only the NVidia graphics driver and the PhysX driver.

    See if that gets rid of the problem.
    Ztruker, Jan 13, 2017
  5. faeth Win User
    I had this bsod 3 days ago and completely reinstalled driver with DDU so its not the problem i have. But i still getting ntoskrnl BSOD with PAGE_FAULT_IN_NONPAGED_AREA or DRIVER_IRQL_NOT_LESS_OR_EQUAL and caused by driver ntoskrnl.exe +14a6f0
    faeth, Jan 13, 2017
  6. Ztruker Win User
    Ztruker, Jan 13, 2017
  7. faeth Win User
    Yes i updated mi GF driver yesterday. But can you analize the other dmp file in my zip ? Because when i get bsod with specific problem like nvidia driver or tcpip its easy to fix but i dont know what to do with bsod caused by driver ntoskrnl.exe with no advanced info what specific driver caused problem

    another bsod today again ntoskrnl.exe and critical_structure_corruption
    faeth, Jan 14, 2017
  8. Ztruker Win User

    Windows 10 fresh install BSOD (ntoskrnl.exe)

    Code: BugCheck 50, {fffffd93c200f890, 0, fffffdc4c7875db0, 2} Could not read faulting driver name Probably caused by : win32kfull.sys ( win32kfull!_PostTransformableMessageExtended+80 )[/quote] Almost surely caused by a device driver but no indication of which one.

    Try enabling Driver Verifier, see if that shows us anything useful.

    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to

    Windows 10 fresh install BSOD (ntoskrnl.exe) [​IMG]
    Windows 10 fresh install BSOD (ntoskrnl.exe) [​IMG]

    and make sure the correct boxes are checked.

    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it.

    Also would be a good idea to test your ram.
    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses

    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    Windows 10 fresh install BSOD (ntoskrnl.exe) [​IMG]
    Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

    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.

    Windows 10 fresh install BSOD (ntoskrnl.exe) [​IMG]
    Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

    Take a picture when done and post in the forum please.
    Ztruker, Apr 5, 2018

Windows 10 fresh install BSOD (ntoskrnl.exe)

  1. Windows 10 fresh install BSOD (ntoskrnl.exe) - Similar Threads - fresh install BSOD

  2. Fresh Windows 10 install - BSOD

    in Windows 10 BSOD Crashes and Debugging
    Fresh Windows 10 install - BSOD: Hi, I'm trying to install Windows 10 on a new SSD disk but keep on getting "Kernel Security Check Failure" as soon as i try to boot from the USB. It started with me wanting to move over an old internal HD to my computer that already had windows 7 installed on it. However...
  3. 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!AgeiZ1AnXkV6esFtCX3uiwaGGuA?e=SlXCUk...
  4. 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...
  5. BSOD on fresh Windows Install

    in Windows 10 BSOD Crashes and Debugging
    BSOD on fresh Windows Install: I built my PC in May, and have done no hardware changes since then, but have recently had a massive issue with BSODs. On Monday, I was having issues with just application crashes. Games would constantly hard crash, and attempts to repair them would fail. Anti-virus scans...
  6. 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...
  7. BSOD on fresh install

    in Windows 10 BSOD Crashes and Debugging
    BSOD on fresh install: Just did a fresh install a couple days ago, and still getting multiple BSOD`s. I have basicly just let the rig sit there with the power on to see if it was stable. It was not.... I have not installed any drivers or anything myself. Just webbrowsers, spotify and fan control...
  8. BSOD on fresh Windows 10 installation

    in Windows 10 BSOD Crashes and Debugging
    BSOD on fresh Windows 10 installation: Just got a "Kernel Security Check Failure" BSOD on a fresh installation of Windows 10 (Version 1703 OS Build 15063.413) which is about five days old. At the time of the crash I was watching a YouTube video. Thanks 88551
  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. ntoskrnl bsods on fresh install

    in Windows 10 BSOD Crashes and Debugging
    ntoskrnl bsods on fresh install: Hello, I've recently update to x99 platform and I've freshly installed Windows 10 Pro I'm having all sorts of issue with it. I ended up reading all sorts of threads regarding bsods in Windows 10 etc (things that didn't happen on the old x79 platform) Before posting...