Sign in with
Sign up | Sign in
Your question

Windows 7 Blue Screen of Death NTFS_FILE_SYSTEM 0x00000024 Ntfs.sys

Last response: in Windows 7
Share
December 2, 2010 7:58:00 PM

Hello,

I have been getting this same blue screen of death error for a while now. I built my own computer and am moderately knowledgeable. I have scoured the internet for an attempted fix and have not gotten a solution.

I am using BlueScreenView to tell me about the error:
http://imgur.com/uKd1L

I have also tried using chkdsk using the boot from cd option. This did not come up with any errors.

I have also used the memtest to check both sticks of RAM from here:http://www.memtest86.com/download.html

I have also tried running sfc /scannow in the cmd window, with no errors reporting.

Here is my dump data, I realize there is an issue with the symbols so I'm trying to fix that and hopefully you can still use this dump file.. if not any help on fixing the symbols would be appreciated.
Quote:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\120210-15147-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50
Debug session time: Thu Dec 2 15:17:38.462 2010 (UTC - 6:00)
System Uptime: 0 days 0:01:21.147
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800393cef8, fffff8800393c760, fffff80002ad3d74}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+72d74 )

Followup: MachineOwner
---------



December 2, 2010 8:17:22 PM


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\120210-20404-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a0c000 PsLoadedModuleList = 0xfffff800`02c49e50
Debug session time: Thu Dec 2 06:24:06.735 2010 (UTC - 6:00)
System Uptime: 0 days 11:50:20.171
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {c08a2, 0, 0, 0}

Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )

Followup: MachineOwner
---------

1: 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: 00000000000c08a2
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x24

PROCESS_NAME: SteamTmp.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff88001215e95 to fffff80002a7c740

STACK_TEXT:
fffff880`0890b6b8 fffff880`01215e95 : 00000000`00000024 00000000`000c08a2 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0890b6c0 fffff880`01215ae8 : 00000001`00000000 00000000`00000000 00000000`00000000 00000fff`ff8a0000 : Ntfs!NtfsPagingFileIo+0x155
fffff880`0890b7c0 fffff880`00c0323f : fffffa80`04cf5fb0 fffffa80`04cf5c10 fffffa80`055abd30 00000000`00000000 : Ntfs! ?? ::FNODOBFM::`string'+0x9e89
fffff880`0890b870 fffff880`00c016df : fffffa80`0494bde0 fffffa80`04cf5c10 fffffa80`0494bd00 fffffa80`04cf5c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0890b900 fffff800`02a6e1f2 : fffffa80`04cf5c30 fffffa80`05685f20 00000000`00000043 fffff880`009ea180 : fltmgr!FltpDispatch+0xcf
fffff880`0890b960 fffff800`02a6e4f5 : 00000000`00000001 00000000`00000001 fffff880`0890ba60 fffff800`02a77f30 : nt!IoPageRead+0x252
fffff880`0890b9f0 fffff800`02a978bb : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff680`00000000 : nt!MiIssueHardFault+0x255
fffff880`0890bac0 fffff800`02a7a82e : 00000000`00000000 00000000`0002e2ea 00000000`00000a01 00000000`7708de60 : nt!MmAccessFault+0x14bb
fffff880`0890bc20 00000000`76fa51df : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`00053010 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fa51df


STACK_COMMAND: kb

FOLLOWUP_IP:
Ntfs!NtfsPagingFileIo+155
fffff880`01215e95 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: Ntfs!NtfsPagingFileIo+155

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f

FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsPagingFileIo+155

BUCKET_ID: X64_0x24_Ntfs!NtfsPagingFileIo+155

Followup: MachineOwner
---------
!