Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Mon Apr  7 00:40:20.328 2008 (GMT+8)
System Uptime: 0 days 2:45:05.904
Loading Kernel Symbols
.......................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 23, {e0100, a7d12144, a7d11e40, aae6e812}



Probably caused by : klif.sys ( klif+11812 )

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

kd> !analyze -v
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

FAT_FILE_SYSTEM (23)
    If you see FatExceptionFilter 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: 000e0100
Arg2: a7d12144
Arg3: a7d11e40
Arg4: aae6e812

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




EXCEPTION_RECORD:  a7d12144 -- (.exr 0xffffffffa7d12144)
ExceptionAddress: aae6e812 (klif+0x00011812)
  ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
  Parameter[0]: 00000001
  Parameter[1]: 00000000
Attempt to write to address 00000000

CONTEXT:  a7d11e40 -- (.cxr 0xffffffffa7d11e40)
eax=00000000 ebx=00000000 ecx=00000000 edx=867f201d esi=855fa008 edi=855fa1bf
eip=aae6e812 esp=a7d1220c ebp=855fa008 iopl=0        nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000            efl=00010246
klif+0x11812:
aae6e812 5d              pop    ebp
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  firefox.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

WRITE_ADDRESS:  00000000

BUGCHECK_STR:  0x23

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 804f054c to aae6e812

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
a7d1223c 804f054c 86734ae8 855fa000 00000000 klif+0x11812
a7d1226c f73d7bb1 a7d124b4 f73dea17 851210e0 nt!IopfCompleteRequest+0xa2
a7d12274 f73dea17 851210e0 855fa008 00000000 Fastfat!FatCompleteRequest_Real+0x49
a7d12284 f73de86d a7d10080 866f9458 00000000 Fastfat!FatCommonCreate+0x12d6
a7d124b4 f73dbce0 851210e0 855fa008 a7d10080 Fastfat!FatCommonCreate+0x1136
a7d124f8 804edfe3 86750618 855fa008 866bc790 Fastfat!FatFsdCreate+0x52
a7d12508 f73fc876 855fa1d8 866f9550 00000000 nt!IopfCallDriver+0x31
a7d12554 804edfe3 86750ac0 00000001 855fa1fc sr!SrCreate+0x150
a7d12564 aae6fd00 855fa018 8670c560 866bc790 nt!IopfCallDriver+0x31
a7d1260c aae724e3 00734ae8 855fa008 804edfe3 klif+0x12d00
a7d12708 805b390a 866fbb68 00000000 85a70e28 klif+0x154e3
a7d12790 805afdeb 00000000 a7d127d0 00000040 nt!ObpLookupObjectName+0x56a
a7d127e4 8056a3b1 00000000 00000000 d1288800 nt!ObOpenObjectByName+0xeb
a7d12860 8056ad28 a7d12a14 00000000 a7d129f8 nt!IopCreateFile+0x407
a7d128bc 8056d3fa a7d12a14 00000000 a7d129f8 nt!IoCreateFile+0x8e
a7d128fc 8053ca28 a7d12a14 00000000 a7d129f8 nt!NtCreateFile+0x30
a7d128fc 804fd735 a7d12a14 00000000 a7d129f8 nt!KiFastCallEntry+0xf8
a7d129a0 aae64f8f a7d12a14 00000000 a7d129f8 nt!ZwCreateFile+0x11
a7d12a0c aae6eaac 00000000 000000e4 852628e7 klif+0x7f8f
00000000 00000000 00000000 00000000 00000000 klif+0x11aac


FOLLOWUP_IP:
klif+11812
aae6e812 5d              pop    ebp

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  klif+11812

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: klif

IMAGE_NAME:  klif.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  47752977

STACK_COMMAND:  .cxr 0xffffffffa7d11e40 ; kb

FAILURE_BUCKET_ID:  0x23_klif+11812

BUCKET_ID:  0x23_klif+11812

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

Hi there,
wat OS you are using?
Make sure that your minidump function is enabled.

Hi there, go to my computer, right click properties, then go to advanced tab, click the Settings button on startup and recovery,
then make sure that the write debugging information is set to small dump 64KB. make sure the path is correctly set for the minidump folder.
C:\Windows\minidump

Once this is done, whenever you encounter BSOD, the dump file will be there.
but bear in mind that previous BSOD are not recorded.
You shall wait for future BSOD and then look into that folder if any.

Please check System Log in Event Viewer and post what is there here.
Thanks

MACHINE_CHECK_EXCEPTION,
refers here
http://en.wikipedia.org/wiki/Machine_Check_Exception
http://forums.nvidia.com/lofiversion/index.php?t17514.html

are you using NVIDIA GC?
Does your latest BSOD in the minidump file already?

Hi there,
at the Startup and Recovery bar there, please untick "automatic restart"

You can go through some reading at the link below.
http://www.windowsbbs.com/windows-xp/61745..._exception.html
http://www.techspot.com/vb/topic48052.html

i suspect it should be hardware failure that causes your BSOD, it might be PSU issue or HDD issue and little posibility Mobo Issue.
Btw,
please do untick the automatic restart, if BSOD persist,
try go to the minidump folder and look around.

Thanks