BSOD playing FIFA 14, ntoskrnl.exe, usbehci.sys,IRQL_NOT_LESS_OR_EQUAL

Additional Info:

1. Not overclocking
2. 750W PSU

Attached the SF Diagnostic Tool zip. BSOD started since:

1. Replaced motherboard and processor.
2. Fresh installation of Windows 7.
3. Upgraded from Kaspersky Internet Security 2013 to 2014.


Happened 6 out of 7 while playing FIFA 14, used to be okay with previous spec.

What I did so far:

1. Ran memtest+ (1 pass 0 error).
2. Rollback nvidia driver to a more stable version.
3. Ran sfc /scannow with no error.
4. Furmark stress test more than 10 minutes capped at 90°c (10fps)

Code:

 
Whocrashed Analysis:
 
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
On Mon 2/17/2014 6:07:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021814-7722-01.dmp
This was probably caused by the following module: usbehci.sys (usbehci+0x7027) 
Bugcheck code: 0xD1 (0xFFFFFA800D530000, 0x2, 0x1, 0xFFFFF88005686027)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbehci.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: EHCI eUSB Miniport Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 that cannot be identified at this time. 
 
 
 
On Mon 2/17/2014 6:07:00 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbehci.sys (usbehci+0x7027) 
Bugcheck code: 0xD1 (0xFFFFFA800D530000, 0x2, 0x1, 0xFFFFF88005686027)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbehci.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: EHCI eUSB Miniport Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 that cannot be identified at this time. 
 
 
 
On Sun 2/16/2014 6:27:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021714-7004-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0xA (0xFFFFFA900524A948, 0x2, 0x0, 0xFFFFF800034D5CFB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR 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 that cannot be identified at this time. 
 
 
 
On Sun 2/16/2014 2:49:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021614-6973-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x2D906) 
Bugcheck code: 0xD1 (0x200000000, 0x9, 0x8, 0x200000000)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 that cannot be identified at this time. 
 
 
 
On Fri 2/14/2014 12:09:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021414-8080-01.dmp
This was probably caused by the following module: klflt.sys (klflt+0x1D705) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001E1D705, 0xFFFFF8800AC7FC70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\klflt.sys
product: Kaspersky? Anti-Virus R
company: Kaspersky Lab ZAO
description: Filter Core [fre_wlh_x64]
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. 
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: klflt.sys (Filter Core [fre_wlh_x64], Kaspersky Lab ZAO). 
Google query: Kaspersky Lab ZAO SYSTEM_SERVICE_EXCEPTION
 
 
 
On Thu 2/13/2014 6:48:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021414-8751-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F) 
Bugcheck code: 0x119 (0x7000000, 0xFFFFFA80087A0410, 0xFFFFFA800A885010, 0xFFFFFA800B23C300)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
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 that cannot be identified at this time. 
 
 
 
On Tue 2/11/2014 1:27:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021114-8548-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
Bugcheck code: 0xA (0xFFFFFAE0016FEC7A, 0x2, 0x0, 0xFFFFF800032CFD67)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: MicrosoftR WindowsR 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 that cannot be identified at this time. 
 
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
7 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: 
 
klflt.sys (Filter Core [fre_wlh_x64], Kaspersky Lab ZAO)
--------------------------------------------------------------------------------

Hope to hear from you guys soon and thanks for your time!

Cheers,
Bryan

Welcome to the Forum.

