NTFS_FILE_SYSTEM

S

Shalini

Hello All,
My filter Driver behaves randomly and sometimes it fails and crashes the
system at the boot time .
This is the Bugcheck report that i am getting from the debugger.
I am virtually tired of this bug.

Any ideas???
Regards
Shal.


*** Fatal System Error: 0x00000024
(0x001901FD,0x81BD8A80,0xC0000102,0x00000000)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
.........................
Loading unloaded module list

Loading User Symbols
****************************************************************************
***
*
*
* Bugcheck Analysis
*
*
*
****************************************************************************
***

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1901fd, 81bd8a80, c0000102, 0}

*************************************************************************
*** ***
*** ***
*** 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. ***
*** ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt!KiBugCheckDebugBreak+19 )

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

nt!RtlpBreakWithStatusInstruction:
8050d064 cc int 3
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: 001901fd
Arg2: 81bd8a80
Arg3: c0000102
Arg4: 00000000

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

*************************************************************************
*** ***
*** ***
*** 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. ***
*** ***
*** ***
*************************************************************************

BUGCHECK_STR: 0x24_C0000102

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 805226a5 to 8050d064

STACK_TEXT:
f8993438 805226a5 00000003 00000000 00000024
nt!RtlpBreakWithStatusInstruction
f8993484 80522dea 00000003 00000100 81bd8a80 nt!KiBugCheckDebugBreak+0x19
f899384c 804fc1bb 00000024 001901fd 81bd8a80 nt!KeBugCheck2+0x43c
f899386c f8418568 00000024 001901fd 81bd8a80 nt!KeBugCheckEx+0x19
f8993890 f8457464 81bd8a80 c0000102 e12af560 Ntfs!NtfsRaiseStatus+0x57
f89938f8 f8429071 81bd8a80 81bd82c8 e12af560 Ntfs!NtfsReadMftRecord+0x1a3
f8993930 f84290f8 81bd8a80 81bd82c8 e12af560 Ntfs!NtfsReadFileRecord+0x78
f8993968 f8434cb0 81bd8a80 e12af558 e12af560
Ntfs!NtfsLookupInFileRecord+0x35
f8993a18 f845d8d2 81bd8a80 81b925b0 00000000
Ntfs!NtfsUpdateScbFromAttribute+0x65
f8993a48 f845b5d6 81bd8a80 81bd82f8 81bd82c8 Ntfs!NtfsOpenSystemFile+0x86
f8993cb8 f844a3c8 81bd8a80 81bd8de8 81bd8a80 Ntfs!NtfsMountVolume+0x13ed
f8993cc8 f8417fc7 81bd8a80 81bd8de8 81bd8b80
Ntfs!NtfsCommonFileSystemControl+0x37
f8993d74 804ebd08 81bd8a80 00000000 81bcb640 Ntfs!NtfsFspDispatch+0x1a0
f8993dac 80559026 81bd8a80 00000000 00000000 nt!ExpWorkerThread+0xfe
f8993ddc 8050f513 804ebc35 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
nt!KiBugCheckDebugBreak+19
805226a5 eb59 jmp nt!KiBugCheckDebugBreak+0x74 (80522700)

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiBugCheckDebugBreak+19

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7de38f

STACK_COMMAND: kb

BUCKET_ID: 0x24_C0000102_nt!KiBugCheckDebugBreak+19

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

Will Denny

Hi

Try the following link to MVP Jim Eshelman's web page:

"0x00000024: NTFS_FILE_SYSTEM"
http://aumha.org/win5/kbestop.php#0x24

--

Will Denny
MS-MVP Windows - Shell/User


