Help with windows 10 pc freezing, (upgrade from Win 7)

Vegito

Reputable
Oct 14, 2015
2
0
4,510
Okay I built a computer quite awhile back(2010 or 11), and it's been working great until the past few months. At least once a day, my computer freezes, whether I'm playing games (sc2, wow mostly) , or just browsing the net.

At first I thought it may have been the hard drive, but recently I bought a 500 gb ssd, and installed a fresh copy of win 7 to test the issue, and the problem still occurred. I have checked the temps, and they seem fine imo, but I will state them down below as well. Also the graphics cards, I had one in a diff computer that worked fine so I swapped them out to see if it was that, and the pc still froze, with the other computer working fine. I did the same thing with the power supply with no success.

Computer freezing specs:
CPU: Amd Athlon x4 630 2.8ghz
GPU XFX radeon 5750 HD 1gb
HDD WD 1 TB (original windows install)
SSD Patriot Blast 480 GB
RAM I think(Brand guessing) a corsair 4gb, and 2 2GB G Skill DDR3
PSU 650Watt Antec
Win 10 64 bit

Temps:
Cpu gets to around 55c in games, 25-30 idle, browsing the net
GPU get to around 60-65c in games, and 35c idle (both)
SSD 30c
HDD 35-40c

PC that works fine specs
CPU: Amd Phenom II 965 3.2ghz OC to 3.6
GPU: Asus Radeon 5770 HD 1GB (very similar cards) the one I swapped to test
HDD: WD 750 GB
SSD: 220 GB (forget brand)
RAM 3 4 GB Corsair DDR3
PSU 750 Watt Antec
Win 7 64 bit

At the moment I forget the models of the motherboards. Will update when I get home. All I know is the brand, one is Asus (on the freezing pc), and the other is gigabyte.



 
Solution
Did you "upgrade" from win7 to win10? or did you do a fresh install of win10? These issues may be caused by not having a fresh install.

Also look in the Event Viewer, locate the time that it froze, and see what you can gather from the errors/warnings that are present. Post them here, if I don't know what the codes mean. Someone else may know.

EdwardJenkinsS

Distinguished
Oct 12, 2015
81
1
18,665
Did you "upgrade" from win7 to win10? or did you do a fresh install of win10? These issues may be caused by not having a fresh install.

Also look in the Event Viewer, locate the time that it froze, and see what you can gather from the errors/warnings that are present. Post them here, if I don't know what the codes mean. Someone else may know.
 
Solution

Vegito

Reputable
Oct 14, 2015
2
0
4,510


I upgraded windows 7 to 10, so not a fresh install on the TB hdd, but I did have a fresh install on a new ssd that caused the same error, so I don't think it's the installation or hard drive itself.

this is what I found in the event viewer

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 10/14/2015 3:34:34 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (35184372088832),(2)
User: SYSTEM
Computer: Rimlyn
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-10-14T22:34:34.866176500Z" />
<EventRecordID>10381</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Rimlyn</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>
 

EdwardJenkinsS

Distinguished
Oct 12, 2015
81
1
18,665
Sadly Event ID: 41 doesn't really tell us to much. As this just shows us that it shut down in an unexpected way. Tell me some of the errors that are either right before or right after. The times that they occurred and this one occurred should be very close.