Code:

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck A, {fffffa900524a948, 2, 0, fffff800034d5cfb}
Probably caused by : klif.sys ( klif+1c6e3 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 3B, {c0000005, fffff88001e1d705, fffff8800ac7fc70, 0}
Probably caused by : klflt.sys ( klflt+1d705 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Kaspersky is contributing to the BSOD's. Please remove it for testing purpose.

Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

Good and Free system security combination.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-


wdcsam64.sys Wed Apr 16 14:39:08 2008 (4805BB2C)
Western Digital SCSI Arcitecture Model (SAM) WDM driver [br] 2008 driver version has known BSOD issues in Windows
Driver Reference Table - wdcsam64.sys

xusb21.sys Wed Apr 8 20:28:44 2009 (49DCB49C)
XBox USB wireless controller [br] BSOD issues in Win7 with 2009 driver (found in mid-2012)
Driver Reference Table - xusb21.sys

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

AppleCharger.sys Tue Feb 19 10:17:09 2013 (5122FCC5)
GIGABYTE On/Off Charge driver. See here for details - GIGABYTE ON/OFF Charge [br] May cause BSOD on Win7/8 systems - uninstall to test (haven't seen recently (15Jan2013))
Driver Reference Table - AppleCharger.sys

Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

Reduce items at start-up: Startup Programs - Change

Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums

Run Disk Check on your Hard Drive(s): Disk Check

If this does not provide stability. Test RAM.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Summary:

Code:

Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Feb 18 00:07:00.251 2014 (UTC + 6:00)
System Uptime: 0 days 8:11:08.172
BugCheck D1, {fffffa800d530000, 2, 1, fffff88005686027}
Probably caused by : usbehci.sys ( usbehci+7027 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Mon Feb 17 00:27:53.013 2014 (UTC + 6:00)
System Uptime: 0 days 2:34:00.936
BugCheck A, {fffffa900524a948, 2, 0, fffff800034d5cfb}
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : klif.sys ( klif+1c6e3 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sun Feb 16 20:49:40.813 2014 (UTC + 6:00)
System Uptime: 0 days 9:06:40.972
BugCheck D1, {200000000, 9, 8, 200000000}
Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::Isr+3d6 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  fifa14.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Fri Feb 14 18:09:09.993 2014 (UTC + 6:00)
System Uptime: 0 days 2:09:15.772
BugCheck 3B, {c0000005, fffff88001e1d705, fffff8800ac7fc70, 0}
Probably caused by : klflt.sys ( klflt+1d705 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  fraps.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Fri Feb 14 00:48:25.128 2014 (UTC + 6:00)
System Uptime: 0 days 8:06:28.018
BugCheck 119, {7000000, fffffa80087a0410, fffffa800a885010, fffffa800b23c300}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+8c )
BUGCHECK_STR:  0x119
PROCESS_NAME:  fifa14.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Feb 11 19:27:38.597 2014 (UTC + 6:00)
System Uptime: 0 days 0:34:56.487
BugCheck A, {fffffae0016fec7a, 2, 0, fffff800032cfd67}
Probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+77 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  mscorsvw.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

What other steps have you completed?

Removed Kaspersky, replaced with Microsoft Security Essential and MalwareByte.

Reduce items at start-up = Done
Run a System file check (SFC) = Done
Check for heating issues using Speccy = Done

P.S. I ran driver verifier and bsod keeps showing non-stop preventing me from starting windows. Tried safe mode to turn off driver verifier but couldn't find any log about which driver causing the bsod, not even blue screen view or whocrashed, any idea where and how to find it?

Wow! Those bug checks are all over the place. Normally, that would indicate bad memory or an errant driver/malware walking over memory. The system event logs ended too soon to be of much use but here's what I've gleaned from bits and pieces;
Windows activation is failing.
Kaspersky left the Registry damaged.
A BIOS update failed - This can cause major hardware problems.
Nvidia console had some type of error but I don't recall what it was. (I didn't write any of this down.)
Windows failed to load various services numerous times.
The CD/DVD controller failed.
And a few others I forgot.

I think the best course of action at this point is to start from scratch at the motherboard. Clear CMOS memory and try to do a BIOS flash via USB. DO NOT use a Windows based update program. Your system is not stable enough to rely on it. Then do a clean install of Windows. Follow that with your motherboard drivers from the CD that came with the board.

Don't add any applications until your system can be stabilized in the "stock" environment.

carwiz said:

Wow! Those bug checks are all over the place. Normally, that would indicate bad memory or an errant driver/malware walking over memory. The system event logs ended too soon to be of much use but here's what I've gleaned from bits and pieces;
Windows activation is failing.
Kaspersky left the Registry damaged.
A BIOS update failed - This can cause major hardware problems.
Nvidia console had some type of error but I don't recall what it was. (I didn't write any of this down.)
Windows failed to load various services numerous times.
The CD/DVD controller failed.
And a few others I forgot.

I think the best course of action at this point is to start from scratch at the motherboard. Clear CMOS memory and try to do a BIOS flash via USB. DO NOT use a Windows based update program. Your system is not stable enough to rely on it. Then do a clean install of Windows. Follow that with your motherboard drivers from the CD that came with the board.

Don't add any applications until your system can be stabilized in the "stock" environment.

Hey there, thanks for your reply, I've reformatted my hdd and reinstalled everything since post #3, no more kaspersky and nvidia. Windows activated as well. I'll upload the SF Diagnostic result again. Just had another bsod today.

Is there any chance insufficient power causes bsod?

What name and model of display are you using?

Added: Also post an image of your Disk Management screen please.