Multiple BSOD New custom Build ntfs.sys ntoskrnl.exe

Page 1 of 5 123 ... LastLast

  1. Posts : 30
    Windows 7 Professional 64-bit
       #1

    Multiple BSOD New custom Build ntfs.sys ntoskrnl.exe


    I recently rebuilt my computer with almost all new parts except the 2 160GB HDD's which have all of my old data. I am getting multiple BSOD's but they usually refer to the driver ntfs.sys as the culprit from what I can find.

    My previous system was receiving ntoskrnl.exe BSOD's but they were fairly rare. My new machine is getting them sporadically but usually a couple a day. It BSOD's once I ran the SF_Diagnostic Tool.

    I have attached the dump files it created.

    My PC Specs are in my "System Specs" portion of my profile

    3.5Ghz FX-6300
    8GB GSKILL Ripjaw X
    1x Samsung M 120Gb SSD
    1x WD Blue 1TB
    GigaByte GA-970A-UD3
      My Computer


  2. Posts : 3,056
    Windows 10
       #2

    Hello :) , The file you uploaded is corrupt, try running the SFDT again using the Grab All option.

    Seeing how old the drives are I would recommend testing them.

       Warning
    This method should NOT be performed on an SSD!

    Testing the HDD:

    1. Perform a Disk Check | Disk Check
    2. Then Post the results following | THIS METHOD
    3. Download SeaTools for Windows if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
    4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.
      My Computer


  3. Posts : 30
    Windows 7 Professional 64-bit
    Thread Starter
       #3

    OK. I will attempt to get the whole file once I get back home. I will run the Disk Check on my other hard drives and see if it finds any errors.
      My Computer


  4. Posts : 3,056
    Windows 10
       #4

    Keep us posted :) .
      My Computer


  5. Posts : 30
    Windows 7 Professional 64-bit
    Thread Starter
       #5

    Alright, I got the full dump created. The checkdisk is still running on one of the drives.

    The checkdisk completed on both of my old drives and it didn't find any errors
    Last edited by tunaktu86; 05 Sep 2013 at 03:06.
      My Computer


  6. Posts : 3,056
    Windows 10
       #6

    Thanks :) .

    First of all test your RAM.

    Code:
    CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
    2 errors : !nt (fffff80003535c04-fffff80003535c3c)
    fffff80003535c00  2c  db  d8  ff *ed  5f  ff  ff  ff  49  8b  cd  e8  53  30  d5 ,...._...I...S0.
    ...
    fffff80003535c30  89  70  18  48  89  78  20  41  54  48  83  ec *22  48  83  22 .p.H.x ATH.."H."
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  STRIDE
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE
    Testing the RAM:
    koolkat77 said:
    Test and Diagnose RAM Issues with Memtest86+:

       Tip

    • Pay close attention to part 3 of the tutorial "If you have errors"
    • Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

    *When you're done post a picture of results.


    Install Service Pack 1:

    Code:
    Windows 7 Kernel Version 7600 MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.17273.amd64fre.win7_gdr.130318-1532




    Outdated Drivers:

    - Razerlow.sys Mon Nov 07 08:33:11 2005


    - lmimirr.sys Wed Apr 11 01:32:45 2007


    - LMIRfsDriver.sys Mon Jul 14 19:26:56 2008


    Update, remove if possible, LogMeIn and Synapse 2.0.




    Code:
    Installed Physical Memory (RAM)    8.00 GB
    Page File Space    1.50 GB
    Reset your Page File:

    Start Menu> RUN> "control.exe system" (without the qoutes)
    On the Left hand side you'll see click it.
    In this windows
    Choose click the settings for Performance.
    Then Advanced once more
    Then "Change"
    Deselect
    Choose "No paging file" Click the "Set" button.
    Confirm all the windows, restart the PC, reverse the procedure and restart again to take effect.





    Once that is done enable Driver Verifier:
    Arc said:
    Enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip




    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  7. Posts : 30
    Windows 7 Professional 64-bit
    Thread Starter
       #7

    • I ran MemTestx86+ for 6 hours which equated to 4 passes with 0 errors.
    • Service Pack 1 installed
    • Razer Driver updated
    • Synapse 2.0 removed
    • Pagefile size set to system managed


    I did have one strange occurrence. Previously before I got to this forum I found Memtestx86 (no +) and ran that. It errored out quickly and rebooted my machine. I unseated my ram switched around locations of the sticks and then ran memtextx86+

    I am going to leave the computer on for the day to see if it gets any BSOD.
    Last edited by tunaktu86; 06 Sep 2013 at 05:45. Reason: forgotten thought
      My Computer


  8. Posts : 3,056
    Windows 10
       #8

    Thanks for the update :) .
    Four passes in not enough unfortunately but it's PC, if it gets BSOD's again I ask you to test the RAM thoroughly.

    Memtest86+ and Memtest86 are two different groups, we here find 86+ to be more reliable.
    Keep us posted.
      My Computer


  9. Posts : 30
    Windows 7 Professional 64-bit
    Thread Starter
       #9

    After my last post I turned on Driver Verify as suggested in the troubleshooting. The computer started up fine, the desktop and icons showed up, then the screen went all cross-hatched and showed the cursor as working and frozen in the center of the screen. It was similar to the picture below but i could still make out the basics of what was on the screen. Very jumbled and cross hatched but it could still be seen.

    The computer never went BSOD. It just stayed on that screen, probably for about 15 minutes before I restarted.

      My Computer


  10. Posts : 3,056
    Windows 10
       #10

    First components that might be causing this are the GPU / Monitor(less likely).
    Since you don't have an integrated GPU do you have a spare GPU to test with?
      My Computer


 
Page 1 of 5 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 21:54.
Find Us