Sign in with
Sign up | Sign in
Your question

I need some serious expert help on this error...

Tags:
Last response: in Windows 8
Share
February 20, 2013 4:10:40 AM



Ever since I got my new pc, which was 3 months ago, I've been getting this message a lot, it occurs randomly, at one point I couldn't even install a pc game so I figured it was a memory problem thus I removed 2 of the memory chips (i have 4 8gb chip). after that the game installed perfectly but once in a while I still get this annoying frking message randomly, and it'll restart my pc... what am i suppose to do?

I run windows 8 pro 64bit 6.2.9200 Build 9200
Intel core i7-3970ghz, 6cores, 12 logical processors overclocked @ around 4100ghz
16gb ram
radeon hd 7970
need more info please ask ;(

thanks for helping!

More about : expert error

a b * Windows 8
February 20, 2013 4:34:13 AM

Grab the C:\Windows\Minidump\021513-7640-01.dmp file, zip it up and upload it to a hosting site (whichever one you prefer is fine, as long as an account is not required to download)

We can use it to figure out what's going on.
m
0
l
February 20, 2013 6:44:04 AM

The_Prophecy said:
Grab the C:\Windows\Minidump\021513-7640-01.dmp file, zip it up and upload it to a hosting site (whichever one you prefer is fine, as long as an account is not required to download)

We can use it to figure out what's going on.



ok I uploaded it on http://www.2shared.com/file/LHPlqQKJ/021913-6625-01.htm...

it's a similar file to the one you mention since there are a plenty of them in the folder.. ;(
m
0
l
Related resources
February 21, 2013 6:15:25 PM

soo any luck? ._.
m
0
l
a b * Windows 8
February 21, 2013 6:32:01 PM

somebody open that and post it.
m
0
l
February 21, 2013 9:40:56 PM

Here is your debug file after analyzing, Looks like a bad driver...... can you start in SAFE mode?

*******************************************************************************
* *
* 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: fffffa8020330028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba00001f, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000000200a2, 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: System

CURRENT_IRQL: f

STACK_TEXT:
fffff880`009d0a68 fffff801`69a37965 : 00000000`00000124 00000000`00000000 fffffa80`20330028 00000000`ba00001f : nt!KeBugCheckEx
fffff880`009d0a70 fffff801`69bce789 : 00000000`00000001 fffffa80`0ceb54e0 00000000`00000000 fffffa80`20330028 : hal!HalBugCheckSystem+0xf9
fffff880`009d0ab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x249


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN

BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN

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

m
0
l
February 22, 2013 3:53:16 AM

Fishwagon said:
Here is your debug file after analyzing, Looks like a bad driver...... can you start in SAFE mode?

*******************************************************************************
* *
* 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: fffffa8020330028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba00001f, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000000200a2, 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: System

CURRENT_IRQL: f

STACK_TEXT:
fffff880`009d0a68 fffff801`69a37965 : 00000000`00000124 00000000`00000000 fffffa80`20330028 00000000`ba00001f : nt!KeBugCheckEx
fffff880`009d0a70 fffff801`69bce789 : 00000000`00000001 fffffa80`0ceb54e0 00000000`00000000 fffffa80`20330028 : hal!HalBugCheckSystem+0xf9
fffff880`009d0ab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x249


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN

BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN

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


yes i can start is safe mode, what should I do?

The blue screen of deaths happens randomly, but it never happened when im playing games like black ops 2, ac3, crysis3, etc
m
0
l
February 22, 2013 10:48:07 AM

Stop 0x124 errors are notoriously hard to troubleshoot as they could be anything. It could be memory overheating, a driver, whatever...

First stop overclocking and see if that stabilizes your system.

If not, then try running a full Memtest86 on it to stress the RAM. That would probably be the first place I'd look (http://www.memtest86.com/). Utility is free, so download it and run it.

Also make sure all fans are working. If a fan is dying, then temps will go up and when they reach a certain point, wham, BSOD

Do one at a time of course to isolate issue.
m
0
l
February 22, 2013 2:01:12 PM

Fish is spot on...unoverclock that CPU...I would have to ask what the point of the overclock is?

Yes, it's nice to have numbers....but do you really need higher numbers to run anything with that CPU?
With your GPU as well you should be running any game over 100fps...which it's doubtful you can see! (note most people can not tell the difference between 30fps and 60fps (as long as there is no jitter))

I had an issue with games randomly crashing on my i7-920 (which I had overclocked) - I unclocked it and my issues went away...and with my nVidia 670 in my rig I really don't notice any frame rate issue ever....you GPU is better in tests than mine, and your CPU is better too! :) 
m
0
l
!