Recently reimaged computer - NTFS_FILE_SYSTEM BSOD

Page 1 of 3 123 LastLast

  1. Posts : 20
    Windows 7 Professional x64
       #1

    Recently reimaged computer - NTFS_FILE_SYSTEM BSOD


    Hi all,

    I had my computer reimaged about a month ago by a professional service and it seemed to be working OK afterwards, until yesterday when I experienced an NTFS_FILE_SYSTEM blue screen. I ran a chkdsk directly afterwards and it didn't seem to report any problems. Today, around 30 minutes ago, I got another NTFS_FILE_SYSTEM BSOD. Looks like something is certainly not working correctly.

    Does anyone have an idea of what could be causing this?

    Log file Zip:
    Attachment 390973

    System Specs:

    Win 7 SP 1
    i7-4770 3.4 GHz
    32 GB RAM (Not original)
    GTX 1070 8 GB (Not original)

    Screenshot from BlueScreenView report:
    Attachment 390972
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #2

    Upload the chkdsk log Check Disk (chkdsk) - Read Event Viewer Log





    Diagnostics Test

     HDD TEST


    Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
    Run the long test.
       Note
    Do not run SeaTools on an SSD as the results will be invalid.

    Make a photo of the result and post it.

    Run HDTune to
    • scan for errors, no quick scan but full scan
    • check the health,
    • benchmark.

    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    • the error scan,
    • the health,
    • the benchmark incl. following
      • transfer rate,
      • access time,
      • burst rate,
      • cpu usage.
      My Computer


  3. Posts : 20
    Windows 7 Professional x64
    Thread Starter
       #3

    I ran Memtest86 and received many errors. Will try to swap out the RAM tomorrow and see if the situation is resolved.
      My Computer


  4. Posts : 20
    Windows 7 Professional x64
    Thread Starter
       #4

    I thought that had been the issue, but it is looking like there could be more than one contributing cause.

    Tested all four sticks of RAM with Memtest, received errors. So I removed half of them (slots B1 and B2) and ran the test again on the remaining two sticks (in slots A1 and A2), and there were no errors. Then I swapped the good RAM into B1 and B2 and ran the tests again, and no errors.

    Updated logs are attached: Attachment 391226

    Chkdsk log and HD Tune screenshots: Attachment 391228

    Additionally, when trying to set the storage controller mode to IDE/SATA in order to run SeaTools, the only other available option is RAID.

    Attachment 391227
      My Computer


  5. Posts : 7,050
    Windows 10 Pro
       #5

    The updated log is unfortunately empty.

    Additionally, when trying to set the storage controller mode to IDE/SATA in order to run SeaTools, the only other available option is RAID.
    I would recommend to post this in the tutorial, there is a great chance that the problem is quicker solved there than when I try to handle it.
      My Computer


  6. Posts : 20
    Windows 7 Professional x64
    Thread Starter
       #6

    Here's an archive I made by hand of the minidump files:
    https://www.dropbox.com/s/tcbw4gsvwt...Dumps.zip?dl=0

    I ran Driver Verifier with all non-Microsoft drivers checked, as well as ntfs.sys, ntoskrnl.exe, and netio.sys, as those were showing up frequently in Blue Screen View (unless it's not a good idea to test those?). Got an additional BSOD on reboot but unfortunately it did not save to logs.
      My Computer


  7. Posts : 7,050
    Windows 10 Pro
       #7

    NTFS is the Windows NT File System driver,
    If NTFS causes problems, you would need to reinstall Windows as the software part of the hard drive would cause problems.

    Ntoskrnl is the Windows Kernel
    If Ntoskrnl causes problems you wouldn't be able to boot Windows at all in any way!

    NETIO is the Windows Network Input Output driver
    If NETIO causes problems, you would more likely have network connection issues.


    Basically, a Windows driver is NEVER the cause. Bluescreen Viewer, WhoCrashed and similar programs show them for 1 reason only, because these drivers were the last active before the BSOD function was called but that doesn't make them the cause.
    If what those programs show would be true Microsoft wouldn't have sold so many Windows copies in the first place, more likely would they either do something entirely different or they would've shut down everything a long time ago.
      My Computer


  8. Posts : 20
    Windows 7 Professional x64
    Thread Starter
       #8

    Ok, thanks for the info. I'll run Driver Verifier again without any of the MS drivers selected.
      My Computer


  9. Posts : 20
    Windows 7 Professional x64
    Thread Starter
       #9

    Ran Driver Verifier with every driver other than a Microsoft driver selected, and the resulting BSOD:

    IRQL_NOT_LESS_OR_EQUAL

    Updated logs as of the most recent crash:

    https://www.dropbox.com/s/4ke8irhz4a...16_v2.zip?dl=0
      My Computer


  10. Posts : 7,050
    Windows 10 Pro
       #10

    Upload a new zip from the DM Log Collector. Only dumps is enough when requested.
      My Computer


 
Page 1 of 3 123 LastLast

  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 05:46.
Find Us