Windows 10: BSOD - various types, every 3-4 days, ntoskrnl.exe

Hi,
I've been plagued by random BSoD for years. Tried everything from googling, BIOS updates (have the latest), frequent driver updates and rollbacks to identify the problematic one, driververifier, memtest for RAM sticks (RAM works fine), you name it. Clean installed Windows 10 several months back, but the BSoD just doesn't go away.

I've been trying to analyze crash dumps with WhoCrashed, in 99% of cases it was generic, referencing ntoskrnl.exe, very few pointed to Logitech webcam (no new driver since 2012, claims to be compatible with Windows 10) or Avast (got rid of it, didn't help).

At this point I am desperate as this is getting frustrating. Often times I come back to my pc while it was idling to find out it crashed and rebooted, sometimes crash while camming or watching a movie, other times when shutting it down it decides to bluescreen on the shutdown screen. Here is a summary view of crash dumps:

Attachment 139725

Any help would be appreciated.

Thanks

:)

 

SYSTEM_SERVICE_EXCEPTION 00000000`c0000005

Just got the BSOD. I really don't know how to read the minidump files. I am reading it on bluescreenview. It says the ntoskrnl.exe was the cause.

032218-14734-01.dmp 3/22/2018 3:46:08 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff801`a784b00e ffff8885`ecbb0e30 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+175510 x64 ntoskrnl.exe+175510 E:\tools\032218-14734-01.dmp 4 15 16299 1,125,444 3/22/2018
3:55:42 PM

I have updated the BIOS on it to the newest one.

This is a Lenovo laptop.

Windows 10 Pro x64 bit

 

BSOD Kernel_Security_check_Failure

Hi All Im having BSODs at least 3 times a day an anyone shed any light please?

according to minidump its caused by this...

ntoskrnl.exe+142760

and this...

storport.sys+372a

Thanks

A

 

CODE]
Dump file creation failed due to error during dump creation.[/CODE]

Code: The attempt by user LUKAS-PC\Lukas to restart/shutdown computer LUKAS-PC failed[/quote] Code: The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{1270ab68-e3a0-11e6-86ce-806e6f6e6963}#0000000008100000.[/quote] Code: Dump file creation failed due to error during dump creation.[/quote] Code: BugCheck 3B, {c0000005, fffff800d377130d, ffffe5012ae89810, 0} Probably caused by : memory_corruption[/quote] Code: BugCheck 139, {3, fffff800d7409670, fffff800d74095c8, 0} *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : memory_corruption[/quote] Code: BugCheck 1000007E, {ffffffffc0000005, fffff8035c4e133b, ffffdd016e8926e8, ffffdd016e891f20} *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : memory_corruption[/quote] Code: BugCheck 139, {e, ffff8d0095cf2610, ffff8d0095cf2568, 0} Probably caused by : memory_corruption[/quote] Code: BugCheck C2, {7, 0, 0, ffff800b90dafbc0} unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPagedPoolEnd unable to get nt!MmNonPagedPoolStart unable to get nt!MmSizeOfNonPagedPoolInBytes GetUlongFromAddress: unable to read from fffff8014a5464e0 GetUlongFromAddress: unable to read from fffff8014a5464e0 Probably caused by : memory_corruption[/quote] Code: BugCheck 1A, {41792, ffffed800002d6b8, 2000000000, 0} Probably caused by : memory_corruption[/quote] Code: BugCheck 139, {e, ffffb1011e2442d0, ffffb1011e244228, 0} *** WARNING: Unable to verify timestamp for aswSnx.sys *** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys Probably caused by : memory_corruption[/quote] Code: BugCheck 50, {ffffcbb883ed24b8, 0, ffffcb9308c5a4c4, 2} Could not read faulting driver name Probably caused by : memory_corruption[/quote] Code: BugCheck 1A, {3451, ffff84d540d2b838, ffffc104554667c0, 0} *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : memory_corruption[/quote] Code: BugCheck 1000007E, {ffffffffc0000005, fffff803cc80974d, ffff998060762668, ffff998060761ea0} *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : memory_corruption[/quote] Code: BugCheck EF, {ffff9080928217c0, 0, 0, 0} ----- ETW minidump data unavailable----- Probably caused by : svchost.exe[/quote] Code: BugCheck A, {ffffac8cb217330b, 2, 1, fffff803968d00c4} Probably caused by : win32kfull.sys ( win32kfull!SetProcessPriorityByClass+40 )[/quote] Code: BugCheck A, {20000000, ff, 0, fffff8010acd30c2} Probably caused by : memory_corruption[/quote] Code: BugCheck A, {100000000008, ff, 9f, fffff8026425d3a8} Probably caused by : win32kbase.sys ( win32kbase!GreAcquireSemaphoreSharedInternal+f )[/quote] Code: BugCheck 50, {ffffb106e5c241f0, 0, fffff80c89c8cf84, 0} *** WARNING: Unable to verify timestamp for lvrs64.sys *** ERROR: Module load completed but symbols could not be loaded for lvrs64.sys Could not read faulting driver name *** WARNING: Unable to verify checksum for win32k.sys Probably caused by : memory_corruption[/quote]
lvrs64.sys
Logitech Camera driver
Logitech Support + Downloads


Hi Smartik1,

There were nearly 30 crashes in the event log during the past 2 months.
Have you been doing any over clocking?
Do you use software or hardware RAID?

Were you at any time using an antivirus other than Windows defender on this computer?
Avast?

Open administrative command prompt and type or copy and paste these commands:

1) Winver (in the pop up view the windows version and build and post into the thread)
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
When these have completed right click on the top bar or title bar of the administrative command prompt box, then left click on edit then select all, then right click on the top bar again, then left click on edit then copy, then paste into the thread.

5) Run the Avast uninstall tool in safe mode:
Avast Uninstall Utility | Download aswClear for Avast Removal

6) Open device manager and look for the Logitech Camera. Uninstall this driver.
Code: lvrs64 Logitech RightSound Fi Logitech RightSound Fi Kernel Manual Running OK TRUE FALSE 9,600 269,440 0 23/10/2012 03:11:24 C:\WINDOWS\system32\DRIVERS\lvrs64.sys 3,456[/quote] Find a new driver from the manufacturers web site: Logitech Support + Downloads

7) Run Memtest86+ version 5.01 for 8 or more runs. The number of runs are important and sometimes it takes runs in the teens to find RAM or dim problems. When the test completes please make and image and post into the thread.

8) perform windows updates. If there are any failures please post the KB# and the error code.

 

Hi,
Thanks for the rapid response. To answer your questions:

I never played with manual overclocking. This motherboard comes with a feature called "OC Genie" that does automatic overclocking. I used it initially when I got the PC 4 years ago, however at some point it refused to boot up after a BIOS update. I read into it and apparently you are not supposed to update BIOS on overclocked hardware. This motherboard has a backup BIOS so I switched off OC Genie and have been on my backup BIOS ever since (it is fully up to date).

I don't use hardware RAID, I have Intel Rapid Storage utility installed, but don't think it does anything without actual Raid.

I have been using Avast for many years, however it is not until recently that I've seen a few references to an avast process in my crash dumps. That is where I uninstalled it, however the BSoD didn't stop.

Commands:
1) Windows 10 Version 1703 (OS Build 15063.413)
2) Tried that many times in the past, always comes out clean.
3) Don't know this one, did it anyway.
4) Know this one as well, haven't had issues with this disk before, also came out clean.

Code: Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>winver C:\WINDOWS\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.15063.0 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. C:\WINDOWS\system32>chkdsk /scan The type of the file system is NTFS. Stage 1: Examining basic file system structure ... 425216 file records processed. File verification completed. 10846 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 534368 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Security descriptor verification completed. 54577 data files processed. CHKDSK is verifying Usn Journal... 35150752 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 124263423 KB total disk space. 60440172 KB in 214038 files. 142120 KB in 54578 indexes. 0 KB in bad sectors. 537471 KB in use by the system. 65536 KB occupied by the log file. 63143660 KB available on disk. 4096 bytes in each allocation unit. 31065855 total allocation units on disk. 15785915 allocation units available on disk. C:\WINDOWS\system32>[/quote] Attachment 139816

5) I've already used that utility when I uninstalled Avast as I also wanted to make sure it is gone.

6) My Webcam is C310, I've tried both Logitech as well as Windows detected drivers for it, however as I mentioned the latest drivers are from 2012 and Logitech claimed the cam is compatible with Windows 10. If you check the site now, they re-designed it and there no longer is a driver download section. The right drivers are automatically pulled by Windows.
I checked Amazon reviews on the cam and only 1 guy got BSoD from the cam, everybody else confirmed it is Windows 10 compatible. A bit of detail, I read about a conflict between Realtek and Logitech sound drivers (this driver relates to sound not image by the way so it is not under the imaging devices, but under sounds). Apparently disabling other recording devices besides Logitech fixed it for the guy, but not for me. The source is this:
How I Fixed A Logitech Webcam Blue Screen Issue

7) As mentioned, ran it few months ago as I ran into this forum at the time and saw it as first step advice. It didn't crash or detect any errors.

8) Always have Windows up to date, haven't had any issues:

Attachment 139817

Best regards

Lukas

 

Forgot to mention, a lot of the times the crash dumps double up. When I checked WhoCrashed, it tends to create 2 per crash quite often.

 

I ran memtest overnight and ran into errors on test 7. Found this that could explain it:

Failed Memtest86 test #7 - G.SKILL TECH FORUM

My max supported memory by the system is 1600, but my ram sticks are 1333.

Here are photos of my memtest results:
Imgur: The most awesome images on the Internet

How conclusive is this? Would it be worth swapping the 4x4 setup for a new 2x8 at 1600? I'll still have to go for DDR3 as the CPU and motherboard don't support higher.

Thanks

 

Run Memtest86+ version 5.01 for at least 8 runs on each RAM in only one Dim. Please post images for each.