WhoCrashed - ReportCode:
System Information (local)
computer name: DRAGAN
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Sempron(tm) Processor 2800+ AMD586, level: 15
1 logical processors, active mask: 1
RAM: 536133632 total
VM: 2147352576, free: 2042052608
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 9/20/2011 12:55:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini092011-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFC1610D7C, 0x0, 0xFFFFFFFF805036AE, 0x0)
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 Tue 9/20/2011 11:33:56 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini092011-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x47EA6)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF8051EEA6)
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 Tue 9/20/2011 9:10:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini092011-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x4E (0x99, 0x15BE4, 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.
On Tue 9/20/2011 8:07:43 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini092011-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x4E (0x8F, 0x7EC2, 0x7CC2, 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 Mon 9/19/2011 5:43:25 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091911-02.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0xA3D2)
Bugcheck code: 0x1A (0x41284, 0xA640001, 0x2198, 0xFFFFFFFFC0883000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software MEMORY_MANAGEMENT
On Mon 9/19/2011 9:52:00 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091911-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x1AA41)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF8051EEA6)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
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 Compatible Windows 2000 Display driver, Version 56.73 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation CUSTOM_ERROR
On Sun 9/18/2011 9:16:25 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091811-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x4E (0x99, 0x0, 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 Sun 9/18/2011 5:09:14 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091811-03.dmp
This was probably caused by the following module: aswtdi.sys (aswTdi+0xC03)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF804F9D36)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswtdi.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! TDI Filter Driver
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: aswtdi.sys (avast! TDI Filter Driver, AVAST Software).
Google query: aswtdi.sys AVAST Software CUSTOM_ERROR
On Sun 9/18/2011 2:53:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091811-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFC0F39CFB, 0x0, 0xFFFFFFFF805036AE, 0x0)
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 Sun 9/18/2011 2:10:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091811-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x1AA41)
Bugcheck code: 0x10000050 (0xFFFFFFFFC1ADF0FB, 0x0, 0xFFFFFFFF805036AE, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
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 Compatible Windows 2000 Display driver, Version 56.73 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation CUSTOM_ERROR
On Sat 9/17/2011 9:21:34 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091711-02.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x1AA41)
Bugcheck code: 0x4E (0x99, 0x71EC, 0x3, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
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.
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 Compatible Windows 2000 Display driver, Version 56.73 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation PFN_LIST_CORRUPT
On Sat 9/17/2011 8:18:15 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091711-01.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0xA34)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF8051EEA6)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswmon2.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Filter Driver for Windows XP
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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: aswmon2.sys AVAST Software CUSTOM_ERROR
On Fri 9/16/2011 7:39:21 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091611-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x4E (0x8F, 0x1FFA6, 0x1FDA6, 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 Fri 9/16/2011 12:16:30 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091611-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x4E (0x99, 0x7B42, 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.
On Thu 9/15/2011 5:03:09 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091511-03.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x1AA41)
Bugcheck code: 0x4E (0x99, 0x0, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
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.
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 Compatible Windows 2000 Display driver, Version 56.73 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation PFN_LIST_CORRUPT
The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\Mini060311-03.dmp
C:\WINDOWS\Minidump\Mini071411-01.dmp
C:\WINDOWS\Minidump\Mini071511-01.dmp
C:\WINDOWS\Minidump\Mini071611-04.dmp
C:\WINDOWS\Minidump\Mini080211-02.dmp
C:\WINDOWS\Minidump\Mini081311-03.dmp
C:\WINDOWS\Minidump\Mini082811-03.dmp
C:\WINDOWS\Minidump\Mini082911-03.dmp
Conclusion
On your computer a total of 248 crash dumps have been found. Only 240 could be analyzed. Only 15 are included in this report. 8 third party drivers have 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:
aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software)
aswtdi.sys (avast! TDI Filter Driver, AVAST Software)
nv4_disp.dll (NVIDIA Compatible Windows 2000 Display driver, Version 56.73 , NVIDIA Corporation)
nv4_mini.sys (NVIDIA Compatible Windows 2000 Miniport Driver, Version 56.73 , NVIDIA Corporation)
aswsp.sys (avast! self protection module, AVAST Software)
aswsnx.sys (avast! Virtualization Driver, AVAST Software)
alcxwdm.sys (Realtek AC'97 Audio Driver (WDM), Realtek Semiconductor Corp.)
nv_agp.sys (NVIDIA nForce AGP Filter, NVIDIA Corporation)
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.
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 actually 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.
System Information (local)
computer name: DRAGAN
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Sempron(tm) Processor 2800+ AMD586, level: 15
1 logical processors, active mask: 1
RAM: 536133632 total
VM: 2147352576, free: 2042052608
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 9/20/2011 12:55:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini092011-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFC1610D7C, 0x0, 0xFFFFFFFF805036AE, 0x0)
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 Tue 9/20/2011 11:33:56 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini092011-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x47EA6)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF8051EEA6)
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 Tue 9/20/2011 9:10:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini092011-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x4E (0x99, 0x15BE4, 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.
On Tue 9/20/2011 8:07:43 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini092011-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x4E (0x8F, 0x7EC2, 0x7CC2, 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 Mon 9/19/2011 5:43:25 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091911-02.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0xA3D2)
Bugcheck code: 0x1A (0x41284, 0xA640001, 0x2198, 0xFFFFFFFFC0883000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software MEMORY_MANAGEMENT
On Mon 9/19/2011 9:52:00 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091911-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x1AA41)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF8051EEA6)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
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 Compatible Windows 2000 Display driver, Version 56.73 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation CUSTOM_ERROR
On Sun 9/18/2011 9:16:25 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091811-04.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x4E (0x99, 0x0, 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 Sun 9/18/2011 5:09:14 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091811-03.dmp
This was probably caused by the following module: aswtdi.sys (aswTdi+0xC03)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF804F9D36)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswtdi.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! TDI Filter Driver
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: aswtdi.sys (avast! TDI Filter Driver, AVAST Software).
Google query: aswtdi.sys AVAST Software CUSTOM_ERROR
On Sun 9/18/2011 2:53:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091811-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x2C6AE)
Bugcheck code: 0x10000050 (0xFFFFFFFFC0F39CFB, 0x0, 0xFFFFFFFF805036AE, 0x0)
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 Sun 9/18/2011 2:10:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091811-01.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x1AA41)
Bugcheck code: 0x10000050 (0xFFFFFFFFC1ADF0FB, 0x0, 0xFFFFFFFF805036AE, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
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 Compatible Windows 2000 Display driver, Version 56.73 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation CUSTOM_ERROR
On Sat 9/17/2011 9:21:34 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091711-02.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x1AA41)
Bugcheck code: 0x4E (0x99, 0x71EC, 0x3, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
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.
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 Compatible Windows 2000 Display driver, Version 56.73 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation PFN_LIST_CORRUPT
On Sat 9/17/2011 8:18:15 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091711-01.dmp
This was probably caused by the following module: aswmon2.sys (aswMon2+0xA34)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x1, 0xFFFFFFFF8051EEA6)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\aswmon2.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Filter Driver for Windows XP
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: aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software).
Google query: aswmon2.sys AVAST Software CUSTOM_ERROR
On Fri 9/16/2011 7:39:21 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091611-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x4E (0x8F, 0x1FFA6, 0x1FDA6, 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 Fri 9/16/2011 12:16:30 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091611-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21CC5)
Bugcheck code: 0x4E (0x99, 0x7B42, 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.
On Thu 9/15/2011 5:03:09 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091511-03.dmp
This was probably caused by the following module: nv4_disp.dll (nv4_disp+0x1AA41)
Bugcheck code: 0x4E (0x99, 0x0, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 56.73
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.
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 Compatible Windows 2000 Display driver, Version 56.73 , NVIDIA Corporation).
Google query: nv4_disp.dll NVIDIA Corporation PFN_LIST_CORRUPT
The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\Mini060311-03.dmp
C:\WINDOWS\Minidump\Mini071411-01.dmp
C:\WINDOWS\Minidump\Mini071511-01.dmp
C:\WINDOWS\Minidump\Mini071611-04.dmp
C:\WINDOWS\Minidump\Mini080211-02.dmp
C:\WINDOWS\Minidump\Mini081311-03.dmp
C:\WINDOWS\Minidump\Mini082811-03.dmp
C:\WINDOWS\Minidump\Mini082911-03.dmp
Conclusion
On your computer a total of 248 crash dumps have been found. Only 240 could be analyzed. Only 15 are included in this report. 8 third party drivers have 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:
aswmon2.sys (avast! File System Filter Driver for Windows XP, AVAST Software)
aswtdi.sys (avast! TDI Filter Driver, AVAST Software)
nv4_disp.dll (NVIDIA Compatible Windows 2000 Display driver, Version 56.73 , NVIDIA Corporation)
nv4_mini.sys (NVIDIA Compatible Windows 2000 Miniport Driver, Version 56.73 , NVIDIA Corporation)
aswsp.sys (avast! self protection module, AVAST Software)
aswsnx.sys (avast! Virtualization Driver, AVAST Software)
alcxwdm.sys (Realtek AC'97 Audio Driver (WDM), Realtek Semiconductor Corp.)
nv_agp.sys (NVIDIA nForce AGP Filter, NVIDIA Corporation)
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.
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 actually 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.
