BSOD Screen 0x00000124 Help ASAP Please!

[Ferni36]

Hey please i need some help , Ive recently Bought a New Computer from EBAY and im having problems with it , this only happens when i play games , Example : Crysis 2 and Amnesia Heres the code i get on the Blue screen :

STOP : 0X00000124 (0X0000000000000000 , 0XFFFFFA800838B028 , 0X00000000B620A000 , 0X000000000000135)

Please help the guy who i bought it from says its something to do with the drivers not being installed right or something like that. But on the device manager it says they are installed correctly. ;\

Computer Specs :

8GB RAM
ATI RADEON HD 5670
Windows 7
AMD Phenom X II x4 940 Processor
1TB

 

[yowanvista]

0x124 is caused by defective hardware, mostly the RAM or GPU are the culprits
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[Ferni36]

Could you tell me exactly which hardware it is or? ;\

 

[yowanvista]

Your only way to determine the cause is to do stress tests
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
OCCT (OverClock Checking Tool) 3.0.0 download from Guru3D.com

 

[cluberti]

Correct - a 124 is a Windows crash because the CPU passed on information that the system hit an error that was uncorrectable in hardware. Windows then crashes with a 0x124 bugcheck to halt the system to prevent further damage. Without the .dmp file(s) associated with the bugcheck, we can't tell you anything other than "test your RAM, test your disk(s), and test your CPU". One of them reported an error to the CPU controller, which then passed it on to Windows, which bugchecked with information about that error and wrote it to a .dmp file, if one was created at the time of the crash.

 

[Ferni36]

Correct - a 124 is a Windows crash because the CPU passed on information that the system hit an error that was uncorrectable in hardware. Windows then crashes with a 0x124 bugcheck to halt the system to prevent further damage. Without the .dmp file(s) associated with the bugcheck, we can't tell you anything other than "test your RAM, test your disk(s), and test your CPU". One of them reported an error to the CPU controller, which then passed it on to Windows, which bugchecked with information about that error and wrote it to a .dmp file, if one was created at the time of the crash.

For some reason i cant compress a folder with all the DUMP files in it , It wont let me , any other way i can send them to you?

 

[yowanvista]

Correct - a 124 is a Windows crash because the CPU passed on information that the system hit an error that was uncorrectable in hardware. Windows then crashes with a 0x124 bugcheck to halt the system to prevent further damage. Without the .dmp file(s) associated with the bugcheck, we can't tell you anything other than "test your RAM, test your disk(s), and test your CPU". One of them reported an error to the CPU controller, which then passed it on to Windows, which bugchecked with information about that error and wrote it to a .dmp file, if one was created at the time of the crash.

For some reason i cant compress a folder with all the DUMP files in it , It wont let me , any other way i can send them to you?

Copy the Dump files to your desktop then .zip them

 

[Ferni36]

Correct - a 124 is a Windows crash because the CPU passed on information that the system hit an error that was uncorrectable in hardware. Windows then crashes with a 0x124 bugcheck to halt the system to prevent further damage. Without the .dmp file(s) associated with the bugcheck, we can't tell you anything other than "test your RAM, test your disk(s), and test your CPU". One of them reported an error to the CPU controller, which then passed it on to Windows, which bugchecked with information about that error and wrote it to a .dmp file, if one was created at the time of the crash.

For some reason i cant compress a folder with all the DUMP files in it , It wont let me , any other way i can send them to you?

Copy the Dump files to your desktop then .zip them

I have , but it wont let me zip them... ;\

 

[yowanvista]

For some reason i cant compress a folder with all the DUMP files in it , It wont let me , any other way i can send them to you?

Copy the Dump files to your desktop then .zip them

I have , but it wont let me zip them... ;\

Use 7-zip
7-Zip

 

[Ferni36]

Copy the Dump files to your desktop then .zip them

I have , but it wont let me zip them... ;\

Use 7-zip
7-Zip

Says acces denied to all of them

 

[yowanvista]

I have , but it wont let me zip them... ;\

Use 7-zip
7-Zip

Says acces denied to all of them

Unless there is a problem with ownership of files in your computer this method should work: http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

 

[Ferni36]

Use 7-zip
7-Zip

Says acces denied to all of them

