Sorry, I'm a total noob at this. Any help in deciphering and possible fixes to the "who crashed" results I have would greatly be appreciated.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 4/22/2014 8:59:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042214-20046-01.dmp
uptime: 00:01:30
This was probably caused by the following module: ntfs.sys (Ntfs! ?? ::FNODOBFM::`string'+0x2899)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880069E5918, 0xFFFFF880069E5170, 0xFFFFF880012E3317)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 4/22/2014 8:59:36 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:01:30
This was probably caused by the following module: tdrpman.sys (tdrpman+0xB4490)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880069E5918, 0xFFFFF880069E5170, 0xFFFFF880012E3317)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\tdrpman.sys
product: Acronis Try&Decide
company: Acronis
description: Acronis Try&Decide Volume Filter Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: tdrpman.sys (Acronis Try&Decide Volume Filter Driver, Acronis).
Google query: Acronis NTFS_FILE_SYSTEM
On Mon 4/21/2014 5:59:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042014-23415-01.dmp
uptime: 00:07:01
This was probably caused by the following module: fltmgr.sys (fltmgr!FltpProcessOperationStatusCallbacks+0x2D)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800113164D, 0x0, 0x200000000000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 4/21/2014 2:56:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042014-18595-01.dmp
uptime: 00:02:02
This was probably caused by the following module: Unknown (0xFFFFF80002E7EC00)
Bugcheck code: 0x50 (0xFFFFF69000051170, 0x0, 0xFFFFF80002F86147, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: PAGE_FAULT_IN_NONPAGED_AREA
On Sun 4/20/2014 9:58:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042014-18860-01.dmp
uptime: 00:06:29
This was probably caused by the following module: win32k.sys (0xFFFFF96000158F63)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000158F63, 0xFFFFF88008899990, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
tdrpman.sys (Acronis Try&Decide Volume Filter Driver, Acronis)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 4/22/2014 8:59:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042214-20046-01.dmp
uptime: 00:01:30
This was probably caused by the following module: ntfs.sys (Ntfs! ?? ::FNODOBFM::`string'+0x2899)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880069E5918, 0xFFFFF880069E5170, 0xFFFFF880012E3317)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 4/22/2014 8:59:36 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:01:30
This was probably caused by the following module: tdrpman.sys (tdrpman+0xB4490)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880069E5918, 0xFFFFF880069E5170, 0xFFFFF880012E3317)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\tdrpman.sys
product: Acronis Try&Decide
company: Acronis
description: Acronis Try&Decide Volume Filter Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: tdrpman.sys (Acronis Try&Decide Volume Filter Driver, Acronis).
Google query: Acronis NTFS_FILE_SYSTEM
On Mon 4/21/2014 5:59:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042014-23415-01.dmp
uptime: 00:07:01
This was probably caused by the following module: fltmgr.sys (fltmgr!FltpProcessOperationStatusCallbacks+0x2D)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800113164D, 0x0, 0x200000000000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 4/21/2014 2:56:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042014-18595-01.dmp
uptime: 00:02:02
This was probably caused by the following module: Unknown (0xFFFFF80002E7EC00)
Bugcheck code: 0x50 (0xFFFFF69000051170, 0x0, 0xFFFFF80002F86147, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: PAGE_FAULT_IN_NONPAGED_AREA
On Sun 4/20/2014 9:58:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042014-18860-01.dmp
uptime: 00:06:29
This was probably caused by the following module: win32k.sys (0xFFFFF96000158F63)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000158F63, 0xFFFFF88008899990, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
tdrpman.sys (Acronis Try&Decide Volume Filter Driver, Acronis)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Facebook
Twitter
Instagram