Windows 10: BSOD - Unknown Cause - WARNING: Unable to verify timestamp for win32k.sys

Discus and support BSOD - Unknown Cause - WARNING: Unable to verify timestamp for win32k.sys in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi all, I need your help, I have been plagued the past few days with intermittent bluescreens. I have tried to diagnose the issue myself, putting the... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by nullN0VA, Jul 23, 2020.

  1. nullN0VA Win User

    BSOD - Unknown Cause - WARNING: Unable to verify timestamp for win32k.sys


    Hi all,

    I need your help, I have been plagued the past few days with intermittent bluescreens.

    I have tried to diagnose the issue myself, putting the .dmp files through WinDbg, following countless forum suggestions to no avail.

    I have a few dump files, one of which pointed out this error:

    "*** WARNING: Unable to verify timestamp for CorsairGamingAudioamd64.sys"

    So, I uninstalled iCue completely, from the registry also, redownloaded the latest software and forced firmware updates on all my corsair peripherals.

    It happened again, another BSOD but a different error.

    "WARNING: Unable to verify timestamp for win32k.sys"

    I am at a loss, I have now tried updating the USB 3.0 drivers and have not had it since, the BSODs are so intermittent, however, I cannot be sure that this has solved the issue.

    What I have tried:


    • Completely removing and installing NVIDIA drivers using DDU in Safe Mode and reinstalling the drivers. I left out the audio drivers, however, as I didn't think I needed them as I don't use HDMI and it's just another driver that could go awry.


    • Running memtest 86, no errors after turning off XMP and setting the mHz and voltage manually, so memory now seems fine.


    • All windows updates have been installed.


    • I checked the health of my HDD's, according to crystaldiskinfo they are all healthy. I have also done all the sfc /scannow and /fixnow w.e

    I am at a loss, I have linked my most recent dump files to my google drive which you should be able to access here.

    Please help, thank you.

    EDIT:

    I have suspicions that it could be caused by my PS4 wireless adapter the official Sony one however, I am not sure.

    :)
     
    nullN0VA, Jul 23, 2020
    #1
  2. nullN0VA Win User

    BSOD - Unknown Cause - WARNING: Unable to verify timestamp for win32k.sys

    Hi all,

    I need your help, I have been plagued the past few days with intermittent bluescreens.

    I have tried to diagnose the issue myself, putting the .dmp files through WinDbg, following countless forum suggestions to no avail.

    I have a few dump files, one of which pointed out this error:

    "*** WARNING: Unable to verify timestamp for CorsairGamingAudioamd64.sys"

    So, I uninstalled iCue completely, from the registry also, redownloaded the latest software and forced firmware updates on all my corsair peripherals.

    It happened again, another BSOD but a different error.

    "WARNING: Unable to verify timestamp for win32k.sys"

    I am at a loss, I have now tried updating the USB 3.0 drivers and have not had it since, the BSODs are so intermittent, however, I cannot be sure that this has solved the issue.

    What I have tried:

    • Completely removing and installing NVIDIA drivers using DDU in Safe Mode and reinstalling the drivers. I left out the audio drivers, however, as I didn't think I needed them as I don't use HDMI and it's just another driver that could go awry.
    • Running memtest 86, no errors after turning off XMP and setting the mHz and voltage manually, so memory now seems fine.
    • All windows updates have been installed.
    • I checked the health of my HDD's, according to crystaldiskinfo they are all healthy. I have also done all the sfc /scannow and /fixnow w.e
    I am at a loss, I have linked my most recent dump files to my google drive which you should be able to access here.

    Please help, thank you.

    EDIT:

    I have suspicions that it could be caused by my PS4 wireless adapter (the official Sony one) however, I am not sure.
     
    nullN0VA, Jul 30, 2020
    #2
  3. WilliamDz Win User
    BSOD - Unknown Cause - WARNING: Unable to verify timestamp for win32k.sys

    It looks like you enabled Driver Verifier already. That flagged ScpVBus.sys as the culprit, a driver for controller.

    Previous to that, when driver verifier was not running, the stack back trace on the other dump indicates USB device coming into play right before causing the system to bugcheck. Its a fair assumption that this is what's causing your system crashes.

    Btw, dont forget to disable driver verifier.
     
    WilliamDz, Jul 30, 2020
    #3
  4. BSOD - Unknown Cause - WARNING: Unable to verify timestamp for win32k.sys

    BSOD UNEXPECTED_KERNEL_MODE_TRAP EXCEPTION_DOUBLE_FAULT 'probably caused by SamsungRapidDiskFltr.sys'

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

    *** ERROR: Module load completed but symbols could not be loaded for SamsungRapidDiskFltr.sys

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

    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys

    Probably caused by : SamsungRapidDiskFltr.sys ( SamsungRapidDiskFltr+14d9b )

    The crashes are being caused by Samsung RAPID Mode Disk Filter driver

    Uninstalling the related program should resolve this issue.
     
    Sumit Dhiman2, Jul 30, 2020
    #4
