windows crash blue screen

One BSOD is usually not enough for a definitive answer. Yours showed
STOP 0x00000024: NTFS_FILE_SYSTEM Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure



Back up your hard drive just in case. Take a hard drive test.

Test Hard Drive www.carrona.org/hddiag.html or this test http://www.tacktech.com/display.cfm?ttid=287
http://pcsupport.about.com/od/toolso.../tophddiag.htm

Uninstall your anti virus and replace with MSE, Microsoft security Essentials

Check to be sure that you have sufficient memory available.

Code:

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_050111-21450-01.zip\050111-21450-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03250000 PsLoadedModuleList = 0xfffff800`0348de50
Debug session time: Sun May  1 13:28:07.450 2011 (GMT-4)
System Uptime: 0 days 6:35:50.058
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff8800a18dae8, fffff8800a18d350, fffff800032a54c8}
Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteFile+57b )
Followup: MachineOwner
---------
0: 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: 00000000001904fb
Arg2: fffff8800a18dae8
Arg3: fffff8800a18d350
Arg4: fffff800032a54c8
Debugging Details:
------------------
 
EXCEPTION_RECORD:  fffff8800a18dae8 -- (.exr 0xfffff8800a18dae8)
ExceptionAddress: fffff800032a54c8 (nt!MmPurgeSection+0x0000000000000558)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT:  fffff8800a18d350 -- (.cxr 0xfffff8800a18d350)
rax=0000000000000002 rbx=fffffa80038c9f00 rcx=fffffa80005cecb1
rdx=fffffa8001d29cb1 rsi=0000000000000000 rdi=fffff8000343ae80
rip=fffff800032a54c8 rsp=fffff8800a18dd20 rbp=0000000000000000
 r8=fffffa8001d29cb0  r9=fffffa8000000008 r10=fffffa800c8f2668
r11=fffff8800a18dcf0 r12=0000000000000002 r13=0000000000000000
r14=0000000000000000 r15=fffff8a003ba9bc0
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!MmPurgeSection+0x558:
fffff800`032a54c8 f0410fba2a1f    lock bts dword ptr [r10],1Fh ds:002b:fffffa80`0c8f2668=????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x24
PROCESS_NAME:  SC2.exe
CURRENT_IRQL:  2
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
LAST_CONTROL_TRANSFER:  from fffff800032a5b82 to fffff800032a54c8
STACK_TEXT:  
fffff880`0a18dd20 fffff800`032a5b82 : 00000000`00000000 fffffa80`0c54ee00 00000000`00000000 00000000`00000000 : nt!MmPurgeSection+0x558
fffff880`0a18de10 fffff880`0169edef : fffffa80`0b0ea0c8 00000000`00000000 fffff8a0`00000000 00000000`00000000 : nt!CcPurgeCacheSection+0x172
fffff880`0a18de80 fffff880`016b7cea : fffff880`0a18e6f0 fffff8a0`03a6d5e0 fffff8a0`1078cbc0 fffff880`0a18e17c : Ntfs!NtfsDeleteFile+0x57b
fffff880`0a18e100 fffff880`01628829 : 00000000`00000000 fffff880`0154f78c fffff880`0a18e650 fffff880`0a17d000 : Ntfs!NtfsCommonCleanup+0x15da
fffff880`0a18e510 fffff800`032cfe5a : fffff880`0a18e650 00000000`00000002 fffffa80`06f62880 fffff800`033f52dd : Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`0a18e540 fffff880`016283e2 : fffff880`01628810 fffff880`0a18e650 fffff880`0a18e900 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`0a18e620 fffff880`016c7324 : fffff880`0a18e6f0 fffff880`0a18e6f0 fffff880`0a18e6f0 00000000`00000000 : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`0a18e690 fffff880`0150523f : fffff880`0a18e6f0 fffffa80`0d540010 fffffa80`0d540368 fffffa80`07318cd0 : Ntfs!NtfsFsdCleanup+0x144
fffff880`0a18e900 fffff880`015036df : fffffa80`097d88e0 00000000`00000000 fffffa80`078c2c00 fffffa80`0d540010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0a18e990 fffff800`035d484f : fffffa80`0d540010 fffffa80`0ae76060 00000000`00000000 fffffa80`0b574520 : fltmgr!FltpDispatch+0xcf
fffff880`0a18e9f0 fffff800`035ba724 : 00000000`00000000 fffffa80`0ae76060 fffffa80`0d540100 fffffa80`0b574520 : nt!IopCloseFile+0x11f
fffff880`0a18ea80 fffff800`035d4341 : fffffa80`0ae76060 fffffa80`00000001 fffff8a0`0328a3d0 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`0a18eb00 fffff800`035d4254 : 00000000`0000119c fffffa80`0ae76060 fffff8a0`0328a3d0 00000000`0000119c : nt!ObpCloseHandleTableEntry+0xb1
fffff880`0a18eb90 fffff800`032bf993 : fffffa80`06c17060 fffff880`0a18ec60 00000000`fffdb000 00000000`fffdb000 : nt!ObpCloseHandle+0x94
fffff880`0a18ebe0 00000000`77a7f7aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a7f7aa
 
FOLLOWUP_IP: 
Ntfs!NtfsDeleteFile+57b
fffff880`0169edef 443af3          cmp     r14b,bl
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  Ntfs!NtfsDeleteFile+57b
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME:  Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4d79996d
STACK_COMMAND:  .cxr 0xfffff8800a18d350 ; kb
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteFile+57b
BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteFile+57b
Followup: MachineOwner
---------

The reports are usually not definitive, they are subjective. One rarely gives the answer. Anything that is listed in my report can be the problem. The most likely is the Hard Drive, but thats a subjective guess.