Windows 10: BSOD: ntoskrnl.exe and more Solved

Page 4 of 9 FirstFirst ... 23456 ... LastLast
  1.    09 Feb 2016 #31

    To bluescreens in a row, I attached the file. I checked with another program and the driver ntoskrnl.exe is still the issue. I hope my hardware is alright... Shall I run memtest 86?
    Last edited by EUWDIAMOND; 09 Feb 2016 at 14:44.
      My ComputerSystem Spec

  2.    10 Feb 2016 #32

    had another one, again ntoskrnl.exe. But they are not as frequent as they used to be so thats a progress.
      My ComputerSystem Spec


  3. Posts : 12,505
    Windows 10 Pro
       10 Feb 2016 #33




    BSOD: ntoskrnl.exe and more Diagnostic Test BSOD: ntoskrnl.exe and more
     RAM TEST

    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
      My ComputersSystem Spec

  4.    10 Feb 2016 #34

    Will do this. Do you know to what ntoskrnl.exe is related and what part of my software could be damaged if the ram is alright? Windows? Drivers? Registry? Something else?
      My ComputerSystem Spec


  5. Posts : 12,505
    Windows 10 Pro
       10 Feb 2016 #35

    Ntoskrnl.exe is a Windows kernel file, it is the core of Windows that is referenced to when it is the last active. It is pretty much a standard thing to assume that it isn't correct. If the core of Windows has problems you would experience so much more problems then bluescreens.

    If the memory is alright then you have other hardware problems, I noticed that driver verifier caused the crashes but driver verifier was unable to mark a driver as the cause what indicates hardware problems.
      My ComputersSystem Spec

  6.    11 Feb 2016 #36

    I ran memtest for 9 Passes, 0 errors, which means my ram is fine and Im very happy for that. What shall I do next?
      My ComputerSystem Spec


  7. Posts : 12,505
    Windows 10 Pro
       11 Feb 2016 #37

    Try following hardware tests



    BSOD: ntoskrnl.exe and more Diagnostic Test BSOD: ntoskrnl.exe and more
     CPU TEST

    Run Prime95 and/or IntelBurnTest to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums

    Note   Note
    If you're overclocking anything, please stop it and set everything back to default while troubleshooting

    warning   Warning
    Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.





    BSOD: ntoskrnl.exe and more Diagnostic test BSOD: ntoskrnl.exe and more
     GPU TEST

    Run Furmark to test your GPU. Furmark tutorial

    Note   Note
    Run Furmark for around 30 minutes


    warning   Warning
    Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high


    Please fill in your system specs
    Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.
    How to fill in your system specs:

      My ComputersSystem Spec

  8.    14 Feb 2016 #38

    I found the culprit. It might sound very stupid, but it is my keyboard. I thought back on when the bluescreens first started to occur and it was when I swapped my keyboard. I swapped it back and didnt have a bluescreen for 3 days. However, the keyboard without bsod is garbage and the other one is great but apparently it causes bsods. It is a Corsair Strafe, the one with the red keys. What would you suggest doing? There are no drivers available as far as I know.
      My ComputerSystem Spec


  9. Posts : 12,505
    Windows 10 Pro
       14 Feb 2016 #39

    What would you suggest doing? There are no drivers available as far as I know.
    No drivers = get rid of it and get another one which actually does have drivers for Windows 10.
      My ComputersSystem Spec

  10.    21 Feb 2016 #40

    Hello,

    I have only had 2 Bluescreens in the past six days (since I swapped the keyboard) which is great. However, I had another one today. What is the procedure to fix / check the issue? It was again caused by the driver ntoskrnl.exe. Caused by address: ntoskrnl.exe+142480. Maybe you can trace back the root of this problem with this informatio

    edit: Is there safe way to check the functionality of the SSD? I've only investigated my HDD, which appears to be fine. However, my computer mainly crashes when I play a game which is located on the ssd.
      My ComputerSystem Spec


 
Page 4 of 9 FirstFirst ... 23456 ... LastLast

Related Threads
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...
BSOD ntoskrnl.exe fix? in BSOD Crashes and Debugging
Computer has been crashing a ton recently and I am looking for a fix, please respond if you know any anything.
Ntoskrnl.exe Bsod in BSOD Crashes and Debugging
Hello, i have costume build pc for a years now , i think last year i had to change cooler and its probably when my problems started , or could be later im not sure , basicly now everyday when i first start up pc its getting freezed , if i restart...
Solved BSOD in ntoskrnl.exe in BSOD Crashes and Debugging
This is the most recent BSOD. I have no idea on what is causing the problem. I dont know if it's a chipset driver, graphics card issue, sound card issue, or an on the mainboard component that is causing the issue. This morning I was rendering 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 04:22.
Find Us