Windows 10: BSOD completely random NTFS.sys & ntoskrnl.exe related

Discus and support BSOD completely random NTFS.sys & ntoskrnl.exe related in Windows 10 BSOD Crashes and Debugging to solve the problem; HI i had my brand new lenovo laptop few days ago and after installing windows 10 home I started to get completely random BSOD 2-4 times per day . My... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by ahmedespo, Nov 15, 2018.

  1. ahmedespo Win User

    BSOD completely random NTFS.sys & ntoskrnl.exe related


    HI i had my brand new lenovo laptop few days ago and after installing windows 10 home I started to get completely random BSOD 2-4 times per day .
    My drivers are from lenovo web site then i tried different versions of windows 10 64bit
    I ran memtest86 to test my ram and all tests passed successfully
    please i am very disappointed and disparate so any help from a professional will be appreciated .
    thank you in advance *Smile
    DESKTOP-6IBG30Q-Thu_11_15_2018_223045_52.zip

    :)
     
    ahmedespo, Nov 15, 2018
    #1
  2. ARC
    Arc Win User

    Random BSOD while browsing internet


    BitDefender is nothing special. mwac.sys causes BSODs anywhere.
    A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
    In that very thread, the suggested action apparently worked.

    The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
    As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
    That is why I posted that my suggestion may work, or may not. Let us see where it goes.
     
  3. BSOD ntoskrnl, plz help!

    Hello, I'm having bsod when I launch benchmark with sisoft sandra.

    I got 2 different bsod DRIVER_CORRUPTED_XPOOL and DRIVER_OVERRAN_STACK_BUFFER all with the same driver ntoskrnl.

    what to do?

    i'm using win10 64bit.

    thank you
     
    S_Bourghol, Nov 15, 2018
    #3
  4. ConiGL Win User

    BSOD completely random NTFS.sys & ntoskrnl.exe related

    ConiGL, Nov 15, 2018
    #4
Thema:

BSOD completely random NTFS.sys & ntoskrnl.exe related

Loading...
  1. BSOD completely random NTFS.sys & ntoskrnl.exe related - Similar Threads - BSOD completely random

  2. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: KUKutter_UKFirstly, I would like to say that I am posting this again because after having an instant reply from an 'Andrew', and posting my dmp files as requested on July 24th I haven't heard anything back since! I have responded a couple of times but nothing is happening to...
  3. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: Hi there, My new machine around 8 months old now runs perfectly most of the time. Uptime 3 - 6 weeks at a time. NO issues at all - I am a heavy PC user: Gaming, Audio Work and some 3D modelling, so my machine goes through its paces.Every now and then on boot, I get the error...
  4. BSOD Crashes Relating to dxgmms2.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD Crashes Relating to dxgmms2.sys: Hi,I've been experiencing intermittent BSOD crashes in Windows 10. The most recent one had a message relating to dxgmms2.sys, and previous crashes seem to implicate a driver/drivers being the cause of these crashes. I have run memory tests and found nothing wrong with the...
  5. Random BSOD ntoskrnl, ntkrnlmp executables

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD ntoskrnl, ntkrnlmp executables: I have a Lenovo laptop with the following specs: Intel Core i7-8550U 4C / 8T, 1.8 / 4.0GHz, 8MB Integrated Intel UHD Graphics 620 Intel SoC Platform 16GB Soldered DDR4-2400 512GB SSD M.2 2280 PCIe NVMe 13.9" UHD 3840x2160 IPS 300nits Glossy I started getting random...
  6. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...
  7. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...
  8. BSOD playing overwatch ntoskrnl related?

    in Windows 10 BSOD Crashes and Debugging
    BSOD playing overwatch ntoskrnl related?: Hello, I recently got a new graphics card, as well as upgrading my OS to windows ten. However before and after these actions I receive various BSODs but only while playing Overwatch. Looking into it they seem to be related to the ntoskrnl.exe process, but I may be...
  9. Random BSODs (ntoskrnl,memory_management)

    in Windows 10 BSOD Crashes and Debugging
    Random BSODs (ntoskrnl,memory_management): Hello, first timer here. Long story short, after i updated to windows 10 from 8.1 i started experiencing some randomly BSODs. So i downloaded the ISO and made a clean install.Immidiatelly after my newly formated pc i installed Avast,mozilla and Asrock's Suite to check for...
  10. Frequent dxgmms2.sys related BSOD's

    in Windows 10 BSOD Crashes and Debugging
    Frequent dxgmms2.sys related BSOD's: Since the last windows update I get frequent crashes with the above source referenced. My Nvidia graphic driver is overwritten by a seemingly unstable one by windows update. My only resolution to cure the problem is to roll back to an older version, whereby I can play...