Around the end of September and on this month, my computer has started freezing almost every time I logged into my desktop (forcing me to shut it off with the power button). Sometimes it would freeze twice in a row. On October 21st, it froze 3 times in a row and then a few hours later, I got a BSOD. It had the code: 0x00000124 and a bunch of other numbers. When I shut down my computer with the power button and logged back into my desktop, a window popped up with information. Here it is:
[I]Problem signature:
Problem Event Name:BlueScreen
OS Version:6.1.7600.2.0.0.768.3
Locale ID:1033
Additional information about the problem:
BCCode:124
BCP1:0000000000000000
BCP2:FFFFFA8007E4B028
BCP3:00000000FE000000
BCP4:0000000000800400
OS Version:6_1_7600
Service Pack:0_0
Product:768_1
Files that help describe the problem:
C:\Windows\Minidump\102111-81432-01.dmp
C:\Users\Bryan\AppData\Local\Temp\WER-121524-0.sysdata.xml
Read our privacy statement online:
[url]http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409[/url]
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt[/I]
That was the first and only time (so far) this has happened to me. I ran MDSCHED and it detected no problems.
Here is a link to my computer information: [url]http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01892903&cc=us&dlc=en&lang=en&lc=en&product=4007357#N250[/url]
^That is the **exact** computer I have. I got it on February 10th, 2010. I did not have any problems with it until September and this month. Last time I cleaned it was on October 22nd, the day after I got the 0x00000124 bluescreen error.
I will post the .dmp file I received that day in hopes that someone will analyze it for me:
[URL="http://www.sendspace.com/file/ftk0mj"]http://www.sendspace.com/file/ftk0mj[/URL]
Now for the 0x0000007F error. On October 22nd, after I opened it up, cleaned it and plugged it back in, I received the 0x7F error after logging in to my desktop. I've read that, like 0x124, it is a hardware issue. But that was the only time I received that error (as with 0x124).
The weird part is, like I've said, I haven't gotten these errors again AND my computer has stopped freezing up on start up. I remember that on the 22nd, I removed a program called "Sculptris" because I noticed that my computer froze a lot more often when i had that installed, despite only having used it once. Could that have been the culprit, despite everyone saying this is a hardware error? I still don't feel safe, of course as I know something is wrong with my computer.
I didn't get any problems from the 23rd-25th. I have even been able to play games. But today, my computer got stuck on the start up screen. The black screen where it says "Starting windows" and there's a windows logo above it. I had to shut off my computer with the power button and then I ran "startup repair". It's seemingly fine now.
So, can anyone please help and can someone analyze that .dmp file? I don't really know exactly what's wrong with my computer.
Scan for malware using Malwarebytes and/or Microsoft Security Essentials.
Try updating as many drivers as possible, (not all at onc,e but one at a time).
[code]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007e4b028, fe000000, 800400}
Probably caused by : hardware
Followup: MachineOwner
---------
2: 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: fffffa8007e4b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: audiodg.exe
CURRENT_IRQL: f
STACK_TEXT:
fffff880`02f6ca58 fffff800`0320b903 : 00000000`00000124 00000000`00000000 fffffa80`07e4b028 00000000`fe000000 : nt!KeBugCheckEx
fffff880`02f6ca60 fffff800`02da3293 : 00000000`00000001 fffffa80`07e4cd30 00000000`00000000 fffffa80`07e4cd80 : hal!HalBugCheckSystem+0x1e3
fffff880`02f6caa0 fffff800`0320b5c8 : 00000000`00000728 fffffa80`07e4cd30 fffff880`02f6ce30 fffff880`02f6ce00 : nt!WheaReportHwError+0x263
fffff880`02f6cb00 fffff800`0320af1a : fffffa80`07e4cd30 fffff880`02f6ce30 fffffa80`07e4cd30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f6cc50 fffff800`0320add5 : 00000000`00000004 00000000`00000001 fffff880`02f6ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f6cc90 fffff800`031fee88 : 00000000`016803d0 00000000`02a2f890 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02f6ccc0 fffff800`02c8be6c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02f6ccf0 fffff800`02c8bcd3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6ce30 000007fe`fb837ca8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`02a2f710 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fb837ca8
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
Followup: MachineOwner
---------
[/code]
Here's the reading of the .dmp file for reference.
Wow, thank you very much. I appreciate it. So can you or anyone help me analyze it?
It says "VISTA_DRIVER_FAULT" and under it, it says "audiog.exe". I don't understand, I don't have Vista, I have Windows 7. And did "audiog.exe" cause this? But there is a part that worries me: "FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE".
So what, my processor is dying?
Sorry, you need to Log In to post a reply to this thread.