Multiple Problems?

[Rastaman694]

So I've had some weird problems over the past couple of months and can't put my finger on what's going on. 
My System specs

I5 3570k(@ Stock clock)
Gigabyte Z77x-D3H Motherboard
Radeon Sapphire 7950 Vapor x
8gb Ram
Windows 10 Home
Rosewill TACHYON 550w 

A couple of months ago, My cpu was overclocked to 4.1ghz at 1.235 vcore. I went to turn my computer on one day and it wouldn't get past post. Naturally, as this was a simple unstable overclock, I cleared the CMOS, and the computer started up fine. However, ever since, I've had some weird happenings. First off, core 1 in my CPU is reading about a 10c higher difference in temperature from the other core. I know it's normal for one core to be hotter but this was never the case before this. The motherboard temperature also appears to be stuck at 28c and has not changed ever since. 

Also, ever since this happened, my pc has had some random BSODs and freezes. Just yesterday, for example, I had left my pc on desktop with no major tasks running for a few minuets, and came back to find the computer had frozen and had to restart in order to unfreeze it. 

In addition, at times when I shut down the system, I will get a memory write error. This, however, I'm sure is a ram issue, but I'm not completely sure. Lastly, Every now and then the system will get stuck on the shutdown screen and not shut down, and sometimes the system will even start itself up(I will admit though that this is pretty rare).

Unfortunately for me, I'm convinced this could be a combination of problems, but am not sure where to start exactly with troubleshooting to determine if this is correct or not. Could this be a dying CPU or motherboard, or PSU, or maybe windows is corrupted, or all of the above maybe? Any help is appreciated. Thanks all.

[Enderman]

did you upgrade to windows 10 instead of doing a proper clean install?

[FAQBytes]

So I've had some weird problems over the past couple of months and can't put my finger on what's going on. 

My System specs

I5 3570k(@ Stock clock)

Gigabyte Z77x-D3H Motherboard

Radeon Sapphire 7950 Vapor x

8gb Ram

Windows 10 Home

Rosewill TACHYON 550w 

A couple of months ago, My cpu was overclocked to 4.1ghz at 1.235 vcore. I went to turn my computer on one day and it wouldn't get past post. Naturally, as this was a simple unstable overclock, I cleared the CMOS, and the computer started up fine. However, ever since, I've had some weird happenings. First off, core 1 in my CPU is reading about a 10c higher difference in temperature from the other core. I know it's normal for one core to be hotter but this was never the case before this. The motherboard temperature also appears to be stuck at 28c and has not changed ever since. 

Also, ever since this happened, my pc has had some random BSODs and freezes. Just yesterday, for example, I had left my pc on desktop with no major tasks running for a few minuets, and came back to find the computer had frozen and had to restart in order to unfreeze it. 

In addition, at times when I shut down the system, I will get a memory write error. This, however, I'm sure is a ram issue, but I'm not completely sure. Lastly, Every now and then the system will get stuck on the shutdown screen and not shut down, and sometimes the system will even start itself up(I will admit though that this is pretty rare).

Unfortunately for me, I'm convinced this could be a combination of problems, but am not sure where to start exactly with troubleshooting to determine if this is correct or not. Could this be a dying CPU or motherboard, or PSU, or maybe windows is corrupted, or all of the above maybe? Any help is appreciated. Thanks all.

Do you have an extra hard drive laying around?

[aneil1998]

You can probably try to get the motherboard/CPU checked out at a local computer store.

 

I had a similar issue where my desktop would never turn off even after i shut it down, while playing games it will lock up, starting it would take sometime as i have to keep on turning it off and back on until it posted as it would never post. My issue was a dying motherboard caused by a generic PSU.

[Rastaman694]

did you upgrade to windows 10 instead of doing a proper clean install?

Yes I just did the upgrade from windows 7

 

Do you have an extra hard drive laying around?

I have some external drives but all of my sata drives are currently installed already in this system

 

You can probably try to get the motherboard/CPU checked out at a local computer store.

 

I had a similar issue where my desktop would never turn off even after i shut it down, while playing games it will lock up, starting it would take sometime as i have to keep on turning it off and back on until it posted as it would never post. My issue was a dying motherboard caused by a generic PSU.

I may end up doing that.  I'm not so sure its the CPU that's causing it since the system can still work the way it is but the stuck temp sensor on my motherboard may be a sign that it is that.

[Enderman]

Yes I just did the upgrade from windows 7

ok well theres your problem...

 

the fix is to do a clean install, which you should have done in the first place

