Recently reimaged computer - NTFS_FILE_SYSTEM BSOD

[User16457]

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:
View 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:
View attachment 390972

 

[axe0]

Upload the chkdsk log :ar: http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html

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.

 

[User16457]

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

 

[User16457]

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: View attachment 391226

Chkdsk log and HD Tune screenshots: View 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.

View attachment 391227

 

[axe0]

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.

 

[User16457]

Here's an archive I made by hand of the minidump files:
https://www.dropbox.com/s/tcbw4gsvwt9mtzg/UpdatedDumps.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.

 

[axe0]

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.

 

[User16457]

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

 

[User16457]

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/4ke8irhz4ahc439/UpdatedDumps_9-1-16_v2.zip?dl=0

 

[axe0]

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

 

[User16457]

DM Log Collector Zip: https://www.dropbox.com/s/87ks14xg6lqd0ub/TOM-PC-Thu_09_01_2016_135120_05.zip?dl=0

 

[axe0]

Run following command in an admin command prompt, it'll create a few files on the desktop, zip these up and upload the zip please.

 

[User16457]

Attached are the two files that were created:

View attachment 391262

 

[axe0]

Apologies for the trouble, a few errors were present in the previous code, please try this code:

msinfo32 /nfo "%USERPROFILE%\Desktop\SFdebugFiles\msinfo32.nfo"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
"%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"

It should create 3 files on the desktop
1. msinfo32.nfo
2. uninstall.txt
3. installed.txt
zip these up and upload the zip.

 

[User16457]

Thanks,

I tried the new code and it looked like it was collecting some information, but there was a notification of a syntax error. Looks like no files were produced.

The error said: "ERROR: Invalid syntax. Type "REG EXPORT /?" for usage."

 

[axe0]

Again a few errors...
I've tested the commands separately on my system, they work successfully.
If it doesn't work this time we'll have to do it without them.

Please run following code in an admin command prompt, it should create the 3 files mentioned in post #14

msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components "%USERPROFILE%\Desktop\installed.txt"

 

[User16457]

Got two of the files this time, but there was still an error.

Here are two of the three: View attachment 391279

 

[axe0]

I cannot find the 0xC1 crash from the picture you posted in the previous page, but I did find a 0xA crash with verifier enabled which is the last from yesterday, 1:05 PM. Were the Windows drivers still checked in the driver verifier settings at that time?

 

[User16457]

At the time of the IRQL_NOT_LESS_OR_EQUAL crash at 1:05 yesterday, only the non-Microsoft drivers were selected.

 

[axe0]

Indicative to hardware problems or other problems, at least not a driver issue!

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.