Windows 7: BSOD for over a few months

Tony1990 · 01 Jun 2011

Hi, I'm coming here because everytime I format my computer into Windows 7, it'll show up a BSOD of uncorrectable hardware error while playing games, but in this case, it's Grand Theft Auto - San Andreas.

Any ideas?

I tried replacing the hard drive, RAM, and updating my graphics card.

JMH · 01 Jun 2011

Quote: Originally Posted by Tony1990

Hi, I'm coming here because everytime I format my computer into Windows 7, it'll show up a BSOD of uncorrectable hardware error while playing games, but in this case, it's Grand Theft Auto - San Andreas.

Any ideas?

I tried replacing the hard drive, RAM, and updating my graphics card.

Hello Tony & welcome,
If you are getting BSOD's & want them analyzed please follow the directions below -

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.

To ensure minidumps are enabled:
** Until a .dmp file is generated, the Minidump folder may not exist.**

*Go to Start, in the Search Box type: sysdm.cpl Press Enter.
*Under the Advanced tab, click on the Startup and Recovery Settings... button.
*Ensure that Automatically restart is unchecked.
*Under the Write Debugging Information header select Small memory dump (256 kb) in the drop down box (the 256kb varies).
*Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
*OK.
Reboot if changes have been made.

Tony1990 · 01 Jun 2011

ok there i uploaded them

Tony1990 · 02 Jun 2011

wat do i do now

**yowanvista** · 02 Jun 2011

Your CPU may be defective, this is a hardware error caused by bad hardware

Information

Run Prime 95 to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.

Stop 0x124 - what it means and what to try

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: 00000000, Machine Check Exception
Arg2: 853ad024, Address of the WHEA_ERROR_RECORD structure.
Arg3: b2000010, High order 32-bits of the MCi_STATUS value.
Arg4: 00010c0f, 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:  GTA_SA.EXE

CURRENT_IRQL:  1f

STACK_TEXT:  
8276ed2c 82622f3f 00000124 00000000 853ad024 nt!KeBugCheckEx+0x1e
8276ed68 82719f04 853a3341 853ad024 826b34f0 hal!HalBugCheckSystem+0xab
8276ed98 826231f1 853adea8 82630e40 00000000 nt!WheaReportHwError+0x230
8276eeac 826232e3 853adea8 853adef8 00000000 hal!HalpMcaReportError+0x3b
8276eed0 8262354f 00000000 853adef8 8276eff0 hal!HalpMceHandler+0x8b
8276eee0 826195f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x3b
8276eff0 82616261 00000000 801da000 00000000 hal!HalpMcaExceptionHandler+0x87
8276eff0 00000000 00000000 801da000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS

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

Tony1990 · 02 Jun 2011

There's only the automatic method and manual method, which do I choose?

Tony1990 · 02 Jun 2011

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

THat was for the 2nd worker for Large FFT's.

**yowanvista** · 02 Jun 2011

Quote: Originally Posted by Tony1990

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

THat was for the 2nd worker for Large FFT's.

It confirms that you've got a defective CPU, you should buy a new one or RMA it if still under warranty

Windows 7: BSOD for over a few months

BSOD for over a few months problems?