Windows 10: Win10 16k Errors in Event Viewer in 7 days. Fresh Install 14 days ago

Discus and support Win10 16k Errors in Event Viewer in 7 days. Fresh Install 14 days ago in Windows 10 Performance & Maintenance to solve the problem; Hi, I am requesting help again. I am taking a bit of a different approach. While it will be declined, I will pay for the fix from an established... Discussion in 'Windows 10 Performance & Maintenance' started by Tonys317, Nov 15, 2017.

  1. Tonys317 Win User

    Win10 16k Errors in Event Viewer in 7 days. Fresh Install 14 days ago


    Hi,

    I am requesting help again. I am taking a bit of a different approach. While it will be declined, I will pay for the fix from an established member, if not declined you got it.

    Fresh install of Windows 10 which upgraded me to build 1709 (11/2/2017).
    5-8 months ago problems with disk usage spiking to 100%. Resources being "Hijacked"/stolen or lost(task manager). This has been an issue with many since Win 8. I've tried EVERY recommended fix. 3 people on MSTECHNET/MS Community said this spiking to 100% resource usage could be the cause of the other errors. Is there an out of the box fix?

    Picture is less than .1% of the errors. Image is just there as "proof of problem" not really for diagnostics in my mind. Also keep in mind event viewer was slammed with absurd amounts of errors prior to this fresh install (Weeks/Months ago). And the first week after the install (5-8ish months ago). This is a home PC, nothing special.

    What I have done. Hardware passes EVERYTIME:

    Checked Maleware with forums (Bleeping/Malewarebytes)
    CPUID: HWmonitor and Core Temp (Temps & Voltage PASS)
    Lifeguard WesternDigital's Hard Drive Diagnose (Pass); Tried HD Test program recommended here (Passed)
    MEMTEST & other "Passmark" diagnostic programs (Pass)
    Windows Maintance/Trouble Shooting (No Issues Found)
    Checked with Intel, Nvidia, Lenovo & all other device MANFS to verify 100% drivers are updated (DONE!)
    Visually inspected (No signs of heat damage, dust, no smells - PASS)

    In my unprofessional opinion this does not appear to be a hardware error. Are there any logs/reports I could share for advice?

    :)
     
    Tonys317, Nov 15, 2017
    #1
  2. WJJK Win User

    Windows 10 boot time not visible in event viewer

    About 3 weeks ago I installed Windows 10 on a PC that had Windows 7 running. Everything works fine but I can't find the boot time anymore in the event viewer. Just as in Windows 7 I go to the event viewer - Applications and services log - Microsoft - Windows
    - Diagnostics Performance - Operational and filter eventID = 100. All I get is an empty list. Apparently, boot time is not recorded. Shutdown time (eventID = 200) is recorded for a few days but most days is missing. Does anyone know what to do about this?
     
  3. Windows 10 Home: Start menu doesn't work, Right click doesn't work on Taskbar icons, Notification doésn't work, Clock not displayed.

    I did a system restore, re installed a fresh copy of Win10, the "solution" worked for a month, two days ago it started again Win10 16k Errors in Event Viewer in 7 days.  Fresh Install 14 days ago :(
     
    AndrésRuiz, Nov 15, 2017
    #3
  4. Win10 16k Errors in Event Viewer in 7 days. Fresh Install 14 days ago

    Hi Tonys317.

    Definitely not what you want. Is this a bought machine, if so what is the make and model? (Should be on sticker on box).

    If this is custom at some point you are likely going to have to open case and get MB make and model.

    Could you share Version and build number (Windows key + R, type winver, enter

    So you clean installed a few weeks backs. Did you check device manager after install to see if you have any yellow exclamation marks. Please open section headings.

    You likely install your software already, other than Malwarebytes what other AV products are you using?

    If you boot to safe mode, hold down shift key and click restart to get menu started, is the error occurring?

    Boot to Advanced Startup Options in Windows 10

    If not return to a normal boot and see if this happens with a clean boot.

    Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts


    Ken
     
    Caledon Ken, Nov 16, 2017
    #4
  5. clam1952 Win User
    clam1952, Apr 4, 2018
    #5
Thema:

Win10 16k Errors in Event Viewer in 7 days. Fresh Install 14 days ago

Loading...
  1. Win10 16k Errors in Event Viewer in 7 days. Fresh Install 14 days ago - Similar Threads - Win10 16k Errors

  2. Return after the 14 days?

    in Microsoft Windows 10 Store
    Return after the 14 days?: I purchased forza horizon 5 just under 6 months ago for pc. The game seemed fun at first but would run like garbage, even on a high end machine. I have only put in a few hours, as I keep coming back to the game every once in a while, hoping that it received a optimization...
  3. Return after the 14 days?

    in Windows 10 Gaming
    Return after the 14 days?: I purchased forza horizon 5 just under 6 months ago for pc. The game seemed fun at first but would run like garbage, even on a high end machine. I have only put in a few hours, as I keep coming back to the game every once in a while, hoping that it received a optimization...
  4. Return after the 14 days?

    in Windows 10 Software and Apps
    Return after the 14 days?: I purchased forza horizon 5 just under 6 months ago for pc. The game seemed fun at first but would run like garbage, even on a high end machine. I have only put in a few hours, as I keep coming back to the game every once in a while, hoping that it received a optimization...
  5. 1646 errors in the last 7 days in Event Viewer, how can I resolve these errors?

    in Windows 10 BSOD Crashes and Debugging
    1646 errors in the last 7 days in Event Viewer, how can I resolve these errors?: The server {9E175B6D-F52A-11D8-B9A5-505054503030} did not register with DCOM within the required timeout. The server {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} did not register with DCOM within the required timeout. These two errors are the common culprits, appears to generate...
  6. Fresh Win10 Install of 1 day and now BSOD....

    in Windows 10 BSOD Crashes and Debugging
    Fresh Win10 Install of 1 day and now BSOD....: I did a clean install of Win10 Pro yesterday, drivers all updated, my programs re-installed, no device manager problems... In the evening while browsing with FireFox on this forum and a second window open for another forum the system locked up and then BSOD........saying...
  7. BSOD on win10 (also 7) Multiple / day clean installs

    in Windows 10 BSOD Crashes and Debugging
    BSOD on win10 (also 7) Multiple / day clean installs: Getting BSOD on Win7, Win10 both while gaming. replaced graphics card (twice) 2 different cards. ntoskrnl.exe was one I recall. Maybe causing memory corruption now. Typically only occurs using ArchAge Game. reinstalled game a few times as well. reinstalled windows 7 4 times,...
  8. Event Viewer Error on fresh install startup. Struggle to Game

    in Windows 10 Support
    Event Viewer Error on fresh install startup. Struggle to Game: Hello, I've been having issues for the past year. I built my starter gaming pc and I installed Windows 8.1 Pro. I was having issues playing games mostly Ubisoft games whether they booted directly from Uplay or steam. So I decided to upgrade to windows 10 pro using the free...
  9. Fresh Win 10 install Event Viewer Errors

    in Windows 10 Support
    Fresh Win 10 install Event Viewer Errors: Got a reoccurring problem with my pc shutting down unexpectedly. Thought it might be a corrupt install so i reinstalled windows 10 and the errors came back anyway. Then after a couple re-installs later and bunch of research i still came up with nothing. So i installed my...
  10. 3 Day old Win 10 Install 400+ Errors in Event Viewer

    in Windows 10 Support
    3 Day old Win 10 Install 400+ Errors in Event Viewer: Title about sums it up. Fresh windows 10 Professional 64bit install. I installed the GPU Tweak II software for my GTX 980 ti which required a system restart to complete. While restarting, an error message popped up (one of the 0x08xxxxxxxx type of errors) but then...