Unless there is a problem with ownership of files in your computer this method should work: http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

For some reason it says i have no Permission to zip the files... do you need all the DUMP files?

 

[Ferni36]

Says acces denied to all of them

Unless there is a problem with ownership of files in your computer this method should work: http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

For some reason it says i have no Permission to zip the files... do you need all the DUMP files?

Ok ive done it , Heres the DUMP Files please tell me whats wrong thanks...

 

[yowanvista]

Seems to be a RAM or GPU issue, test your RAM and your GPU with the GPU test in OCCT
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800838b028, b620a000, 135}

Probably caused by : hardware

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: fffffa800838b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b620a000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Crysis2.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8ac8 fffff800`02e17903 : 00000000`00000124 00000000`00000000 fffffa80`0838b028 00000000`b620a000 : nt!KeBugCheckEx
fffff800`00ba8ad0 fffff800`02fd45a3 : 00000000`00000001 fffffa80`08542810 00000000`00000000 fffffa80`08542860 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8b10 fffff800`02e175c8 : 00000000`00000728 fffffa80`08542810 fffff800`00ba8e70 00000000`00000000 : nt!WheaReportHwError+0x263
fffff800`00ba8b70 fffff800`02e16f1a : fffffa80`08542810 fffff800`00ba8e70 fffffa80`08542810 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8cc0 fffff800`02e0ae8f : 00000000`0866fa1c 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8d00 fffff800`02ebcfec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff800`00ba8d30 fffff800`02ebce53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 00000000`0100acff : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0866be38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x100acff


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

 

[Ferni36]

Seems to be a RAM or GPU issue, test your RAM and your GPU with the GPU test in OCCT
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800838b028, b620a000, 135}

Probably caused by : hardware

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: fffffa800838b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b620a000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Crysis2.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8ac8 fffff800`02e17903 : 00000000`00000124 00000000`00000000 fffffa80`0838b028 00000000`b620a000 : nt!KeBugCheckEx
fffff800`00ba8ad0 fffff800`02fd45a3 : 00000000`00000001 fffffa80`08542810 00000000`00000000 fffffa80`08542860 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8b10 fffff800`02e175c8 : 00000000`00000728 fffffa80`08542810 fffff800`00ba8e70 00000000`00000000 : nt!WheaReportHwError+0x263
fffff800`00ba8b70 fffff800`02e16f1a : fffffa80`08542810 fffff800`00ba8e70 fffffa80`08542810 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8cc0 fffff800`02e0ae8f : 00000000`0866fa1c 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8d00 fffff800`02ebcfec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff800`00ba8d30 fffff800`02ebce53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 00000000`0100acff : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0866be38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x100acff


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

Is it just the RAM? because that would be an easy fix ill get the guy who sent me the PC to get me some new ram. Thanks for answering btw

 

[Ferni36]

Seems to be a RAM or GPU issue, test your RAM and your GPU with the GPU test in OCCT
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800838b028, b620a000, 135}

Probably caused by : hardware

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: fffffa800838b028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b620a000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Crysis2.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`00ba8ac8 fffff800`02e17903 : 00000000`00000124 00000000`00000000 fffffa80`0838b028 00000000`b620a000 : nt!KeBugCheckEx
fffff800`00ba8ad0 fffff800`02fd45a3 : 00000000`00000001 fffffa80`08542810 00000000`00000000 fffffa80`08542860 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8b10 fffff800`02e175c8 : 00000000`00000728 fffffa80`08542810 fffff800`00ba8e70 00000000`00000000 : nt!WheaReportHwError+0x263
fffff800`00ba8b70 fffff800`02e16f1a : fffffa80`08542810 fffff800`00ba8e70 fffffa80`08542810 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8cc0 fffff800`02e0ae8f : 00000000`0866fa1c 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8d00 fffff800`02ebcfec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff800`00ba8d30 fffff800`02ebce53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 00000000`0100acff : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0866be38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x100acff


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

Also , The CPU was overclocked.... would that be the problem?

 

[cluberti]

That's always the best place to start. This particular bugcheck is blaming one of the locations in the CPU's L1 cache specifically, so setting it back to stock (and making sure it's staying cooled properly) are good starts.