Why did my computer crash (Details included)?

Question

Why did my computer crash? I was listening to iHeartRadio with Comodo Dragon, then I closed Dragon and it immediately crashed.


==================================================
Dump File : 081713-35677-01.dmp
Crash Time : 8/17/2013 1:17:32 PM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 0x001904fb
Parameter 2 : 0xaefe6950
Parameter 3 : 0xaefe6530
Parameter 4 : 0x82ad5169
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+1aac3
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+debf0
Stack Address 1 : Ntfs.sys+1aac3
Stack Address 2 : Ntfs.sys+191cd
Stack Address 3 : ntkrnlpa.exe+7ee0e
Computer Name :
Full Path : C:\Windows\Minidump\081713-35677-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 146,512
Dump File Time : 8/17/2013 1:18:46 PM
==================================================

What's wrong?

Answer 1

That error says it had trouble reading an important file. There are three main causes for errors like this:



1. a file on your system is corrupt. This happens sometimes. You can try running the System File checker (type "cmd" into the start menu search box, right click on the search result and choose "run as Administrator", then type "sfc /scannow" and hit enter) and Check Disk (from the same command prompt, run "chkdsk C: /F /scan")



2. Your hard drive is messed up. Check Disk hopefully will find out.



3. Your RAM is messed up. Run the "Windows Memory Diagnostic" tool to find out.

Answer 2

Hi,



One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.



Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.



Try in the command box Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.



Arnak

Answer 3

CCleaner is the best tool on the market to clean up your pc. Download here http://j.mp/UrAJA4