Windows 8 and 8.1 Forums

ntfs.sys X.24 BSOD

  1. #1

    Posts : 6
    Windows 8 Pro

    ntfs.sys X.24 BSOD

    So I have been having a few issues with my system as of late... have not been able to pin point where they are coming from though.

    What do you guys think?

      My System SpecsSystem Spec

  2. #2

    Posts : 5,139
    Win8.1Pro - Finally!!!

    You have 5 hard drives. What is the make/model/wattage and age of your Power Supply?

    This device is disabled. Is this deliberate? If so, why?
    Microsoft Kernel Debug Network Adapter ROOT\KDNIC\0000 This device is disabled.
    If not using it, please uninstall it's software.
    If using it, please re-enable it and update the software.

    We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
    There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

    Here's some suggestions:
    - Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
    - Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than mid-2012 with SSD's.
    - Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
    - Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
    ....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
    - Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
    06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
    05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives:
    27 Feb 2013 - I'm starting to see much better reliability with SSD's using current (mid-2012 and later) storage drivers. I have withdrawn my objections to using these devices in everyday systems.
    If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

    Please remove the Western Digital software as it has been known to cause BSOD's on some Windows systems.

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    lirsgt.sys Sat Mar 6 14:53:01 2004 (404A2C1D)
    part of a Copy Protection platform developed by Tages SA

    atksgt.sys Mon Oct 20 03:50:38 2008 (48FC384E)
    part of a Copy Protection platform developed by Tages SA

    MBfilt64.sys Thu Jul 30 23:40:32 2009 (4A7267B0)
    Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver)

    LGVirHid.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
    Logitech Gamepanel Virtual HID Device Driver

    LGBusEnum.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
    Logitech Keyboard

    TRIXX.sys Wed Oct 6 12:14:37 2010 (4CACA06D)
    Sapphire TriXX Tweak Utility

    If this doesn't stop the BSOD's, please try the following stuff:

    CHKDSK /R /F:
    Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
    FWIW - I know that the /F is supposed to be redundant, but I prefer to have it run anyway.
    When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

    Elevated Command Prompt:
    Go to Start and type in "cmd.exe" (without the quotes)
    At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

    CHKDSK LogFile:
    Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
    Expand the Windows logs heading, then select the Application log file entry.
    Double click on the Source column header.
    Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
    Copy/paste the results into your next post.
    2) Try these free hardware diagnostics (start with the hard drive tests): Hardware Diagnostics

    The following is for informational purposes only.
    **************************Thu Apr 11 03:49:08.098 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\041113-10046-01.dmp]
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16551.amd64fre.win8_gdr.130306-1502
    System Uptime:0 days 4:33:25.811
    Probably caused by :ntkrnlmp.exe ( nt!ExReleaseResourceAndLeavePriorityRegion+4b0 )
    BugCheck 24, {b50019060b, fffff88009bc9128, fffff88009bc8960, fffff88000a9de65}
    BugCheck Info: NTFS_FILE_SYSTEM (24)
    Arg1: 000000b50019060b
    Arg2: fffff88009bc9128
    Arg3: fffff88009bc8960
    Arg4: fffff88000a9de65
    BUGCHECK_STR:  0x24
    CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
    MaxSpeed:     3500
    CurrentSpeed: 3500
      BIOS Version                  P2.60
      BIOS Release Date             01/16/2013
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    **************************Thu Apr 11 03:49:08.098 2013 (UTC - 4:00)**************************
    lirsgt.sys                  Sat Mar  6 14:53:01 2004 (404A2C1D)
    wdcsam64.sys                Wed Apr 16 04:39:08 2008 (4805BB2C)
    atksgt.sys                  Mon Oct 20 03:50:38 2008 (48FC384E)
    MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
    LGVirHid.sys                Mon Nov 23 20:36:48 2009 (4B0B38B0)
    LGBusEnum.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)
    TRIXX.sys                   Wed Oct  6 12:14:37 2010 (4CACA06D)
    RTKVHD64.sys                Tue Jun 19 04:50:56 2012 (4FE03D70)
    EtronXHCI.sys               Tue Jul  3 07:00:15 2012 (4FF2D0BF)
    EtronHub3.sys               Tue Jul  3 07:00:21 2012 (4FF2D0C5)
    k57nd60a.sys                Sun Aug 26 00:58:34 2012 (5039ACFA)
    intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
    HECIx64.sys                 Mon Dec 17 14:32:21 2012 (50CF7345)
    speedfan.sys                Sat Dec 29 15:59:35 2012 (50DF59B7)
    LEqdUsb.Sys                 Thu Jan  3 03:12:57 2013 (50E53D89)
    LHidEqd.Sys                 Thu Jan  3 03:12:59 2013 (50E53D8B)
    LHidFilt.Sys                Thu Jan  3 03:13:04 2013 (50E53D90)
    AtihdW86.sys                Tue Jan 15 15:41:28 2013 (50F5BEF8)
    LGSHidFilt.Sys              Thu Jan 17 15:15:00 2013 (50F85BC4)
    dump_storahci.sys           Fri Mar  1 21:15:44 2013 (513160D0)
    atikmpag.sys                Mon Mar 18 21:29:26 2013 (5147BF76)
    atikmdag.sys                Mon Mar 18 22:47:22 2013 (5147D1BA)
      My System SpecsSystem Spec

  3. #3

    Posts : 6
    Windows 8 Pro

    Wow. Thank you for the comprehensive information!

    I will work through everything you posted after I get off work. I do have my system overclocked and has been very stable for the last month or so and just in the last week it's started giving me problems.

    This is the PSU that I am using at the moment, a OCZ Fatal1ty 1000W and is around 6 months old. OCZ Fatal1ty 1000W Individually-Sleeved Modular Gaming 80Plus Gold Power Supply compatible with Intel Sandy Bridge Core i3 i5 i7 and AMD Phenom: Computers & Accessories

    Microsoft Kernel Debug Network Adapter ROOT\KDNIC\0000 This device is disabled.

    Is disabled because I saw that it was the cause of one of the crashes... and looked up info on it and it was not something that needed to be enabled. Should I enable it back again?

    Also, I am using an 800D case that comes with a SATA hot swap bay and have all my drives connected to it... could that also be the cause of the issues? Have had the case around a month since I put everything together.
      My System SpecsSystem Spec

  4. #4

    Posts : 5,139
    Win8.1Pro - Finally!!!

    Long ago I learned that the first troubleshooting step in an overclocked system is to remove the overclock. This is for 2 reasons:
    1) in case the overclock is at fault (and it hasn't damaged any hardware yet) - this will fix the problem.
    2) the tests we use for troubleshooting are based on a standard system operating normally - so an overclocked system won't necessarily give correct results because of the stress on the components. This is why I recommend stopping the overclock completely while troubleshooting.

    Also, I found that overclocks will degrade over time - the system just won't be able to hold a high overclock forever. The system will get older and it's tolerance for this sort of stress will lessen - resulting in more errors.

    PSU looks OK to me (but I'm not a hardware specialist)

    Leave the Microsoft Kernel Debug network Adapter disabled for now - but we may have to revisit it later on.
    If having problems with it, I'd start looking at programs that are "network aware"

    Hot swap stuff may/may not be involved. Let's see what further BSOD's (if any) indicate. The NTFS indicates (to me) a problem somewhere in the storage sub-system (could be either hardware or software).
      My System SpecsSystem Spec

  5. #5

    Posts : 6
    Windows 8 Pro

    I was originally getting crashes while playing several games. So I removed my OC on my GPU's and for the most part I thought that it was the reason why I was having issues. Things seemed to be working fine, but it just seems that the crashes occur at a random amount of time.

    Crashes were caused by a mix of the driver for that MS Kernel Debug network adapter driver or NTFS.exe. Right before this last BSOD occurred I played a game, it ran fine, but then crashed/stopped responding when I exited it. I did not touch anything after that. I left the PC up and running, then this morning I simply opened IE and it went straight into the BSOD.

    Could the GPU's be responsible in anyway for that specific BSOD? Just so I can rule them out in my mind.
      My System SpecsSystem Spec

  6. #6

    Posts : 5,139
    Win8.1Pro - Finally!!!

    A STOP 0x24 error is an error that involves the NTFS.sys driver - which is the driver for the filesystem on your hard drive.
    As such, it's probably not real likely that it's your vido card affecting this. But it is very likely that something in the storage sub-system is causing this. CHKDSK is the tool of choice for fixing NTFS problems - but if it's another component in the storage sub-system, the problems may just return (so you may see errors if you run CHKDSK again).

    BTW - run the CHKDSK command on all hard drives. It's not uncommon for a problem with one hard drive to affect the entire system.

    BSOD analysis is a bit tricky.
    First we try to eliminate all possible 3rd party driver issues (by far the most common reason for BSOD's).
    Once we're confident that we've gotten all of them - then we move on to hardware testing or Windows repairs (hardware is the next most likely issue).
    But we don't follow it exactly as there are certain "givens" that help out a lot more than others. For example, if you're short of Windows Updates - updating them is one of the most likely fixes for BSOD's (and it'll fix some issues with 3rd party drivers also). We also look at things like overclocking to get the system as stable as possible while we're starting work on it.

    While we can suspect hardware issues (some BSOD's are more likely to be hardware than others), we can't see a pattern of hardware errors until we have 4 or 5 memory dumps to work with. The reason for this is that hardware errors generate random BSOD error codes. There are exceptions here also - sometimes the error will even point out "hardware" as a cause.

    But then, be aware that "hardware" can also be:
    - borked (broken) hardware (several different procedures used to isolate the problem device)
    - BIOS issues (check for updates at the motherboard manufacturer's website)
    - overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
    - compatibility issues (3rd party hardware/drivers)
    - low-level driver problems
    - or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

    They all can cause lower level errors that simulate a hardware problem.
    In short, please continue doing the things that I've mentioned. If unable to do them, just post back and we'll either suggest other things to try - or we'll have you hold off to see if it matters or not.
    Keep us informed of the changes that you made/
    As any BSOD's occur, please zip up and upload the contents of C:\Windows\Minidump so we can analyze them.
      My System SpecsSystem Spec

  7. #7

    Posts : 6
    Windows 8 Pro

    I just wanted to post back that I have resolved my problem. Seems to be caused by something rather bizarre.

    So I had decided to change the TIM paste that I was using for my processor a few weeks ago. I took the processor out to clean off the old paste. So during that time, it seems that I let, either a tiny piece of the paper towel or something just land into the socket of the processor. The piece lodged itself in between the pins of the socket.

    I am so happy that it didn't simply kill the system... the chip... the motherboard or catch on fire (even though it was way too tiny to start a fire...) Taught me a valuable lesson to make sure to check the socket before laying the chip in.

    The reason I decided to look, was because some one mentioned that maybe my water block was either on too tight or the clamp to push the processor in was not on properly and the pins were not making contact properly. Or worst, that I had bent pins.

    My guess is that this little piece of debris was blocking whatever pin is responsible for the area of stuff I am having issues with. Since I was still getting the same BSOD while the whole system was in stock clocks. Now that I removed it, things went back to normal.

    John I greatly appreciate your help! Thank you for providing all of your knowledge to help solve this. Even though it was something totally bizarre.
      My System SpecsSystem Spec

  8. #8

    Posts : 5,139
    Win8.1Pro - Finally!!!

    I provide advice based on my experience - but it's the user (you) who actually solves the problem.
    That's how I got started on this stuff many, many years ago.

    Thanks for letting us know the solution to this! I'm sure it'll help others who come looking for help with similar problems!
    Good luck!
      My System SpecsSystem Spec

  9. #9

    Posts : 16
    Windows 8.1 Enterprise x64

    Hi Y'all.

    Ok. I've been having the BSoD with multiple errors causing the crashes.

    May 31st: NETIO.SYS
    Jun 2nd: CNG.SYS
    Jun 3rd: WMILIB.SYS
    Jun 6th: NTFS.SYS

    I have dmp files for all 3 crashes if requested.

    After the CNG.SYS crash I ran MEMTEST86 from a UEFI USB drive and after 6 hours it returned no errors with my memory modules. The NETIO.SYS error had me thinking it was my Samsung SSD which runs the Win8.1 x64 Enterprise OS but after running diagnostics on the SSD it returned no errors. Now getting the NTFS.SYS error I'm baffled at what's causing these different errors virtually everyday for the past week.

    So, what ideas can be offered for me to look into that's causing these errors?

      My System SpecsSystem Spec

  10. #10

    Posts : 5,139
    Win8.1Pro - Finally!!!

    cmcole101 - please start your own topic so that your problem can get the individual attention that it deserves.
    Also, Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum):
    Eight Forums: Blue Screen of Death (BSOD) Posting Instructions
    Ten Forums: BSOD - Posting Instructions - Windows 10 Forums
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
ntfs.sys X.24 BSOD

Similar Threads
Thread Forum
How to debug BSOD on W8 caused by ntoskrnl or ntfs.sys :(
Hi guys, my desktop was perfectly fine a week ago and suddenly I got a BSOD or two per day (4 to 5 hours using my computer). All that I can remember is that I upgraded my GC driver 2 days before that and did some trick I didn't understand in the registry to help Battlefield 4 loading facter. I...
BSOD Crashes and Debugging
BSOD with different errors, 8.1, sytem thread, ntfs
Hello everyone, I am having BSOD issues... used to have them some months ago, then none... a couple days ago they started again, today, got 3 already. Working not really possible. I didn't write them down quickly enough, but one was NTFS, one was system thread exception. I have not...
BSOD Crashes and Debugging
BSOD everyday related to ntfs.sys ntoskrnl.exe win32k.sys
My computer, since I built it around 6 months ago, has been constantly crashing, 1-3 times per day. I have tried re-seating the ram modules and graphics card, and reinstalling windows 8. On the current install I have installed no third party drivers, and left everything to windows update. My...
BSOD Crashes and Debugging
Ntfs bsod
I thought I solved this problem, but something else is popping up causing a BSOD. Please see attached.
BSOD Crashes and Debugging
bsod ntfs crash
Hi there, Im looking for some help with a crash, which this time is saying its re: NTFS. (here is html output from bluescreen viewer app) 295,336
BSOD Crashes and Debugging
Ntfs.sys BSOD crash
Wasn't really doing anything had a game up and chrome and was afk and it randomly crashed. Picture of BSOD: The full dump and minidump on my dropbox: ==================================================
BSOD Crashes and Debugging
BSOD before and after reformat - ntfs.sys
Hey all I had been getting a few different BSODs on my newly put together computer. I unfortunately did not save the error codes for them so I can't tell you exactly what they were. The BSODs seemingly happened randomly. Sometimes when the computer was asleep, sometimes when I was browsing the...
BSOD Crashes and Debugging

Eight Forums Android App Eight Forums IOS App Follow us on Facebook