Page 1 of 2 12 LastLast
  1.    11 Jun 2017 #1
    Join Date : Jun 2017
    Posts : 18
    Windows 10 64bit

    BSOD on startup ntoskrnl.exe / ntfs.sys (MEMORY MANAGEMENT)


    Hi

    Short story - after installing two new memory sticks these error started happening only when i cold boot my PC. It doesnt happen every time, it happens randomly. Now for a first time it happened when i was browsing the internet (1 min after the cold boot). Thinks I've tried:

    1. Swapping memory poistions
    2. MemTest - 8+ hours - no errors
    3. MemTest+ - 4+ hours - no errors
    4. Windows Memory Diagnostic - no errors
    5. Driver updates and fixes
    6. Registry cleanups and etc.

    I haven't tried to reinstall Windows. In my BIOS the settings are set to Auto, voltages and freq. are 1.5-1600 (like the chips say)
    I am attaching the log as guided in the FAQ section.
    If I need to provide anything else feel free to guide me
    (i havent had this problem with my 2x4GB sticks that I used)

    Cheers!
      My ComputerSystem Spec
  2.    11 Jun 2017 #2
    Join Date : Jun 2015
    Posts : 12,860
    Windows 10 Pro

    Disable fast startup
    Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials




    BSOD on startup ntoskrnl.exe / ntfs.sys (MEMORY MANAGEMENT) Diagnostic Test BSOD on startup ntoskrnl.exe / ntfs.sys (MEMORY MANAGEMENT)
     DRIVER VERIFIER

    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.


    Please fill in your system specs
    Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
    The PSU, cooling and other stuff are NOT mentioned in the tool.

    In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.

      My ComputersSystem Spec
  3.    12 Jun 2017 #3
    Join Date : Jun 2017
    Posts : 18
    Windows 10 64bit
    Thread Starter

    Thanks for the fast reply.
    I have disabled the fast startup and I will test few cold boots to see if the error persist.
    Just a question - If the same configuration worked flawlessly before why now I should disaable it? Just curious.

    I also followed the driver verified tutorial.

    Greetings,
    Martin
      My ComputerSystem Spec
  4.    12 Jun 2017 #4
    Join Date : Jun 2015
    Posts : 12,860
    Windows 10 Pro

    For various reasons fast startup can cause errors over time.
      My ComputersSystem Spec
  5.    14 Jun 2017 #5
    Join Date : Jun 2017
    Posts : 18
    Windows 10 64bit
    Thread Starter

    For now the BSOD doesnt appear, also no System events that indicate such errors.
    May I leave the thread open few days more - for testing reasons? Then I will mark it as Solved.
      My ComputerSystem Spec
  6.    14 Jun 2017 #6
    Join Date : Jun 2015
    Posts : 12,860
    Windows 10 Pro

    That is up to you
      My ComputersSystem Spec
  7.    15 Jun 2017 #7
    Join Date : Jun 2017
    Posts : 18
    Windows 10 64bit
    Thread Starter

    for now there arent any bluescreens. my question is - did driver verifier do something in this case or its the fast startup ? tx
      My ComputerSystem Spec
  8.    15 Jun 2017 #8
    Join Date : Jun 2015
    Posts : 12,860
    Windows 10 Pro

    Driver verifier may sometimes help a system to stabilize, in some situations driver verifier can be used for stabilization to boot a system.
      My ComputersSystem Spec
  9.    16 Jun 2017 #9
    Join Date : Apr 2017
    Posts : 8,658
    windows 10 professional version 1607 build 14393.969 64 bit

    Code:
    BugCheck 1000007E, {ffffffffc0000005, fffff8031f7c1909, ffffe6012b13c5a8, ffffe6012b13bde0}
    
    *** WARNING: Unable to verify checksum for win32k.sys
    Probably caused by : memory_corruption
    Code:
    BugCheck 1000007E, {ffffffffc0000005, fffff8017769dc38, ffff9680be8c24f8, ffff9680be8c1d30}
    
    *** WARNING: Unable to verify checksum for win32k.sys
    Probably caused by : memory_corruption
    Code:
    BugCheck 1A, {6000, ffff8485bb2f1b20, ffffffffc0000225, 0}
    
    Probably caused by : memory_corruption
    Code:
    Filter Manager failed to attach to volume
    Code:
    Windows failed fast startup with error status 0xC00000D4.
    Code:
    Windows failed fast startup with error status 0xC0000001.
    Code:
    Windows failed fast startup with error status 0xC0000001.
    Code:
    Windows failed fast startup with error status 0xC00000D4.
    Code:
    Crash dump initialization failed!
    Code:
    The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_KINGSTON&Prod_DataTraveler_3.0&Rev_1.01#60A44C3FACC9AF2040000D0F&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.
    Code:
    Microsoft-Windows-StartupRepair
    Startup Repair failed.
    Code:
    Windows failed fast startup with error status 0xC0000001.
    Code:
    Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
    Code:
    Windows failed fast startup with error status 0xC0000001.
    Code:
    Windows failed fast startup with error status 0xC0000001.
    Code:
    Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C
    Code:
    {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\M\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost.
    Code:
    A corruption was discovered in the file system structure on volume G:.
    
    The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x100000000002a.  The name of the file is "\SW2013_SP0.0_SSQ\SW2013_sp0_x86_Multilanguage.iso\kor_boot.ttf".
    Code:
    A corruption was discovered in the file system structure on volume G:.
    
    The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x100000000002b.  The name of the file is "\SW2013_SP0.0_SSQ\SW2013_sp0_x86_Multilanguage.iso\malgunn_boot.ttf".
    Code:
    A corruption was discovered in the file system structure on volume G:.
    
    The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x100000000002c.  The name of the file is "\SW2013_SP0.0_SSQ\SW2013_sp0_x86_Multilanguage.iso\malgun_boot.ttf".
    Code:
    A corruption was discovered in the file system structure on volume G:.
    
    The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x100000000002d.  The name of the file is "\SW2013_SP0.0_SSQ\SW2013_sp0_x86_Multilanguage.iso\meiryon_boot.ttf".
    Code:
    A corruption was discovered in the file system structure on volume G:.
    
    The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x100000000002e.  The name of the file is "\SW2013_SP0.0_SSQ\SW2013_sp0_x86_Multilanguage.iso\meiryo_boot.ttf".
    Code:
    A corruption was discovered in the file system structure on volume G:.
    
    The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x100000000002f.  The name of the file is "\SW2013_SP0.0_SSQ\SW2013_sp0_x86_Multilanguage.iso\msjhn_boot.ttf".
    Code:
    A corruption was discovered in the file system structure on volume G:.
    
    The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x1000000000030.  The name of the file is "\SW2013_SP0.0_SSQ\SW2013_sp0_x86_Multilanguage.iso\msjh_boot.ttf".
    Code:
    The file system structure on volume G: cannot be corrected.
    Please run the chkdsk utility on the volume G:.
    Code:
    The file system structure on volume G: cannot be corrected.
    Please run the chkdsk utility on the volume G:.

    1) What was happening that you had attempted a Windows startup repair?
    When the repair failed what did you do?

    2) The logs report many times that Windows failed fast startup.
    Please turn off fast startup.
    Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

    3) There is corruption on drive G

    4) The Master File Table (MFT) contains multiple corrupted file records.

    5) Back up all of your files if they have not yet been backed up.

    5) Open administrative command prompt and type or copy and paste:
    chkdsk /x /f /r

    6) Check all of your drives with either HD Sentinel, Crystal Disk, or HD Tune using SMART and post images into the thread of the images and the data.

    7) Check all of your drives with Sea Tools for Windows using SMART, short, and long generics

    http://www.seagate.com/support/downl...ls-win-master/
    How to use SeaTools for Windows
    CrystalDiskInfo - Software - Crystal Dew World
    http://www.hdtune.com/
    Hard Disk Sentinel - HDD health and temperature monitoring
      My ComputerSystem Spec
  10.    17 Jun 2017 #10
    Join Date : Jun 2017
    Posts : 18
    Windows 10 64bit
    Thread Starter

    Hey, zbook! Thanks for the reply!

    1. Drive G: was a removable drive plugged in that time in my computer - an old and corrupted flash disk that I already threw in the trash
    2. I am attaching 3 logs from seatools, no errors and one screenshot with warning from CrystalDisk Info

    One of my drives, The MAXTOR 320GB (disk volume E) is really old - around 10 years, so I am expecting to have some troubles with it. It even clicks from time to time. When I am ready to say goodbye I will threw it too

    Disabling fast startup for now seems to fixed the problem.

    Thanks again

    PS: I ran chkdsk (for a second time btw) - everything seems ok.
      My ComputerSystem Spec

 
