1.    16 Aug 2017 #1
    Join Date : Aug 2017
    Posts : 3
    windows 10 home

    Failure to start windows completely, power cycles on its own, starts


    Ok, so my computer has started to do something weird on startup.

    Sometimes it fully boots normally on the first try. Great!

    About half the time, though, it does not. It gets to the part where you get the windows logo and the spinning semi-circle of white dots, and then it freezes, blackscreens, turns off all my peripherals, power cycles, and starts up normally.

    I am still able to use the computer, for now, but this worries me; my baby is sick. What do?

    The DM log collector file is attached
      My ComputerSystem Spec
  2.    16 Aug 2017 #2
    Join Date : Nov 2015
    Posts : 2,860
    64bit Win 10 Pro ver 1709 Build 16299.64

    Hello,

    When did this start to happen. I ask because there is only one crash dump file from today. Prior to that there was one on Aug 6th and one on Aug 1st. The full list of BSOD events captured is shown below
    Attachment 149152

    Another error is that your system occasionally fails Fast Startup:
    Attachment 149153

    You could try turning off this feature: Turn On or Off Fast Startup in Windows 10
      My ComputersSystem Spec
  3.    17 Aug 2017 #3
    Join Date : Aug 2017
    Posts : 3
    windows 10 home
    Thread Starter

    Thank you for your response, I will test the fast startup and update after. Whatever it is, it's happening almost every day, so if there's only 3 fast startup fails... well, it has occurred many more than three times. Would it be helpful if i reboot repeatedly, write down the time of the occurrences, then provide another DM log to help match up those times to what's going on?

    Thank you again, and I will update soon either way.
      My ComputerSystem Spec
  4.    17 Aug 2017 #4
    Join Date : Apr 2017
    Posts : 8,615
    windows 10 professional version 1607 build 14393.969 64 bit

    Hi EveryDamnTime,

    In addition to philc43 findings the video problems may explain many of the freezes and black screens.
    There were 16 bsod mini dump files debugged.
    There were 5 misbehaving drivers identified:

    nvlddmkm.sys: Nvidia graphics card
    avipbb.sys: Avira antivirus
    MBAMChameleon.sys: Malwarebytes
    farflt.sys: Malwarebytes
    FocusriteUSB.sys

    Code:
    BugCheck 116, {ffff9803da9524a0, fffff80158c06028, ffffffffc000009a, 4}Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2386fda73b467ac8\nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption
    Code:
    VIDEO_TDR_FAILURE (116)Attempt to reset the display driver and recover from timeout failed.Arguments:Arg1: ffff9803da9524a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).Arg2: fffff80158c06028, The pointer into responsible device driver module (e.g. owner tag).Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.Arg4: 0000000000000004, Optional internal context dependent data
    A VIDEO_TDR_ERROR always relates to the system's graphics card (TDR = Timeout Detection Recovery).

    This Video TDR error could be due to:
    a) drivers
    b) heat
    c) power to the card
    d) a faulty PCI-e slot
    e) defective GPU

    Perform the following steps:
    1) Ensure the GPU is free from dust build up and that the fan is working correctly
    2) Reseat the GPU and check that all connections are securely made
    3) Measure the GPU's temperatures at idle and under load and report the results into the thread
    4) Check PSU voltages in BIOS and report the 3.3, 5, and 12V values5) Try a different video card in the system
    6) Run memtest86+ version 5.01 for at least 8 runs.
    Memtest86+ - Advanced Memory Diagnostic Tool
    When Memtest86+ has completed 8 or more runs use a camera or smart phone camera to take a picture and post an image into the thread.

    The number of passes is critical as fewer than 8 passes produces a high incidence of false negatives.
    A false negative is a pass when there is Malfunctioning RAM.

    The computer has 32 GB of RAM so test 16 GB at a time if possible.
    If that is not possible then test 8 GB at a time but you will then not be able to fully check the dual channel capability of the DIMM/MB.
    It will take approximately 1 - 2 hours /GB RAM.
    https://answers.microsoft.com/en-us/...-test-ram.html
    7) Uninstall Avira antivirus
    How do I uninstall my Avira Antivirus product?
    8) Uninstall Malwarebytes
    9) Uninstall Focusrite
    10) The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.The computer manufacturer's web site is preferred. Enter the computer's serial or product number and the operating system to view available drivers.If you use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.https://www.wagnardsoft.com/Display Driver Uninstaller Download version 17.0.7.2https://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.htmlhttp://www.nvidia.com/Download/index.aspx





    Code:
    ffffcd80`508cb218  fffff80a`4cb3db91Unable to load image \SystemRoot\system32\DRIVERS\avipbb.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for avipbb.sys*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys avipbb+0xdb9
    Code:
    avipbb       avipbb                 avipbb                 Kernel        System     Running    OK         TRUE        FALSE        4,096             102,400     0          7/6/2017 6:30:52 AM    C:\WINDOWS\system32\DRIVERS\avipbb.sys           4,096
    farflt.sys Malwarebytes Anti-Ransomware Protection Downloads: https://www.malwarebytes.org/downloads/
    Support: https://www.malwarebytes.org/support/


    Code:
    Event[1664]:  Log Name: System  Source: Display  Date: 2017-06-14T10:47:41.098  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-I9T1C86  Description: Display driver nvlddmkm stopped responding and has successfully recovered.
    Code:
    Event[1736]:  Log Name: System  Source: Display  Date: 2017-06-14T10:55:08.554  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-I9T1C86  Description: Display driver nvlddmkm stopped responding and has successfully recovered.
    Code:
    Event[1763]:  Log Name: System  Source: Display  Date: 2017-06-14T11:09:40.034  Event ID: 4101  Task: N/A  Level: Warning  Opcode: Info  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-I9T1C86  Description: Display driver nvlddmkm stopped responding and has successfully recovered.
    Code:
    Event[2942]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-04T12:49:43.278  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[3658]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-15T15:26:59.718  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[4142]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-21T02:07:59.265  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[4386]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-23T07:24:39.231  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[4487]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-25T07:26:32.246  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[4636]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-25T12:03:44.184  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[4698]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-26T07:30:36.215  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[4763]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-26T07:42:37.215  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[4883]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-26T14:26:49.978  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[4943]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-27T04:44:58.930  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[5023]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-27T12:10:42.540  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[5084]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-28T04:04:29.805  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[5199]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-31T07:40:17.930  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[5273]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-07-31T09:24:38.773  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[5354]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-08-01T07:45:48.977  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[5550]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-08-05T06:02:15.852  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[5649]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-08-06T16:00:44.726  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[6017]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-08-12T04:25:41.634  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[6103]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-08-14T08:29:58.021  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    Event[6231]:  Log Name: System  Source: Microsoft-Windows-Kernel-Power  Date: 2017-08-16T07:11:31.884  Event ID: 41  Task: N/A  Level: Critical  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-I9T1C86  Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Code:
    FocusriteUSB Focusrite USB          Focusrite USB          Kernel        Manual     Running    OK         TRUE        FALSE        4,096             61,440      0          6/8/2017 4:58:59 AM    C:\WINDOWS\system32\drivers\FocusriteUSB.sys     4,096
    Code:
    BugCheck 139, {3, ffffe480a96c2610, ffffe480a96c2568, 0}*** WARNING: Unable to verify timestamp for FocusriteUSB.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSB.sys*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption
    Code:
    ffffe480`a96c32e8  fffff809`c49b48d6Unable to load image \SystemRoot\System32\drivers\FocusriteUSBSwRoot.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBSwRoot.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBSwRoot.sys FocusriteUSBSwRoot+0x48d6
    Code:
    ffffe480`a96c21f8  fffff809`c52d1600Unable to load image \SystemRoot\system32\DRIVERS\avipbb.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for avipbb.sys*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys avipbb+0x21600
    Code:
    ffffaf81`d3bd62e8  fffff80a`192548d6Unable to load image \SystemRoot\System32\drivers\FocusriteUSBSwRoot.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBSwRoot.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBSwRoot.sys FocusriteUSBSwRoot+0x48d6
    Code:
    ffffaf81`d3bd51f8  fffff80a`190a1600Unable to load image \SystemRoot\system32\DRIVERS\avipbb.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for avipbb.sys*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys avipbb+0x21600
    Code:
    BugCheck 116, {ffffa807d2b9d010, fffff80ac0c76028, ffffffffc000009a, 4}Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2386fda73b467ac8\nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sysProbably caused by : nvlddmkm.sys ( nvlddmkm+a16028 )
    VIDEO_TDR_FAILURE (116)Attempt to reset the display driver and recover from timeout failed.Arguments:Arg1: ffffa807d2b9d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).Arg2: fffff80ac0c76028, The pointer into responsible device driver module (e.g. owner tag).Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.Arg4: 0000000000000004, Optional internal context dependent data.
    Code:
    ffffbc80`284622e8  fffff807`f68d48d6Unable to load image \SystemRoot\System32\drivers\FocusriteUSBSwRoot.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBSwRoot.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBSwRoot.sys FocusriteUSBSwRoot+0x48d6
    Code:
    ffffbc80`284611f8  fffff807`f7b11600Unable to load image \SystemRoot\system32\DRIVERS\avipbb.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for avipbb.sys*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys avipbb+0x21600
    Code:
    ffffbb00`c1b612e8  fffff807`97fa48d6Unable to load image \SystemRoot\System32\drivers\FocusriteUSBSwRoot.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBSwRoot.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBSwRoot.sys FocusriteUSBSwRoot+0x48d6
    Code:
    ffffbb00`c1b601f8  fffff807`983d1600Unable to load image \SystemRoot\system32\DRIVERS\avipbb.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for avipbb.sys*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys avipbb+0x21600
    Code:
    ffffe001`2ee4f2e8  fffff804`616d48d6Unable to load image \SystemRoot\System32\drivers\FocusriteUSBSwRoot.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBSwRoot.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBSwRoot.sys FocusriteUSBSwRoot+0x48d6
    Code:
    ffffe001`2ee4e1f8  fffff804`61521600Unable to load image \SystemRoot\system32\DRIVERS\avipbb.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for avipbb.sys*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys avipbb+0x21600
    Code:
    ffff9c01`e7f2f250  fffff80d`743b12a0Unable to load image \SystemRoot\System32\drivers\FocusriteUSBSwRoot.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBSwRoot.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBSwRoot.sys FocusriteUSBSwRoot+0x112a0
    Code:
    ffff9c01`e7f2e1f8  fffff80d`74d81600Unable to load image \SystemRoot\system32\DRIVERS\avipbb.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for avipbb.sys*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys avipbb+0x21600
    Code:
    ffffd801`9badc5d0  fffff80f`8ce848d6Unable to load image \SystemRoot\System32\drivers\FocusriteUSBSwRoot.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBSwRoot.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBSwRoot.sys FocusriteUSBSwRoot+0x48d6
    Code:
    ffff9a01`188be5d0  fffff80b`9c4a48d6Unable to load image \SystemRoot\System32\drivers\FocusriteUSBSwRoot.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBSwRoot.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBSwRoot.sys FocusriteUSBSwRoot+0x48d6
    Code:
    ffffab81`5cb915d0  fffff802`662d48d6Unable to load image \SystemRoot\System32\drivers\FocusriteUSBSwRoot.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBSwRoot.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBSwRoot.sys FocusriteUSBSwRoot+0x48d6
    Code:
    ffffa601`5b8ac5d0  fffff80a`bcad48d6Unable to load image \SystemRoot\System32\drivers\FocusriteUSBSwRoot.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBSwRoot.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBSwRoot.sys FocusriteUSBSwRoot+0x48d6
    Code:
    ffff9880`c6bd35d0  fffff80e`7f1c48d6Unable to load image \SystemRoot\System32\drivers\FocusriteUSBSwRoot.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBSwRoot.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBSwRoot.sys FocusriteUSBSwRoot+0x48d6
    Code:
    ffffd980`2ac635d0  fffff80b`92bc48d6Unable to load image \SystemRoot\System32\drivers\FocusriteUSBSwRoot.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBSwRoot.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBSwRoot.sys FocusriteUSBSwRoot+0x48d6


    Code:
    ffffe500`8b7db2d8  fffff803`93103385Unable to load image \SystemRoot\system32\drivers\FocusriteUSBAudio.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBAudio.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBAudio.sys FocusriteUSBAudio+0x3385
    Code:
    ffffe500`8b7da3d0  fffff803`8e5c48d6Unable to load image \SystemRoot\System32\drivers\FocusriteUSBSwRoot.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for FocusriteUSBSwRoot.sys*** ERROR: Module load completed but symbols could not be loaded for FocusriteUSBSwRoot.sys FocusriteUSBSwRoot+0x48d6
      My ComputerSystem Spec
  5.    17 Aug 2017 #5
    Join Date : Aug 2017
    Posts : 3
    windows 10 home
    Thread Starter

    So I turned off fastboot as directed by philc43. Fastboot was checked on, but hibernate was not. I have booted ~4-5 times with no issue, whereas before it was happening almost every time.

    zbook, Should I be worried about that other stuff if the system now appears to be booting normally? This did start around the time i installed the focusrite device and it's drivers. That was also around the time i installed malwarebytes, i don't know what was first. I made several system changes around that time.

    Additional info: The issue usually seemed to happen at the spot on the windows loading screen (spinning white dots in a circle below windows logo) when it would normally flash to black for a second then continue, so that may be the cause or effect of some video problem. When the issue occurred, it would just not come back from flashing black. Now it does come back, which i *think* is normal behavior that has occurred since the day i built it.
    I also uninstalled some Thrustmaster joystick drivers today, that I had reason to believe were causing some issue, and that gave me a few really bad boots (proper bluescreens) but then stopped.

    TLDR; i think fastboot was the culprit of the original issue. The more i look at fastboot, the more i think it is cancer.
      My ComputerSystem Spec
  6.    17 Aug 2017 #6
    Join Date : Nov 2015
    Posts : 2,860
    64bit Win 10 Pro ver 1709 Build 16299.64

    See how it performs for a day or so and then post a new set of log files if you get any more BSOD events. What we are looking for is stability so aim to make as few changes as possible while checking if you have reached a stable configuration.
      My ComputersSystem Spec
  7.    17 Aug 2017 #7
    Join Date : Apr 2017
    Posts : 8,615
    windows 10 professional version 1607 build 14393.969 64 bit

    Please verify that Windows defender is active after uninstalling the antivirus products with misbehaving drivers.
    Some of the software products may be able to be reinstalled at a later time.
    During the troubleshooting it is best to keep the misbehaving applications and their drivers uninstalled so that if the drivers misbehave again that they don't confound the process to achieve a stable computer environment.
      My ComputerSystem Spec

 


