- Apr 1, 2019
- 2,786
Since the last F-Secure Safe update 3/9 I have been getting Blue Screens when I wake the computer up on occasion. Anybody else seen this?
Please provide comments and solutions that are helpful to the author of this topic.
No, that page is just advertising Systweak's Advanced Driver Updater, which you have to pay to use and most definitely will not fix the issue.Well If your looking for the solution for this problem then you should check this out
Pretty much the same I would recommend, but if it happens " regular " or from time to time, and if I recall correct the OP even paid for the product is to create the FSDIAG file and then do not hesitate contact the official F-Secure support, either via phone or chat. Avoid the forum as one want an actual support ticket created in these cases.You may want to install BlueScreenView or WhoCrashed, as they quite possibly will be able to identify what driver is causing the crash.
Blue screen of death (STOP error) information in dump files.
Displays information about blue screen crashes occured on your system. (MiniDump Reader)www.nirsoft.net
Looks like ntoskrnl.exe C:\WINDOWS\system32\ntoskrnl.exe . So I'll have to take a look at all my drivers and make sure they are up to date.You may want to install BlueScreenView or WhoCrashed, as they quite possibly will be able to identify what driver is causing the crash.
Blue screen of death (STOP error) information in dump files.
Displays information about blue screen crashes occured on your system. (MiniDump Reader)www.nirsoft.net
Do the easy part first, remove all your ram sticks, wipe the contact points with isopropyl alcohol, reinsert. Check for blue screen errors. Ntoskenl blue screen is mostly related to memory errors.Looks like ntoskrnl.exe C:\WINDOWS\system32\ntoskrnl.exe . So I'll have to take a look at all my drivers and make sure they are up to date.
If that’s the case then one of them may be going bad. Just odd it occurred within a couple days of installing F-Secure and I’ve not had a blue screen in the year and a half since I built this computer.Do the easy part first, remove all your ram sticks, wipe the contact points with isopropyl alcohol, reinsert. Check for blue screen errors. Ntoskenl blue screen is mostly related to memory errors.
It's rare that the memory sticks going bad, it just may be a contact issue...you can try your luck by cleaning it.If that’s the case then one of them may be going bad. Just odd it occurred within a couple days of installing F-Secure and I’ve not had a blue screen in the year and a half since I built this computer.
I will try that after a couple software and driver checks. Seems like it would be hard for the contacts to get dirty since the modules haven’t been removed since they were installed.It's rare that the memory sticks going bad, it just may be a contact issue...you can try your luck by cleaning it.
Well hopefully I can RMA. I’m guessing it won’t be a fast process. But definitely just a coincidence with F-Secure.Well memtest86 failed right off the bat. Looks like I’m ordering some ram.
Thanks for the tip @roger_m , very useful tool!You may want to install BlueScreenView or WhoCrashed, as they quite possibly will be able to identify what driver is causing the crash.
Blue screen of death (STOP error) information in dump files.
Displays information about blue screen crashes occured on your system. (MiniDump Reader)www.nirsoft.net
Interesting. I wonder if F-Secure just happened to cause the system to hit the bad memory addresses on my module. I had t had a blue screen that I can think of since building the thing a year and a half ago.I was getting blue screen on startups ( occasionally ) while F-Secure was installed.
No more blue screen since 2 days ago, that's when i've uninstalled F-Secure. not sure if that was the cause tho. but all good for now
Yep, it just works. Probably will leave F-Secure on my laptop. Not sure for the desktop. However the 50+ Memtest86 errors are concerning. I pulled the "bad" ram stick and am waiting to see if it happens again.Recently I have also seen reporting of BSOD on some other product's forum.
Not a solution to your problem, but IMO, just stick to Microsoft Defender unless there's a reason to switch to something else. I know you have used Defender and OSA combo for a while now and probably wanted to try something new for a change, but my suggestion would be to keep using that combo for the most stable and problem free experience.