Solved "Unknown" BSOD errors, Periodic BSOD and changing status errors.

[ImSorry]

"Unknown" BSOD errors, Periodic BSOD and changing status errors.

I've been having issues with BSOD for the last couple of months. I have looked for a fix to my issues, but what was recommended for me to do wasn't really helpful. I simply can't find a fix to it and nothing seems to work. I'm planning on a clean reinstall of my OS since it's about that time for a clean install, but I'm a bit busy so I can't really do that at the moment.

If anyone could help me this, it would be greatly appreciated.

The BSODs started to pop up like 3 months ago, before that my laptop was completely ok. Nothing was happening to it and nothing was wrong with it at all and worked as it should. I wondered if it was something I had installed but I hadn't installed anything on my laptop for a while around that time. I install everything I would ever need at the start of every clean reinstall of my OS so I couldn't really do a system restore because there was no restore point to go back to. I looked around and one of the bluescreens lead me to a wifi driver issue. After that I reinstalled the latest wifi driver for my laptop, but the issue is still the same.

The blue screen happens when I do nothing or when I do something, it really doesn't matter what program it is or what's open or if nothing is open at all. It seems that the blue screen comes in intervals of time, let's say every 12 hours. Since I sleep in a call with my fiance because I have issues falling asleep alone, the BSOD would happen while in a call, but it's also happened to me when I've just been listening to music, or have come back from the restroom and the laptop doesn't have any programs running at all. The blue screen seems to happen around morning time the most, but if I reset my laptop the night before, the BSOD doesn't happen the morning after. I get a different BSOD error sometimes too, It's not always consistent.

I really don't know what's happening to the laptop.
Here's what I got after the most recent BS:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2058

Additional information about the problem:
BCCode: d1
BCP1: FFFFF8800B8644E0
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF880063F3360
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\040420-22978-01.dmp
C:\Users\I'm_Sorry\AppData\Local\Temp\WER-54210-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

DM log collector info

Pictures of some BSODs

Thank you for your time <3

 

[MrPepka]

Update or uninstall WOMic - check updates in program
Update Intel Rapid Storage driver - Downloads for Intel(R) Rapid Storage Technology (Intel(R) RST)

 

[ImSorry]

Update or uninstall WOMic - check updates in program
Update Intel Rapid Storage driver - Downloads for Intel(R) Rapid Storage Technology (Intel(R) RST)

Thank you, I'll get back to you if this helps.

 

[ImSorry]

Update or uninstall WOMic - check updates in program
Update Intel Rapid Storage driver - Downloads for Intel(R) Rapid Storage Technology (Intel(R) RST)

Ok, so I uninstalled "Intel Rapid Storage" and I still got the BSOD. That got me thinking that it might just have been WOMic all this time. I can't uninstall WOMic because I need it to connect my phones microphone to my laptop and use it as a mic. My laptop kept blue screening and I was about to just give in and uninstall womic until like 3 days ago I realized it didn't bsod anymore. Turns out this program is a bit weird with my computer. I monitored womic and realized that the times it blue screened were always when it was open in the mornings.
so I tested something out, I would connect my mic and close the program (mic would still be connected even after it was closed so I could still talk) and it wouldn't blue screen anymore, and then I tested the program being always on, and it would always blue screen after a while. So it was just womic being dumb, though it's still a bit worrisome to know i have a program that can blue screen my stuff.

MrPepka, thanks a lot. You gave me an angle to attack this issue from. Before you told me it was related to either of the 2, I had absolutely no clue where to start looking for an issue. I'm so grateful for your assistance.