Similar Threads
Thread Forum
Start starts slow, Search, Cortana Won't Start
Microsoft Windows So apparently after a recent "update" (let it be known I don't like the Win 10 lack of update control) The Start opens slowly (click once and wait 2 seconds), Search (Magnifying Glass) does not launch and Cortana from the...
General Support
Solved Power failure Windows 10
Hello, please help me. My problem is accidentally run out of power while installing upgrading to Windows 10 from Windows 7. I have successfully installed Windows 10 through a bootable drive created with the Media Creation Tool from Microsoft. The...
Windows Updates and Activation
Solved Power down button does not completely turn computer power off
I recently upgraded Windows 7 to Windows 10. When I power down the system from the menu, my computer does not completely turn off. The procedure I use is described below: Click Windows_Start_button > Power > Shutdown The system closes...
Performance & Maintenance
Windows 10 will not start after power failure
Been running Windows 10 Upgrade for about 1 week now. Everything was working great until a power failure this afternoon. Turned PC back on and got this message " Computer did not shut down correctly" then this message "Preparing automatic repair"...
General Support
Windows 10 results in repeated Internal Power Failure in Dell Inspiron
Hi. I have a relatively new Dell Inspiron 7000 series (7548). Installed Windows 10 and about 15 seconds after logging in I keep getting an error message about an internal power failure. What an absolute f#$% up. I have never had a problem with the...
General Support
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:25.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums