Page 19 of 77 FirstFirst ... 917181920212969 ... LastLast

  1. Joined : Nov 2015
    Posts : 181
    Windows 10 Pro x64
       08 Nov 2015 #181

    Anabase61 said: View Post
    No SSD. And the update is: Freeze at 16:30 and at 16:33, just after rebooting and login. No time to do anything, screen frozen. The system is 3 days old, and was delivered with Windows 10 directly (not an upgrade), i assume ASUS did a clean install as i'm not able to do it again, the system not being delivered with an OS distribution media. Not much OEM drivers on this machine. ASUS MB and ASUS Graphic card, Toshiba HD, and i don't know the RAM brand as i don't want to open the box yet (i will lose the warranty), that's it.
    I also removed all extra software installed for free on this machine because i don't need and don't trust it. Meaning remains W10 (fully patched, Office 2013, Avast and Chrome).....I haven Electronic Engineer diploma from 1984, have spent 32 years in IT with broad technical background, and now i don't have any clue on how to move forward.

    I am open to any suggestions.
    Have you looked at the event logs yet (Win + R, then eventvwr.msc then OK) There will be 5 main categories (Applications, System, etc.) under Windows Logs, and starting with Applications, select to filter the current log and tick the boxes for Critical, Warning, and error.

    If you remember around what time of day the freezes happened, check the log around those times. If you don't remember, and the hangs begin again, make a note of the time and once rebooted, check the event viewer (using the filter from above) to see what's causing issues.

    If you find it's an issue with Windows itself, there is a known issue that causes explorer.exe hangs and corrupted context menus that was fixed weeks ago on the Insider builds, of which should be pushed out to non-insiders this Tuesday encompassed within the large update for Windows 10
      My System SpecsSystem Spec


  2. Joined : Nov 2015
    Posts : 3
    Windows 10 64bits (French)
       08 Nov 2015 #182

    JW0914 said: View Post
    Have you looked at the event logs yet (Win + R, then eventvwr.msc then OK) There will be 5 main categories (Applications, System, etc.) under Windows Logs, and starting with Applications, select to filter the current log and tick the boxes for Critical, Warning, and error.

    If you remember around what time of day the freezes happened, check the log around those times. If you don't remember, and the hangs begin again, make a note of the time and once rebooted, check the event viewer (using the filter from above) to see what's causing issues.

    If you find it's an issue with Windows itself, there is a known issue that causes explorer.exe hangs and corrupted context menus that was fixed weeks ago on the Insider builds, of which should be pushed out to non-insiders this Tuesday encompassed within the large update for Windows 10
    Sure i did, before even looking on the net. There is a few Error 56 which had been mentioned above in this forum, but interestingly and unfortunately, this error doesn't happen not systematically, the last freeze didn't come with Error 56. Nothing relevant in Application logs (as there is not much remaining applications anyway). the last system hang happned today at 10:26, 10:42, 11:51; 16:30, 16:34 (GMT+1). And this doesn't give me any clue either. Now it's dusk, i will go cooking, and see what's going on tomorrow morning. Whatever monster update will come on coming Patch Tuesday will be welcome anyway.
      My System SpecsSystem Spec


  3. Joined : Aug 2015
    Posts : 15
    windows 10 build 10240
       09 Nov 2015 #183

    Having the same problems here as well. Random lock-ups, screens go into sleep mode, reboots out of nowhere. I know my system was solid on windows 7. It's really starting to get annoying. I've tested my my hardware all to come back with no issues. Try latest drivers, windows 10 is really starting to get on my nerves. Microsoft has to get on this.. I read up on a lot of forums with people having the same problems but no solution. I'm seriously thinking of Ubuntu, or ANYTHING other than windows 10. really disappointed with microsoft, considering the windows 10 beta was more stable than the final release.
      My System SpecsSystem Spec


  4. Joined : Nov 2015
    Posts : 181
    Windows 10 Pro x64
       09 Nov 2015 #184

    Most of the issues you and others are reporting have been fixed weeks ago on the Insider builds... if you'd like to get them fixed, simply take the insiders build. Privacy issues most, like me, were concerned about, such as the keylogger, are now able to be disabled via privacy settings without disqualifying you from being on the insider builds.

    With that said, there is a large update being pushed publicly on this week's patch tuesday that should include most of the coding fixes that took effect on insiders builds from weeks past.

    While the issues you and others have could very well be coding bugs in Windows 10, many are due to third party software and drivers. I understand most aren't power users; however, to complain about this problem and that problem, while refusing to actually troubleshoot your problem by reviewing, and then researching, what errors are being recorded in the event logs, you lose the privilege to be taken seriously and paid attention to.
    • This doesn't mean your experience or what you have to say isn't important, it's simply a point that if you refuse to help yourself, you shouldn't expect someone else to help you.

    The fact alone that most who've clean installed and troubleshooted their event logs don't have the massive range of issues experienced speaks for itself.

    scotto1682 said: View Post
    ...screens go into sleep mode, reboots out of nowhere.
    This isn't a bug and is due to either settings within Control Panel or Settings, or it's user error. Windows would show a BSOD if it rebooted out of nowhere due to software issues, with the only other issue able to cause random reboots is a hardware issue, such as a faulting HDD, overheating, etc (of which you've stated you've ruled out hardware). Either way, it it was due to a software or hardware error, it would be recorded in the event logs.
    scotto1682 said: View Post
    ...I know my system was solid on windows 7.
    You're speaking to an OS that's almost a decade old, is at it's end of life, and shortly will no longer be supported. One would naturally assume an OS that old would be more stable than an OS only a few months old.
    scotto1682 said: View Post
    ...Windows 10 beta was more stable than the final release.
    Mainly because Windows 8/8.1 drivers were still able to be used up until a certain point in the build process. Windows 8/8.1 drivers and their system files, such as dll's, are not compatible with Windows 10 in any way, shape or form.

    • The majority of issues currently experienced (especially when the problems are varied and affecting numerous processes within the OS) are almost always due to third party software and/or driver issues, where either the end user installed Windows 8/8.1 drivers, or OEMs and manufacturers have included Windows 8/8.1 dll's and system files in their Windows 10 driver packages
      • Broadcom/Dell both did so for Broadcom's latest AC wifi card, rendering any Windows 10 system with that card and Windows 10 drivers package installed completely unstable with BSODs every 15 - 60 min.
      • This is one of the main reasons why once you've upgraded and verified your device's hardware ID is registered and activated (i.e. Windows is activated), it's highly recommended to clean install after backing up your personal files (if you use the system partition for storing your user files, as it's recommended to move all user file folders to a non-system partition).
        • ​You'll want to ensure, prior to reformatting the system partition during install, you copy the %appdata% folder from each user's user folder. While most of the files in the appdata folder will not be needed, there are files in that folder you will probably want to save (many applications store your customization files in the appdata folder)
    Last edited by JW0914; 09 Nov 2015 at 13:23.
      My System SpecsSystem Spec


  5. Joined : Nov 2015
    Posts : 1
    Windows 10
       09 Nov 2015 #185

    Look to your antivirus


    Having had a row with McAfee over refund uninstalled and downloaded Avira. Can't tell you the number of problems found and fixed - when McAfee was saying 'everything fine' 20 minutes before. Seems to have fixed the problem for me. Win 10 now running like a dream! No more freezes and FAST. So look to your antivirus. Hope this helps. Know not much if have one that's not great and have long active subscription. I lost money, but Boy was is worth it!

    Keepoman said: View Post
    Hi! I have been getting these random freezes a couple of times now which locks up the entire system and forces me to do a hard restart and i have tried EVERYTHING to resolve it, but no luck. I tried updating all drivers to the newest, did a sfc /scannow which repaired all the corrupt files, firmware update of HDD and defragging the HDD.
    I know there is nothing wrong with my hardware because this ONLY happens in Windows 10 and not in Windows 8.1. This is the 2nd time i'm installing Windows 10 to see if the issue was resolved somehow, but nope. Also tried with a upgrade and with a clean install 2 times.

    Does anyone have any tips or fixes for this? It's really starting to drive me crazy..
      My System SpecsSystem Spec


  6. Joined : Aug 2015
    Posts : 15
    windows 10 build 10240
       09 Nov 2015 #186

    JW0914 said: View Post
    Most of the issues you and others are reporting have been fixed weeks ago on the Insider builds... if you'd like to get them fixed, simply take the insiders build. Privacy issues most, like me, were concerned about, such as the keylogger, are now able to be disabled via privacy settings without disqualifying you from being on the insider builds.

    With that said, there is a large update being pushed publicly on this week's patch tuesday that should include most of the coding fixes that took effect on insiders builds from weeks past.

    While the issues you and others have could very well be coding bugs in Windows 10, many are due to third party software and drivers. I understand most aren't power users; however, to complain about this problem and that problem, while refusing to actually troubleshoot your problem by reviewing, and then researching, what errors are being recorded in the event logs, you lose the privilege to be taken seriously and paid attention to.
    • This doesn't mean your experience or what you have to say isn't important, it's simply a point that if you refuse to help yourself, you shouldn't expect someone else to help you.

    The fact alone that most who've clean installed and troubleshooted their event logs don't have the massive range of issues experienced speaks for itself.

    This isn't a bug and is due to either settings within Control Panel or Settings, or it's user error. Windows would show a BSOD if it rebooted out of nowhere due to software issues, with the only other issue able to cause random reboots is a hardware issue, such as a faulting HDD, overheating, etc (of which you've stated you've ruled out hardware). Either way, it it was due to a software or hardware error, it would be recorded in the event logs.

    You're speaking to an OS that's almost a decade old, is at it's end of life, and shortly will no longer be supported. One would naturally assume an OS that old would be more stable than an OS only a few months old.

    Mainly because Windows 8/8.1 drivers were still able to be used up until a certain point in the build process. Windows 8/8.1 drivers and their system files, such as dll's, are not compatible with Windows 10 in any way, shape or form.

    • The majority of issues currently experienced (especially when the problems are varied and affecting numerous processes within the OS) are almost always due to driver issues where either the end user installed Windows 8/8.1 drivers, or OEMs and manufacturers have included Windows 8/8.1 dll's and system files in their Windows 10 driver packages
      • Broadcom/Dell both did so for Broadcom's latest AC wifi card, rendering any Windows 10 system with that card and Windows 10 drivers package installed completely unstable with BSODs every 15 - 60 min.
      • This is one of the main reasons why once you've upgraded and verified your device's hardware ID is registered and activated (i.e. Windows is activated), it's highly recommended to clean install after backing up your personal files (if you use the system partition for storing your user files, as it's recommended to move all user file folders to a non-system partition).
        • ​You'll want to ensure, prior to reformatting the system partition during install, you copy the %appdata% folder from each user's user folder. While most of the files in the appdata folder will not be needed, there are files in that folder you will probably want to save (many applications store your customization files in the appdata folder)

    So, update. I don't experience BSOD. i did have an issue with my monitors just shutting down, system still seems to be running, but cannot get my screens back. after adjusting some voltages within my bios that issued has cleared up. now my only main issue is mouse and keyboard become unresponsive. I have them both plugged directly to the USBs on the PC itself. I have only used the drivers provided by Microsoft, and a windows 10 Display driver from Nvidia. I do have a few legacy components hooked up. an old logitech webcam(which drivers came from Microsoft) and a dell USB hub that's built into my monitor. I checked my event viewer, it has an Event 12 HAL error, and an event 10010 DistributedCOM telling me the cortanaUI app failed to register with DCOM.. with the Event 12 it says I would more than likely have to update my system firmware, but I'm already running the latest BIOS for my board. (ASUS striker II extreme BIOS version 1402) I'm going to try running the SFC, see if that comes up with anything. But for updating my BIOS I'm at a loss, unless I contact ASUS about my BIOS. is there any setting that should be adjusted within windows 10 to operate smoothly with legacy BIOS since I don't have a UEFI? Honestly I've been busting my head for the past couple months with these issues, so please don't say I haven't been trying to help myself. Any help would be appreciated. I'll post back if file check comes up with anything corrupt, also getting insider builds from this point on. thanks!

    UPDATE: did a complete scan of any corrupt files, came back no issues there.
    Last edited by scotto1682; 09 Nov 2015 at 13:47.
      My System SpecsSystem Spec


  7. Joined : Nov 2015
    Posts : 181
    Windows 10 Pro x64
       10 Nov 2015 #187

    scotto1682 said: View Post
    So, update. I don't experience BSOD. i did have an issue with my monitors just shutting down, system still seems to be running, but cannot get my screens back. after adjusting some voltages within my bios that issued has cleared up. now my only main issue is mouse and keyboard become unresponsive. I have them both plugged directly to the USBs on the PC itself. I have only used the drivers provided by Microsoft, and a windows 10 Display driver from Nvidia. I do have a few legacy components hooked up. an old logitech webcam(which drivers came from Microsoft) and a dell USB hub that's built into my monitor. I checked my event viewer, it has an Event 12 HAL error, and an event 10010 DistributedCOM telling me the cortanaUI app failed to register with DCOM.. with the Event 12 it says I would more than likely have to update my system firmware, but I'm already running the latest BIOS for my board. (ASUS striker II extreme BIOS version 1402) I'm going to try running the SFC, see if that comes up with anything. But for updating my BIOS I'm at a loss, unless I contact ASUS about my BIOS. is there any setting that should be adjusted within windows 10 to operate smoothly with legacy BIOS since I don't have a UEFI? Honestly I've been busting my head for the past couple months with these issues, so please don't say I haven't been trying to help myself. Any help would be appreciated. I'll post back if file check comes up with anything corrupt, also getting insider builds from this point on. thanks!

    UPDATE: did a complete scan of any corrupt files, came back no issues there.
    While I did reply directly to your post, the comment about refusing to troubleshoot wasn't directed at you personally, but directed at all who read it. In the future, if you've done troubleshooting, please post what troubleshooting you've done, as well as if you're seeing any errors in the event log (exactly what you did in the reply above).

    Contacting ASUS for beta firmware is probably not going to garnish a result, as as soon as they release an updated version, if will be automatically updated on their drivers site for your model of device.

    As far as your monitor goes, if the issue does come back after you've already adjusted settings within the BIOS, the most likely cause would be a drivers issue or a bad cable. If you took Nvidia's driver through Windows Update, download the most recent WHQL driver from Nvidia's site directly and update the driver with that setup package. If you have a different cable on hand, swap it out, however if you don't, don't immediately go out and buy one - verify first whether or not the drivers directly from Nvidia solved the issue.

    Have you verified if any errors (yellow question marks) are showing up in device manager? While I mentioned it above in reference to nvidia, if a manufacturer offers drivers on their support site, it's always recommended to utilize those in lieu of the generic ones downloaded via Windows Update. In addition to being generic, Windows Update drivers will also generally not be the most recent drivers available.

    As to the keyboard and mouse, is it a regular run of the mill keyboard, or does it have macro buttons, assignable or otherwise? If so, see if there's a driver's update from the manufacturer of the keyboard. If it is just a regular, run of the mill keyboard:

    • Power down the system and unplug the main power cord (if a laptop, remove the battery as well), hold down the power button for 30 seconds, release, plug power cord back in, and turn the system on. If the problem still exists, proceed below.
    • If this is a desktop, and the USB ports are on a pcie card, turn the system off, unplug the main power cable, hold the power button down for 30 seconds, open the case, unseat, then reseat the pcie card, close the case, plug power cord back in, and turn on the system. If the problem still exists, proceed below.
    • Verify if the issue occurs if the keyboard and mouse are plugged into different USB ports (try the ones on your monitor)
    • Hook a different device (preferably a keyboard or mouse, however any device should do) into the USB ports the mouse and keyboard are currently connected to, and see if the other device becomes non-responsive as well. The webcam would be a perfect way to do so, as you can simply turn it on and verify via the small preview window whether or not it freezes up. Make sure you leave it connected for 2x as long as it takes for the unresponsive issues to occur with the keyboard and mouse (this ensures you've left it connected long enough to replicate the issue)


    While it would be out of the ordinary for both a keyboard and mouse to both fail at the time same time, if they were a package deal when you bought them, it would be a good idea to rule them out by connecting them to a different device to verify if the issue goes away (preferably another device running Win 10).
    Last edited by JW0914; 10 Nov 2015 at 09:01.
      My System SpecsSystem Spec


  8. Joined : Nov 2015
    Posts : 2
    Windows 10
       10 Nov 2015 #188

    Hey I've been following this thread along and found this is my eventvwr.msc:
    Code:
    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          11/9/2015 5:43:35 PM
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (35184372088832),(2)
    User:          SYSTEM
    Computer:      Tim-PC
    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.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
        <EventID>41</EventID>
        <Version>3</Version>
        <Level>1</Level>
        <Task>63</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000200000000002</Keywords>
        <TimeCreated SystemTime="2015-11-09T16:43:35.861475200Z" />
        <EventRecordID>134559</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>Tim-PC</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">0</Data>
        <Data Name="BugcheckParameter1">0x0</Data>
        <Data Name="BugcheckParameter2">0x0</Data>
        <Data Name="BugcheckParameter3">0x0</Data>
        <Data Name="BugcheckParameter4">0x0</Data>
        <Data Name="SleepInProgress">0</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
        <Data Name="BootAppStatus">0</Data>
      </EventData>
    </Event>
    This occurs everytime my pc freezes. It happened twice last 7 days.
    Any idea what causes this, it's quite annoying :P

    EDIT: it might also be me pressing the hard reset button ?
      My System SpecsSystem Spec


  9. Joined : Nov 2015
    Posts : 181
    Windows 10 Pro x64
       10 Nov 2015 #189

    timvosch said: View Post
    Hey I've been following this thread along and found this is my eventvwr.msc:
    Code:
    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          11/9/2015 5:43:35 PM
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (35184372088832),(2)
    User:          SYSTEM
    Computer:      Tim-PC
    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.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
        <EventID>41</EventID>
        <Version>3</Version>
        <Level>1</Level>
        <Task>63</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000200000000002</Keywords>
        <TimeCreated SystemTime="2015-11-09T16:43:35.861475200Z" />
        <EventRecordID>134559</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>Tim-PC</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">0</Data>
        <Data Name="BugcheckParameter1">0x0</Data>
        <Data Name="BugcheckParameter2">0x0</Data>
        <Data Name="BugcheckParameter3">0x0</Data>
        <Data Name="BugcheckParameter4">0x0</Data>
        <Data Name="SleepInProgress">0</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
        <Data Name="BootAppStatus">0</Data>
      </EventData>
    </Event>
    This occurs everytime my pc freezes. It happened twice last 7 days.
    Any idea what causes this, it's quite annoying :P

    EDIT: it might also be me pressing the hard reset button ?
    If your hard reset button immediately reboots the PC, and this event error occurs immediately following the hard reset, then yes the hard reset would be the cause of a dirty power down error.

    Unless a system is frozen and completely unresponsive for more than 10 minutes (unless you're RAM utilization is in the 90% range), it's ill-advisable to do a dirty power down [hard reset]. Whenever you shutdown or reboot, a specific flag is added to a file in the winsxs folder and this flag controls and directs Windows to do a specific set of operations during the shutdown or reboot, of which are entirely skipped when a dirty power down occurs. There are times when that's the only way to solve an unresponsiveness issue, however it should always be used as a last resort. If a dirty power down does occur, once you're back at the login screen, you should reboot the PC (prior to logging in) to allow it to clear the flag in the winsxs folder.
      My System SpecsSystem Spec


  10. Joined : Aug 2015
    Posts : 15
    windows 10 build 10240
       10 Nov 2015 #190

    JW0914 said: View Post
    While I did reply directly to your post, the comment about refusing to troubleshoot wasn't directed at you personally, but directed at all who read it. In the future, if you've done troubleshooting, please post what troubleshooting you've done, as well as if you're seeing any errors in the event log (exactly what you did in the reply above).

    Contacting ASUS for beta firmware is probably not going to garnish a result, as as soon as they release an updated version, if will be automatically updated on their drivers site for your model of device.

    As far as your monitor goes, if the issue does come back after you've already adjusted settings within the BIOS, the most likely cause would be a drivers issue or a bad cable. If you took Nvidia's driver through Windows Update, download the most recent WHQL driver from Nvidia's site directly and update the driver with that setup package. If you have a different cable on hand, swap it out, however if you don't, don't immediately go out and buy one - verify first whether or not the drivers directly from Nvidia solved the issue.

    Have you verified if any errors (yellow question marks) are showing up in device manager? While I mentioned it above in reference to nvidia, if a manufacturer offers drivers on their support site, it's always recommended to utilize those in lieu of the generic ones downloaded via Windows Update. In addition to being generic, Windows Update drivers will also generally not be the most recent drivers available.

    As to the keyboard and mouse, is it a regular run of the mill keyboard, or does it have macro buttons, assignable or otherwise? If so, see if there's a driver's update from the manufacturer of the keyboard. If it is just a regular, run of the mill keyboard:

    • Power down the system and unplug the main power cord (if a laptop, remove the battery as well), hold down the power button for 30 seconds, release, plug power cord back in, and turn the system on. If the problem still exists, proceed below.
    • If this is a desktop, and the USB ports are on a pcie card, turn the system off, unplug the main power cable, hold the power button down for 30 seconds, open the case, unseat, then reseat the pcie card, close the case, plug power cord back in, and turn on the system. If the problem still exists, proceed below.
    • Verify if the issue occurs if the keyboard and mouse are plugged into different USB ports (try the ones on your monitor)
    • Hook a different device (preferably a keyboard or mouse, however any device should do) into the USB ports the mouse and keyboard are currently connected to, and see if the other device becomes non-responsive as well. The webcam would be a perfect way to do so, as you can simply turn it on and verify via the small preview window whether or not it freezes up. Make sure you leave it connected for 2x as long as it takes for the unresponsive issues to occur with the keyboard and mouse (this ensures you've left it connected long enough to replicate the issue)


    While it would be out of the ordinary for both a keyboard and mouse to both fail at the time same time, if they were a package deal when you bought them, it would be a good idea to rule them out by connecting them to a different device to verify if the issue goes away (preferably another device running Win 10).
    most of my issues have long since cleared up, but brought a new problem. the black screen with just mouse pointer when I resume from sleep mode. I checked my event viewer, and no errors leading up to my hard reset. I've been through all my cables, s-ata, video power cable, tried re-seating my memory, video card, audio card re-setting bios, all that good stuff. tried unplugging re-plugging any USBs. And It's definitely not an over-heating issue. I swear I'm ready to Lose it with my PC. one thing I did notice is I have the steam client installed and it seems to show a time out once and a while. But I don't think that would cause a complete system lock-up, and if I shut it down in my startup, it refuses to function when I manually start it once my PC is fully loaded up. And yes, I went directly to Nvidias website to get my latest driver. I also keep it up to date through my nvidia geforce experience. for a few more specs, I am running a kingston v200 SSD as my OS drive, an intel 300gb SSD as a secondary drive, OCZ 750 watt PSU, and 750ti video card. other than my USB perifs I really don't have anything else plugged to the board. I'm using just a cheap wireless keyboard, along side my razer naga mouse. I'm getting the th2_release Core 10586 right know.. after that said and done I'll see what happens. really not too fond of windows 10. I understand I'm running on dated hardware, but it should still be more than able to run windows 10. having flashbacks of Vista. lol!!
      My System SpecsSystem Spec


 
Page 19 of 77 FirstFirst ... 917181920212969 ... LastLast


Similar Threads
Thread Forum
Windows 10 installation process freezes at 32% and 6%
During the first three attempts at installing windows 10, the process has frozen at 32% total installation and 6% on the "drivers and features" section. The entire process freezes and no animations play. No errors, after reboot from the freeze it...
Installation and Setup
Solved Windows 10 Installation Freezes
I am on an Alienware Aurora R3 with Windows 7 Ultimate x64. I ran the media creation tool to upgrade to Windows 7, and it gets as far as 100% copying data. It then restarts, the dots circle once, and then they freeze. I force a restart and it...
Installation and Setup
Computer freezes due to Windows 10
Does anyone have this problem? A friend of mine recently installed Windows 10 and the computer started to freeze because of it. It was then downgraded back to Windows 8 but the problem persisted.
General Support
Configuring update for Windows 10 freezes at 100%
I have an ASUS Desktop with a Core i7 3770, 16GB Ram, an Nvidia GTX 970, and a 250 GB Intel SSD and a 2 TB HDD. Windows 8.1 is loaded on the SSD. I am trying to update to Windows 10 with the free upgrade icon in the bottom left corner since it say...
Installation and Setup
Windows 10 Issue - Boots fine and works for 2 mins, then freezes
Specs: AMD FX-8350 @ 4.3GHz 16GB RAM GTX 970 4GB 120GB SSD 1TB HDD So I have had an earlier build of Windows 10 TP on my system installed onto my SSD and I was using that as my daily driver for about a month or so. It worked great and I was...
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 04:39.
Find Us
Twitter Facebook Google+



Windows 10 Forums