[FAQBytes]

Yes I just did the upgrade from windows 7

 

I have some external drives but all of my sata drives are currently installed already in this system

 

I may end up doing that.  I'm not so sure its the CPU that's causing it since the system can still work the way it is but the stuck temp sensor on my motherboard may be a sign that it is that.

If you have one that isn't in RAID, transfer all the files off, then try doing a clean install and see if that fixes it. Other wise, you might be SOL.

[Rastaman694]

ok well theres your problem...

 

the fix is to do a clean install, which you should have done in the first place

Yeah that was a pretty dumb move on my part.  Going to try the reset feature.  Would this work or should I just do a totally clean install?

 

If you have one that isn't in RAID, transfer all the files off, then try doing a clean install and see if that fixes it. Other wise, you might be SOL.

None are in RAID.  I'll give it a shot this week. I'd much rather this be just a windows corruption error rather than a hardware thing.

[FAQBytes]

Yeah that was a pretty dumb move on my part.  Going to try the reset feature.  Would this work or should I just do a totally clean install?

 

None are in RAID.  I'll give it a shot this week. I'd much rather this be just a windows corruption error rather than a hardware thing.

GL, and let me know how it goes.

[Leonard]

I feel the failed OC messed up your BIOS's timing/sensors.

 

1. have you tried re-flashing the BIOS or flashing it with a newer version?
2. what were the BSOD codes? If they are like B or D could just be a voltage issue.
3. do you use the adaptive method for OCing or straight voltage? Adaptive is better.
4. do you do a system software maintenance regularly?  You should.
5. did you install the proper chipset drivers for win10 to run on your MOBO of are you using generic?

Advice....

1. re-install what ever windows you came from and see if you keep getting the issues, if this works then it is probably a driver issue, mainly chipset/BIOS

[Enderman]

Yeah that was a pretty dumb move on my part.  Going to try the reset feature.  Would this work or should I just do a totally clean install?

pretty sure reset works too

 

i just like doing the full clean install to be sure

[Rastaman694]

 

I feel the failed OC messed up your BIOS's timing/sensors.

 

1. have you tried re-flashing the BIOS or flashing it with a newer version?
2. what were the BSOD codes? If they are like B or D could just be a voltage issue.
3. do you use the adaptive method for OCing or straight voltage? Adaptive is better.
4. do you do a system software maintenance regularly?  You should.
5. did you install the proper chipset drivers for win10 to run on your MOBO of are you using generic?

Advice....

1. re-install what ever windows you came from and see if you keep getting the issues, if this works then it is probably a driver issue, mainly chipset/BIOS

 

1. I updated it to the newest version yesterday.

2. If you mean when I had that incident happen where it would not get past post, it didn't BSOD.  If you mean the BSODs I get sometimes, their honestly all different.  Most recent one I got was during an install.  Honestly not sure of the code that came with it.

3. I used straight voltage. Couldn't get an offset oc to work on my system it kept overvolting (not to dangerous levels but still higher than it should.)

4. I do monthly virus scans and defrags on my mechanical drive, and make sure my SSDs are working good.  I also do weekly ccleaner scans and registry cleaning scans.

5. I use Intel Driver Update Utility.  It's telling me that I'm up to date on my chipset drivers.

[Leonard]

1. I updated it to the newest version yesterday.

2. If you mean when I had that incident happen where it would not get past post, it didn't BSOD.  If you mean the BSODs I get sometimes, their honestly all different.  Most recent one I got was during an install.  Honestly not sure of the code that came with it.

3. I used straight voltage. Couldn't get an offset oc to work on my system it kept overvolting (not to dangerous levels but still higher than it should.)

4. I do monthly virus scans and defrags on my mechanical drive, and make sure my SSDs are working good.  I also do weekly ccleaner scans and registry cleaning scans.

5. I use Intel Driver Update Utility.  It's telling me that I'm up to date on my chipset drivers.

1. okay
2. Yes they are different but the codes repeat and by the repetition you can tell/have a good idea what need to be done to correct the issue. In your case i feel you nede some more CPU voltage. Also, never do a program/OS install with an OC unless you know it is a stable one.
3. okay
4. cool then we can rule out drivers, it has to be a BIOS corruption or more votlage needed or a component dying or just the win10 update process causing this .
5. okay 

[Rastaman694]

 

