Windows 10: BSOD: SYMBOL_NAME: win32kfull+30438

Discus and support BSOD: SYMBOL_NAME: win32kfull+30438 in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello! I play Far Cry 5 and have been BSOD Here is my dump file: Microsoft R Windows Debugger Version 10.0.19041.1 AMD64 Copyright c Microsoft... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Artyom Shershakov, Jul 23, 2020.

  1. BSOD: SYMBOL_NAME: win32kfull+30438


    Hello! I play Far Cry 5 and have been BSOD


    Here is my dump file:





    Microsoft R Windows Debugger Version 10.0.19041.1 AMD64

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Users\artem\Desktop\072420-37640-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP 8 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Machine Name:

    Kernel base = 0xfffff807`74e00000 PsLoadedModuleList = 0xfffff807`75a2a310

    Debug session time: Fri Jul 24 04:14:06.937 2020 UTC + 6:00

    System Uptime: 5 days 12:58:23.063

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    .........................................................

    Loading User Symbols

    Loading unloaded module list

    ...........................................

    For analysis of this file, run !analyze -v

    6: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    SYSTEM_SERVICE_EXCEPTION 3b

    An exception happened while executing a system service routine.

    Arguments:

    Arg1: 00000000c0000005, Exception code that caused the bugcheck

    Arg2: ffffecd525f20438, Address of the instruction which caused the bugcheck

    Arg3: fffffb0191a42d20, Address of the context record for the exception that caused the bugcheck

    Arg4: 0000000000000000, zero.



    Debugging Details:

    ------------------



    *** WARNING: Unable to verify timestamp for win32kfull.sys



    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 5



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-PR8KSGB



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 61



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 84



    Key : Analysis.System

    Value: CreateObject





    BUGCHECK_CODE: 3b



    BUGCHECK_P1: c0000005



    BUGCHECK_P2: ffffecd525f20438



    BUGCHECK_P3: fffffb0191a42d20



    BUGCHECK_P4: 0



    CONTEXT: fffffb0191a42d20 -- .cxr 0xfffffb0191a42d20

    rax=000000007f3736a1 rbx=ffffeca704747ec0 rcx=ffffeca7046b2820

    rdx=0000000000000000 rsi=ffffeca700728fa8 rdi=0000000000000200

    rip=ffffecd525f20438 rsp=fffffb0191a43720 rbp=ffffeca704747f08

    r8=0000000000000000 r9=0000000000000000 r10=ffffecd525c89330

    r11=ffffae0f3029c910 r12=000000000000000a r13=000000000000000a

    r14=ffffeca704747ef4 r15=ffffeca704747ef0

    iopl=0 nv up ei pl nz na pe nc

    cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010202

    win32kfull+0x30438:

    ffffecd5`25f20438 8b8a10040000 mov ecx,dword ptr [rdx+410h] ds:002b:00000000`00000410=????????

    Resetting default scope



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: csrss.exe



    STACK_TEXT:

    fffffb01`91a43720 ffffeca7`04ea2f60 : fffffb01`91a43730 00000000`00000001 ffffecd5`25c2b151 00000000`00000000 : win32kfull+0x30438

    fffffb01`91a43728 fffffb01`91a43730 : 00000000`00000001 ffffecd5`25c2b151 00000000`00000000 00000000`00000000 : 0xffffeca7`04ea2f60

    fffffb01`91a43730 00000000`00000001 : ffffecd5`25c2b151 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffb01`91a43730

    fffffb01`91a43738 ffffecd5`25c2b151 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffeca7`04747ec0 : 0x1

    fffffb01`91a43740 ffffecd5`25f1ff36 : 00000000`00000010 00000000`1c886dd6 00000000`00000003 00000000`00000004 : win32kbase!UserSessionSwitchLeaveCrit+0x81

    fffffb01`91a437b0 00000000`00000010 : 00000000`1c886dd6 00000000`00000003 00000000`00000004 fffffb01`00000005 : win32kfull+0x2ff36

    fffffb01`91a437b8 00000000`1c886dd6 : 00000000`00000003 00000000`00000004 fffffb01`00000005 fffffb01`91a438b0 : 0x10

    fffffb01`91a437c0 00000000`00000003 : 00000000`00000004 fffffb01`00000005 fffffb01`91a438b0 00000000`00000000 : 0x1c886dd6

    fffffb01`91a437c8 00000000`00000004 : fffffb01`00000005 fffffb01`91a438b0 00000000`00000000 00000000`00000000 : 0x3

    fffffb01`91a437d0 fffffb01`00000005 : fffffb01`91a438b0 00000000`00000000 00000000`00000000 ffffeca7`006578d0 : 0x4

    fffffb01`91a437d8 fffffb01`91a438b0 : 00000000`00000000 00000000`00000000 ffffeca7`006578d0 fffff807`00000040 : 0xfffffb01`00000005

    fffffb01`91a437e0 00000000`00000000 : 00000000`00000000 ffffeca7`006578d0 fffff807`00000040 ffffffff`800057d4 : 0xfffffb01`91a438b0





    SYMBOL_NAME: win32kfull+30438



    MODULE_NAME: win32kfull



    IMAGE_NAME: win32kfull.sys



    STACK_COMMAND: .cxr 0xfffffb0191a42d20 ; kb



    BUCKET_ID_FUNC_OFFSET: 30438



    FAILURE_BUCKET_ID: 0x3B_c0000005_win32kfull!unknown_function



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {c8562915-20db-1d44-10f6-80418b3fecc4}



    Followup: MachineOwner

    ---------


    Here is my Event Viewer:

    -<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    -<System>
    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
    <EventID>41</EventID>
    <Version>8</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000400000000002</Keywords>
    <TimeCreatedSystemTime="2020-07-23T22:15:12.0141248Z" />
    <EventRecordID>2534</EventRecordID>
    <Correlation/>
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>DESKTOP-PR8KSGB</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    -<EventData>
    <Data Name="BugcheckCode">59</Data>
    <Data Name="BugcheckParameter1">0xc0000005</Data>
    <Data Name="BugcheckParameter2">0xffffecd525f20438</Data>
    <Data Name="BugcheckParameter3">0xfffffb0191a42d20</Data>
    <Data Name="BugcheckParameter4">0x0</Data>
    <Data Name="SleepInProgress">0</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
    <Data Name="BootAppStatus">0</Data>
    <Data Name="Checkpoint">41</Data>
    <Data Name="ConnectedStandbyInProgress">false</Data>
    <Data Name="SystemSleepTransitionsToOn">7</Data>
    <Data Name="CsEntryScenarioInstanceId">0</Data>
    <Data Name="BugcheckInfoFromEFI">false</Data>
    <Data Name="CheckpointStatus">0</Data>
    <Data Name="CsEntryScenarioInstanceIdV2">0</Data>
    <Data Name="LongPowerButtonPressDetected">false</Data>
    </EventData>
    </Event>



    Can anyone help me understand what is was happend?

    P.S. Sorry for my english :

    :)
     
    Artyom Shershakov, Jul 23, 2020
    #1

  2. BSOD: SYMBOL_NAME: win32kfull+30438

    Hello! I play Far Cry 5 and have been BSOD

    Here is my dump file:

    Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Users\artem\Desktop\072420-37640-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Machine Name:

    Kernel base = 0xfffff807`74e00000 PsLoadedModuleList = 0xfffff807`75a2a310

    Debug session time: Fri Jul 24 04:14:06.937 2020 (UTC + 6:00)

    System Uptime: 5 days 12:58:23.063

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    .........................................................

    Loading User Symbols

    Loading unloaded module list

    ...........................................

    For analysis of this file, run !analyze -v

    6: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************

    SYSTEM_SERVICE_EXCEPTION (3b)

    An exception happened while executing a system service routine.

    Arguments:

    Arg1: 00000000c0000005, Exception code that caused the bugcheck

    Arg2: ffffecd525f20438, Address of the instruction which caused the bugcheck

    Arg3: fffffb0191a42d20, Address of the context record for the exception that caused the bugcheck

    Arg4: 0000000000000000, zero.

    Debugging Details:

    ------------------

    *** WARNING: Unable to verify timestamp for win32kfull.sys

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.Sec

    Value: 5

    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-PR8KSGB

    Key : Analysis.DebugData

    Value: CreateObject

    Key : Analysis.DebugModel

    Value: CreateObject

    Key : Analysis.Elapsed.Sec

    Value: 61

    Key : Analysis.Memory.CommitPeak.Mb

    Value: 84

    Key : Analysis.System

    Value: CreateObject

    BUGCHECK_CODE: 3b

    BUGCHECK_P1: c0000005

    BUGCHECK_P2: ffffecd525f20438

    BUGCHECK_P3: fffffb0191a42d20

    BUGCHECK_P4: 0

    CONTEXT: fffffb0191a42d20 -- (.cxr 0xfffffb0191a42d20)

    rax=000000007f3736a1 rbx=ffffeca704747ec0 rcx=ffffeca7046b2820

    rdx=0000000000000000 rsi=ffffeca700728fa8 rdi=0000000000000200

    rip=ffffecd525f20438 rsp=fffffb0191a43720 rbp=ffffeca704747f08

    r8=0000000000000000 r9=0000000000000000 r10=ffffecd525c89330

    r11=ffffae0f3029c910 r12=000000000000000a r13=000000000000000a

    r14=ffffeca704747ef4 r15=ffffeca704747ef0

    iopl=0 nv up ei pl nz na pe nc

    cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010202

    win32kfull+0x30438:

    ffffecd5`25f20438 8b8a10040000 mov ecx,dword ptr [rdx+410h] ds:002b:00000000`00000410=????????

    Resetting default scope

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXNTFS: 1 (!blackboxntfs)

    BLACKBOXPNP: 1 (!blackboxpnp)

    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: csrss.exe

    STACK_TEXT:

    fffffb01`91a43720 ffffeca7`04ea2f60 : fffffb01`91a43730 00000000`00000001 ffffecd5`25c2b151 00000000`00000000 : win32kfull+0x30438

    fffffb01`91a43728 fffffb01`91a43730 : 00000000`00000001 ffffecd5`25c2b151 00000000`00000000 00000000`00000000 : 0xffffeca7`04ea2f60

    fffffb01`91a43730 00000000`00000001 : ffffecd5`25c2b151 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffb01`91a43730

    fffffb01`91a43738 ffffecd5`25c2b151 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffeca7`04747ec0 : 0x1

    fffffb01`91a43740 ffffecd5`25f1ff36 : 00000000`00000010 00000000`1c886dd6 00000000`00000003 00000000`00000004 : win32kbase!UserSessionSwitchLeaveCrit+0x81

    fffffb01`91a437b0 00000000`00000010 : 00000000`1c886dd6 00000000`00000003 00000000`00000004 fffffb01`00000005 : win32kfull+0x2ff36

    fffffb01`91a437b8 00000000`1c886dd6 : 00000000`00000003 00000000`00000004 fffffb01`00000005 fffffb01`91a438b0 : 0x10

    fffffb01`91a437c0 00000000`00000003 : 00000000`00000004 fffffb01`00000005 fffffb01`91a438b0 00000000`00000000 : 0x1c886dd6

    fffffb01`91a437c8 00000000`00000004 : fffffb01`00000005 fffffb01`91a438b0 00000000`00000000 00000000`00000000 : 0x3

    fffffb01`91a437d0 fffffb01`00000005 : fffffb01`91a438b0 00000000`00000000 00000000`00000000 ffffeca7`006578d0 : 0x4

    fffffb01`91a437d8 fffffb01`91a438b0 : 00000000`00000000 00000000`00000000 ffffeca7`006578d0 fffff807`00000040 : 0xfffffb01`00000005

    fffffb01`91a437e0 00000000`00000000 : 00000000`00000000 ffffeca7`006578d0 fffff807`00000040 ffffffff`800057d4 : 0xfffffb01`91a438b0

    SYMBOL_NAME: win32kfull+30438

    MODULE_NAME: win32kfull

    IMAGE_NAME: win32kfull.sys

    STACK_COMMAND: .cxr 0xfffffb0191a42d20 ; kb

    BUCKET_ID_FUNC_OFFSET: 30438

    FAILURE_BUCKET_ID: 0x3B_c0000005_win32kfull!unknown_function

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {c8562915-20db-1d44-10f6-80418b3fecc4}

    Followup: MachineOwner

    ---------

    Here is my Event Viewer:

    -
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    -
    <System>

    <Provider
    Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />

    <EventID>41</EventID>

    <Version>8</Version>

    <Level>1</Level>

    <Task>63</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000400000000002</Keywords>

    <TimeCreated
    SystemTime="2020-07-23T22:15:12.0141248Z" />

    <EventRecordID>2534</EventRecordID>

    <Correlation
    />

    <Execution
    ProcessID="4" ThreadID="8" />

    <Channel>System</Channel>

    <Computer>DESKTOP-PR8KSGB</Computer>

    <Security
    UserID="S-1-5-18" />

    </System>

    -
    <EventData>

    <Data Name="BugcheckCode">59</Data>

    <Data Name="BugcheckParameter1">0xc0000005</Data>

    <Data Name="BugcheckParameter2">0xffffecd525f20438</Data>

    <Data Name="BugcheckParameter3">0xfffffb0191a42d20</Data>

    <Data Name="BugcheckParameter4">0x0</Data>

    <Data Name="SleepInProgress">0</Data>

    <Data Name="PowerButtonTimestamp">0</Data>

    <Data Name="BootAppStatus">0</Data>

    <Data Name="Checkpoint">41</Data>

    <Data Name="ConnectedStandbyInProgress">false</Data>

    <Data Name="SystemSleepTransitionsToOn">7</Data>

    <Data Name="CsEntryScenarioInstanceId">0</Data>

    <Data Name="BugcheckInfoFromEFI">false</Data>

    <Data Name="CheckpointStatus">0</Data>

    <Data Name="CsEntryScenarioInstanceIdV2">0</Data>

    <Data Name="LongPowerButtonPressDetected">false</Data>

    </EventData>

    </Event>

    Can anyone help me understand what is was happend?

    P.S. Sorry for my english BSOD: SYMBOL_NAME:  win32kfull+30438 :)
     
    Artyom Shershakov, Jul 30, 2020
    #2
  3. ARC
    Arc Win User
    Random BSOD while browsing internet


    BitDefender is nothing special. mwac.sys causes BSODs anywhere.
    A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
    In that very thread, the suggested action apparently worked.

    The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
    As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
    That is why I posted that my suggestion may work, or may not. Let us see where it goes.
     
  4. Nikhar_K Win User

    BSOD: SYMBOL_NAME: win32kfull+30438

    APC_INDEX_MISMATCH ( win32kfull!EditionIsSAS+1197 ) randomly when I move the touchpad after a (certain) amount of sleep

    Hi,



    Thank you for writing to Microsoft Community Forums.



    Please reply with the following details to help you with the appropriate troubleshooting steps:



    • Are you able to boot the computer to Desktop?
    • Are you using a USB mouse or the Touchpad of the computare?
    • Which build version of Windows 10 is installed on the computer? To check type:
      winver in the search bar on the Taskbar and hit
      Enter.


    As per the dump file shared by you, I see that the win32kfull file is causing this issue. It could be due to old version of Windows installed on the computer or a possible memory corruption. I suggest you to refer the troubleshooting steps mentioned
    below and see if that helps:



    Method 1: Update Windows



    I suggest check for latest Windows Updates on the computer and install them. You can check for updates by going to
    Settings >> Update & Security >> Windows Update >> Check for updates.



    Method 2: Update drivers



    As you have mentioned that this occurs when you move the mouse, so I suggest you to try updating the Touchpad drivers and check, you can follow the steps mentioned below:



    1. Press Windows key + X, and select
      Device Manager.
    2. Expand Mouse.
    3. Right click on the display driver and select
      Update Drivers.

    4. Restart the computer if prompted.


    Article for reference: Update drivers in Windows 10.



    If you get the message that best drivers are already installed, you can download the Touchpad drivers from

    ASUS E203NA
    .



    Method 3: Run Memory Diagnostic



    You can run the Memory Diagnostic tool and check for memory corruption. Please follow the steps mentioned below:



    Run memory diagnostic to find any memory corruption issue.



    1. Open Start Menu and type
      Memory
      .
    2. Now click on Windows Memory Diagnostic.
    3. Click on Restart now and check for problems.
    4. Follow the on screen instructions


    Please reply with the status of the issue, we will be glad to help you further.



    Regards,

    Nikhar Khare

    Microsoft Community - Moderator
     
    Nikhar_K, Jul 30, 2020
    #4
