Several BSODs on Windows 7

[deepakmenonk]

I am getting several BSOD's, and it is very random. I dont know what i have to do. Please help me. I have got system_services_exception, page fault in non-paged area, klif.sys, win32k.sys, ntfs,sys BSOD's. Please help me and tell me what i should be doing. Thanks in advance

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 25-Feb-11 11:38:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-17440-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1D2384)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000212384, 0xFFFFF88008DB9C00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Fri 25-Feb-11 10:55:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-18610-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880088454E8, 0xFFFFF88008844D40, 0xFFFFF8800153560D)
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 Fri 25-Feb-11 10:23:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-16426-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003287317, 0xFFFFF88007855550, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 25-Feb-11 1:58:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022511-18564-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000360CFD0, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 08-Feb-11 2:45:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020811-16302-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800AB0C0B8, 0xFFFFF8800AB0B910, 0xFFFFF8800154860D)
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 08-Feb-11 2:45:40 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: klif.sys (klif+0x2F54D)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800AB0C0B8, 0xFFFFF8800AB0B910, 0xFFFFF8800154860D)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\klif.sys
product: Kaspersky™ Anti-Virus ®
company: Kaspersky Lab
description: Klif Mini-Filter [fre_wlh_AMD64]
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: klif.sys (Klif Mini-Filter [fre_wlh_AMD64], Kaspersky Lab).
Google query: klif.sys Kaspersky Lab NTFS_FILE_SYSTEM




On Mon 07-Feb-11 1:17:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020711-14804-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF900C3A6E000, 0x0, 0xFFFFF800032BFF83, 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 Sat 05-Feb-11 9:12:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020611-16660-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xB8A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880014458A0, 0xFFFFF880076FFB60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Sat 05-Feb-11 8:44:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020611-15225-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880085FBD68, 0xFFFFF880085FB5C0, 0xFFFFF8800127D44F)
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 Sat 05-Feb-11 12:04:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020511-19765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003755ED6, 0xFFFFF8800B838C00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 04-Feb-11 9:22:08 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020411-18813-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008F4F8A8, 0xFFFFF88008F4F100, 0xFFFFF8800172460D)
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 Sun 30-Jan-11 5:48:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\013011-15397-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800035BE76A, 0xFFFFF8800BB2A100, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 29-Jan-11 8:46:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\013011-16504-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0xFFFFF6FC50078000, 0x0, 0x0, 0xFFFFF80003270B16)
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 Sat 29-Jan-11 3:13:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012911-17581-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000327F00C, 0xFFFFF8800A022010, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 27-Jan-11 4:30:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012711-16224-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4A92)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000E4A92, 0xFFFFF8800AA38130, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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.



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

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

klif.sys (Klif Mini-Filter [fre_wlh_AMD64], Kaspersky Lab)

 

[Mark56]

Although only mentioned in one dump file I would remove Kaspersky and replace it with Microsoft Security Essentials, this if a free a very good quality anti virus.

Use this tool first

http://www.crystalidea.com/kaspersky-uninstall-tool

Then install from MSE from here making sure you choose the correct version for your OS.

http://www.microsoft.com/security_essentials/support.aspx?mkt=en-us

I would also run the manufacturers diagnostics on your hard drive.

Identify the make of your hard drive and then use one of the links below to get the manufacturers diagnostic for ISO CD. Burn the image file to a CD, boot the PC with the disc in the drive and run the diagnostics. You first need to set the CD drive to 1st in the boot order in the Bios setup.

If you do not have an image burner use this free software to make the CD.

http://www.isoimageburner.com/



ExcelStor: http://www.excelstor.com/eng/support.php?sub_id=3

Hitachi/IBM: http://www.hitachigst.com/support/downloads/

Samsung: http://www.samsung.com/global/business/hdd/support/utilities/Support_HUTIL.html

Toshiba: http://sdd.toshiba.com/main.aspx?Path=ServicesSupport/FujitsuDrivesUSandCanada/SoftwareUtilities

Seagate, Maxtor & Quantum:http://www.seagate.com/www/en-us/support/downloads

Western Digital:http://support.wdc.com/product/download.asp?lang=en

 

[deepakmenonk]

Checked harddisk.

I dont know if i have to remove kaspersky for that problem.. If its the only way i could do that. And in the internet there seems to be problems related to klif.sys of kaspersky, but i couldnt understand them. My hard disk is seagate and i did a manufacture diagnostic check, but it seems to be fine. All the BSOD's tells that this not a hardware problem, but due to some driver mismatch or possible malware attack. Can you please suggest me a way to handle it. Thanks a lot.

 

[Mark56]

Can you please suggest me a way to handle it. Thanks a lot.

I just have!

Kaspersky was quoted in a crash dump so I have given the correct advise to remove it and to use Microsofts own AV which should not cause any further problems. You cannot possibly know if this is going to cure these BSOD's unless you try it.

The driver klif.sys was the only one in any of the crash dumps that was not a windows driver and that makes it a prime suspect.

Please remove Kaspersky, install and scan with MSE and see what happens. I cannot give further guidance until you have replaced Kaspersky.

Ntfs.sys was also in the dumps, this often indicates a hard drive problem hence my advise to run the diagnostics.

Once you have removed Kaspersky you will need to waite and see if any further BSOD's occur before moving on to more tests.

Do you have any other third party software for anti virus, spyware, etc, or firewall?

For a quick check, click start and type dxdiag into the search box, a box will open above with a blue circle with a yellow cross in it, click on it and the GUI will open. Wait for the green bar to complete and then flip through the pages and check on each one that no problems are reported in the box on the bottom of each page.