Windows 8 and 8.1 Forums


BSOD after launching system NTFS_FILE_SYSTEM

  1. #1


    Posts : 1
    Windows 8.1 64bit

    BSOD after launching system NTFS_FILE_SYSTEM


    Today I turn on my laptop as usual and after launching system without doing anything BSOD appears - NTFS_FILE_SYSTEM. I think I have all drivers updated. What should I do?
    Last edited by nismo; 17 Nov 2014 at 11:37.

      My System SpecsSystem Spec

  2. #2


    Posts : 2,480
    Windows 10 Pro x64


    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Mihael\Desktop\111514-7781-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
    Machine Name:
    Kernel base = 0xfffff801`6a612000 PsLoadedModuleList = 0xfffff801`6a8e8370
    Debug session time: Sat Nov 15 11:51:18.036 2014 (UTC + 1:00)
    System Uptime: 1 days 14:40:19.778
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    ................................................
    Loading User Symbols
    Loading unloaded module list
    ............................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 24, {b500190637, ffffd001149d9a68, ffffd001149d9270, fffff8016a659dfc}
    
    Probably caused by : memory_corruption ( nt!MiOffsetToProtos+1ac )
    
    Followup: MachineOwner
    ---------
    
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    NTFS_FILE_SYSTEM (24)
        If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
        parameters are the exception record and context record. Do a .cxr
        on the 3rd parameter and then kb to obtain a more informative stack
        trace.
    Arguments:
    Arg1: 000000b500190637
    Arg2: ffffd001149d9a68
    Arg3: ffffd001149d9270
    Arg4: fffff8016a659dfc
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  ffffd001149d9a68 -- (.exr 0xffffd001149d9a68)
    ExceptionAddress: fffff8016a659dfc (nt!MiOffsetToProtos+0x00000000000001ac)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000028
    Attempt to read from address 0000000000000028
    
    CONTEXT:  ffffd001149d9270 -- (.cxr 0xffffd001149d9270;r)
    rax=0000000000000000 rbx=ffffe000ff1b62a0 rcx=000000000000ca5c
    rdx=000000000000fff0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8016a659dfc rsp=ffffd001149d9ca0 rbp=0000000000000000
     r8=0000000000000000  r9=000002c094ab60b0 r10=000002bfca55afd8
    r11=7ffffffffffffffc r12=0000000000000000 r13=ffffe000ff1b6318
    r14=0000000000000000 r15=ffffd001149d9d88
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    nt!MiOffsetToProtos+0x1ac:
    fffff801`6a659dfc 0fb74e28        movzx   ecx,word ptr [rsi+28h] ds:002b:00000000`00000028=????
    Last set context:
    rax=0000000000000000 rbx=ffffe000ff1b62a0 rcx=000000000000ca5c
    rdx=000000000000fff0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8016a659dfc rsp=ffffd001149d9ca0 rbp=0000000000000000
     r8=0000000000000000  r9=000002c094ab60b0 r10=000002bfca55afd8
    r11=7ffffffffffffffc r12=0000000000000000 r13=ffffe000ff1b6318
    r14=0000000000000000 r15=ffffd001149d9d88
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    nt!MiOffsetToProtos+0x1ac:
    fffff801`6a659dfc 0fb74e28        movzx   ecx,word ptr [rsi+28h] ds:002b:00000000`00000028=????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  explorer.exe
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000028
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8016a972138
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
     0000000000000028 
    
    FOLLOWUP_IP: 
    nt!MiOffsetToProtos+1ac
    fffff801`6a659dfc 0fb74e28        movzx   ecx,word ptr [rsi+28h]
    
    FAULTING_IP: 
    nt!MiOffsetToProtos+1ac
    fffff801`6a659dfc 0fb74e28        movzx   ecx,word ptr [rsi+28h]
    
    BUGCHECK_STR:  0x24
    
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8016a65c3dd to fffff8016a659dfc
    
    STACK_TEXT:  
    ffffd001`149d9ca0 fffff801`6a65c3dd : 00000000`00000000 00000000`00000000 00000000`00000040 ffffe000`ff1b62a0 : nt!MiOffsetToProtos+0x1ac
    ffffd001`149d9d60 fffff801`6a65d0ba : 00000000`00000000 ffffe000`f35ea070 00000001`00000001 ffffd001`0fb40830 : nt!MmMapViewInSystemCache+0x79
    ffffd001`149d9ed0 fffff801`6a659aaf : 00000000`00000001 ffffe000`fa3394d0 00000000`00000001 fffff801`00000001 : nt!CcGetVacbMiss+0x122
    ffffd001`149d9f60 fffff801`6a9c35f6 : 00000000`00000001 00000000`00000000 ffffd001`149da070 ffffd001`149da088 : nt!CcGetVirtualAddress+0x36f
    ffffd001`149da000 fffff801`ab18244e : ffffc000`8bb7d000 ffffc000`a3d2f438 00000000`00001000 ffffc000`a3d2f430 : nt!CcMapData+0x72
    ffffd001`149da070 fffff801`ab17ee34 : ffffe000`f8b9a018 ffffc000`a3d2f430 ffffc000`a3d2f390 ffffc000`a462f140 : Ntfs!ReadIndexBuffer+0xde
    ffffd001`149da0f0 fffff801`ab179074 : 00000000`00000001 fffff801`aaf16ff8 ffffe000`f7542380 ffffc000`9a42d920 : Ntfs!FindFirstIndexEntry+0x154
    ffffd001`149da180 fffff801`ab16b3e9 : ffffc000`a462f140 ffffc000`a462f140 ffffe000`fb7c1368 00000000`0000002a : Ntfs!NtfsRestartIndexEnumeration+0x154
    ffffd001`149da3f0 fffff801`ab1834c2 : 00000000`00000000 ffffe000`f37d66c0 ffffd001`149da910 00000000`00000000 : Ntfs!NtfsQueryDirectory+0xaed
    ffffd001`149da7a0 fffff801`ab183619 : 00000000`00000000 ffffe000`fb7c1010 00000000`00000000 ffffd001`149da910 : Ntfs!NtfsCommonDirectoryControl+0xa2
    ffffd001`149da7e0 fffff801`aad7fcf8 : ffffe000`fb7c1368 ffffe000`fb7c1010 ffffe000`f8b9a018 ffffd001`149da808 : Ntfs!NtfsFsdDirectoryControl+0xb9
    ffffd001`149da850 fffff801`aad7e0b6 : ffffe000`f4d2ddf0 00000000`00000000 ffffe000`fb7c1010 ffffe000`fb8a3070 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x258
    ffffd001`149da8f0 fffff801`6aa50e30 : 00000000`00000002 ffffd001`149daa49 00000000`00000000 00000000`00000000 : fltmgr!FltpDispatch+0xb6
    ffffd001`149da950 fffff801`6a76c9b3 : 00000000`00000000 00000000`0b2f26fc ffffe000`f7542380 ffffd001`149dab80 : nt!NtQueryDirectoryFile+0x1cc
    ffffd001`149daa90 00007fff`564819ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0446e4b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`564819ca
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!MiOffsetToProtos+1ac
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53fe6f2e
    
    IMAGE_VERSION:  6.3.9600.17328
    
    STACK_COMMAND:  .cxr 0xffffd001149d9270 ; kb
    
    IMAGE_NAME:  memory_corruption
    
    BUCKET_ID_FUNC_OFFSET:  1ac
    
    FAILURE_BUCKET_ID:  0x24_nt!MiOffsetToProtos
    
    BUCKET_ID:  0x24_nt!MiOffsetToProtos
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x24_nt!mioffsettoprotos
    
    FAILURE_ID_HASH:  {66fb006a-b066-dd1f-f2c2-6e8caaa30c35}
    
    Followup: MachineOwner
    ---------
    Check your RAM using Memtest RAM - Test with Memtest86+ - Windows 7 Help Forums make sure you test each stick separately. Also, run SFC. SFC /SCANNOW : Run in Command Prompt at Boot - Windows 7 Help Forums
      My System SpecsSystem Spec

BSOD after launching system NTFS_FILE_SYSTEM
Related Threads
I ran into 2 BSODs on my computer today. I'm running Windows 8.1 Professional. 1) SYSTEM_SERVICE_EXCEPTION (0x0000003b) 120914-8234-01.dmp 2) NTFS_FILE_SYSTEM (0x00000024) 120914-8156-01.dmp I've attached the related DMP files as well as the CBS and DISM logs below. 55085
Hello when i try to launch a game or google chrome i got blue screen of death with this error code 0x8000000000000002 Did memory check and harddisk check no problems , installed latest nvidia driver , for now it did not blue screened me but it is matter of minutes as it does blue screen randomly ....
The BSOD displays "system_service_exception (win32k.sys)" when I launch TreePad Business Edition (Treepad Business Edition: All-in-one Organizer, PIM/database, Word Processor, notes manager, search engine, Web site generator and much more!) from the PC or SD card; same result in XP or W7...
Thank you.
Windows 8 nothing is launching? in Software and Apps
So recently on my Windows 8 laptop i have a problem where no apps open. I have tried to open everything in the start screen but nothing opens. When i go to desktop nothing opens except for files?? This has been going on for a while and I cant seem to find a solution :cry:.
Solved BSOD on install: ntfs_file_system in Installation & Setup
When I try to install windows 8 preview on my old computer, I keep getting a BSOD and it says this " ntfs_file_system " The reason why I'm installing windows 8 on old computer is because I'm having issues with it (mainly i can't install any Microsoft Office,random freezing,, and sumtimes can't...
Solved Apps not launching? in Drivers & Hardware
Hi, I've installed the 32-bit Preview of Windows 8 on my HP Slate. It installed without problems :D, replacing Win7. The problem is that apps don't launch in Metro mode. The only app that launches is the Control Panel. All other tiles bounce when I tap them but nothing else happens. I...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook