Question BSODs that started happening all the sudden. Tried everything I could think of.

Toggle sidebar Toggle sidebar
T

TheLazP

Apr 7, 2020
14
1
15
Hello,
So, I suddenly starting having BSODs, at first it seemed to be accusing my Antivirus(Which was Kaspersky), my Ethernet/Network(Killer E2200 Gigabit Ethernet Controller) and my USB Audio, I would have them while browsing(+watching videos) and gaming which happened once. Apologies since I do not have the dumps of those occurrences.

After those happened I tried the following:
  • Updated my GPU Driver.
  • Reinstalled my Headset drivers and made it work with the Razer Software.
  • Uninstalled Kaspersky and installed another antivirus (Bitdefender Free Edition).
  • Did both DISM.exe /Online /Cleanup-image /Restorehealth and sfc /scannow on CMD.
  • Checked temperatures and everything is very good in temps even while gaming.
  • Updated my Network Adapter(Killer E2200 Gigabit Ethernet Controller) which was using a 2016 Driver, I think, and now it's updated to a 20/09/2018 Driver (9.0.0.49) according to Device Manager.
  • Updated my Realtek High Definition Audio Driver and disabled its software cause I do not need it.
  • Updated 2 Universal Serial Bus controllers (Intel 8 Series/C220 Series USB EHCI #1 - 8C26 and Intel 8 Series/C220 Series USB EHCI #2 - 8C2D).
  • Updated my Storage controller (Intel C220 series chipset SATA AHCI Controller).
  • Updated 8 System devices (Intel Management Engine Interface ; Intel 8 Series/C220 Series PCI Express Root Port #4 - 8C16 ; Intel Xeon processor E3 - 1200 v3/4th Gen Core processor PCI Express x16 Controller - 0C01 ; Intel Z87 LPC Controller - 8C44 ; Synaptics SMBus Driver ; Intel Extreme Tuning Utility Device Driver ; Intel 8 Series/C220 Series PCI Express Root Port #1 8C10).
  • Did a CHKDSK and restarted the PC for it to run.

    Here's my Specs:
  • Windows 10 Home 64-bit
  • GPU → NVIDIA GeForce GTX 660 Ti
  • CPU → Intel Core i7 4770K
  • RAM (4) → 16,0GB Dual-Channel DDR3 @ 800MHz (9-9-9-24) -- Slot #1: G.Skill 4gb F3-12800CL9-4GBXL | Slot #2: Corsair 4gb CMZ8GX3M2A1600C9 | Slot #3: <Same as 1> | Slot #4: <Same as 2>
  • Motherboard → MSI Z87-G45 GAMING (MS-7821) (BIOS V1.9, Date: 21/07/2014)
  • PSU → XFX PRO 650w Core Edition
  • HDD → Western Digital WDC 1TB WD10EZEX-00KUWA0 (SATA)
  • Keyboard → Razer BlackWidow Tournament Edition
  • Mouse → Razer Abyssus 2014 (Model no. RZ01-0119)
  • Microphone → FIFINE K669B USB
  • Headset → Razer Kraken USB
  • Webcam → Logitech HD Webcam C270
After all I did, I now get BSODs which using BluescreenViewer and WhoCrashed don't accuse an easy to pin-point Driver, here's the only Dump(s) I have now:

• 102220-50781-01.dmp
[DRIVER_IRQL_NOT_LESS_OR_EQUAL | 0xD1 | 0x0 | 0x2 | 0x1 | 0xfffff807545d1377 | fwpkclnt.sys | fwpkclnt.sys+1377 | FWP/IPsec Kernel-Mode API | Microsoft® Windows® Operating System | 10.0.19041.572 (WinBuild.160101.0800) | x64 | ntoskrnl.exe+3f45a0 | 22/10/2020 16:35:32]
Code: 
On Thu 22/10/2020 16:25:53 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102220-50781-01.dmp
This was probably caused by the following module: fwpkclnt.sys (0xFFFFF807545D1377)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF807545D1377)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\fwpkclnt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FWP/IPsec Kernel-Mode API
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a 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.

• MEMORY.DMP
Code: 
On Thu 22/10/2020 16:25:53 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: e2xw1.sys (e2xw10x64+0x987C)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF807545D1377)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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: e2xw1.sys .
Google query: e2xw1.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL

Thank you in advance!
 
Last edited:
Sort by date Sort by votes
T

TheLazP

Apr 7, 2020
14
1
15
I just got another BSOD after posting this and was in a Discord call + a few hours of browsing, right after it restarted and I tried to post about it I got ANOTHER one and after I restarted, ANOTHER one. One of the BSODs was a KMODE_EXCEPTION_NOT_HANDLED

All new dumps:
Code: 
On Thu 22/10/2020 19:49:04 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102220-42187-01.dmp
This was probably caused by the following module: iastore.sys (0xFFFFF800342343B6)
Bugcheck code: 0xD1 (0x20, 0x2, 0x0, 0xFFFFF800342343B6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\iastore.sys
product: Intel Virtual RAID on CPUdriver
company: Intel Corporation
description: Intel Virtual RAID on CPUdriver - x64
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

Code: 
On Thu 22/10/2020 19:49:04 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: iastore.sys (0xFFFFF800342343B6)
Bugcheck code: 0xD1 (0x20, 0x2, 0x0, 0xFFFFF800342343B6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\iastore.sys
product: Intel Virtual RAID on CPUdriver
company: Intel Corporation
description: Intel Virtual RAID on CPUdriver - x64
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

Code: 
On Thu 22/10/2020 19:31:35 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102220-54546-01.dmp
This was probably caused by the following module: e2xw10x64.sys (0xFFFFF8063FA5CFE6)
Bugcheck code: 0xD1 (0xFFFF94B4816AA294, 0xA, 0x1, 0xFFFFF8063FA5CFE6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\e2xw10x64.sys
product: Killer e2400 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2400 PCI-E Gigabit Ethernet Controller
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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: e2xw10x64.sys (Killer e2400 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: e2xw10x64.sys Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
---
Code: 
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\102220-73750-01.dmp
---
I have now uninstalled the Killer Driver and let Windows deal with it in case it was due to that, it installed a Killer E2200 Gigabit Ethernet Controller (14/09/2016, 9.0.0.42) , I am not messing with anything anymore this is ridiculous.. :c Also I do not understand why the BSODs have it as e2400 but on Device Manager it shows up as a e2200..
I don't know why suddenly I started having all of these issues, I haven't installed anything really for it to cause all of this, I did a lot of Driver updates sure but I am even unsure if they're the culprit here since it didn't stop after updating a bunch.

Edit:. Adding my MSConfig + DXDiag + 6 Dumps Download
MSConfig: https://pastebin.com/XHRtzeBz
DXDiag: https://pastebin.com/6JR0uqfH
Dumps Download: https://drive.google.com/drive/folders/15ZrB7-GqR0W3jy1HTE7V5VRtWLpOHE_2?usp=sharing

Edit:. As of 23/10/2020 after a few hours of no BSODs, I did a Antivirus scan on the Windows folder(it finished) and I was able to do everything pretty much till I had one while I went away from the PC, only had YouTube opened, one tab and Discord but everything was idle not doing anything besides my antivirus doing another scan on my "Users" folder cause why not, suddenly one happened while I was away, uploaded to the Google Drive link
Code: 
On Fri 23/10/2020 13:59:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102320-52234-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF8042E4986AD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8042E4986AD, 0xFFFFFE011CFE00C8, 0xFFFFFE011CFDF900)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
Code: 
On Fri 23/10/2020 13:59:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (0xFFFFF8042E4986AD)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8042E4986AD, 0xFFFFFE011CFE00C8, 0xFFFFFE011CFDF900)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
 
Last edited:
Upvote 0 Downvote
Sony_Simon92

Sony_Simon92

Oct 25, 2020
3
0
10
today i reset the cmos (taking battery out für 10 min) and reflashed the newest BIOS with an USB Stick (FAT32)
i re-installed W10 1909 and take only 2 RAM Slots (2x 8 GB) so i will show how it works.

I installed only the Chipset and ME driver from MSI, Audio and LAN from realtek.cz.
I dont install any OC software for now.

In a german forum, they told me that many of my BSOD´s where comming from Intel Extreme Tuning Utility Device Driver -> but i never installed it, i think my Driver installation programm was doing this -> https://sdi-tool.org/ so i never will user this again if the pc is now working
 
Upvote 0 Downvote
T

TheLazP

Apr 7, 2020
14
1
15
I uninstalled Synaptics SMBus Driver and Intel Extreme Tuning Utility Device Driver.
So far my only issue isn't even a BSOD, but a sudden both monitors black screen and PC Restart - all so fast.

My BIOS is updated.
 
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