Solved Having random restarts and getting BSOD afterwards?

[Mooshie]

Hello all, I'm finally opening a thread about an issue im having for 5-6 months.

I bought a partially new system about 6 months ago. My old parts were bought in Nov 2010.
My old parts were ASUS GTX 470, Thermaltake Litepower 700 Psu and Thermaltake Element T Case.

After buying the new system. I started having random restarts, no warnings no BSOD. Sometimes my computer
just shut itself down, didnt open for 10 min (needed to plug the psu adapter off and on). I researched a bit, asked for help in forums. And decided it was a PSU issue. And i finally bought a new Corsair CX750 750w 80+ bronze (4-5 days ago). I did the replacement myself, it seemed like the issue was fixed. But i had the issues again and again. Auto-restart on system failure was open, i turned it off so i could see BSOD. But today i had 2 new restarts, no BSOD but, when i logged on windows, i saw a warning on each, saying that "Windows has recovered from an unexpected shutdown"

So i thought these are considered as BSOD. I will upload the dump file. And i thought i was going crazy when searching the problem. I checked almost everything. I have no temperature problems.

And most importantly, the restarts i experienced before didnt have these "unexpected shutdown" warnings. Those were just plain restarts and recorded as Event ID 6008 - "The previous shutdown at xxxx was unexpected." But these two are new, they are recorded like this;

A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor ID: 2

Event ID 18
Source : WHEA Logger

I know i'm repeatedly saying this but i must say it again, restarts are completely random. Sometimes when listening to music, sometimes when playing video games, sometimes watching a video, sometimes browsing the internet, EVEN sometimes when idle.

Thanks, I don't know if i gave all the details properly, please correct me if I'm wrong

Edit :

I had two restarts in last 2 hours with no warnings even though turning off the auto-restart option

For some reason the SystemInfo program didn't do its job, im adding my system specs manually here;

MOBO > ASUS M5A99X EVO - American Megatrends 0901, 02.12.2011
CPU & Cooler > Stock AMD FX-8150 - NO OC
MEMORY > PATRIOT 8GB(4X2)GAMER II SECTOR 5 DDR3 1333MHZ CL9 XMP 1.2 DUAL KIT
POWER SUPPLY > CORSAIR CX750 80+ Bronze
VIDEO CARD > Single ASUS GTX470
HDDs/Optical drives > 3.5" 1TB Barracuda Sata 3.0 32MB Cache 7200Rpm + 160 GB SAMSUNG HDD
O/S > Win7 64 Bit SP1
Case > THERMALTAKE ELEMENT T

 

[Mooshie]

I normally wouldn't write a second post but i had to.

Please somebody help, so many people reads but nobody helps and that makes me lose hope.

 

[Dave76]

Welcome to Seven Forums.

Can you fill in your system specs?
You can use this app to find them: Speccy Free System information Utility
Then enter them in the 'My System Specs' drop box at the lower left of any of your posts.


You're having CPU and Graphics card crashes.

Most common stop code is STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
Usual causes:  Hardware, Incompatibility, May be driver corruption
Probably caused by : AuthenticAMD
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

Your last System Event Log is from 2012-12-20, we need more recent info to analyze this.
To check the System Event Log settings.
1. Start Event Viewer.
2. In the console tree, expand Windows Logs and select System.
3. On the Action menu, click Properties.
4. In the General Tab, ensure 'Enable logging' is checked.
Maximum log size should be 20480
Under 'When maximum event log size is reached': select 'Overwrite events as needed (oldest events first)'
Click OK.

If you are still not getting new System Event Logs, you can 'Clear Log' on the same page.

From your System Events Log:

Event[34831]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2012-12-19T16:50:32.612
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Feanor
  Description: 
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor ID: 4

Your App Events Log has many 'Live Kernal Event' errors with not much info from these.

Read this post and follow steps 1-9, ask any questions you have.
Stop 0x124 - what it means and what to try

Use Core Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

 

[Mooshie]

Hello, much appreciated for your reply

I have filled my system specs now.