Thema:

BSOD: SYMBOL_NAME: win32kfull+30438

Loading...
  1. BSOD: SYMBOL_NAME: win32kfull+30438 - Similar Threads - BSOD SYMBOL_NAME win32kfull+30438

  2. Having a BSOD from Win32kfull by closing a specific Winforms Control

    in Windows 10 Gaming
    Having a BSOD from Win32kfull by closing a specific Winforms Control: Win32kfull BSOD since KB5034848 with Exception_Double_Fault in the symbol named win32kfull!SetOrClrWF+18eBSOD is caused while closing a specific WinForms complex control in an application developed by my companyIntroduced since KB5034848Stlll present with KB5035853...
  3. Having a BSOD from Win32kfull by closing a specific Winforms Control

    in Windows 10 Software and Apps
    Having a BSOD from Win32kfull by closing a specific Winforms Control: Win32kfull BSOD since KB5034848 with Exception_Double_Fault in the symbol named win32kfull!SetOrClrWF+18eBSOD is caused while closing a specific WinForms complex control in an application developed by my companyIntroduced since KB5034848Stlll present with KB5035853...
  4. problem with win32kfull!TimersProc+0x1e1

    in Windows 10 Gaming
    problem with win32kfull!TimersProc+0x1e1: Hello everyone, I faced such a problem after reinstalling the OS: problem with win32kfull!TimersProc+0x1e1 and I was thrown into the blue screen of death during the game. I noticed a decrease in performance and anunplanned picture in games, although it used to be smooth, but...
  5. problem with win32kfull!TimersProc+0x1e1

    in Windows 10 Software and Apps
    problem with win32kfull!TimersProc+0x1e1: Hello everyone, I faced such a problem after reinstalling the OS: problem with win32kfull!TimersProc+0x1e1 and I was thrown into the blue screen of death during the game. I noticed a decrease in performance and anunplanned picture in games, although it used to be smooth, but...
  6. BSOD SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30 Dump File

    in Windows 10 Gaming
    BSOD SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30 Dump File: I'm not sure how to read this or where to start. Hoping to get some assistance with my dump file: For analysis of this file, run !analyze -v 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * *...
  7. BSOD SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30 Dump File

    in Windows 10 Software and Apps
    BSOD SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30 Dump File: I'm not sure how to read this or where to start. Hoping to get some assistance with my dump file: For analysis of this file, run !analyze -v 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * *...
  8. BSOD SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30 Dump File

    in Windows 10 BSOD Crashes and Debugging
    BSOD SYMBOL_NAME: nt!KeAcquireSpinLockAtDpcLevel+30 Dump File: I'm not sure how to read this or where to start. Hoping to get some assistance with my dump file: For analysis of this file, run !analyze -v 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * *...
  9. BSOD win32kfull

    in Windows 10 Drivers and Hardware
    BSOD win32kfull: HiI have started to get this blue screen error any ideas. There are no driver problems in device manager. Please let me know if you can see what has happened,I have left the latest dmp files herehttps://www.dropbox.com/sh/ei6t5oy0u4afik3/AAB8iAzMZhNvWtGnSTHePIK3a?dl=0Thanks...
  10. win32kfull Randomly Crashes

    in Windows 10 BSOD Crashes and Debugging
    win32kfull Randomly Crashes: Hi, In the last two weeks my computer started to have randomly bsod's related to win32kfull, the last time it has happened the computer was idle. Windows 10 64bits. 164924