I have hardware problem? LivekernelEvent - win32k.sys log,when closing system.

Have Windows 10 AU UPDATE. When i am clicking close system ( turn off pc ) , system closing fine, pc closing fine. But after that when i boot to Windows 10 it boots fine but event log sometimes register livekernelevent: win32k.sys.There was not bluescreen i dont saw a bluescreen. So question. It is related to my hardware or system?

LivekernelEvent - win32k.sys - it is related to hardware issue?

But why i dont saw a bluescreen and windows only report this.

Memtest86 no errors. Games are not crashing.No Bsods,no freezing etc.

Windows 10 ,newest Anniversary update.

PC:6700k stock

Asus Z170-P

Corsair 750

16GB DDR4 Kingston

Gtx 1080 Ti Fe

Maybe a BUG? because it does not display any BSODs or works strange.
Reply to litwicki23
6 answers Last reply Best Answer
More about hardware problem livekernelevent win32k sys log closing system
  1. Event viewer always has errors in it, I wouldn't worry too much about them if PC is working fine

    You’re sure to see some errors and warnings in the Event Viewer, even if your computer is working fine.

    The Event Viewer is designed to help system administrators keep tabs on their computers and troubleshoot problems. If there isn’t a problem with your computer, the errors in here are unlikely to be important. For example, you’ll often see errors that indicate a program crashed at a specific time, which may have been weeks ago.

    You got a bite on tenforums but its just saying there isn't a lot around about this event. Its possibly related to a change made in last windows 10 update, there is a new version of Win 10 next month so they might be doing some preparation ahead of time.

    try updating your graphics drivers -

    If you turn off fast startup it may fix this as well: and set PC to never hibernate -
    Reply to Colif
  2. Here:

    Somebody said:"Could also be corrupt windows files, heat issues, bad PSU, bad CMOS battery, bad drivers, and so on."

    So it can hardware?;[
    Reply to litwicki23
  3. corrupt windows files: try this

    right click start button
    choose command prompt (admin)
    type SFC /scannow and press enter
    once its complete, copy paste command below into same window and press enter
    DISM /Online /Cleanup-Image /RestoreHealth

    SFC cleans/fixes system files, DISM cleans/fixes the files SFC uses to compare system files, so if SFC failed first time, try it again and restart PC

    generally, drivers would cause BSOD, you not getting those

    You could have a bad cmos battery, they normally last longer than your mothrboard has been around (over 5 years or so) but it could be just a bad battery.

    PSU is hardest thing on list, which model corsair PSU is it? And even then, if only sign you have there is a problem is this event in event viewer, I don't think it is enough to replace PSU for.
    Reply to Colif
  4. 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.

    It happens when i close system (by clicking shutdown ). And boot up again. Then in log sometimes i have that entry. Any ideas? Hardware or software more related?
    Reply to litwicki23
  5. Best answer
    its probably software is my guess. Did you try turning fast startup off?

    Windows 10 doesn't turn off when you shut it off. it goes into hybred hibernate so its sleeping until you click power button again and it springs back to life. Its possible something on your PC doesn't wake up properly and you get that warning.

    By turning off fast startup, it forces PC to turn off when you shut it down, and though start up may be a little slower if you have a hdd, it may not cause that error occasionally.
    Reply to Colif
  6. OK i will try thanks !:)
    Reply to litwicki23
Ask a new question Answer

Read More

windows 10 Blue Screen Hardware Problem