System Information (local)
--------------------------------------------------------------------------------
Computer name: RENÉELENOVO
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: 80FG, LENOVO, Lenovo Z70-80
CPU: GenuineIntel Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8500887552 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 03-01-17 18:07:33 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010317-38843-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8033831425C)
Bugcheck code: 0x109 (0xA39FE762A690A9AD, 0xB3B6F3E8F910FD37, 0xFFFFF8033831425C, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 03-01-17 18:07:33 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8033831425C)
Bugcheck code: 0x109 (0xA39FE762A690A9AD, 0xB3B6F3E8F910FD37, 0xFFFFF8033831425C, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 Sun 01-01-17 09:02:42 your computer crashed
crash dump file: C:\WINDOWS\Minidump\010117-33343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1A (0x41793, 0xFFFF9F800002FC10, 0x4, 0x3)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 31-12-16 09:38:37 your computer crashed
crash dump file: C:\WINDOWS\Minidump\123116-33375-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF808CEE9EAEC)
Bugcheck code: 0x109 (0xA3A026E1610E65D5, 0xB3B73367B38F72EF, 0xFFFFF808CEE9EAEC, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: NT-bestandssysteemstuurprogramma
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 Thu 29-12-16 09:25:27 your computer crashed
crash dump file: C:\WINDOWS\Minidump\122916-33828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x53E, 0x1CF2BD10, 0xFFFFE001D60B5000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. Only 5 are included in this report. 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:
avgidsdrivera.sys (AVG IDS Application Activity Monitor Driver., AVG Technologies CZ, s.r.o.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