And i have the same settings as you said. It is weird that my last logs are from 2012-12-20 because i get new logs everyday. I get two types of logs after the restarts. Sometimes it is this WHEA-Logger along with "unexpected shutdown" log,
sometimes "unexpected shutdown" log alone.

I am using HWMonitor for monitoring cpu temps. Here are the temps with idle and Prime95

Idle : Core=25-30 CPU=40-45
Tested with Prime95 blend test : Core=57-58 CPU=68-69
I asked about these temps in Overclockers.com forum and they told me it is OK unless CPU gets higher than 70 and core gets higher than 60. And they told me that only 1-2 games can stress my cpu as Prime95 blend test did.

 

[Dave76]

Good work on the system specs.
You can try letting the SF Diagnostic Tool sit for a few more minutes before zipping the file, this may allow a full System Events Log to be written.

Don't agree with what they told you at that forum.
AMD CPUs usually run very cool, if they are running warm/hot then there is an issue to address.
AMD FX 8-Core Black Edition
Max CPU temp is 61°C, add 5°C for max Core temp of 66°C.
The CPU temps are from the CPU case, the Core temps are from inside the CPU case. The Core temps are higher than the CPU temps, your temps posted above are reverse of that, so may be switched. It's also possible that the monitor program has them switched, not uncommon.

Use another monitoring program to verify the temps.
Core Temp linked above or HWiNFO64
Also make sure you have the latest version of HWMonitor, this may improve the reading from your CPU.

I have seen AMD CPUs run Prime95 at less than 50°C.
Make sure your CPU cooler is securely attached, too tight or too loose may cause the temps to be too high.
If that doesn't help, remove the CPU cooler, clean with isopropyl alcohol, re-apply the thermal paste. Re-install the CPU cooler.

When the CPU temps are under control you can run a CPU test to look for further issues.
OCCT stability checking tool Run the CPU:OCCT test for at least 30 minutes, be sure to monitor your CPU and GPU temps.
Set the time before you start.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.
How to Post a Screenshot in Seven Forums

 

[Mooshie]

Hi, i tried to do the log stuff but everytime i try it, logs last in December 23rd 2012. So i cleared the log.

And i'd like to correct a misunderstanding(if there is)

Term i used "core" actually is "Package" in HWMonitor. I am putting the link of the thread on the OC forum(I have a screenshot of my cpu temps). Stock AMD FX-8150 temperature - Overclockers Forums

And putting here 2 new screenshots of my cpu temps (Monitored with both CoreTemp and HWMonitor, idle and under load)

Idle :

Under load

And i realized that my FANIN1 rpm in the forum link screenshot is lower (around 1000) than todays FANIN1 readings (1500 rpm). My rear fan sometimes makes clicking noises I will clean it ASAP. I added this just to fill in the blanks.


I will try to tightening or loosening the cpu fan but I must say that I'm avoiding opening the fan for the possible RMA situations.

I downloaded OCCP test and did it. But a very weird thing happened. I did the test and got the results but i realized that Prime95 was still working (for like 50-60 min alone and for 30 min with OCCP) and didn't cause a restart. Afterwards, i did the test without Prime95 and got the results too. And still didn't crash. I will upload both.

I don't know if it is possible but after all the tests, my processor seems to be working overclocked. CoreTemp and OCCP proves that my cores are performing at 3913 mhz instead of 3600. I will update it as soon as i restart.
AFTER RESTART EDIT: Well, that is weird too, when idle they seem 3900 mhz when under load, it goes between 3300-3600-3900, i bet that is common sorry if i got carried away quickly

Note : In the first test (with Prime95+OCCP) my display went off and came back again. There was a notification at right bottom corner saying that "Nvidia Graphics Driver 310.90 failed and recovered" (this is the basic explanation).

 

[Dave76]

That clears up the CPU and Core temps.
It's not unusual for monitoring programs to show different temps, OCCT and Core temp are giving the same readings, max 57°C, these are likely accurate.
Those temps should be better but, aren't bad. If there is a RMA concern just check if the CPU cooler is loose or maybe too tight.

Running Prime95 and OCCT at the same time can give poor results, both will compensate for available load usage.

Info from the OCCT run show some issues.
The 3.3, 5 and 12 voltage readings are a little low, OCCT and HWMonitor are almost the same. Monitoring program voltage readings always need to be taken with a healthy percent of error margin but when consistent in two different programs there is an issue.
The Thermaltake Litepower 700 PSU is not known as a quality unit. The original manufacturer 'Solytech' is not even a medium level quality OEM, only gives a 2yr warranty, max output is 576 watts, not certified. Very suspect.
How old is the PSU?
Did it come with your case?
A poor or failing PSU can cause all kinds of issues that are hard to troubleshoot, and can possibly cause damage to other components, CPU, RAM, graphics cards, motherboard, etc.

The CPU frequency, CPU Vcore and Bus speed are all fluctuating too much, this can be a BIOS issue or possibly an unstable PSU. This is related to the BSoD stop code 124.
What BIOS version do you have?
The latest version is 1604, all of them list 'Improve system stability' you may need to update your BIOS. Let us know if you have any questions about doing this.

 

[Mooshie]

Well, as i said in post #1, I thought these problems as PSU problems. I had that PSU with my case. I had issues just like today. So i replaced my Thermaltake Litepower 700 with a brand new CORSAIR CX750 (i heard corsair is a quality unit). My new PSU is 1-2 weeks old. I opened this thread because new PSU didn't fix my problems. My BIOS version is 0901 according to msinfo32. I thought about updating it but i heard that is risky because if my computer restarts or crashes during the update, my MoBo could be ruined. So i tried asking for help from here so i could see if anything is wrong besides my BIOS version.

Note : I don't have an UPS

 

[Dave76]

Corsair is a good brand.
As I said, the voltage readings from the monitoring programs can be inaccurate, but it is something to check.
It's possible that the old PSU could have damaged the motherboard or CPU, this is difficult to troubleshoot.

Did you do any of the testing steps in the link in post#3?
Stop 0x124 - what it means and what to try

Another possibility is bent CPU pins, but you don't want to remove the CPU so the options are narrowing quickly.

BIOS updating use to cause motherboard bricking quite a bit several years ago, don't see it happening much anymore but it does still occasionally happen.

You should consider updating the BIOS or take your system to a repair shop to update the BIOS and test the motherboard. In most cases testing the motherboard requires removing it and with the right equipment it can be tested, most shops don't have the necessary equipment. Installing another motherboard is what most will do to eliminate this possibility.
Bench testing the motherboard is another option, but again is not easy, remove the motherboard, then remove all components, connect the PSU, then install components one at a time starting the system and checking the beep codes until the wrong beep code identifies a problem component.

Let us know what you want to do.

 

[Mooshie]

Thanks Dave!

I didn't do the 0x124 tests until we come to a conclusion. Now I decided to do all the steps, update the BIOS, checking CPU cooler (tight or loose). After all these steps, if these problems occur again, I will take my case to the technical service of the firm i bought the pc from. All of my hardware are under warranty. I hope that they will fix what causes it.

Finally,

You focused so much in this thread and helped me a lot. Therefore you have my respect Thank you again. I will update this thread about the latest news.

 

[Dave76]

You're welcome.

Sounds like a good plan.
Let us know the results of the tests and BIOS update.

 

[Mooshie]

30 min ago, I updated my BIOS via Asus Suite II. This program also auto-arranges voltages and stuff. And i also cleaned my rear fan(which had a lot of dust on it). I checked if the CPU cooler is tight or loose, I didn't understand if it is tight or loose, so i opened and closed the clip on it. So far so good, I will update if a failure happens and will go on next steps.

 

[Dave76]

Sounds good.

Let us know if you have any questions or problems.

 

[Mooshie]

Yes I can finally say that i have fixed my problem. Any of the steps i explained in post #12 might have fixed the problem. But i think the key was BIOS update. Thank you Dave

 

[Dave76]

Great news.

You're welcome, let us know if you have any questions.

You can mark this thread 'Solved'.