BSOD very random ntoskrnl.exe

Page 2 of 2 FirstFirst 12

  1. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #11

    Norton Internet Security causes the same issue with a greater frequency. Every 20% norton users are victim of this issue.... every 100% mcafee users, too :)

    I'd suggest you to use Microsoft Security Essentials. Many of us using the program happily over a very long time, without a single issue..... neither virus nor BSOD.
      My Computer


  2. Posts : 31
    Windows 7 64 bit Ultimate
    Thread Starter
       #12

    thanks for the explanation
      My Computer


  3. Posts : 31
    Windows 7 64 bit Ultimate
    Thread Starter
       #13

    I find some other thing.

    On 5 January nvidia release new driver 310.90

    On 6 January begun bsod on my pc. (i haven't install 310.90)

    On 25 mars Nvidia release new driver 314.22. And again i haven't install these drivers

    On 26 mars begun bsod again after a period when haven't bsod.

    This happens with different types of drivers. 306.97 and other 2 different version.

    I think are not the drivers themselves, but the system to update of the control panel nvidia. (Perhaps conflict with Kaspersky ?)

    Is it possible?

    Thanks
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #14

    If you want, you may use Kaspersky..... it it problems again.
      My Computer


  5. Posts : 31
    Windows 7 64 bit Ultimate
    Thread Starter
       #15

    I wrote this to understand the problem more deeply, not for Kaspersky

    It is interesting and curious?
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #16

    nvidia control panel does not conflict with kaspersky.
    the 310.14 WHQL is known to be buggy .... it caused many a problems there.

    But the 306.22 WHQL never failed on the driver itself.

    Kaspersky causes BSOD on itself, it does not conflict with the display driver at all, but it conflicts a lot of system elements.

    Finally, if the issue is caused by display driver auto update failure, the failing module would not have been nvlddmkm.sys but something else.
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:24.
Find Us