Windows 10: "Your PC encountered a problem and needs to restart." - Round 2.

Is it possible for you to determine any patterns by comparing information from the multiple dumps that I shared here?

 

I've been unable to find proper onces, I need more data from around the time of the crashes.

 

What kind of data? Is it data that is likely gone now due to my system restorations, or something that could still exist?

 

Mainly the data from event logs

 

Would any of the events logs that I currently have on my computer be useful? And if so, what would be the best way to export all of them?

 

The event logs you still have is collected by the DM Log Collector, I've already gone through it.

 

Ah, I see.

 

As I see it, the best thing to do now is waiting for a few (3+) crashes to occur hoping we have some luck with the event logs.

 

I just now had another crash. I was using my computer (only light usage - I was only using a web browser to fill out some information on a web page), when my screen suddenly went black for a few seconds and my computer automatically restarted.

Here's the information from BlueScreenView:

==================================================
Dump File : 050817-22484-01.dmp
Crash Time : 5/8/2017 11:17:47 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : ffff9a0a`719088f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6b3827
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.14393.1066 (rs1_release_sec.170327-1835)
Processor : x64
Crash Address : ntoskrnl.exe+6b3827
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\050817-22484-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 14393
Dump File Size : 262,144
Dump File Time : 5/8/2017 11:18:02 PM
==================================================

And here's the ZIP file containing all of the detailed information:

Attachment 134185

I'll try not to perform a system restore unless necessary. But this time, I'm currently noticing some possible issues with the way that my system is working right now, so I might have to. I'll notify you if I do wind up having to perform a restore.

EDIT: What I thought was an issue with how my system is running post-crash seems to have been a false alarm. It appears that I ought to be able to avoid restoring my system for the time being.

 

Code: 0x00000124: WHEA_UNCORRECTABLE_ERROR (9.05.2017 06:17:47) [Windows 10] CAUSED BY: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV WHEA Notify: Machine Check Exception Type: BUS error Error: BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4) PROCESS: System Usual causes: Hardware, Incompatibility, May be driver corruption[/quote]
Seems a Problem which goes to the direction "processor problem". Maybe there are problems with the clocks or the temperature.

Did u overclock? Because there is the overclocking software AMD Overdrive installed.
Code: Process C:\Program Files (x86)\AMD\OverDrive\AODAssist.exe[/quote]
U should revert all OC settings in this application to stock settings. After that u should completely remove this software from your system because its known for causing bluescreens.

So mate, if this fixes your problem you owe us a crate of beer *Wink

 

@BSODHunter, please read this post for an explanation what the WHEA error means.

 

Yes. AMD Overdrive can cause this

 

I know, did you think the OP responded? *Smile

 

U should revert all OC settings in this application to stock settings. After that u should completely remove this software from your system because its known for causing bluescreens.[/quote] This is a long story, but here's a short version. One of the things that I checked when troubleshooting this BSOD problem was my CPU temperature. I found out that my CPU gets hot at times (sometimes over 70 degrees Celcius). I tried various things, including replacing my thermal paste. It turns out that the overheating was because of a built-in overclocking feature in my CPU called AMD Turbo Core, which causes my 3.4 Ghz processor to go all the way up to 3.6 Ghz when it thinks it needs to. Whenever Turbo Core kicks on, my CPU starts to overheat. I've read that as bad as this is, it's actually a very normal occurrence on a computer with a stock processor (such as mine).

In some computers, this feature can be disabled in the BIOS. In mine, it cannot. So I had two options. One is to turn my maximum CPU power down to 99% in Windows Power Options (which works perfectly and completely prevents overheating, but underclocks my processor down to 3.0 Ghz, thus losing 0.4 Ghz of processor power).

Another option is to install AMD Overdrive and use it to disable Turbo Core (without enabling any overclocking features). I downloaded and installed AMD Overdrive for this purpose. However, its results proved unsatisfactory to me. You see, my settings did not stay permanent. Whenever I restarted my computer, Turbo Core was enabled again. So I stopped using it after less than a day of having it installed. Yes, it's still installed on my computer, but it's not being used. I went back to the Windows Power Options solution (unsatisfactory though it may).

In a nutshell, though, AMD Overdrive was installed on my system as an attempt to solve a heating problem that I used to have, which I suspected at the time may have been the cause of these BSODs (something I now find doubtful, as I'm still getting crashes even after solving the overheating problem). In other words, it was installed as an attempt to solve this BSOD problem. I have never used it or anything else to intentionally overclock my system.

 

allright, I understand. Then, like axe0 said, we have to wait for more BSODs.

But in your case its like an car which vibrates like crazy while driving. U begin with doing some tests, analysis and so on. Then u begin to change the easy things, like the tires. But is wont dissapear....then u begin to change all mounts and components, clutch, transmission, turbo, motor, and so on. Everything. At the end u loose many hours of your lifetime and the problem ist just an technical design failure which cant be fixed.