Thema:

BSOD - Unknown Cause - WARNING: Unable to verify timestamp for win32k.sys

Loading...
  1. BSOD - Unknown Cause - WARNING: Unable to verify timestamp for win32k.sys - Similar Threads - BSOD Unknown Cause

  2. 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys

    in Windows 10 Gaming
    0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys: Hi, Dear Moderators!Me need your help.My PC has a BSOD every day, error 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys.I changed the CPU, RAM, GPU, Motherboard, power unit, Windows reinstalled.And I just don't know what else to...
  3. 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys

    in Windows 10 Software and Apps
    0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys: Hi, Dear Moderators!Me need your help.My PC has a BSOD every day, error 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys.I changed the CPU, RAM, GPU, Motherboard, power supply.And I just don't know what else to check. Can it be in...
  4. 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys

    in Windows 10 BSOD Crashes and Debugging
    0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys: Hi, Dear Moderators!Me need your help.My PC has a BSOD every day, error 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys.I changed the CPU, RAM, GPU, Motherboard, power supply.And I just don't know what else to check. Can it be in...
  5. WARNING: Unable to verify timestamp for win32k.sys

    in Windows 10 Gaming
    WARNING: Unable to verify timestamp for win32k.sys: Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [D:\Desktop\\031022-19218-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search...
  6. WARNING: Unable to verify timestamp for win32k.sys

    in Windows 10 Software and Apps
    WARNING: Unable to verify timestamp for win32k.sys: Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [D:\Desktop\\031022-19218-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search...
  7. WARNING: Unable to verify timestamp for win32k.sys

    in Windows 10 Drivers and Hardware
    WARNING: Unable to verify timestamp for win32k.sys: Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [D:\Desktop\\031022-19218-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search...
  8. Blue Screen error - WARNING: Unable to verify timestamp for Ntfs.sy

    in Windows 10 Gaming
    Blue Screen error - WARNING: Unable to verify timestamp for Ntfs.sy: Microsoft R Windows Debugger Version 10.0.22000.194 AMD64 Copyright c Microsoft Corporation. All rights reserved. Loading Dump File [G:\APA\Minidump\Mini082721-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable...
  9. Blue Screen error - WARNING: Unable to verify timestamp for Ntfs.sy

    in Windows 10 Software and Apps
    Blue Screen error - WARNING: Unable to verify timestamp for Ntfs.sy: Microsoft R Windows Debugger Version 10.0.22000.194 AMD64 Copyright c Microsoft Corporation. All rights reserved. Loading Dump File [G:\APA\Minidump\Mini082721-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable...
  10. WARNING: Unable to verify timestamp for win32k.sys

    in Windows 10 Drivers and Hardware
    WARNING: Unable to verify timestamp for win32k.sys: I have been getting BSODs recently after I replaced mobo, GPU, NVME, cooling system and PSU.I have done MEMtest all good no error. Ran DriverVerifier to stress test third party driver with no issues.Below are bugcheck analysis:DRIVER_OVERRAN_STACK_BUFFER f7 A driver has...