Windows 10: Kinda BSOD but unknown cause

Hello!
My pc turns on after only several attempts - sometimes it gets to the welcome screen and says it does not recognize user or something about RPC but not sure. But when i do turn it on and wake it up from sleep or sometime just random i get a small box saying that the pc will restart in one minute.

This is what i gathered from the event viewer because that is the only information i get because the restart warning does not give any discription about the problem.


<?xml version="1.0" encoding="UTF-8"?>
<Events>
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="49152">1015</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-09-27T18:50:27.148579300Z" />
<EventRecordID>29729</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>JRoze</Computer>
<Security />
</System>
<EventData>
<Data>C:\WINDOWS\system32\lsass.exe</Data>
<Data>c0000005</Data>
</EventData>
<RenderingInfo Culture="lv-LV">
<Message>A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code c0000005. The machine must now be restarted.</Message>
<Level>Error</Level>
<Task />
<Opcode />
<Channel />
<Provider>Microsoft-Windows-Wininit</Provider>
<Keywords>
<Keyword>Classic</Keyword>
</Keywords>
</RenderingInfo>
</Event>
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-09-27T18:50:26.928909700Z" />
<EventRecordID>29727</EventRecordID>
<Channel>Application</Channel>
<Computer>JRoze</Computer>
<Security />
</System>
<EventData>
<Data>lsass.exe</Data>
<Data>10.0.14393.187</Data>
<Data>57cf9e87</Data>
<Data>CRYPT32.dll</Data>
<Data>10.0.14393.0</Data>
<Data>5789984c</Data>
<Data>c0000005</Data>
<Data>0000000000032e5c</Data>
<Data>6c</Data>
<Data>01d218effb6225ee</Data>
<Data>C:\WINDOWS\system32\lsass.exe</Data>
<Data>C:\WINDOWS\System32\CRYPT32.dll</Data>
<Data>50b844a1-ce35-4fbf-b92e-01371ab9a0d8</Data>
<Data />
<Data />
</EventData>
<RenderingInfo Culture="lv-LV">
<Message>Faulting application name: lsass.exe, version: 10.0.14393.187, time stamp: 0x57cf9e87
Faulting module name: CRYPT32.dll, version: 10.0.14393.0, time stamp: 0x5789984c
Exception code: 0xc0000005
Fault offset: 0x0000000000032e5c
Faulting process id: 0x6c
Faulting application start time: 0x01d218effb6225ee
Faulting application path: C:\WINDOWS\system32\lsass.exe
Faulting module path: C:\WINDOWS\System32\CRYPT32.dll
Report Id: 50b844a1-ce35-4fbf-b92e-01371ab9a0d8
Faulting package full name:
Faulting package-relative application ID:</Message>
<Level>Error</Level>
<Task>Application Crashing Events</Task>
<Opcode>Info</Opcode>
<Channel />
<Provider />
<Keywords>
<Keyword>Classic</Keyword>
</Keywords>
</RenderingInfo>
</Event>
</Events>

Hope you will be able to help.

:)

 

BSOD caused by unknown driver

These crashes were related to memory corruption (probably caused by a driver).

Please run these two tests to verify your memory and find which driver is causing the problem. Please run verifier first. You do not need to run memtest yet unless verifier does not find the cause, or you want to.

If you are over-clocking anything reset to default before running these tests.
In other words STOP!!! If you do not know what this means you probably are not






1-Driver verifier (for complete directions see our wiki here)

2-Memtest. (You can read more about running memtest here)

Old drivers from as far back as 2006 that must either be upgraded or removed

i8042HDR.sys 11/20/2006 5:09:25 AM fffff800`17ae0000 fffff800`17ae8000 0x00008000 0x456170c5

ANDROIDUSB.sys 10/26/2009 4:54:23 AM fffff800`1cb50000 fffff800`1cb5f000 0x0000f000 0x4ae563bf

LGBusEnum.sys 11/23/2009 9:36:48 PM fffff800`17bb0000 fffff800`17bb3d80 0x00003d80 0x4b0b38b0

LGVirHid.sys 11/23/2009 9:36:48 PM fffff800`161d0000 fffff800`161d2480 0x00002480 0x4b0b38b0

amdkmafd.sys 9/22/2012 9:04:42 PM fffff800`196d0000 fffff800`196da000 0x0000a000 0x505e602a

 

BSOD caused by unknown driver

Whenever I try to use android's fastboot my system randomly crashes. The only thing I get on BSOD screen is "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED".

Dump

 

Hi Hellriserguy,

I see you have some stuff on your system that is known for causing a lot of trouble.
Do you have a system restore point from prior the installation of the IObit software?

 

No I do not have one. The interesting thing is this. The laptop was working well until 19th august with one problem the dedicated Nvidia GPU caused the pc to crash with a BSOD within few minutes. So the GPU was disabled and everything worked fine. But on the 19th of August a gave it a way for repairs for three weeks and it came back because there are no spare parts available. That would be ok but it started these weird crashes that never happened before. Any Ideas?

 

Clean install the system, the IObit programs can and mostly will mess up a system very bad.

 

Would you recommend any products like the iobit ones that are safe?

 

• Advanced SystemCare - None, all features IObit shows on the page overview are not possible to achieve
• Driver Booster 3 - none, driver update programs are known for causing a lot of problems, the best and safest method is manually by checking the laptop manufacturer or motherboard manufacturer for bios and driver updates
• IObit Malware Fighter - Malwarebytes Anti-Malware
• IObit Uninstaller - Revo Uninstaller
• Smart Defrag - None, defragging of a HDD normally isn't required for a long time