New
#1
BSOD ntfs.sys (Ntfs+0x5A88)
System Information (local)
--------------------------------------------------------------------------------
computer name: UNKKA-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., M4A87TD/USB3
CPU: AuthenticAMD AMD Phenom(tm) II X6 1055T Processor AMD586, level: 16
6 logical processors, active mask: 63
RAM: 4293058560 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 30.6.2015 4:23:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063015-37128-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009570288, 0xFFFFF8800956FAE0, 0xFFFFF80002ECF4D4)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® -käyttöjärjestelmä
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 30.6.2015 4:23:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009570288, 0xFFFFF8800956FAE0, 0xFFFFF80002ECF4D4)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® -käyttöjärjestelmä
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.