I'm new here, so I hope I didn't do anything wrong here...
These are my sytem spec.
System report.txt 26.74KB 182 downloads
I have constant problems with BSoD...
I suspect that my hard is in bad condition, and probably RAM but i'm not asking about this...
but let me hear what you have to say about crashes...
This are crash reports:
On Wed 11.1.2012 0:25:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011112-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x24672E)
Bugcheck code: 0x1000008E (0xFFFFFFFFE0000001, 0xFFFFFFFFF7BFF925, 0xFFFFFFFFA6E402E4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Windows XP Display driver, Version 285.58
company: NVIDIA Corporation
description: NVIDIA Windows XP Display driver, Version 285.58
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.
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: nv4_disp.dll (NVIDIA Windows XP Display driver, Version 285.58 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Tue 10.1.2012 21:02:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011012-05.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x606BA)
Bugcheck code: 0x4E (0x99, 0x23631, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 10.1.2012 17:21:48 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011012-04.dmp
This was probably caused by the following module: npfs.sys (Npfs+0x5F1C)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFF7C0CF1C, 0xFFFFFFFFB759DAB4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
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 which cannot be identified at this time.
On Tue 10.1.2012 11:03:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011012-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x98910)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8056F910, 0xFFFFFFFFB754DC7C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 10.1.2012 8:44:14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011012-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x606BA)
Bugcheck code: 0x1A (0x41284, 0x4A2A001, 0x1AAB, 0xFFFFFFFFC0503000)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 10.1.2012 7:29:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011012-01.dmp
This was probably caused by the following module: eamon.sys (eamon+0x1B052)
Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFB7AEDF74, 0xFFFFFFFFB7AEDC70, 0xFFFFFFFF80551AE2)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\eamon.sys
product: ESET Smart Security
company: ESET
description: Amon monitor
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: eamon.sys (Amon monitor, ESET).
Google query: eamon.sys ESET NTFS_FILE_SYSTEM
On Mon 9.1.2012 16:56:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini010912-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x40F7B)
Bugcheck code: 0x1000000A (0x28, 0x2, 0x0, 0xFFFFFFFF80517F7B)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 9.1.2012 6:39:26 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini010912-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x606BA)
Bugcheck code: 0x4E (0x99, 0x210A6, 0x3, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer.
Edited by Denis Fajković, 10 January 2012 - 06:55 PM.