Windows 10: Constant freezing/lockups with mouse/keyboard usage in windows 10

Discus and support Constant freezing/lockups with mouse/keyboard usage in windows 10 in Windows 10 BSOD Crashes and Debugging to solve the problem; This will be a little lengthy, so I apologize beforehand. I have been having constant problems with windows 10 freezing. The problem started in the... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Fcao, Jan 16, 2018.

  1. Fcao Win User

    Constant freezing/lockups with mouse/keyboard usage in windows 10


    This will be a little lengthy, so I apologize beforehand. I have been having constant problems with windows 10 freezing. The problem started in the beginning of January, but it is possible that my computer was not used in the past two months. This computer is primarily a gaming computer and I was extremely busy for the past couple of months, so if I did use it, it would have only been a handful of times. When I started using the computer in the beginning of January the computer started out working just fine. Then windows installed a few updates and I installed a video game. Then I started having a few computer freezes, but they were few and spread out. I originally thought the problem was just related to the game because the crashes usually happened around the times when i was loading or closing the game. However, that was just about all I was doing at the time. The problem also became significantly worse very quickly. I do not know if a meltdown update was applied or not. The fall creators update was applied, but I have since removed that update during my troubleshooting ventures.

    On to the actual problem. After booting my computer, my computer freezes after 12 minutes. I measured the time from when the log in screen first shows up until the computer freezes. It is almost exactly twelve minutes every time. The variation is small enough that it could just be a difference in when I hit the start button for the timer. The computer freezes, but I can move the mouse around and use the keyboard. Windows can generally be minimized and maximized, but nothing can be closed. If a file is transferring, installing, or downloading, that obviously freezes. 90% of the time the only solution is to hold the power button. There are rare occasions where it will pull itself out of the freeze, but the computer has serious limitations after that. The are also times where the computer completely freezes and not even the mouse will move. If it pulls itself out of a freeze, files will not always save or transfer. This has caused problems during my troubleshooting because I cannot use software to try and log the issue because the files will not save. Sometimes the file explorer will show folders, but not text. The drives sometimes show a blank white page with no text or the usual graphic. The computer can then freeze again at any moment and it will never pull itself out of that freeze. Task manager cannot be opened during the freeze and if it was previously opened, it cannot end tasks. Oddly enough, if the computer pulls itself out of being frozen and I already have a video game (Elder scrolls online at the moment) running, I can continue playing that game without too much trouble, but trying to do other tasks or even restarting that game may not work and may cause the computer to freeze and need to be shut down with the power button. It seems like trying to multi-task increases the chances of the computer freezing again.

    At first, I suspected a hardware issue, but I have gone through numerous troubleshooting suggestions and nothing has helped. I ran a windows check on the memory and hard drive. I pulled a memory stick and tested each of them one at a time. I switched hard drives. I tried a clean install on my main hard drive (SSD) and a backup hard drive (SSD). I removed the windows fall creators update. I have tried booting into safe mode. I ran a program from intel to check my CPU. I have tried numerous other suggestions that I found online, but I cannot remember them all because they are things I would not normally know to try. When I used my old ssd, it still had windows 7 on it. I did not test it very thoroughly, but when windows 7 was running on my other hard drive, I did not encounter any freezing issues. It should have frozen at least twice. I figured that my hard drive must have been the problem, so I installed windows 10 on that hard drive. I immediately ran into a freezing problem once windows 10 was installed. Tomorrow (or later today actually), I am going to try installing Ubuntu and see if the computer still freezes. At this point, I suspect the problem is windows 10. The only other thing I can think of would be the motherboard because the freezes almost seem like everything just stops responding. The CPU, Ram, and disk drive usage do not spike during the freezes. There are some windows errors in the event viewer that show the disk drives not responding like they should, but that makes sense considering the computer is frozen.

    I would appreciate any suggestions.

    To anyone who reads this in the next few minutes, I will update this post with the requested zip file in a few minutes. i have to restart my computer to be able to attach the file. Yes, I wrote this on my broken computer.

    :)
     
  2. G.E.E. Win User

    Loss of Keyboard and Mouse functions (USB issues) after recent updates which included KB4074588

    To whom it may concern and members of the community,

    After a recent update which included KB4074588, I have lost my keyboard and mouse (USB) during the use of my computer after a fresh install of Windows 10 Pro and receiving the required updates. Not only is this issue on this computer it has also recently
    occurred on my new HP laptop. I have done some research into this matter and in my findings, there were many comments on various websites pertaining to this issue. I have found that installing the mentioned required March 5, 2018, KB4090913 did not completely
    fix the issue.

    Here are my findings. After a manual install of KB4090913 via this link, Microsoft Update Catalog, I have not encountered the unrecoverable lockups of both my keyboard and mouse requiring a hard reset. I do now hear
    the occasional sound of an unplugged device and either the keyboard and or mouse still result in a lockup of roughly 2 seconds of either device. This temporary lockup also happens with or without the sound of a device disconnect and can be seen by the stuttering
    of the mouse when being moved across the screen.

    Can we please get this issue completely resolved as soon as possible? Losing the keyboard or mouse even momentarily during the time I am on my computer causing loss of work or causing me to have to redo my work is not acceptable.

    Thank you,

    GE
     
    G.E.E., Jan 16, 2018
    #2
  3. Windows 10 mouse and keyboard issues

    I installed windows 10 and my mouse and keyboard freeze. Any way to correct it?
     
    ColleenHirsch, Jan 16, 2018
    #3
  4. Fcao Win User

    Constant freezing/lockups with mouse/keyboard usage in windows 10

    Sorry it took a while to get the zip file uploaded. I made that post before I went to sleep and didn't know it would need moderator approval. I can't find a way to edit my first post, so I'll put the file here.

    Edit:
    I feel I should mention that the issue is not the graphics card or power supply. Both of those have been changed recently.
     
  5. zbook New Member
    There were no BSOD mini dump files.
    The logs had many entries related to drive file corruption.
    There were many i/o retried.

    1) open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    5) chkdsk /x /f /r
    Run this command on all drives/partitions.
    Use the syntax: chkdsk /x /f /r C: or chkdsk / /f /r D: and change the drive letter to the applicable drive letter.
    This may take many hours so plan to run overnight.
    6) use the information in this link to find the results of the chkdsk scans in the event viewer. Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share links:
    Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

    7) Uninstall Comodo firewall

    8) Create a bootable windows 10 iso:
    Download Windows 10
    9) Indicate if you have backed up all important files.
    10) Indicate whether you have made a backup image.
    11) Indicate whether you would be able to perform a clean install.
    12) Indicate whether you had problems upgrading to windows 10 version 1709

    13) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

    14) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread

    15) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
    > on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
    > on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread

    16) In the left lower corner search type services > open windows error reporting service > scroll to the startup type column > right click > left click on properties > post an image into the thread

    17) Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
    Resplendence Software - WhoCrashed, automatic crash dump analyzer
    18) Click analyze > look for dead or deaddead in the results > post the results into the thread
    19) Run this log collector after the above steps and post a zip into the thread:
    log collector v2-beta08.zip

    20) Run HDTune:
    HD Tune website
    to check the health,
    scan for errors, no quick scan but full scan
    run a benchmark.
    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    the health,
    the error scan,
    the benchmark incl. following
    transfer rate,
    access time,
    burst rate,
    cpu usage.
    Take Screenshot in Windows 10 General Tips Tutorials


    cmdguard.sys COMODO Firewall Pro Sandbox Driver Comodo Discussion Board and Support Forums | Comodo Community Requires registration

    Code: Event[2956]: Log Name: System Source: iaStorA Date: 2018-01-17T04:34:11.241 Event ID: 129 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: Reset to device, \Device\RaidPort0, was issued.Event[2957]: Log Name: System Source: Disk Date: 2018-01-17T04:36:41.021 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x5f9130 for Disk 1 (PDO name: \Device\00000035) was retried.Event[2958]: Log Name: System Source: Disk Date: 2018-01-17T04:36:41.272 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x982380 for Disk 1 (PDO name: \Device\00000035) was retried.Event[2959]: Log Name: System Source: Disk Date: 2018-01-17T04:36:41.272 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x982280 for Disk 1 (PDO name: \Device\00000035) was retried.Event[2960]: Log Name: System Source: Disk Date: 2018-01-17T04:36:41.272 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x982180 for Disk 1 (PDO name: \Device\00000035) was retried.Event[2961]: Log Name: System Source: Disk Date: 2018-01-17T04:36:41.272 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x981f80 for Disk 1 (PDO name: \Device\00000035) was retried.Event[2962]: Log Name: System Source: Disk Date: 2018-01-17T04:36:41.272 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x982080 for Disk 1 (PDO name: \Device\00000035) was retried.Event[2963]: Log Name: System Source: Disk Date: 2018-01-17T04:36:41.272 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x981e80 for Disk 1 (PDO name: \Device\00000035) was retried.Event[2964]: Log Name: System Source: Disk Date: 2018-01-17T04:36:41.522 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x981d80 for Disk 1 (PDO name: \Device\00000035) was retried.Event[2965]: Log Name: System Source: Disk Date: 2018-01-17T04:36:41.522 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0xf41f8b0 for Disk 1 (PDO name: \Device\00000035) was retried.Event[2966]: Log Name: System Source: Disk Date: 2018-01-17T04:36:41.522 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x981c80 for Disk 1 (PDO name: \Device\00000035) was retried.Event[2967]: Log Name: System Source: Disk Date: 2018-01-17T04:36:41.522 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0xf41f9b0 for Disk 1 (PDO name: \Device\00000035) was retried.Event[2968]: Log Name: System Source: Disk Date: 2018-01-17T04:36:41.522 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0xf41f6b0 for Disk 1 (PDO name: \Device\00000035) was retried.Event[2969]: Log Name: System Source: Disk Date: 2018-01-17T04:36:41.522 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0xf41f7b0 for Disk 1 (PDO name: \Device\00000035) was retried.[/quote] Code: Event[2956]: Log Name: System Source: iaStorA Date: 2018-01-17T04:34:11.241 Event ID: 129 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: Reset to device, \Device\RaidPort0, was issued.[/quote] Code: Event[2725]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2018-01-16T23:12:46.902 Event ID: 98 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-ID21LG7 Description: Volume E: (\Device\HarddiskVolume6) requires an Online Scan. An Online Scan will automatically run as part of the next scheduled maintenance task. Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.[/quote] Code: Event[2672]: Log Name: System Source: Disk Date: 2018-01-16T22:02:28.994 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x2a24a70 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2673]: Log Name: System Source: Disk Date: 2018-01-16T22:02:29.244 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x69781f8 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2674]: Log Name: System Source: Disk Date: 2018-01-16T22:02:29.995 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0xc102250 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2675]: Log Name: System Source: Disk Date: 2018-01-16T22:02:30.496 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0xb64f562 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2676]: Log Name: System Source: Disk Date: 2018-01-16T22:02:30.496 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x4e1ff68 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2677]: Log Name: System Source: Disk Date: 2018-01-16T22:02:37.509 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x5f0c88 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2678]: Log Name: System Source: Disk Date: 2018-01-16T22:02:44.273 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x290d870 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2679]: Log Name: System Source: Disk Date: 2018-01-16T22:02:48.780 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x59549e0 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2680]: Log Name: System Source: Disk Date: 2018-01-16T22:03:11.769 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x9d6f10 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2681]: Log Name: System Source: Disk Date: 2018-01-16T22:03:15.777 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x3ed12f8 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2682]: Log Name: System Source: Disk Date: 2018-01-16T22:03:26.547 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x6972dd0 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2683]: Log Name: System Source: Disk Date: 2018-01-16T22:03:27.298 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0xa26b78 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2684]: Log Name: System Source: Disk Date: 2018-01-16T22:03:27.799 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x5a25d8 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2685]: Log Name: System Source: Disk Date: 2018-01-16T22:03:29.302 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0xfa8058 for Disk 1 (PDO name: \Device\00000034) was retried.[/quote] Code: Event[2672]: Log Name: System Source: Disk Date: 2018-01-16T22:02:28.994 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x2a24a70 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2673]: Log Name: System Source: Disk Date: 2018-01-16T22:02:29.244 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x69781f8 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2674]: Log Name: System Source: Disk Date: 2018-01-16T22:02:29.995 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0xc102250 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2675]: Log Name: System Source: Disk Date: 2018-01-16T22:02:30.496 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0xb64f562 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2676]: Log Name: System Source: Disk Date: 2018-01-16T22:02:30.496 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x4e1ff68 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2677]: Log Name: System Source: Disk Date: 2018-01-16T22:02:37.509 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x5f0c88 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2678]: Log Name: System Source: Disk Date: 2018-01-16T22:02:44.273 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x290d870 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2679]: Log Name: System Source: Disk Date: 2018-01-16T22:02:48.780 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x59549e0 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2680]: Log Name: System Source: Disk Date: 2018-01-16T22:03:11.769 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x9d6f10 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2681]: Log Name: System Source: Disk Date: 2018-01-16T22:03:15.777 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x3ed12f8 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2682]: Log Name: System Source: Disk Date: 2018-01-16T22:03:26.547 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x6972dd0 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2683]: Log Name: System Source: Disk Date: 2018-01-16T22:03:27.298 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0xa26b78 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2684]: Log Name: System Source: Disk Date: 2018-01-16T22:03:27.799 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0x5a25d8 for Disk 1 (PDO name: \Device\00000034) was retried.Event[2685]: Log Name: System Source: Disk Date: 2018-01-16T22:03:29.302 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The IO operation at logical block address 0xfa8058 for Disk 1 (PDO name: \Device\00000034) was retried.[/quote]
    Code: Event[1604]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2018-01-14T07:53:56.307 Event ID: 98 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-ID21LG7 Description: Volume C: (\Device\HarddiskVolume4) requires an Online Scan. An Online Scan will automatically run as part of the next scheduled maintenance task. Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "[/quote]
     
    zbook, Jan 16, 2018
    #5
  6. Fcao Win User
    Thanks for the assistance. Hopefully I have everything you asked for. I know this isn't technically a BSOD, but I saw other people referred here for freezing issues.

    5) Chkdsk found some issues, but I'm not sure how significant they are. I ran chkdsk recently and it came back with no issues. My computer keeps demanding chkdsk because I keep having to force it to shut down. I think chkdsk already fixed the issue with drive E:. For the included file, I ran chkdsk on C:, where the problem is. I know there are disk errors that show up in the event viewer, but I have tried switching hard drives.

    7) Is there a particular reason I uninstalled Comodo? I can't click the Comodo link because I need my registration to be approved first.

    8) I have backed up my important files. I do not really have a backup image. Although, there may be a windows 7 image in my system reserved partition. I can perform a clean install. I have done several already. My problem started when I booted the computer at the beginning of January after not using it for a couple of months. I am pretty sure that windows updated to 1709 shortly after that. That is about when this problem started. I have since tried removing 1709. Currently, windows says my build version is 1703, so I believe I was successful.

    16) I don't think your instructions are clear for these directions. I cannot right click on startup type at all. I can only open properties for individual startup types. I also do not see the name "windows error reporting service" anywhere. I included a picture of the window in case that helps, but I am unclear on what you need me to do.
     
  7. zbook New Member
    For startup and recovery > system failure > un-check automatically restart
    For startup and recovery > default operating system > check time to display list of operating system 30 sec
    For Ccleaner > un-check memory dumps and windows log files
    The chkdsk was from 1/14/2018.
    Please repeat the chkdsk /x /f /r on each partition/drive:


    C:\Windows\system32>chkdsk /x /f /r
    The type of the file system is NTFS.
    Cannot lock current drive.


    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot

    In the left lower corner search type services > view the row for windows error reporting service > scroll to the startup type column > right click > left click on properties > post an image into the thread

    For the clean install the operating system will be upgraded to 1709.

    If you want to make a backup image that can be done with Macrium: (free edition)
    Macrium Software | Macrium Reflect Free

    There are default settings after a clean install that will need to be modified as above.

    After the clean install allow Windows updates. Do not install any drivers, software, applications, firewalls , etc.
    Report into the thread whether there is freezing when using only Windows updates of non-Microsoft drivers.

    If there is no freezing plan to add the drivers slowly and see if there is any freezing. For example adding 1 driver every four hours.

    Eventually the computer should have a clean install and all up to date drivers and no files and no applications.

    The aim is to eliminate or reduce confounding factors.
    So take this at a slow pace so that you have a good sense of the before and after for each driver.

    So none of the individual modifications need to be made now if you are going to perform a clean install. After the clean install check these areas to make the modifications.

    Please fix the file system on the drives with chkdsk /x /f /r before performing the clean install.


    Clean Install Windows 10 Installation Upgrade Tutorials
    Download Windows 10


    Please run this log collector now and post a zip into the thread:
    log collector v2-beta08.zip
     
    zbook, Jan 16, 2018
    #7
  8. Fcao Win User

    Constant freezing/lockups with mouse/keyboard usage in windows 10

    I don't know why you only ended up with chkdsk from 1/14. It really only wanted to give me that chkdsk for some reason. I think chkdsk for all drives should now be included, but I had trouble getting powershell to put them into a text file. I am still having trouble figuring out what you want me to do with windows error reporting service. I don't see windows error reporting service when I search for services. I have included a screenshot of that. Should I do the fresh install now or after I include the screenshot of windows error reporting service? What do you mean by fixing the file system before doing a fresh install? You mean run chkdsk first? I will have to edit this post with the log collector because I have to restart first. I did the other things you asked.

    Edit: The log collector file is now uploaded.
     
  9. zbook New Member
    The drive file systems have been fixed.
    All of the Windows default settings will be modified as needed after the clean install.
    The fixing of the drive file system and the clean install will eliminate many confounding factors.

    Powershell is not needed at this time.

    The logs reported problems with Windows defender:
    Code: Event[3242]: Log Name: System Source: Service Control Manager Date: 2018-01-17T14:49:02.703 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-ID21LG7 Description: The Windows Defender Antivirus Service service failed to start due to the following error: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.[/quote] The drives are using MBR which is Legacy BIOS.
    UEFI BIOS is faster and offers higher security.
    If you want to you can modify the BIOS to UEFI before the clean install.
    The format will then be GPT.
    With GPT you can have more partitions too.

    Was the Windows upgraded from 7 or 8 during the free perriod or was it an OEM(original equipment manufacturer)?
     
    zbook, Jan 17, 2018
    #9
  10. Fcao Win User
    I will do a clean install. I haven't messed with the bios since the computer was built. I had help with building it so I had no idea it wasn't UEFI bios. I originally bought windows 7 when I built the computer about 5 years ago. I originally bought a 120gb hard drive. It was too small for my needs so I made an image/backup of the drive and transferred everything to a 500 gb drive. I more or less left the 120gb drive alone because I had a 1tb hard disk drive for storage. The 500gb drive was updated during the free windows 8.1 upgrade and then again during the free windows 10 upgrade. The 120gb drive just sat at windows 7 because I never bothered to upgrade it. This computer has been running windows 10 stable for a long time now. I didn't just recently upgrade.
     
  11. zbook New Member
    zbook, Jan 17, 2018
    #11
  12. Fcao Win User
    Hmmm. I appreciate the link, but I've already struggled through the hell of making the drive convert. Guides didn't work for whatever reason. Anyway, I think I made it work. I'm now testing to see if it crashes before installing anything.
     
  13. Fcao Win User

    Constant freezing/lockups with mouse/keyboard usage in windows 10

    Just as update. So far there haven't been any freezing issues. I have been very slowing installing things. My computer was switched to uefi, but loads a lot slower. It's something like 30-45 sec slower. Is that normal? I'll post another update if the computer starts freezing again or if I get everything installed. It will take a while going at this slow pace.
     
  14. zbook New Member
    Please post a zip for troubleshooting:
    log collector v2-beta08.zip
     
    zbook, Jan 17, 2018
    #14
  15. Fcao Win User
    Alright. I also included a couple of screen shots relating to my hard drive. For some reason I cannot access it and cannot convert it to gpt. I can't even wipe it. The total size is listed as 0kb.
     
