Sign in with
Sign up | Sign in
Your question

Computer freezing or randomly rebooting after new CPU+MOBO

Tags:
  • Computers
  • CPUs
  • Motherboards
  • Systems
Last response: in Systems
Share
January 31, 2014 2:25:40 PM

Here is my cpu-z validate http://valid.canardpc.com/awjnwg << Does anything look wrong in here like cpu is 3917 mhz instead of 3900 and ram is 1339
The cpu is AMD FX 6350
The motherboard is Gigabytes GA-990FXA-UD3 board it should be working fine with this cpu.
500W Evga PSU
Gigabyte 650 1 GB
(2x4)8 GB ram 1333 MHZ
Doesn't happen when I reinstalled windows, and probably doesn't happen when in bios either, and the last 2 times it randomly rebooted when it randomly rebooted, where it says starting windows it said something about registry/components/ something it was updating I think help me please, if you need to know anything else please ask me or tell me
Bios is already up to date, and I did reinstall windows before entering it with the new mobo and cpu.

More about : computer freezing randomly rebooting cpu mobo

a b à CPUs
a b V Motherboard
January 31, 2014 2:28:33 PM

Update Bios.
Re install windows.

Download proper drivers.

m
0
l
a b à CPUs
a b V Motherboard
January 31, 2014 2:30:28 PM

On a new install, Windows will download and install updates from Microsoft's server, thus forcing your system to reboot (it will give you a warning and the option to delay for up to 4 hours). The "update registry xxx/177789" is a normal part of this process.

Run all of your Window's Updates (Start>Windows Updates) first and see if this solves any problems. Also be sure you have all of the current drivers for your motherboard and hardware installed.
m
0
l
Related resources
January 31, 2014 2:47:31 PM

Benevolence said:
On a new install, Windows will download and install updates from Microsoft's server, thus forcing your system to reboot (it will give you a warning and the option to delay for up to 4 hours). The "update registry xxx/177789" is a normal part of this process.

Run all of your Window's Updates (Start>Windows Updates) first and see if this solves any problems. Also be sure you have all of the current drivers for your motherboard and hardware installed.


I already used my motherboard disk, and my motherboard is Rev 4.0 which is up to date anyways, and when I run windows updates it usually randomly reboots or freezes completely
m
0
l
a b à CPUs
a b V Motherboard
January 31, 2014 2:53:06 PM

Run HDTUNE and check your hard drive.
Boot MemTest (Memtest.org) from a flash drive and run for at least 4 hours.
Also download the latest drivers from your motherboard's website, your Mobo CD is probably fairly outdated.
In addition high CPU temperatures can also cause this behavior. Run CoreTemp. If your CPU temperatures are over 75C you may have a problem.
m
0
l
January 31, 2014 3:23:20 PM

Benevolence said:
Run HDTUNE and check your hard drive.
Boot MemTest (Memtest.org) from a flash drive and run for at least 4 hours.
Also download the latest drivers from your motherboard's website, your Mobo CD is probably fairly outdated.
In addition high CPU temperatures can also cause this behavior. Run CoreTemp. If your CPU temperatures are over 75C you may have a problem.


I ran those tests on those parts with my old motherboard everything checked out, and CPU temperatures in the CPU-Z validation picture are 45C any other suggestions
m
0
l
a b à CPUs
a c 111 V Motherboard
January 31, 2014 4:33:34 PM

Just to ensure you are aware of the notification Benevolence mentioned, this random restart you speak of...Does it happen, with certainty, between logon and 10 minutes (default option)? I ask because it is easy to lose track of time when you're trying to get a new system up to par, and 10 min can go by while you're still in midst of configurations.

On a separate note, when you check for updates, do you see a message like "Windows Update Error 80XXXXXXX"?

Have you tried returning your BIOS settings to their default values, and then running updates? Improperly configured RAM can cause stability issues.
m
0
l
January 31, 2014 6:56:47 PM

T_T said:
Just to ensure you are aware of the notification Benevolence mentioned, this random restart you speak of...Does it happen, with certainty, between logon and 10 minutes (default option)? I ask because it is easy to lose track of time when you're trying to get a new system up to par, and 10 min can go by while you're still in midst of configurations.

On a separate note, when you check for updates, do you see a message like "Windows Update Error 80XXXXXXX"?

Have you tried returning your BIOS settings to their default values, and then running updates? Improperly configured RAM can cause stability issues.


No I never get a message to postpone my restart and it happens when I am installing updates, like when its shutting down and installing updates it reboots usually.
m
0
l
a b à CPUs
a c 111 V Motherboard
February 1, 2014 12:19:09 AM

Ok, just so we're clear... reboots during updates is a normal operation. Here are some scenarios that can happen during an update:

1. Windows will close all open windows and applications, and then the log off screen will appear. You will see a message stating what percentage is complete.
2. Windows will restart computer.
3. After restart, sometimes you'll see the registry update status; sometimes you'll see the loading screen - it just depends on the update.
4. During an update, it is not uncommon for Windows to restart two or three times, in succession, before you're able to login to Windows.
5. New installations, depending on how old the install file is, can have several updates, so if you keep seeing updates are available - and there are no indications of a failed update - Windows is still downloading patches to get your version up to date.

I apologize if the above scenarios are already common knowledge to you, but I just don't think I am understanding your concern yet. So, if these random restarts are not associated with updates, then you could have a software/hardware conflict. On the other hand, if the random restarts only happen as a result of you trying to update Windows, please clarify if any of the updates have been successful.
m
0
l
February 1, 2014 9:35:14 AM

T_T said:
Ok, just so we're clear... reboots during updates is a normal operation. Here are some scenarios that can happen during an update:

1. Windows will close all open windows and applications, and then the log off screen will appear. You will see a message stating what percentage is complete.
2. Windows will restart computer.
3. After restart, sometimes you'll see the registry update status; sometimes you'll see the loading screen - it just depends on the update.
4. During an update, it is not uncommon for Windows to restart two or three times, in succession, before you're able to login to Windows.
5. New installations, depending on how old the install file is, can have several updates, so if you keep seeing updates are available - and there are no indications of a failed update - Windows is still downloading patches to get your version up to date.

I apologize if the above scenarios are already common knowledge to you, but I just don't think I am understanding your concern yet. So, if these random restarts are not associated with updates, then you could have a software/hardware conflict. On the other hand, if the random restarts only happen as a result of you trying to update Windows, please clarify if any of the updates have been successful.


It randomly restarts and freezes.. when I'm not updating either? And when it restarts on the windows updates it says windows restarted from an error do you want to start in safe mode or start windows regularly so I know it didn't mean to restart
m
0
l
a b à CPUs
a c 111 V Motherboard
February 3, 2014 10:05:34 AM

OK, now we're getting somewhere. The reason for the failed updates is because Windows Update is having write conflicts with your HDD. These conflicts can happen because the system is unstable. Try testing your RAM with MemTest86+. Either download and burn the disc image (.iso) or create a bootable USB (follow instructions on the site). MT86+ tests your RAM in a DOS-like envirionment, so that means it's completely independent of Windows. Allow the test to run for about 6-8 hours, unless errors are detected sooner.
m
0
l
!