System Blue Screen on different situations, adobe flash may be culprit

[Erick Aguilar]

Hello team,

So it has happened now 3 times in the past 2 months that my computer randomly resets as if a power surge was present, recently I found out that the reality is that for some reason my system reset the ability of windows to restart when a Blue Screen was occurring. I set it back to not reboot automatically and searched the bluescreen on nirsoft bluescreenviewer. Saw that the culprit is ntoskrnl.exe.

Since I had received a bluescreen for the same months ago, I took a tip offered here and did a RAM check for a day. No errors came back , this time I am believing it may be a driver of some sort. The Blue Screens have occurred randomly while gaming, doing day to day activities and even when the computer is just idling with the desktop open.

I decided to run the driver verification command on windows to trigger a BSOD on startup, but no BSODs have been triggered whatsoever.

Here is the funny part, whenever my system would randomly restart because of a blue screen, upon logging back into my desktop, the adobe flash player updater would be there to greet me. So I am thinking the updater is triggering something upon execution.

If it is okay, here is the dump file attached if anybody would like to review it.

Thank you!

 

[Erick Aguilar]

Got a BSOD while playing skyrim this time, adobe flash not present.
System is currently AMD A10-5800K @ 4.2 GHZ
GA-F2A85X-UP4
AMD R9-280X
8GB Kingston hyper x blu 1033 X2
cooler master 850w silent pro PSU.

Just purchased the 280X last week and I had encountered a similar BSOD before, attaching all BSODs that have occured this month.

 

[Arc]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 124[/COLOR], {[COLOR=SeaGreen]0[/COLOR], fffffa80098d48f8, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

Follow it: http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696

 

[Erick Aguilar]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
[COLOR=red]BugCheck 124[/COLOR], {[COLOR=seagreen]0[/COLOR], fffffa80098d48f8, 0, 0}
 
Probably caused by : AuthenticAMD
 
Followup: MachineOwner
---------

Follow it: http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696

Thank you,

I have set my CPU to use turbo boost when neeed instead of having it overclocked to it's turbo boost of 4.2.

It has occurred again, nothing else is overclockede, and the GPU is new (bought it last week) you mentioned AUthenticAMD, could it be the drivers for the beta 9.2 version or the fact the the CPU woke up after 6 months of being overclocked and decided it was too much?

 

[Arc]

AUthenticAMD is not anything to be put a lot of importance. It is a stereotype outcome of the stop 0x124.

But oberclocking (and turbo boost) causes stop 0x124 BSODs.

 

[Erick Aguilar]

AUthenticAMD is not anything to be put a lot of importance. It is a stereotype outcome of the stop 0x124.

But oberclocking (and turbo boost) causes stop 0x124 BSODs.

Strange.. it had been running on the turbo boos frequency for months.
I guess it´s just a dying CPU. are there any tests that can determine that? prime 95 or occt?

 

[x BlueRobot]

AuthenticAMD is just a string to prove you have a genuine AMD product.

You could try Prime95, and then run all three tests for a few hours each.

 

[Arc]

Strange.. it had been running on the turbo boos frequency for months.

Well, I was fit for years, but last week I got a cold. Is it strange?

I guess it´s just a dying CPU. are there any tests that can determine that? prime 95 or occt?

First of all, disable all overclocks. If it BSODs with the stock hardware settings then decide about your next steps.

 

[Erick Aguilar]

Strange.. it had been running on the turbo boos frequency for months.

Well, I was fit for years, but last week I got a cold. Is it strange?

I guess it´s just a dying CPU. are there any tests that can determine that? prime 95 or occt?

First of all, disable all overclocks. If it BSODs with the stock hardware settings then decide about your next steps.

Yeah makes sense.

By disabling overclocks i believe you mean the turboboost settings in BIOS as well.

Will test once RAM is done testing, thank you