Thema:

Constant freezing/lockups with mouse/keyboard usage in windows 10

Loading...
  1. Constant freezing/lockups with mouse/keyboard usage in windows 10 - Similar Threads - Constant freezing lockups

  2. Mouse constantly freezing

    in Windows 10 Gaming
    Mouse constantly freezing: My mouse is constantly freezing during log-in. It's a pain so help.Appreciate it, I updated my mouse drivers but it didn't seem to fix my mouse.Thanks, have a good day...
  3. Mouse constantly freezing

    in Windows 10 Software and Apps
    Mouse constantly freezing: My mouse is constantly freezing during log-in. It's a pain so help.Appreciate it, I updated my mouse drivers but it didn't seem to fix my mouse.Thanks, have a good day...
  4. Mouse and Keyboard freezing

    in Windows 10 Drivers and Hardware
    Mouse and Keyboard freezing: I experience frequent every 30 seconds or so a lag, or rather a freeze of both mouse and keyboard simultaneously. Pointer frezes, kebyoard entry stops mid-typing. Lasts for a second or three. When it relieves, it kind of sheds the buffers: mouse jumping to a point where it...
  5. Mouse and Keyboard freezing

    in Windows 10 Software and Apps
    Mouse and Keyboard freezing: I experience frequent every 30 seconds or so a lag, or rather a freeze of both mouse and keyboard simultaneously. Pointer frezes, kebyoard entry stops mid-typing. Lasts for a second or three. When it relieves, it kind of sheds the buffers: mouse jumping to a point where it...
  6. mouse & keyboard lockup

    in Windows 10 BSOD Crashes and Debugging
    mouse & keyboard lockup: I went from v1909 to 20H2 and a couple of times my mouse and keyboard froze. Since it never happened with v1909 I can only assume it is the 20H2 'upgrade'. I don't believe it was a memory issue since I was only surfing with a couple of Edge tabs and Excel open, and I do have...
  7. Constant BSOD and lockups.

    in Windows 10 BSOD Crashes and Debugging
    Constant BSOD and lockups.: I am getting random BSOD errors. All drivers, bios, and windows are updated. I'm starting to the extreme i9 processors are just unstable.. Windows Version 10.0.18363 Build 18363 DESKTOP-MMN0NHO-(2020-04-25_17-42-32).zip 155116
  8. Keyboard and mouse freezing

    in Windows 10 Ask Insider
    Keyboard and mouse freezing: Hey all, after some advice! New system, fresh install of win 10, after bootup all is great and after about 5 minutes, both keyboard and mouse freeze? Both are still showing powered and connected. reinstalled drivers, and clean re-install later. Same problem. Anyone...
  9. Mouse freezes constantly

    in Windows 10 Drivers and Hardware
    Mouse freezes constantly: this started about a week ago - the mouse pointer will intermittently freeze. it happens in all applications, so is likely Windows related. I have not installed/upgraded any software myself at that time auto updates may have happened . its completely random. Sometimes it wont...
  10. Mouse and Keyboard Freeze on Windows 10

    in Windows 10 BSOD Crashes and Debugging
    Mouse and Keyboard Freeze on Windows 10: After auto update to version 1903 on 64 bit processor, the computer freezes when keyboard or mouse is left idle for 2 to 5 minutes. How do I resolve this problem?...