BSOD Kernel Security Check Failure (ntoskrnl.exe)

Page 5 of 6 FirstFirst ... 3456 LastLast

  1. Posts : 14,901
    Windows 10 Pro
       #41

    I like yours too :)

    Let me know how it goes.
      My Computers


  2. Posts : 39
    Windows 10 Home x64
    Thread Starter
       #42

    axe0 said:
    I like yours too :)

    Let me know how it goes.
    Installed the latest Beta Driver to see what happens. will let you know if anything
      My Computer


  3. Posts : 39
    Windows 10 Home x64
    Thread Starter
       #43

    axe0 said:
    I like yours too :)

    Let me know how it goes.
    Spent a few hours playing GTA SA.
    Watched a few youtube videos
    and then a Wild BSOD appeared...

    Attachment 44486
      My Computer


  4. Posts : 14,901
    Windows 10 Pro
       #44

    We'll need to rule out old drivers as they could cause this problem.
    Quite odd, the logitech drivers have reversed to an older version.
    Code:
    lvbflt64		Tue Oct 23 04:10:38 2012 		lvbflt64.sys
    lvrs64		Tue Oct 23 04:11:24 2012 		lvrs64.sys
    lvuvc64		Tue Oct 23 04:12:08 2012 		lvuvc64.sys
    bcmwl63a		Fri Oct 31 20:18:04 2014 		bcmwl63a.sys
    Please check Logitech for driver updates, it is recommended to do nothing else while updating the drivers.
    For the Broadcom network driver, try removing it in the device manager and reboot.
    Windows should automatically install the drivers again.
      My Computers


  5. Posts : 39
    Windows 10 Home x64
    Thread Starter
       #45

    axe0 said:
    We'll need to rule out old drivers as they could cause this problem.
    Quite odd, the logitech drivers have reversed to an older version.
    Code:
    lvbflt64        Tue Oct 23 04:10:38 2012         lvbflt64.sys
    lvrs64        Tue Oct 23 04:11:24 2012         lvrs64.sys
    lvuvc64        Tue Oct 23 04:12:08 2012         lvuvc64.sys
    bcmwl63a        Fri Oct 31 20:18:04 2014         bcmwl63a.sys
    Please check Logitech for driver updates, it is recommended to do nothing else while updating the drivers.
    For the Broadcom network driver, try removing it in the device manager and reboot.
    Windows should automatically install the drivers again.
    Logitech doesn't offer drivers for the C-615 Webcam on their website. that or Im looking in the wrong place, but let me try to update through Device manager
      My Computer


  6. Posts : 39
    Windows 10 Home x64
    Thread Starter
       #46

    axe0 said:
    We'll need to rule out old drivers as they could cause this problem.
    Quite odd, the logitech drivers have reversed to an older version.
    Code:
    lvbflt64        Tue Oct 23 04:10:38 2012         lvbflt64.sys
    lvrs64        Tue Oct 23 04:11:24 2012         lvrs64.sys
    lvuvc64        Tue Oct 23 04:12:08 2012         lvuvc64.sys
    bcmwl63a        Fri Oct 31 20:18:04 2014         bcmwl63a.sys
    Please check Logitech for driver updates, it is recommended to do nothing else while updating the drivers.
    For the Broadcom network driver, try removing it in the device manager and reboot.
    Windows should automatically install the drivers again.

    Hello Again. Sorry for not replying in a while.

    But the I can't seem to find driver updates for any of the stated devices .

    Logitech states that their update software takes care of driver updates (and it states that my drivers are up to date.)
    ASUS (the Manufacturer of my PCI-E WIFI card) states that windows has the drivers built in for the card. (the broadcom device)

    I don't know of anything else I can try other than go through and remove the wifi card and camera, and go for a wired ethernet connection for this pc to see if those are the problem.

    I already added a new graphics card. (R9 270X) and also went to Device manager and uninstalled both the wifi card and camera but that has made no difference.
      My Computer


  7. Posts : 39
    Windows 10 Home x64
    Thread Starter
       #47

    Here is another ZIP with some more recent BSOD's.
    one thing I noticed is that ntoskrnl is flagged 90% of the time when looked at through Bluescreen View.

    another cause that im thinking of is that the powersupply is so noisy that it is causing these problems.
    I noticed that if I set the PC near any tv antenna, the tv connected will not receive any signal. OR if I connect the wifi antennas directly to the Wifi card (instead of the magnetic base), I wont be able to connect to the access point even if it is directly on top of the Computer case.

    Attachment 50974
    Last edited by ssandoval83; 28 Nov 2015 at 15:42. Reason: add some info
      My Computer


  8. Posts : 14,901
    Windows 10 Pro
       #48

    Ntoskrnl.exe is a file from Windows used in the boot process.
    This file is flagged when no other file is present to blame, 99.9% of the time it is not the real cause because if this driver is the cause one would experience much more problems.

    Programs like BluescreenView and WhoCrashed can't be used for this when you want the real cause, because in a lot of crashes the ntoskrnl.exe file is blamed but a 3rd party driver is causing issues, but that driver can't be identified by such programs because they only look at the 'probably caused by'part.

    That sounds like a driver issue, but I can't say too much because I have no experience with such things.
    What tv exactly is it?

    Please try driver verifier for an attempt to find the driver(s) causing issues.
    Note that driver verifier may cause crashes, but doesn't always reveal the driver in the dumps. This is why driver verifier may need to be enabled a few times. Read the instructions below carefully.



    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computers


  9. Posts : 39
    Windows 10 Home x64
    Thread Starter
       #49

    axe0 said:
    Ntoskrnl.exe is a file from Windows used in the boot process.
    This file is flagged when no other file is present to blame, 99.9% of the time it is not the real cause because if this driver is the cause one would experience much more problems.

    Programs like BluescreenView and WhoCrashed can't be used for this when you want the real cause, because in a lot of crashes the ntoskrnl.exe file is blamed but a 3rd party driver is causing issues, but that driver can't be identified by such programs because they only look at the 'probably caused by'part.

    That sounds like a driver issue, but I can't say too much because I have no experience with such things.
    What tv exactly is it?

    Please try driver verifier for an attempt to find the driver(s) causing issues.
    Note that driver verifier may cause crashes, but doesn't always reveal the driver in the dumps. This is why driver verifier may need to be enabled a few times. Read the instructions below carefully.



    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
    The TV issue is a signal interference issue. it seems that the RFI that the powersupply or one of the components in the machine puts out so much RFI on the same frequency as broadcast OTA TV that it will over power the signal and cause the TV to not pick up the channels.

    I will try Driver verifier when I have a chance to better use the computer. as it is getting late and I will probably not be using it later today.
      My Computer


  10. Posts : 14,901
    Windows 10 Pro
       #50

    I thought you are using software for connecting with the TV, that is why I said driver issue :)
      My Computers


 

  Related Discussions
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 18:47.
Find Us




Windows 10 Forums