hi laura
this is a common problem and the blue screen (blue screen of death) indicates a specific problem with your pc or the software installed on it
however your screen information points towards a problem with the n.t.f.s file system,to be more specific "This Stop error indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to drives formatted with the NTFS file system. (A similar Stop message, 0x00000023, exists for the file allocation table [FAT16 or FAT32)] file systems.)
to resolve this problem try this :
Interpret the error message. The stop error is followed by four parameters defined in order of appearance:
Source file and line number.
Optionally contains the address of the exception record.
Optionally contains the address of the context record.
Optionally contains the address where the original exception occurred.
All stop errors due to problems with NTFS or FAT have encoded in their first parameter the source file and the line number within the source file that generated the stop error. The high 16 bits (the first four hexadecimal digits after 0x) identify the source file number, and the lower 16 bits (the last four hexadecimal digits of the parameter) identify the source line in the file where the stop occurred.
Check Event Viewer for error messages from SCSI, FASTFAT (the System Log), or Autochk (the Application Log) that might help determine the device or driver that is causing the error.
Try disabling any virus scanning programs, backup programs, or disk defragmenter tools that constantly monitor your computer, and if possible, run hardware diagnostics tools supplied by your computer manufacturer.
Run chkdsk /r to detect and resolve any file system structural damage.
Depletion of non-paged pool memory can cause this issue. If you create a Services for Macintosh (SFM) volume on a large partition (7 gigabytes or larger) with a large number of files (at least 100,000) while the AppleTalk driver Apf.sys is running, the indexing routine consumes a large amount of non-paged pool memory. If the non-paged pool memory is completely depleted, this error can cause your computer to stop responding (hang). However, if the amount of available non-paged pool memory is very low during the indexing process, another kernel-mode driver requiring non-paged pool memory can also cause this issue. To resolve this issue, increase the amount of installed RAM to increase the quantity of non-paged pool memory available to the kernel, or reduce the number of files on the SFM volume.
however if your pc is using the fat32.fat(file allocation table) file system you need to do the following :
Make sure the drive that contains the corrupted NTFS volume is disconnected, and then start Windows by using Safe mode.
Rename the %SystemRoot%\System32\Drivers\Ntfs.sys file to Ntfs.old, and then shut down the computer (this action prevents the Ntfs.sys driver from loading).
Reconnect the drive that contains the corrupted NTFS volume.
Restart the computer, and then run the following command on the corrupted NTFS volume:
chkdsk driveletter: /f
NOTE: The Chkdsk tool has built-in support for NTFS and does not require the Ntfs.sys driver to make repairs.
After you use the Chkdsk tool to repair the corrupted NTFS volume, rename %SystemRoot%\System32\Drivers\Ntfs.old to Ntfs.sys, and then shut down and restart the computer.
give these a go and if you experience any problems let me know,there may be another solution to this
good luck laura !