1. okay
2. Yes they are different but the codes repeat and by the repetition you can tell/have a good idea what need to be done to correct the issue. In your case i feel you nede some more CPU voltage. Also, never do a program/OS install with an OC unless you know it is a stable one.
3. okay
4. cool then we can rule out drivers, it has to be a BIOS corruption or more votlage needed or a component dying or just the win10 update process causing this .
5. okay 

 

Well, I'm back to stock clock speed since the last failed oc so I'm not sure if it could still be a voltage issue.  Could it still be win10 corruption?  I'm starting to feel like it's a damaged component.

[Leonard]

Well, I'm back to stock clock speed since the last failed oc so I'm not sure if it could still be a voltage issue.  Could it still be win10 corruption?  I'm starting to feel like it's a damaged component.

It could be win10 corruption and or a BIOS corruption also. Sometimes the BIOS gets corrupted when OCs have a major fail like you seem to have, mainly it is the parameter recall system that is affected. It will be hard to tell if the MOBO is the issue unless you have another one. You can asses the GPU by just taking out the dedicated graphics and using the CPU's integrated GPU. Now if it is a MOBO issue you will probably have to upgrade to a newer tier system because z77 MOBOs are almost impossible to find.

[Rastaman694]

It could be win10 corruption and or a BIOS corruption also. Sometimes the BIOS gets corrupted when OCs have a major fail like you seem to have, mainly it is the parameter recall system that is affected. It will be hard to tell if the MOBO is the issue unless you have another one. You can asses the GPU by just taking out the dedicated graphics and using the CPU's integrated GPU. Now if it is a MOBO issue you will probably have to upgrade to a newer tier system because z77 MOBOs are almost impossible to find.

Well with the BIOS corruption, how would I go about diagnosing this?  I forgot to mention above that my system take a slightly longer time to load up now, and most of the time spend is now on the post screen.  Could that be a sign of a corrupted BIOS?

[Leonard]

Well with the BIOS corruption, how would I go about diagnosing this?  I forgot to mention above that my system take a slightly longer time to load up now, and most of the time spend is now on the post screen.  Could that be a sign of a corrupted BIOS?

Yes it is. Normally you would just re-install the BIOS version but you mat have to....

1. save you OC to a file via USB if you can or write down all changes you made in the BIOS because the BIOS will be reset to factory default
2. shut the PC down
3. unplug the PSU's power cord
4. remove the GPU, RAM and the MOBO's battery
5. wait about 1-2 minutes 
6. put back the battery, GPU and RAM
7. plug the power cord back in and power up the PC. You will be prompted yo enter the BIOS to make changes so do that and then reboot
8. re-flash the BIOS then reboot
9. check to see if the problem still happens

If the issue still happens then enable the CPU's GPU and remove the dedicated GPU and power on the PC again and check for errors/issues

[Rastaman694]

Yes it is. Normally you would just re-install the BIOS version but you mat have to....

1. save you OC to a file via USB if you can or write down all changes you made in the BIOS because the BIOS will be reset to factory default
2. shut the PC down
3. unplug the PSU's power cord
4. remove the GPU, RAM and the MOBO's battery
5. wait about 1-2 minutes 
6. put back the battery, GPU and RAM
7. plug the power cord back in and power up the PC. You will be prompted yo enter the BIOS to make changes so do that and then reboot
8. re-flash the BIOS then reboot
9. check to see if the problem still happens

If the issue still happens then enable the CPU's GPU and remove the dedicated GPU and power on the PC again and check for errors/issues

I checked gigabyte's website and it said I would need a floppy disk reader to flash which I do not have.  Is there any other way to do this?  I've never actually flashed my BIOS before so I'm learning as we go here .

[Leonard]

I checked gigabyte's website and it said I would need a floppy disk reader to flash which I do not have.  Is there any other way to do this?  I've never actually flashed my BIOS before so I'm learning as we go here .

No worries about learning, i am too but this seems to be an issue to me. You MOBO is UEFI so you can update the BIOS via the DOS method but you can also do it via Q-Flash. I am sure this method is just by having the BIOS file one your system in a folder like on the desktop then from in the BIOS you navigate to the file and select it via Q-Flash to update the BIOS, very ease to do because my MOBO has the same feature just a different name.

 

Just read your manual about the BIOS and it says your MOBO has 2xBIOS which is the good thing the worrying thing is that the manual also says that if the main BIOS gets corrupted the files are copied over to the backup BIOS and that BIOS will load next boot but you can't update it, now i am not sure if this means that the backup BIOS has to say as is or what. 

 

 

1. Manual's BIOS info.
2. Manual's BIOS info. 2

Read the information very carefully and either print it or write it down so you won't forget the steps.