SYSTEM SERVICE EXCEPTION & IRQL_NOT_LESS_OR_EQUAL Blue screens

Toggle sidebar Toggle sidebar
O

Overrated132

Commendable
Apr 14, 2016
11
0
1,510
Hello,
So I've been having alot of BSOD's with the message being: SYSTEM SERVICE EXCEPTION& IRQL_NOT_LESS_OR_EQUAL BSOD. First it was only while playing games, I had tried loads of things trying to fix it now that I've formatted both my SSD and HDD and reinstalled windows the BSOD's occur sometimes after 5 mins after I've logged into windows I have no idea what to do anymore.

System specs:
CPU: AMD FX-8350
GPU: GTX 760
MOBO: ASROCK 990FX EXTREME 3
RAM: 2X4GB CRUCIAL BALLISTIX
SSD: CRUCIAL M500
HDD: WD 1TB BLUE
 
Solution
Ironsounds
Hello... 5) I suggest disabling your MB audio chip, Blue tooth, Wireless, and LAN chip (save&exit)... this is hardware and Windows will try and communicate to it and Load a driver for it... This can be turned back on later during our tests here. All other MB settings at DEFAULT... ( clear MB CMOS/Bio's )
6) I suggest using MB/CPU GPU here too... if available (love intel CPU, for this test)... too eliminate an external GPU and MB compatibility problem.
Sort by date Sort by votes
Hello... Typically a BSOD/Freeze/Boot problem will report a file that caused the problem... look for that.
1) Go to Computer-manage-Event viewer-Windows logs and read/report/post back the Logged error screens.
2) Are you overclocking?
3) MB performance setting?
4) Did you do Driver/hardware updates before the problem? try a "restore point" before the problem started.

Typically you can Physically remove as many hardware devices AND other MB devices, from the BIO's MB (save&exit)... and still get a Windows OS boot. Then you can add a device at a time till you BSOD again... then you know what the problem device/driver.
 
Upvote 0 Downvote


Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 14/04/2016 16:10:57 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041416-8640-01.dmp
This was probably caused by the following module: wdfilter.sys (WdFilter!MpPostCreate+0xE9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802D7ED78B2, 0xFFFFD000223F56E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\wdfilter.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft antimalware file system filter 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 that cannot be identified at this time.



On Thu 14/04/2016 16:10:57 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: wdfilter.sys (WdFilter!MpPostCreate+0xE9)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802D7ED78B2, 0xFFFFD000223F56E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\wdfilter.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft antimalware file system filter 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 that cannot be identified at this time.



On Thu 14/04/2016 14:36:29 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041416-9156-01.dmp
This was probably caused by the following module: afd.sys (afd!AfdFreeEndpointResources+0xB7)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8035FCD38B2, 0xFFFFD000220536E8, 0xFFFFD00022052F00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: Ondersteunend functiestuurprogramma van WinSock
Bug check description: This indicates that a system thread 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 that cannot be identified at this time.



On Thu 14/04/2016 14:03:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041416-5000-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KxWaitForLockOwnerShip+0x14)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803076E53A4, 0xFFFFD001C9BFE6C8, 0xFFFFD001C9BFDEE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread 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 that cannot be identified at this time.



On Thu 14/04/2016 13:51:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041416-6171-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase!EnterCrit+0x4D)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8025F4C88B2, 0xFFFFD00020A59F80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: Base Win32k Kernel-stuurprogramma
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 that cannot be identified at this time.





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

5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


 
Upvote 0 Downvote

The only info I can give you is that I am not overclocking
and I just formatted all my drives and reinstalled windows and It has become worse
 
Upvote 0 Downvote


I have an 8.1 disc but I updated to w10
 
Upvote 0 Downvote


On win 8.1 I also had some frequent BSOD's but someone recommended updating my bios and that helped. This fix unfortunately doesn't apply to w10 :/
 
Upvote 0 Downvote
Hello... I run WIN 7 with my hardware because it works for my needs... "don't try and fix it if it ain't broken..." B )

So your telling me you had no BSOD with WIn8.1 (update Bio's) and now you do with WIN10 fresh install? am I correct here with your words and my analysis?
4) As a 'Simple test" do a clean install of your WIN 8.1 media and re-test this situation please. (15-30 min)... if you BSOD with both of these OS's, you have a Driver/hardware problem that needs to be isolated by removing Hardware, so Windows does not try to communicate and load drivers for it... basically some Ram, CPU, Video, drive... all else disabled or not plugged in... Simple?
 
Upvote 0 Downvote

Yes you are
 
Upvote 0 Downvote

going to try that now

 
Upvote 0 Downvote
Hello... 5) I suggest disabling your MB audio chip, Blue tooth, Wireless, and LAN chip (save&exit)... this is hardware and Windows will try and communicate to it and Load a driver for it... This can be turned back on later during our tests here. All other MB settings at DEFAULT... ( clear MB CMOS/Bio's )
6) I suggest using MB/CPU GPU here too... if available (love intel CPU, for this test)... too eliminate an external GPU and MB compatibility problem.
 
Upvote 0 Downvote
Solution


I updated my bios again and no bsod for the last 15 min (new record xDD)
I'll let you know if it bsod s again
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom