Windows 10: Windows 10 Pro (64-bit) Keeps Freezing/Locking up


  1. Posts : 6
    Windows 10 Pro x64 ( build 16299.19, version 1709)
       1 Week Ago #1

    Windows 10 Pro (64-bit) Keeps Freezing/Locking up


    I've been getting this issue as of late and I don't know why. Contrary to what seems to be the popular case, I did not suffer through this when I installed the first creators update.

    I've run through certain tests involving file system checks, memory checks, and other software checks (e.g. BIOS, firmware, etc.). I've also checked hardware and given the other posts regarding this issue as of late, I sincerely doubt that it's a hardware malfunction.

    I've made double sure that the most obvious drivers are up to date. I've updated everything I can possibly think of, including my VPN client.

    Incidentally, this issue has only initiated when I had Firefox running. I assumed after the 2nd time that it was due to multimedia content--thusly relating to my video drivers & Firefox--but the third time did not occur with any multimedia being loaded. I simply started Firefox and my machine froze. Left it for an hour and it stayed that way. It's only happened three times so far.

    What's bothering me is that I've been checking the logs to see if anything could clue me in on what's causing this to happen, but just as it occurred to many who suffered through the first creator's update bug, I cannot pinpoint this darn catalyst.

    In my case, this happens randomly. There is no time-bound expectation for this.

    Whatever it is, however, it appears to only be activated when Firefox is running. Whether or not that's accurate needs to be verified.

    I have included an attachment of the files requested for aid in this situation (as per the forum suggestions).

    What can I do to further test this?

    I can only assume Microsoft will eventually get whiff of this seeing as I'm not the only one with this issue.

    It might also be worth mentioning that I cannot rollback to an earlier build due to the fact that I deleted that contingency with the disk cleanup utility. My only option now is to refresh my system or wait to get a fix for this.

    For my sake, I sincerely hope it's sooner than later.

    I'd rather avoid refreshing, but if I must, I will do so.

    ATTACHMENT:
    BRYAN-AMD-Mon_11_06_2017_213913_90.zip
      My ComputerSystem Spec


  2. Posts : 5,345
    Windows 10 Pro X64 16299.19
       1 Week Ago #2

    Zip file contains no dumps. All I can see in Event Viewer output looks like a problem occurred right after you returned from sleep mode:
    Code:
    Event[1467]:
      Log Name: System
      Source: Microsoft-Windows-Power-Troubleshooter
      Date: 2017-11-06T15:27:37.956
      Event ID: 1
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-19
      User Name: NT AUTHORITY\LOCAL SERVICE
      Computer: Bryan-AMD
      Description: 
    The system has returned from a low power state.
    
    Sleep Time: ?2017?-?11?-?06T20:22:30.511311300Z
    Wake Time: ?2017?-?11?-?06T20:27:35.951672700Z
    
    Wake Source: Unknown
    
    Event[1468]:
      Log Name: System
      Source: Microsoft-Windows-DistributedCOM
      Date: 2017-11-06T15:30:38.574
      Event ID: 10010
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: Classic
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: Bryan-AMD
      Description: 
    The server {784E29F4-5EBE-4279-9948-1E8FE941646D} did not register with DCOM within the required timeout.
    
    Event[1469]:
      Log Name: System
      Source: Microsoft-Windows-DNS-Client
      Date: 2017-11-06T15:43:17.611
      Event ID: 1014
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-20
      User Name: NT AUTHORITY\NETWORK SERVICE
      Computer: Bryan-AMD
      Description: 
    Name resolution for the name www.nzblokes.co.nz timed out after none of the configured DNS servers responded.
    
    Event[1470]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-General
      Date: 2017-11-06T17:27:35.768
      Event ID: 12
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: Bryan-AMD
      Description: 
    The operating system started at system time ?2017?-?11?-?06T22:27:35.489275000Z.
    
    Event[1471]:
      Log Name: System
      Source: EventLog
      Date: 2017-11-06T17:27:43.280
      Event ID: 6008
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Bryan-AMD
      Description: 
    The previous system shutdown at 3:30:16 PM on ?11/?6/?2017 was unexpected.
    Without a dump it's hard to determine what the cause is. I didn't see any indication any dumps were created in the Event log either.

    For now, I would suggest not using sleep or hibernate. Instead, setup a screen saver and have it turn off the screen after a set period of time.

    I don't know what memory test you ran but I suggest running memtest86+ as follows. You have 16GB so it will take quite awhile, 12 to 20 hours.

    ===================================================
    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses


    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.


    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.


    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

    Take a picture when done and post in the forum please.

    If that doesn't show any problems then test your GPU (Geforce GTX 750Ti 2GB):
    ===================================================
    Follow this tutorials to stress test your GPU:
    FurMark - GPU Stress Test - Windows 10 Forums

    If you have a AMD APU instead of a discreet GPU, try UNIGINE 3D Benchmark..

    ===================================================

    Let's see what those tests show us.

    Oh, please make sure your PC is configured for small dump files:

    How to Configure Windows 10 to Create Dump Files on BSOD
      My ComputersSystem Spec


  3. Posts : 6
    Windows 10 Pro x64 ( build 16299.19, version 1709)
    Thread Starter
       1 Week Ago #3

    Update:
    I have since had no incidents since my posting here. I've been putting my PC to sleep and letting it sleep on it's own. Incidentally, I do have a screensaver configured, but I also still have my power settings set to sleep after a predetermined time.

    I will run the memory tests with the recommended program today. I will aim for at least 10 passes and I will do the same tomorrow.

    I want to avoid testing my GPU as it seems the suggested program comes with risk. I just got this card.
      My ComputerSystem Spec


  4. Posts : 6
    Windows 10 Pro x64 ( build 16299.19, version 1709)
    Thread Starter
       1 Week Ago #4

    Update


    UPDATE:
    After running the test with memtest86, the result was that my RAM had no errors.

    The pictures of those results are the following:
    Click image for larger version. 

Name:	memtest86_1.PNG 
Views:	3 
Size:	1.50 MB 
ID:	163494Click image for larger version. 

Name:	memtest86_2.PNG 
Views:	2 
Size:	1.47 MB 
ID:	163495Click image for larger version. 

Name:	memtest86_3.jpg 
Views:	2 
Size:	83.4 KB 
ID:	163496

    I am reluctant to continue on with the graphics card test as I've weary of it. I realize that for hardware to be ruled out, conclusive tests must be administered, but this hardware is relatively new. I only purchased it about 9-10 months ago. I understand that doesn't guarantee anything with respect to reliability or faulty hardware, but given the fact that my memory is in good condition (supposedly), I'm willing to bet my GPU is just as fine. Also, considering the other reports being shown not only here, but on other board sites and similar, I can't say this is relating to hardware at all. At least, not as the root cause.

    Since I can't give access to dump files that don't exist, what else is there for me to do?

    Can I not check logs to determine anything? There must be something that can give me at least a clue. Something that suspects the software, not the hardware. This hasn't been happening until I installed the FCU. There must be some software defect causing this.
      My ComputerSystem Spec


  5. Posts : 8,733
    windows 10 professional version 1607 build 14393.969 64 bit
       1 Week Ago #5

    1) In the left lower corner search type system > 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 into the thread

    2) In the left lower corner search type clean > open disk cleanup > post an image of files to delete

    3) If you use Ccleaner or similar software to delete files please comment in the thread.

    4) Download and install Whocrashed > in the left upper corner above analyze click tools > click crash dump test > type: ACCEPT

    5) Click analyze > view report > run the DM log collector > post zip into the thread

    6) Open administrative command prompt and type or copy and paste:
    7) sfc /scannow
    8) dism /onlince /cleanup-image /restorehealth
    9) chkdsk /scan
    10) 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

    11) msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)

    12) taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)

    https://support.microsoft.com/en-us/...oot-in-windows
    How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

    13) shutdown /r (you will reboot the computer so that it is in clean boot)

    Evaluate the performance on your computer in clean boot during typical use.
    Are the boots faster or slower?
    Are the shutdowns faster or slower?
    How has the audio and video performance changed? Is it better, worse, or the same?
    How have the hangs or freezing changed? Are they better, worse, or the same?
    Continue using clean boot indefinitely to monitor performance.

    14) type control in the left lower corner search > click on control panel > click on large or small icons > click on troubleshooting > on the left pane click on view all > run the following windows troubleshooters:

    a) Hardware and Devices
    b) Video Playback
    c) Playing Audio > open audio enhancements > play test sounds > advanced > change sample rate > test multiple sample rates
    d) Recording Audio

    For each troubleshooter make sure that advanced is clicked to apply repairs automatically.
    For each troubleshooter click on view detailed information.
    Report any problems using images that were fixed or not fixed.
      My ComputerSystem Spec


  6. Posts : 5,345
    Windows 10 Pro X64 16299.19
       1 Week Ago #6

    Just thought I'd mention you did not run memtest86+ as asked. You ran memtest86. Different program and not the one we recommend testing with. It also needs to be run for at least 8 full passes as there have been many cases where failures occurred in the later passes.

    Let it slide for now. @zbook will ask if he thinks it's needed later. Good luck.
      My ComputersSystem Spec


  7. Posts : 6
    Windows 10 Pro x64 ( build 16299.19, version 1709)
    Thread Starter
       1 Week Ago #7

    @Ztruker
    The reason I opted for memtest86 was because I found a source that mentioned possible incompatibility with newer builds. Can't remember now which one it was mentioning as I was under the impression they were the same. One just being slightly outdated and the other wasn't.

    I was under the impression that the 8 passes would be run through the "test". It wasn't until I finished it the first time that I realized it only ran 4 passes and that I would effectively have to run 2 tests. Assuming memtest86+ follows in the same operations as the original program does, this would then require that I run two tests in total. Two tests. Not one. That will take time.

    To alleviate any doubt, I will run the test with memtest86+ tonight. I will undoubtedly receive the same result. I'll upload the results for that after I've done the other things zbook as asked.

    Right now, I'm almost positive this is a software issue. I need to determine why it happened and why it isn't happening anymore.
      My ComputerSystem Spec


  8. Posts : 6
    Windows 10 Pro x64 ( build 16299.19, version 1709)
    Thread Starter
       1 Week Ago #8

    Reporting in...


    @zbook
    My results so far are the following:

    1)
    Click image for larger version. 

Name:	defrag_1.PNG 
Views:	10 
Size:	15.1 KB 
ID:	163560
    2)
    Click image for larger version. 

Name:	defrag_2.PNG 
Views:	10 
Size:	19.8 KB 
ID:	163561Click image for larger version. 

Name:	degraf_3.PNG 
Views:	10 
Size:	18.9 KB 
ID:	163562
    3) I don't use CCleaner. I manage my stuff well and my build is pretty fast. SSDs bring me so much joy.

    4) I ran the crash test and wound up with two dump files. I'm assuming DM Log output will carry that in somehow.

    5) I will upload another archive of those files again.

    DM LOG: BRYAN-AMD-Sun_11_12_2017_155715_95.zip

    7) SFC results:
    Click image for larger version. 

Name:	defrag_4.PNG 
Views:	1 
Size:	26.1 KB 
ID:	163563

    8) dism results:

    Deployment Image Servicing and Management tool
    Version: 10.0.16299.15

    Image Version: 10.0.16299.19

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    9) chkdsk results:
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    502272 file records processed.
    File verification completed.
    5368 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    12544 reparse records processed.
    598614 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    12544 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    48172 data files processed.
    CHKDSK is verifying Usn Journal...
    36479680 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    233609215 KB total disk space.
    113112752 KB in 212531 files.
    150644 KB in 48173 indexes.
    0 KB in bad sectors.
    620775 KB in use by the system.
    65536 KB occupied by the log file.
    119725044 KB available on disk.

    4096 bytes in each allocation unit.
    58402303 total allocation units on disk.
    29931261 allocation units available on disk.

    As for the remainder, I will have to get back to you. That will take time.

    - T.R.G.
      My ComputerSystem Spec


 

Related Threads
I'm not sure why my PC is locking up,when it does,there is no sound, I have to hit my reset button..Let me know what I need to post to fix this
Hi, Launching an app such as weather or easy gmail will sometimes bring up the app, freeze on opening and never open and then I can't use the start menu anymore. I have tried running sfc, no problems. I have tried using the powershell to reinstall...
Hi all. Upgraded to W10 a month or so back from W7. Primary reason was I had a new 4K monitor (in addition to two 1080 displays), and the scaling in W10 was supposed to be a lot better. It is, but it's not perfect. Anyway, I can live with...
So I've recently bought a gaming package which had pre picked pc products to be built for me, as I do not know much about computers. This came with windows 8.1 pre installed. After having the pc for about a week it asked me if i wanted to...
When I have my webcam security software running all day (12-hours), the laptop runs fine. But when I shut the software down and then leave the laptop idle, it locks up. It also happens when I start the laptop up and just leave it sit idle. So...
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 04:05.
Find Us