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

  1.    13 Jan 2017 #1

    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.
      My ComputerSystem Spec

  2. Posts : 6,010
    Windows 10 Pro X64 17134.191
       13 Jan 2017 #2

    The 1/11 dump indicates a problem with nvlddmkm.sys.
    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 )
    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.
      My ComputersSystem Spec

  3.    14 Jan 2017 #3

    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
      My ComputerSystem Spec

  4. Posts : 6,010
    Windows 10 Pro X64 17134.191
       14 Jan 2017 #4

    Did you install GeForce Hot Fix driver version 376.48? The zip you uploaded showed you had 376.33.
      My ComputersSystem Spec

  5.    15 Jan 2017 #5

    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
    Last edited by faeth; 15 Jan 2017 at 12:48.
      My ComputerSystem Spec

  6. Posts : 6,010
    Windows 10 Pro X64 17134.191
       16 Jan 2017 #6

    BugCheck 50, {fffffd93c200f890, 0, fffffdc4c7875db0, 2}
    Could not read faulting driver name
    Probably caused by : win32kfull.sys ( win32kfull!_PostTransformableMessageExtended+80 )
    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
    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.

    warning   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.

    Note   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.
      My ComputersSystem Spec


Related Threads
Move cases for my PC and did a clean install of Windows 10 and ran windows update. Was just checking e-mails and the PC randomly BSOD. 115523 Any help is appreciated. Thanks!
Fresh install of Windows 10 Home 64 Bit 4 year old computer, may need some hardware upgrades. BSODs can occur whenever, usually when playing a game (TERA). But can also randomly happen whilst browsing or installing windows updates. I'd like...
Solved ntoskrnl bsods on fresh install in BSOD Crashes and Debugging
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...
Hi, So I upgraded my system. Bought a new motherboard, CPU, CPU Cooler, RAM, PSU & SSD. Installed windows 10, worked fine for the first week. Now when I start my PC in the morning or from when I get in from work, I get a BSOD when the PC...
This is on an old eMachines M6805 laptop that originally came with XP 32-bit. I put a fresh install of Windows 7 32-bit on it which ran fine. I then upgraded that to Windows 10 32-bit. The first time it booted up I was able to log in but got a...
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 23:57.
Find Us