| Hello All,
| My filter Driver behaves randomly and sometimes it fails and crashes the
| system at the boot time .
| This is the Bugcheck report that i am getting from the debugger.
| I am virtually tired of this bug.
|
| Any ideas???
| Regards
| Shal.
|
|
| *** Fatal System Error: 0x00000024
| (0x001901FD,0x81BD8A80,0xC0000102,0x00000000)
|
| Break instruction exception - code 80000003 (first chance)
|
| A fatal system error has occurred.
| Debugger entered on first try; Bugcheck callbacks have not been invoked.
|
| A fatal system error has occurred.
|
| Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
| Loading Kernel Symbols
| ........................
| Loading unloaded module list
|
| Loading User Symbols
|
****************************************************************************
| ***
| *
| *
| * Bugcheck Analysis
| *
| *
| *
|
****************************************************************************
| ***
|
| Use !analyze -v to get detailed debugging information.
|
| BugCheck 24, {1901fd, 81bd8a80, c0000102, 0}
|
| *************************************************************************
| *** ***
| *** ***
| *** 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. ***
| *** ***
| *** ***
| *************************************************************************
| Probably caused by : ntoskrnl.exe ( nt!KiBugCheckDebugBreak+19 )
|
| Followup: MachineOwner
| ---------
|
| nt!RtlpBreakWithStatusInstruction:
| 8050d064 cc int 3
| 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: 001901fd
| Arg2: 81bd8a80
| Arg3: c0000102
| Arg4: 00000000
|
| Debugging Details:
| ------------------
|
| *************************************************************************
| *** ***
| *** ***
| *** 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. ***
| *** ***
| *** ***
| *************************************************************************
|
| BUGCHECK_STR: 0x24_C0000102
|
| DEFAULT_BUCKET_ID: DRIVER_FAULT
|
| LAST_CONTROL_TRANSFER: from 805226a5 to 8050d064
|
| STACK_TEXT:
| f8993438 805226a5 00000003 00000000 00000024
| nt!RtlpBreakWithStatusInstruction
| f8993484 80522dea 00000003 00000100 81bd8a80 nt!KiBugCheckDebugBreak+0x19
| f899384c 804fc1bb 00000024 001901fd 81bd8a80 nt!KeBugCheck2+0x43c
| f899386c f8418568 00000024 001901fd 81bd8a80 nt!KeBugCheckEx+0x19
| f8993890 f8457464 81bd8a80 c0000102 e12af560 Ntfs!NtfsRaiseStatus+0x57
| f89938f8 f8429071 81bd8a80 81bd82c8 e12af560 Ntfs!NtfsReadMftRecord+0x1a3
| f8993930 f84290f8 81bd8a80 81bd82c8 e12af560 Ntfs!NtfsReadFileRecord+0x78
| f8993968 f8434cb0 81bd8a80 e12af558 e12af560
| Ntfs!NtfsLookupInFileRecord+0x35
| f8993a18 f845d8d2 81bd8a80 81b925b0 00000000
| Ntfs!NtfsUpdateScbFromAttribute+0x65
| f8993a48 f845b5d6 81bd8a80 81bd82f8 81bd82c8 Ntfs!NtfsOpenSystemFile+0x86
| f8993cb8 f844a3c8 81bd8a80 81bd8de8 81bd8a80 Ntfs!NtfsMountVolume+0x13ed
| f8993cc8 f8417fc7 81bd8a80 81bd8de8 81bd8b80
| Ntfs!NtfsCommonFileSystemControl+0x37
| f8993d74 804ebd08 81bd8a80 00000000 81bcb640 Ntfs!NtfsFspDispatch+0x1a0
| f8993dac 80559026 81bd8a80 00000000 00000000 nt!ExpWorkerThread+0xfe
| f8993ddc 8050f513 804ebc35 00000000 00000000
nt!PspSystemThreadStartup+0x34
| 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
|
|
| FOLLOWUP_IP:
| nt!KiBugCheckDebugBreak+19
| 805226a5 eb59 jmp nt!KiBugCheckDebugBreak+0x74 (80522700)
|
| FOLLOWUP_NAME: MachineOwner
|
| SYMBOL_NAME: nt!KiBugCheckDebugBreak+19
|
| MODULE_NAME: nt
|
| IMAGE_NAME: ntoskrnl.exe
|
| DEBUG_FLR_IMAGE_TIMESTAMP: 3b7de38f
|
| STACK_COMMAND: kb
|
| BUCKET_ID: 0x24_C0000102_nt!KiBugCheckDebugBreak+19
|
| Followup: MachineOwner
| ---------
|
|
 
F

Fred Gressler

Joined
Jun 3, 2008
Messages
1
Reaction score
0
hard drive trouble?

I got this error very recently on my computer at home, and discovered that my hard drive was failing.

I had a lot of very crucial data that was not backed up (stupid, I know), so I tried to find a cheap data recovery option.

I stumbled upon DriveFish (http://www.drivefish.com) and was shocked at how cheap they can get the job done. Flat rate. $200. Crazy.

Best part is they only charge you a small handling fee if they can't recover your data. They were able to get all of my data back, though, so I happily paid the full fee.

Hope this helps!

-Fred
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

USB driver not working on windows 7 3
BSOD BAD_POOL_HEADER 5
DRIVER_POWER_STATE_FAILURE BugCheck. 0
newbee DRIVER_IRQL_NOT_LESS_OR_EQUAL problem 6
Error Obtained While Loading Driver-Help 3
PAGE_FAULT_IN_NONPAGED_AREA 4
BSOD - With mrxsmb.sys 2
Windows TCPIP.SYS problem BLUESCREEN and reboot 8

Top