- Oct 9, 2012
- 7
- 0
- 10,510
Hello to you all,
I have been having various issues with BSOD. I have purchased driver scanner and updated all drivers (I was having issues before updating drivers though=.
My system randomly freezes, occassionaly online and occassionly just on the desktop. Sometimes it is BSOD or others, it freezes and blurs the screen.
I attached below a copy of the WhosCrashed details.
Memtest is OK so I don't think it is a ram issue.
Please see if you can help!!!
Any queries please let me know.
Daniel
System Information (local)
computer name: PC-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4293058560 total
VM: 2147352576, free: 1971703808
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 09/10/2012 11:07:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100912-46566-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009DF47B8, 0xFFFFF88009DF4010, 0xFFFFF80003078554)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador del sistema de archivos NTFS
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 Mon 08/10/2012 12:41:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100812-37362-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00C2090CF, 0xFFFFF8A00C2090FF, 0x5030D00)
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 Mon 08/10/2012 11:44:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100812-42354-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF8800647B0CB, 0x1, 0xFFFFF8800747B0B5, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Mon 08/10/2012 6:52:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100812-41418-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF80000000E10, 0x0, 0xFFFFF800030CA0FA, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Mon 01/10/2012 7:40:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100812-41808-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800030B85DF)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sun 30/09/2012 17:56:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093012-36707-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x91691)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000A1691, 0xFFFFF880054BDCE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador Win32 multiusuario
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sun 30/09/2012 17:43:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093012-33821-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF87F8F4042F0, 0x1, 0xFFFFF880074342D0, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Sun 30/09/2012 17:12:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093012-45021-01.dmp
This was probably caused by the following module: unknown_module_fffff880`010bdae0.sys (Unloaded_Unknown_Module_fffff880`010bdae0+0x5E73D12)
Bugcheck code: 0x135 (0xFFFFFFFFC0000005, 0xFFFFF8800B521FA0, 0xCFFFFF880018A22, 0xFFFFF8A0001ED851)
Error: REGISTRY_FILTER_DRIVER_EXCEPTION
Bug check description: This bugcheck is caused by an unhandled exception in a registry filtering 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: unknown_module_fffff880`010bdae0.sys .
Google query: unknown_module_fffff880`010bdae0.sys REGISTRY_FILTER_DRIVER_EXCEPTION
Conclusion
8 crash dumps have been found and analyzed. 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:
unknown_module_fffff880`010bdae0.sys
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.
I have been having various issues with BSOD. I have purchased driver scanner and updated all drivers (I was having issues before updating drivers though=.
My system randomly freezes, occassionaly online and occassionly just on the desktop. Sometimes it is BSOD or others, it freezes and blurs the screen.
I attached below a copy of the WhosCrashed details.
Memtest is OK so I don't think it is a ram issue.
Please see if you can help!!!
Any queries please let me know.
Daniel
System Information (local)
computer name: PC-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4293058560 total
VM: 2147352576, free: 1971703808
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 09/10/2012 11:07:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100912-46566-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009DF47B8, 0xFFFFF88009DF4010, 0xFFFFF80003078554)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador del sistema de archivos NTFS
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 Mon 08/10/2012 12:41:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100812-37362-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00C2090CF, 0xFFFFF8A00C2090FF, 0x5030D00)
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 Mon 08/10/2012 11:44:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100812-42354-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF8800647B0CB, 0x1, 0xFFFFF8800747B0B5, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Mon 08/10/2012 6:52:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100812-41418-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF80000000E10, 0x0, 0xFFFFF800030CA0FA, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Mon 01/10/2012 7:40:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100812-41808-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800030B85DF)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sun 30/09/2012 17:56:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093012-36707-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x91691)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000A1691, 0xFFFFF880054BDCE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador Win32 multiusuario
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sun 30/09/2012 17:43:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093012-33821-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF87F8F4042F0, 0x1, 0xFFFFF880074342D0, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Sun 30/09/2012 17:12:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093012-45021-01.dmp
This was probably caused by the following module: unknown_module_fffff880`010bdae0.sys (Unloaded_Unknown_Module_fffff880`010bdae0+0x5E73D12)
Bugcheck code: 0x135 (0xFFFFFFFFC0000005, 0xFFFFF8800B521FA0, 0xCFFFFF880018A22, 0xFFFFF8A0001ED851)
Error: REGISTRY_FILTER_DRIVER_EXCEPTION
Bug check description: This bugcheck is caused by an unhandled exception in a registry filtering 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: unknown_module_fffff880`010bdae0.sys .
Google query: unknown_module_fffff880`010bdae0.sys REGISTRY_FILTER_DRIVER_EXCEPTION
Conclusion
8 crash dumps have been found and analyzed. 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:
unknown_module_fffff880`010bdae0.sys
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.
Facebook
Twitter
Instagram