Sign in with
Sign up | Sign in
Your question

Whocrashed report, BSOD

Tags:
  • Blue Screen
  • Crash
  • Windows XP
Last response: in Windows XP
Share
March 27, 2012 9:10:15 PM

System Information (local)
--------------------------------------------------------------------------------

computer name: SAM-EC42640AAF9
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3211767808 total
VM: 2147352576, free: 2059722752



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Tue 3/27/2012 7:34:39 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032712-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x98FE8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8053A923, 0xFFFFFFFFB35429E8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 Sat 3/24/2012 3:16:29 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032412-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7410D)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8054B10D, 0xFFFFFFFFB82979B0, 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 3/20/2012 6:27:39 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini032012-01.dmp
This was probably caused by the following module: avipbb.sys (avipbb+0xAA84)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF853236, 0xFFFFFFFFB33B1B40, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\avipbb.sys
product: AntiVir Desktop
company: Avira GmbH
description: Avira Driver for Security Enhancement
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: avipbb.sys (Avira Driver for Security Enhancement, Avira GmbH).
Google query: avipbb.sys Avira GmbH KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Mon 3/19/2012 12:59:16 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x4E (0x99, 0x55907, 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 Sat 3/17/2012 6:46:19 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031712-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6D545)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFFB8340D70, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_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 trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 3/15/2012 6:56:31 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x4E (0x99, 0x54E5C, 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 Wed 3/14/2012 11:14:23 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031412-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x98FE8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8053A923, 0xFFFFFFFFB36139E8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 3/13/2012 10:30:23 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x4E (0x99, 0x54116, 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 Mon 3/12/2012 10:14:29 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031212-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x62C34)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF862C34, 0xFFFFFFFFB44BBC54, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 Sat 3/10/2012 10:32:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini031012-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74FD2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8054BFD2, 0xFFFFFFFFB3509820, 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 Fri 3/9/2012 8:57:35 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini030912-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74FD2)
Bugcheck code: 0x10000050 (0xFFFFFFFF80000004, 0x1, 0xFFFFFFFF8054BFD2, 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 Wed 3/7/2012 7:54:15 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini030712-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xDFF0)
Bugcheck code: 0x24 (0x1902FE, 0xFFFFFFFFB362336C, 0xFFFFFFFFB3623068, 0xFFFFFFFF8054BFD2)
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 which cannot be identified at this time.


On Tue 3/6/2012 7:26:03 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini030612-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x4E (0x7, 0x74643, 0x748C2, 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 3/5/2012 10:29:11 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini030512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFE30EA198, 0xFFFFFFFFE30EA240, 0xC150608)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 Sat 3/3/2012 8:24:31 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini030312-01.dmp
This was probably caused by the following module: avipbb.sys (avipbb+0xAA84)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8A2BE358, 0xFFFFFFFF8A2BE4CC, 0xFFFFFFFF805D29B4)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\drivers\avipbb.sys
product: AntiVir Desktop
company: Avira GmbH
description: Avira Driver for Security Enhancement
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
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: avipbb.sys (Avira Driver for Security Enhancement, Avira GmbH).
Google query: avipbb.sys Avira GmbH CRITICAL_OBJECT_TERMINATION





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

254 crash dumps have been found and analyzed. Only 15 are included in this report. 5 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:

avipbb.sys (Avira Driver for Security Enhancement, Avira GmbH)

viahduaa.sys (VIA High Definition Audio Function Driver, VIA Technologies, Inc.)

avgntflt.sys (Avira Minifilter Driver, Avira GmbH)

nv4_disp.dll (NVIDIA Windows XP Display driver, Version 275.33 , NVIDIA Corporation)

unknown

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.




When i leave my computer off for more than 2 hours and turn it back on, i have to force shut it down and turn it back on or it will just keep getting BSOD on start

More about : whocrashed report bsod

March 28, 2012 12:07:14 PM

Well, three of the BSOD's are somewhat typical of bad RAM, and its the easiest thing to rule out. Run memtest86/Prime95 to make sure that isn't the problem. Specifically, Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED, Bug Check 0x4E: PFN_LIST_CORRUPT, and Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION lead me to suspect RAM as the primary culprit.
m
0
l
!