BSOD ntoskrnl.exe Solved

Page 8 of 12 FirstFirst ... 678910 ... LastLast
  1.    21 Jul 2018 #71

    A new BSOD, ran the collector directly after it happened. It will be a while before the dump file is uploaded.
    BSOD ntoskrnl.exe Attached Files
      My ComputerSystem Spec


  2. Posts : 21,730
    windows 10 professional version 1607 build 14393.969 64 bit
       22 Jul 2018 #72

    There were missing folders and files in the latest beta log collector.
    Please re-run the beta log collector and post a new zip into the thread.
    Also open file explorer > this PC > C: > in the right upper corner search for C:\windows\memory.dmp > zip > post a one drive or drop box share link into the thread
      My ComputerSystem Spec

  3.    22 Jul 2018 #73

    Re ran the log collector. The memory dump is being uploaded. Will post the link when it is finished.
    BSOD ntoskrnl.exe Attached Files
      My ComputerSystem Spec


  4. Posts : 21,730
    windows 10 professional version 1607 build 14393.969 64 bit
       22 Jul 2018 #74

    When available please post a memory.dmp with all BSOD:

    Crash dump found at C:\Windows\MEMORY.DMP
    Creation date: 07/22/2018 02:57:15
    Size on disk: 1195 MB
      My ComputerSystem Spec

  5.   My ComputerSystem Spec


  6. Posts : 21,730
    windows 10 professional version 1607 build 14393.969 64 bit
       23 Jul 2018 #76
      My ComputerSystem Spec

  7.    23 Jul 2018 #77

    I did the first time it was recommended. I did not induce a BSOD that night with about 6 hours of continuous use. Should I keep driver verifier on until I get a BSOD?
      My ComputerSystem Spec


  8. Posts : 21,730
    windows 10 professional version 1607 build 14393.969 64 bit
       23 Jul 2018 #78

    1) make sure that you make a brand new restore point
    2) and make sure that you have a backup image (Macrium, Aoemi, Acronis, Paragon, EaseUS, etc)
    3) Use this link for the the custom settings:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
    4) Use this link for the methods to turn off or recover from using Windows driver verifier:
    Enable and Disable Driver Verifier in Windows 10 | Windows 10 Tutorials
    5) Use the tool for 48 hours to find BSOD
    6) After the last BSOD use the tool for an additional 36 hours and then that will complete the troubleshooting with this tool.
    7) The computer and boot may become sluggish while using the tool. It there are problems using the computer then communicate that into the thread and the settings can be modified.
    8) After each BSOD allow the % counter to rise to 100% before rebooting so that there is sufficient time to create the dump file
    9) Use verifier/reset or verifier /bootmode resetonbootfail or system restore to turn off or recover from using the tool and always use the verifier reset first and advance to the other commands only if the prior command fails. System restore often leads to a loss of the dump file and little progress is made in the troubleshooting.
    10) After each BSOD post at the same time: a) beta zip and b) c:\windows\memory.dmp zip
      My ComputerSystem Spec

  9.    29 Jul 2018 #79

    Followed driver verifier instructions exactly. Did a fresh system restore point and enabled driver verifier exactly as prescribed, checking only the non-microsoft drivers. Complete bricked system. Won't boot to windows (hangs on the spinning circle). Tried to reset verifier (received the message "no settings were changed"). Tried to system restore. Gives error 0x800700003. Tried to clean install from recovery drive and USB, gives error 0x80070003. I'm going to pull the SSD and completely wipe it and start again. Hopefully this gives some more troubleshooting data.
      My ComputerSystem Spec


  10. Posts : 21,730
    windows 10 professional version 1607 build 14393.969 64 bit
       30 Jul 2018 #80

    Had you made a Macrium backup image?
    Macrium has a boot rescue which can be tried however it is not likely to turn off Windows driver verifier.
    There are troubleshooting steps using command prompt.
    What happened with the command: verifier /bootmode resetonbootfail?
    Clean install is the most efficient method.
      My ComputerSystem Spec


 
Page 8 of 12 FirstFirst ... 678910 ... LastLast

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 03:51.
Find Us