Windows 10 LiveKernelEvent Hardware error on first boot up

[fleks]

As my title mentioned in my windows reliability feed there are some hardware errors named livekernelevent but i have no idea why,they dont happen regulary but when it happens its always during the boot but only the first one of the day (if id turn my pc down now and start again i wouldnt have one,i already tested this many times")

I have a lot of "Hardware Errors" named LiveKernelEvent in the windows realibility feed that pretty much say "windows stopped working correctly due to a hardware error"
This doesnt happen every day,its very random when it happens actually sometimes a few days in a row then not at all for a week and so on
The only thing that is steady is that IF it happens it always happen on the first boot of the day for example today i started my pc first time at 17:05 then had to reboot twice for updates
---> Hardware error livekernelevent at 17:05. - when this happens it also creates a dmp file in c:\windows/LiveKernelEventReports and all those files are named sys32.k-"date of the day in numbers"

What could this be? Also related to the windows 10 behavior when shutting down the computer or rather using fast startup?
I dont have actual problems on my computer tho,it can be turned off just fine it boots fast and works perfectly fine so to me its only a very annoying bug but the hardware error entry in the realiability feed kinda worries me...
thanks for reading and your help in advance!

 

[Elixer]

Could be virus/malware or RAM issues, also possible to be CPU related.

 

[fleks]

If its hardware or a virus wouldnt it show up steadily and not randomly not for days at all?
For example i found out that it happened on the 8.2 then on the 9.2 i updated my gpu driver (last update was in september yes im lazy...) then it didnt show up for days andat came back on the 14.2 and guess what released on this date.....a new gpu driver from nvidia...
Possible that this is causing some Trouble while booting? I just remembered this now ill try updating tomorrow

 

[Elixer]

Thing is, it really is difficult to narrow down the problem if it only happens sporadically.
Could also be corrupt windows files, heat issues, bad PSU, bad CMOS battery, bad drivers, and so on.
When this starts to happen, you need to start troubleshooting by, for example, running memtest86+ overnight to make sure it has 0 errors (rule out RAM), if that is fine, then you run something like prime95 or OCCT for 6 hours to make sure CPU is fine (rule out CPU).
Once the main things check out, then you start checking for corrupted windows files, and if that checks out, you work on the driver end.
If all this started after a certain update, then you work backwards until you can rule that out.

 

[fleks]

Well seems like its gpu driver related as i said in thebed last Post
I already checked all hardware parts also and found no problems.
How do i check for corrupted Files tho?
That will be my Next check After i tested gpu driver
Also i found a few posts saying this is a windows ten version 1607bug but i dont know if thats true...i mean i dont have problems at all otherwise.

 

[Elixer]

sfc /SCANNOW is one way to check.
https://support.microsoft.com/en-us...l-to-repair-missing-or-corrupted-system-files

 

[fleks]

Already done actually and no integrity lose
Ill check back in here when i tested that gpu driver
But another question
In my windowsfolder theres a folder named “livekerneleventreports“ with dmp files named sys32.k in it and the time of their creation and the error matches.
Do you know how i can read these files?
If i open them with for example the editor it shows nothing and tells me im not allowed to see it or sth like that (yes im doing it as an Admin)
Would probably help checking those i guess i could also upload them if that helps

 

[fleks]

By now i checked the dump files with bluecrashview to find the actual culprit of the error
And everytime the error happens i get another entry in c: windows livekernelevenreports
Everytime this happens this is the only red marked thing,so the reason it happens but i have no **** clue what that is...any help?

http://imgur.com/a/aQWkt

I actually just turned my pc off and then turned it on again (not the first start of the day) and i get no error in the reliability feed,nothing at all and no dumpfile aswell

What is this weird error that only occurs on the first boot but honestly doesnt affect me at all??