Windows 10: BSOD ntoskrnl.exe

Page 2 of 2 FirstFirst 12

  1. Posts : 7
    Windows 10 Home
    Thread Starter
       25 Sep 2017 #11

    My BSODs went away until today. Got a Memory Management BSOD. Running the DM collector log showed the system suffered three additional BSODs between the one in July and the one today. Not understanding how I keep getting BSODs if I am continually updating my Nvidia drivers to the latest ones (I uninstall using DDU every time).
    BSOD ntoskrnl.exe Attached Files
      My ComputerSystem Spec


  2. Posts : 8,733
    windows 10 professional version 1607 build 14393.969 64 bit
       25 Sep 2017 #12

    There was no definitive misbehaving driver in the debugging of the mini dump file.
    It was bugcheck A
    It did display CtHdaSvc.exe
    That is Creative High Definition Audio Service or Sound Blaster Audio Service
    These software programs have multiple drivers.
    They could be uninstalled using control panel/device manager. It is unclear at this juncture how they relate to the bsod.

    Had you tested the Nvidia graphics driver with FurMark?
    If you did what was the duration of testing and the highest temperature?

    Please use one drive or drop box to post a share link for the memory dump:

    memory dump file: %SystemRoot%\MEMORY.DMP or C:\Windows\MEMORY.DMP
    Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.



    Windows driver verifier is a tool that is used to find misbehaving drivers.
    It will repetitively produce bsod until misbehaving drivers are fixed or until it is turned off.

    There are 3 methods commonly used to turn off windows driver verifier and all are done using the windows advanced troubleshooting menu.
    1) startup options (not startup repair) > select #6 safe mode with command prompt > type: verifier reset
    2) command prompt > Administratof X:\Windows\system32.cmd.exe > type: verifier /bootmode resetonbootfail
    3) restore
    The command should be used in the above order and only advance if the prior method fails.
    Using restore typically leads to the loss of the mini dump and little progress is made in the troubleshooting.

    To practice the windows advanced recovery options you can open administrative command prompt and type:
    shutdown /r /o /f /t 00

    Windows driver verifier may produce system sluggishness while it is in use.

    Once the last bsod is found there will be an additional 36 hours of using this tool to see if there are any further bsod. If there are none then troubleshooting with windows driver verifier will be completed.

    This link has the custom test settings for use:
    https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

    This link has the methods to turn off windows driver verifier:
    https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

    This link has information on startup and recovery settings and how to un-check automatic restart so that you have time to view the bsod window. Sometimes the misbehaving driver is displayed in the form *.sys If you see the misbehaving driver please record it and post the information into the thread.

    https://answers.microsoft.com/en-us/windows/wiki/windows_other-system/blue-screen-of-death-bsod/1939df35-283f-4830-a4dd-e95ee5d8669d

    Download and install:
    http://www.nirsoft.net/utils/blue_screen_view.html
    http://www.resplendence.com/whocrashed
    Run them after each BSOD then uninstall the misbehaving driver.

    Post a new zip after each bsod and we will guide you through the troubleshooting:
    BSOD - Posting Instructions - Windows 10 Forums
    Last edited by zbook; 25 Sep 2017 at 08:37.
      My ComputerSystem Spec


  3. Posts : 7
    Windows 10 Home
    Thread Starter
       08 Oct 2017 #13

    Thank you for your reply. I ran FurMark as recommended. It immediately caused a BSOD Memory Management error. I rebooted and reran FurMark and immediately got a BSOD again. Both times pointed to my Nvidia drivers. I tried FurMark again with the stock GPU drivers for my system and the latest drivers from Nvidia. Both times still gave a BSOD. I then sent my machine in for repair and it was determined the motherboard is faulty. Hopefully the replacement will fix the issues with system.
      My ComputerSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
Hello, my PC recently has been receiving a lot of random BSODs . It comes suddenly when I surf the internet, or watching youtube videos. I was thinking that it all comes from my VGA card, but I can still play games such as Dota2 in Ultra settings...
BSOD various ntoskrnl in BSOD Crashes and Debugging
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...
Solved BSoD ntoskrnl.exe in BSOD Crashes and Debugging
So I've had this BSoD three times while playing on a game (Squad). These all occurred randomly within games and the Error calls itself 'page fault in nonpaged area'. Upon checking the dmp file with BluescreenViewer it highlights the ntoskrnl.exe....
BSOD - NTOSKRNL.exe in BSOD Crashes and Debugging
53020 Hi all I've been getting BSOD since playing Fallout 4. Initially I saw it was Nvidia related so I update my graphics and it seems to have cured that one, however now I've been getting a different error. I ran a memtest and all seemed good,...
BSOD because of ntoskrnl.exe in BSOD Crashes and Debugging
Hello guys, I had trouble with my windows 7 : bosd because of ntoskrnl.exe so i decided to do a clean install windows 10 for a new fresh start. But the bsod is still here so i think its probably Hardware problems but wich one ? I've only...
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 04:08.
Find Us