Windows 10: BSOD caused by ntoskrnl.exe and ndis.sys Solved

Page 1 of 2 12 LastLast
  1.    14 Apr 2017 #1

    BSOD caused by ntoskrnl.exe and ndis.sys


    Hi,

    I just moved, this weekend from a HDD to a SSD and installed a watercooling for my CPU. After cloning my disk, I had multiple BSOD, so I decided to use the MediaCreationTool.exe to do a new clean install. But I'm still getting BSOD. It happens quite randomnly (twice during the login screen, the last BSOD).

    Thanks for your help.

    Attachment 130094
      My ComputerSystem Spec

  2.    14 Apr 2017 #2

    I just had two new BSOD. WhoCrashed:
    Code:
    On Sat 15/04/2017 00:33:37 your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801A78491B4, 0xFFFFC681C9086C00, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
    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 Fri 14/04/2017 23:55:00 your computer crashed
    crash dump file: C:\Windows\Minidump\041417-14015-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70) 
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803706C61B4, 0xFFFFDE00C3C6E850, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
    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.
      My ComputerSystem Spec

  3. axe0's Avatar
    Posts : 13,620
    Windows 10 Pro
       15 Apr 2017 #3

    Hi Augustin,

    Unfortunately we have some trouble performing a proper analysis with systems running Windows 10 CU update.
    There are some issues on the side of Microsoft regarding symbols and we'll have to wait until Microsoft fixes this issue. This is, unfortunately, kinda normal since it has also happened with previous builds.
      My ComputersSystem Spec

  4.    22 Aug 2017 #4

    axe0 said: View Post
    Hi Augustin,

    Unfortunately we have some trouble performing a proper analysis with systems running Windows 10 CU update.
    There are some issues on the side of Microsoft regarding symbols and we'll have to wait until Microsoft fixes this issue. This is, unfortunately, kinda normal since it has also happened with previous builds.
    Hi,

    I was wondering if there were any update about that issue. I still have my computer which freezes daily.

    Thanks.
      My ComputerSystem Spec

  5. philc43's Avatar
    Posts : 3,561
    64bit Win 10 Pro ver 1803 Build 17134.285 and W10 Insider Build 18234
       22 Aug 2017 #5

    Please post a new set of logfiles - although there are still a few issues we can analyse the mini-dump files so it is well worth investigating if you still have problems.
      My ComputersSystem Spec

  6.    22 Aug 2017 #6

    Thanks.

    Here are the new logfiles.
      My ComputerSystem Spec


  7. Posts : 20,059
    windows 10 professional version 1607 build 14393.969 64 bit
       22 Aug 2017 #7

    The logs are in a foreign language and cannot be scanned or read. Please re-post using English as the default language so that the logs can be troubleshooted:

    Language - Add, Remove, and Change in Windows 10 Windows 10 General Tips Tutorials
    BSOD - Posting Instructions - Windows 10 Forums
      My ComputerSystem Spec

  8. axe0's Avatar
    Posts : 13,620
    Windows 10 Pro
       22 Aug 2017 #8

    warning   Warning
    Programs that claim to update your drivers install either the wrong or corrupted drivers.
    If you have installed any driver with Driver Booster 4, please remove them as it may cause trouble.

    An easy way to get remove these drivers is by using a restore point prior the installation.
      My ComputersSystem Spec

  9.    22 Aug 2017 #9

    Tanks. In that case I have to reinstall Windows 10, I installationed thel a few months ago, so I have no restore point. Or maybe you have a better solution.

    Here are the logfiles in English.
      My ComputerSystem Spec

  10. axe0's Avatar
    Posts : 13,620
    Windows 10 Pro
       22 Aug 2017 #10

    Is there a log or something of all drivers that have been installed?
      My ComputersSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
Hello, i have been getting bsods for months now. I have tried updating drivers, totally resetting the computer, scanning for viruses / malware i also scanned for errors on seatools for dos and it found some and fixed them and didn`t crash for 5...
Solved Various BSOD Caused by ntoskrnl.exe in BSOD Crashes and Debugging
Hi, I'm facing various BSOD. After I open minidump files via Bluescreenview, it's caused by Ntoskrnl.exe. Here's the minidump files Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. Here's the screenshot of...
Solved BSOD caused by ntoskrnl.exe please help in BSOD Crashes and Debugging
Hey all, I've attached 4 minidumps. Can you please help troubleshoot this intermittent BSOD?
BSOD caused by ntoskrnl.exe in BSOD Crashes and Debugging
Hello! I have recurring blue screens on my laptop and can't seem to figure out what's causing them. Sometimes, the computer also freezes completely without any forewarning and the only way to shut it down is to remoce the battery. I should...
BSOD caused by ntoskrnl.exe in BSOD Crashes and Debugging
BSODs have been happening for a while but I'm not really sure what's the actual cause.
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 03:06.
Find Us