Random BSOD after upgrading to Win10

Hello Guys,

I upgraded to Win10 with massive random BSODs. Im like getting crazy, I updated all drivers manuelly, every little device driver I could found but with no luck. I had Win 7 for several years without a single BSOD but after the upgrade it happens on random. Im getting mad with this Win10. Hope you can help me outta this big mess.

BIG thank you.

• CHEF-PC-18_03_2016_100156,13.zip (3.00 MB, 7 views)

I am not saying that it is Kaspersky that has caused the BSOD; but there is a fair chance that it might be the cause.

Code:

ffffd000`2192b3f8  fffff801`cb01f26aUnable to load image SystemRootsystem32DRIVERSklif.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for klif.sys *** ERROR: Module load completed but symbols could not be loaded for klif.sys  klif+0x1f26a

Please uninstall (not disable; disabling just keeps it away from scanning, not from loading the drivers and services) Kaspersky and let us know the resulting situation.

If the issue continues, we will have to take some further steps.

thank you ARC for your fast response and sorry for my late answer.

I now uninstalled kaspersky as suggested, but with no success. Still got very annoying random reboots, somethimes my PC works for 10 days with not a single reboot, and sometimes it reboots now three times a day. Its horrible.

Again I attached the log file, hope somebody can help.

CHEF-PC-17_04_2016_183609,37.zip

I am not saying that it is Kaspersky that has caused the BSOD; but there is a fair chance that it might be the cause.

Code:

ffffd000`2192b3f8  fffff801`cb01f26aUnable to load image SystemRootsystem32DRIVERSklif.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for klif.sys *** ERROR: Module load completed but symbols could not be loaded for klif.sys  klif+0x1f26a

Please uninstall (not disable; disabling just keeps it away from scanning, not from loading the drivers and services) Kaspersky and let us know the resulting situation.

If the issue continues, we will have to take some further steps.

This time it is bit more clear.

Code:

Use !analyze -v to get detailed debugging information.  BugCheck 1A, {8887, fffffa8000c03690, fffffa8007048f50, 205}  Probably caused by : hardware_ram( ZEROED_PAGE_CORRUPTED )  Followup:     MachineOwner ---

Test your RAM modules for possible errors.

MemTest86+ - Test RAM

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.

Screenshots and Files - Upload and Post in windowssh blog - Windows 10 blog