Sign in with
Sign up | Sign in
Your question

BSOD various errors

Last response: in Windows 7
Share
October 9, 2012 11:36:53 AM

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.

More about : bsod errors

a b $ Windows 7
October 9, 2012 11:44:52 AM

Looks like it could be a dodgy driver. I would suggest updating drivers directly from manufacturer's websites rather than through a utility.

If not, it could be a HDD error. run chkdsk.
m
0
l
October 9, 2012 11:47:53 AM

Thanks for the quick reply.

I have tried them both. The main issues seems to be the following but I cannot find any info regarding it:

unknown_module_fffff880`010bdae0.sys

Does anyone know what this is?

Regards
m
0
l
Related resources
a b $ Windows 7
October 9, 2012 12:09:30 PM

Looks like RAM to me; I'm seeing four separate BSOD's that typically point to failed RAM (Specifically: IRQL_NOT_LESS_OR_EQUAL, PAGE_FAULT_IN_NONPAGED_AREA, BAD_POOL_HEADER, and SYSTEM_SERVICE_EXCEPTION). Even NTFS_FILE_SYSTEM typically points to RAM...

So yeah, run memtest86+ ASAP.
m
0
l
October 9, 2012 12:20:30 PM

Thanks Gamerk.

I have tried this and it came back OK?

Regards
m
0
l
a b $ Windows 7
October 9, 2012 12:35:16 PM

This is obviously a memory problem, what memory test did you use? Try memtest86 for at least three passes preferably more to test the memory. Even if the memory test passes I still think that it is the memory, try buying a cheap single stick of 2Gig of 1333Mhz memory to test.
m
0
l
October 10, 2012 7:03:43 AM

Hi pjmelect,

I left memtest86 running for 3 and a half hours, 4 phases and no errors were found!!!

Can anyone suggest anything else?

I am writing to you from another pc as I can only enter the other in safe mode.

Please help!

Regards
m
0
l
a b $ Windows 7
October 10, 2012 7:52:04 AM

If safe mode lets you in to that machine and it doesn't blue screen then it's either drivers, or HDD corruption.
m
0
l
October 10, 2012 11:36:35 AM

Does anyone have any ideas what it could be specifically?

Regards
m
0
l
a b $ Windows 7
October 11, 2012 8:17:24 AM

If you can get into safe mode and it runs fine, it's most likely a corrupt driver, followed by a corrupt HDD. Update drivers from manufacturers' websites (not with a driver utility) and run chkdsk /f
m
0
l
a b $ Windows 7
October 11, 2012 12:34:21 PM

Well, I've seen some low-end mobos have trouble handling four sticks of RAM with aggressive timings, so it could be a similar problem. You can try running with only one stick of RAM and see if the problem goes away. (If not, try a different stick, just to be safe).

After that, then I'd start to suspect the motherboard. This clearly looks memory related to me. I'm seeing every BSOD I would expect to see if you had memory related problems.

Also, make sure your not overheating. Obvious, I know, but just asking to make sure.
m
0
l
October 11, 2012 4:35:54 PM

Hi all,

I have been reading around and turned verifier on and removed BSOD i believe (i turned all drivers off except for Microsoft).

Now the system hangs :-(

Any thoughts?

I still can't work out what these drivers are from, especially ntoskrnl.exe which seems to be given lots of problems.

Help!

Regards
m
0
l
a b $ Windows 7
October 15, 2012 1:32:02 PM

danielwilliamsongle said:
Hi all,

I have been reading around and turned verifier on and removed BSOD i believe (i turned all drivers off except for Microsoft).

Now the system hangs :-(

Any thoughts?

I still can't work out what these drivers are from, especially ntoskrnl.exe which seems to be given lots of problems.

Help!

Regards

ntoskrnl = NT OS Kernel. A major component of Windows! if that's corrupt, then you can try SFC or a repair from the CD.
m
0
l
a b $ Windows 7
October 15, 2012 6:00:16 PM

^^ No, thats just where the crash was detected; the damage was done long before then. Thats typical of memory related failures.

Looks like turning off all the drivers messed up the system; turn them back on, and run with a single stick of RAM. I suspect the problems will go away. If so, then probably a mobo related issue.
m
0
l
!