BSOD Encountered with MMORPGS and Online Videos

Airst · 23 Feb 2015

I'm not that savvy when it comes to diagnosing issues on my computer. So, before we begin the background story.

I had no issues until today. I attempted to play an MMORPG and found suddenly I was suffering from a BSOD. The firs time I shrugged it off as something randomly strange occurring. After a few more attempts and trying a few other MMOs I have on my PC and still suffering from a BSOD after a few minutes of gameplay (and also while attempting to later watch a video on facebook) I ran a chkdsk. I had both options selected and observed through the hours it took as it went through.

Upon a restart after the chkdsk and another attempt at opening an MMO there was yet again another BSOD restart. I did save the notifications upon restart of a few of the attempts:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFFA8059348CEE
BCP2: 0000000000000000
BCP3: FFFFF88001421F35
BCP4: 0000000000000005
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\022315-16910-01.dmp
C:\Users\[removed for privacy]\AppData\Local\Temp\WER-55551-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800DD57028
BCP3: 00000000B635C000
BCP4: 0000000000000135
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\022315-26847-01.dmp
C:\Users\[removed for privacy]\AppData\Local\Temp\WER-62572-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: FFFFF808034CAC38
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF80003297641
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\022315-17518-01.dmp
C:\Users\[removed for privacy]\AppData\Local\Temp\WER-55692-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800DCBC028
BCP3: 00000000B425A000
BCP4: 0000000000000135
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\022315-20826-01.dmp
C:\Users\[removed for privacy]\AppData\Local\Temp\WER-54054-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I've not had a BSOD on this PC before... ever. My only issue had been viruses obtained through bad flash ads, never something like this.

ICIT2LOL · 24 Feb 2015

Hello and welcome Aird mate I just looked at a very similar post problem and your dump files come up with a very similar issue and so are you overclocking because the issue in the dump files are CPU based see this

random BSOD

So I would suggest if you are OCing then knock it back a notch or two or even go default and see if that fixes the problem.

Airst · 24 Feb 2015

The thing is my PC isn't overclocked. I don't even know how to overclock, didn't mess with my bios at all. Checked my bios set up to make sure something somehow didn't flip and everything was set normally, no overclocking.

Attempted to run my game after turning off my core unlocker (ran previously with NO issues) and after nearly 8 mins of gameplay there was another BSOD. This also happened as I have begun to backup files I wish to save in-case I need/decide to reformat.

Upon using BlueScreenViewer ALL the BSOD are connected with this crash address: ntoskrnl.exe+74ec0

ICIT2LOL · 24 Feb 2015

Again this is starting to sound like another thread I have just been on what we would like is the dump files to be attached to your next post and while the machine is running please run part A: from this ditty of mine - as unlikely as it might sound this may also a be a problem with your PSU.

Using HW Info
PART A:
You can test the volts on the PSU with HW Info HWiNFO, HWiNFO32/64 - Download < download the right bit version and close the right hand window select Sensors and scroll down to the power section where you will see what the volts are doing see my pic.
The original right hand window shows the machine running and is handy for that but for looking at the components in some detail close it and use the main left hand side panel
FOR OTHER COMPONENTS
PART B:
Open each + down into the component itself and then click on it - in the right hand side will appear all sorts of details including brands speeds and other essential info that device. See pic for example.

Airst · 25 Feb 2015

So here's an update:
I contacted one of my family members (one of many IT family members, lol) and they connected to my PC via team viewer and did a diagnostic test.

It isn't an overclocking, CPU, temperature, or RAM/memory issue but rather that my HD is failing because it's just ready for sledgehammer retirement. It's been a long while since I upgraded my PC (it's a custom build) so it's not too shocking.

ICIT2LOL · 25 Feb 2015

Ok Aird then do that and I wouls suggest a largish SSD if you can afford one and you can clone the original drive to it with Macrium if you don't want to go through all that clean install stuff.

However this is what I see in the dump files

Code:

.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa800dca4028, b6004000, 54000135}
Probably caused by : AuthenticAMD
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800dca4028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6004000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000054000135, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
 
BUGCHECK_STR:  0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  wruninstall.ex
CURRENT_IRQL:  f
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`02fddb08 fffff800`03214a3b : 00000000`00000124 00000000`00000000 fffffa80`0dca4028 00000000`b6004000 : nt!KeBugCheckEx
fffff880`02fddb10 fffff800`033d7713 : 00000000`00000001 fffffa80`0ddf86d0 00000000`00000000 fffffa80`0ddf8720 : hal!HalBugCheckSystem+0x1e3
fffff880`02fddb50 fffff800`03214700 : 00000000`00000728 fffffa80`0ddf86d0 fffff880`02fddeb0 00000000`01933700 : nt!WheaReportHwError+0x263
fffff880`02fddbb0 fffff800`03214052 : fffffa80`0ddf86d0 fffff880`02fddeb0 fffffa80`0ddf86d0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fddd00 fffff800`03207e8f : 00000000`045383a1 00000000`00000001 fffff880`02fddf30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fddd40 fffff800`032be7ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02fddd70 fffff800`032be613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fddeb0 00000000`04da1128 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0042b918 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x4da1128
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME:  AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP:  0
IMAGE_VERSION:  
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x124_authenticamd_processor_cache
FAILURE_ID_HASH:  {8bb1abe1-5cc5-4642-921b-5e3d4790100e}
Followup: MachineOwner
---------

So you can see why I was asking after over clocking and why I have not seen anything that is drive related. But if like you say your relatives reckon it is a drive problem then follow my suggestion. Now if after you replace that the problems keep on then you will or might have to look at replacing that CPU

PS Scroll the dump files down to see what I mean