Page 1 of 2 12 LastLast


Similar Threads
Thread Forum
BSOD ntfs.sys and ntoskrnl.exe crashing (System Service Exception)
Hello, The story so far of my problem can be found here: http://www.tomshardware.co.uk/forum/id-3431549/system-service-exception-bsod.html#19774688 Tl;dr: got a brand new PC, crashing constantly, at the moment I'm on the clean installation of...
BSOD Crashes and Debugging
BSOD at random times, ntoskrnl.exe or ntfs.sys or hal.dll cause it
I've been having BSODs for a few months now and only now just got around to looking at the memory dumps to find the cause. Unfortunately, it only shows ntoskrnl.exe, ntfs.sys or hal.dll as the causes, which leaves me unsure with what to do since...
BSOD Crashes and Debugging
Solved BSOD hal.dll+2901, ntoskrnl.exe+19dc04, SynTP.sys+3da5c, NTFS.sys
Hello, Over the last few days I have received 2 BSOD with no visible pattern. They were on 8/2/16 and 8/5/16. The first one blamed NTFS.sys and ntoskrnl.exe and the second one blamed hal.dll, ntoskrnl.exe, SynTP.sys. I have not done anything such...
BSOD Crashes and Debugging
BSOD Memory management ?
Been getting this weird bluescreen just in the last few days, I don't think it's ram because I've ran memtest and 0 errors
BSOD Crashes and Debugging
BSOD caused by NTFS.sys & ntoskrnl.exe on a brand new PC.
There's not much to explain as it can occur randomly, I am guessing it is some driver conflict but I am not tech savvy, regardless, the BSODs are caused by NTFS.sys and ntoskrnl.exe. Here's an image from BlueScreenView 40292
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 06:58.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums