BSOD - random, possibly graphics card related

Hello all,

I encounter BSODs seemingly randomly, but suspect the graphics card, as there was some correlation to crashing when using youtube or gaming (not so much when playing videos e.g. with vlc). Though recently crashes are more random.
There have not been any crashes on shut down or start up.
After the crash a prompt to start normally amongst other options appears, and can restart successfully - it does not freeze upon BSOD.

A friend also suggested an IRQ conflict. In Device Manager there is a yellow triangle next to an "unknown device" which remains after all external devices have been removed from the laptop.
From Device Manager>view resources by type:
(ISA) 0x00000004 (04) Unknown device
The second graphics card according to the System Info tool is the "LogMeIn Mirror Driver". I do not use LogMeIn any more, and did have trouble uninstalling at the time. I am not sure if any other programs use this.

The BSOD states an "uncorrectable hardware error". Have run a chkdsk in the past with no issues apparent.

CPU: AMD Turion(tm) X2 Ultra Dual-Core Mobile ZM-84
Motherboard: Quanta 3063
Graphics Card(s): (1) ATI Mobility Radeon HD 4500/5100 Series (2) LogMeIn Mirror Driver

Thanks for any help.

Hello and welcome James look mate I will have a go because I see you have been waiting for some time.
Now there are a few issues in your machine (how old and model please??)

Now you have used Logmein at some stage and I am wondering if your system hasn't been corrupted somehow.
As for two graphic cards unless it is a high end gamer like my other lappy (Asus ROG) then it is showing only one the second one I think you may be mistaking for the audio set up.
So we need to know the model at least first please.

Code:

*******************************************************************************
*                                                                             *
*                        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: fffffa80050aa038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000181, 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:  audiodg.exe
CURRENT_IRQL:  f
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`009f0a08 fffff800`03217a3b : 00000000`00000124 00000000`00000000 fffffa80`050aa038 00000000`b6000000 : nt!KeBugCheckEx
fffff880`009f0a10 fffff800`033dbc33 : 00000000`00000001 fffffa80`0510e620 00000000`00000000 fffffa80`0510e670 : hal!HalBugCheckSystem+0x1e3
fffff880`009f0a50 fffff800`03217700 : 00000000`00000728 fffffa80`0510e620 fffff880`009f0db0 00000000`0041be00 : nt!WheaReportHwError+0x263
fffff880`009f0ab0 fffff800`03217052 : fffffa80`0510e620 fffff880`009f0db0 fffffa80`0510e620 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f0c00 fffff800`0320ae8f : 00000000`0041be80 00000000`00000001 fffff880`009f0e30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f0c40 fffff800`032c11ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`009f0c70 fffff800`032c1013 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f0db0 00000000`6b71abe1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0290f0c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6b71abe1

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
---------

Hi ICIT2LOL, thanks for the response.

The laptop is a HP Pavilion DV7-2045ea; about 4 years old I think.

The LogMeIn driver is regarded as a second graphics card by the System Info tool from this site. Not sure if this relates to the audio processes that you highlighted in the logs above.

Regarding process: X64_0x124_AuthenticAMD_PROCESSOR_CACHE -
on startup I usually see a command prompt pop up for a few seconds with a line of code with "AMD" in there somewhere.

Ok now there is a few reasons given from researching this one and although it says processor it need not be it itself as you can see form this

http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/bluescreen-error/5030dd7d-864b-4355-9349-b2fee728b23a now depending on your willingness to do the work yourself I think the compound on the chips should at least be looked at (what are the temps in any case - run this and send back ) https://www.piriform.com/speccy

The driver issues are worth a try too see this
http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-dv7-2000-Entertainment-Notebook-PC-series/3884606/model/3944154
When you have run through those
I personally would run these in safe mode just to check
https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
https://www.sevenforums.com/tutorials/433-disk-check.html < if necessary include the /f and /r in the command line as per Option2

Ok mate sorry late reply and I will get back to you as soon as I can as I have to go offline very shortly. But I do want to have a look at few other things in any case the update issue for example could even be on top of other stuff cos it never rains unless it pours eh?

Look the chkdsk might even sort out the stuff that the SFC couldn't so please run that one with those /f and /r "switches" in the command line.

It doesn't matter about the safe mode so much just that sometimes it is better run while the machine is running on the Windows system only.

No worries, I appreciate the response.

Ran the chkdsk using the GUI to do the same functions as /f and /r (file fix and bad sector fix). The log file is attached.

I think the sfc scan result is a false positive.
https://support.microsoft.com/en-us/kb/3068708 says:
"The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or actual corruption on a device that is running this update, and this issue will be fixed in a later service update."

Regarding temperature - having left the fan on full for a few hours (usually leave it on lowest setting) the CPU is at 80°C, and the motherboard is at 62°C according to speccy. The other day the CPU was at 87°C.
This laptop was built badly with heatsink/fan issues, and has not been cleaned properly in a while as I am reluctant to open it up myself.
It used to restart by itself when it got too hot before I bought a fan, and did not BSOD. Though guessing the crashes may be due to overheating - do you think this is the case?

Hum the temps are not good mate and from my experience the AMD stuff usually runs cooler than the Intel hardware, and even that for an Intel is not acceptable for me. I would accept say 30-40C at idle and 60C max scanning or whatever for the Intel so it looks very much like the thermal compound has dried up or has been poorly applied at manufacture.

Now if you are not happy with dealing with that yourself then it means an expensive trip to the techies.

Now to double check the temp have a look in the BIOS and see what the temp is showing in there. Usually F10 on power up for the HP's.

The chkdsk really didn't find much that I can see but first lets check the temps.

Couldn't find any temperature values in the BIOS, but used speedfan and speccy which show the same temp values.
Just now it is: CPU 86°C, motherboard 72°C.

That is odd mate the CPU at least is way too hot for my liking and the motherboard it also seems a bit too hot too.

The BIOS should have given you the temps