BSOD (Locale ID 2057) at seemingly random times

I am running on a Windows 7 64-Bit. It was put together and Windows 7 installed a few days ago (Wednesday 6th June 2012) from brand new parts. I have a link that contains details for most of my build, if any other details are required, I should be able to provide them. I heard the problem may be something to do with my 400w PSU, but I'm not sure.


When it crashes, I usually do not see a blue screen, but I have seen it once. It usually just freezes for a second and my monitor goes black and I the computer restarts with the option to go into safe mode.


I have attached the files required, if anything else is needed, please let me know. The crash has happened during internet browsing, gaming and other tasks, but I have not experienced it whilst it is idle or downloading files in the background.

I have ran all 3 tests on Prime95 for 2-3 hours each and I have received no errors. I also ran Memtest86 for 3 passes with no problem. With Furmark burn in, my GPU seems to level out at around 74-75 degrees celsius after around 5 minutes. I don't think I have any overheating problems with my hardware. I am not overclocking anything.

CPU-Z Screenshot

Here is a copy of the error I receive when I restart:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057


Additional information about the problem:
BCCode: 1
BCP1: FFFFF880012A21F8
BCP2: 0000000000000000
BCP3: 000000000000FFFF
BCP4: 0000000000000001
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1


Files that help describe the problem:
C:\Windows\Minidump\060912-16161-01.dmp
C:\Users\Timothy\AppData\Local\Temp\WER-28688-0.sysdata.xml


Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows


If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Thanks in advance for the help!

Most (with a single exception) of the dump files that you have attached are 124 hardware related.
Your latest;

Code:

BugCheck 124, {0, fffffa8004ffa8f8, 0, 0}
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: fffffa8004ffa8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`031a86f0 fffff800`02cd6ca9 : fffffa80`04ffa8d0 fffffa80`03a69040 00000000`00000004 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a8c10 fffff800`02bb7587 : fffffa80`04ffa8d0 fffff800`02c312d8 fffffa80`03a69040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a8c40 fffff800`02b1e985 : fffff800`02c92ae0 00000000`00000001 fffffa80`04c6a870 fffffa80`03a69040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a8c80 fffff800`02a9d851 : fffff880`010bbe00 fffff800`02b1e960 fffffa80`03a69000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a8cb0 fffff800`02d2ae6a : 00000000`00000000 fffffa80`03a69040 00000000`00000080 fffffa80`039739e0 : nt!ExpWorkerThread+0x111
fffff880`031a8d40 fffff800`02a84f06 : fffff880`02f63180 fffffa80`03a69040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a8d80 00000000`00000000 : fffff880`031a9000 fffff880`031a3000 fffff880`037fe740 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

More specifically

Code:

Common Platform Error Record @ fffffa8004ffa8f8
-------------------------------------------------------------------------------
Record Id     : 01cd45d1441b07e4
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/8/2012 23:49:05
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8004ffa978
Section       @ fffffa8004ffaa50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000100f43
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8004ffa9c0
Section       @ fffffa8004ffab10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 43 0f 10 00 00 08 04 00 - 09 20 80 00 ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8004ffab10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8004ffaa08
Section       @ fffffa8004ffab90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfa00000000070f0f

This is where I would normally do my standard, boilerplate recommendations;

Run sfc /scannow to verify the system files integrity.
Run Chkdsk
Run the correct Hard Drive Diagnostics Tool for your HDD.
Run Memtest86+ overnight, after your computer has been off for about an hour or two so it has a cold start. Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test.
Note!! Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Test RAM sticks individually. When you find a good one then test it in all slots. Post back with the results.
Memtest86+ 4.20 Download.
Guide to using Memtest86+
CPU - Stress Test with Prime95. Run the "Blend" and "Small FFTs" tests.
Video Card - Stress Test with Furmark.

Sounds like you've done most of them, although I would suggest revisiting MemTest86+ and stick with it a little longer, starting on a cold machine.
A decent reference to help understand these types of errors Stop 0x124 - what it means and what to try - Windows 7 Forums
And yes in addition to typical problems resulting from heat / temps, various and sundry physical issues like improperly or mis-seated memory, video or CPU, intentional or unintentional misconfiguration / over clocking, hardware issues can often come from a faulty, failing or just plain old not up to the task PSU.
Considering the diagnostic work you've applied to your problem up to this point maybe the PSU would be a good next step.
Regards
Randy

Hey Randy,

Thanks very much for the informative reply. I'll give Memtest another go tomorrow morning and see how that works out. The PSU was my original suspicion as it is only 400w and on the AMD site, it states 500w is recommended for my GPU. However, the problem doesn't seem to occur exclusively to power related tasks, for example running my CPU at 100% on all 4 cores doesn't cause a crash and neither does running Furmark. Would this rule out a PSU issue or is it not that simple?

Regards,
Tim

Ok, I'm back. Sorry I took so long, I had exams for the past few weeks. I ran memtest last night for 10 passes and received no errors whatsoever. I haven't had any overheating problems either during this time. So you recommend getting a new PSU, any way of checking for sure that this is the issue?

Originally Posted by twb2k8

So you recommend getting a new PSU, any way of checking for sure that this is the issue?

I am not recommending that you run out and buy a new PSU, I am simply suggesting that considering what you have managed to do up to this point in the way of diagnostics it would be something you would want to consider.
In so far as actually testing the PSU, unfortunately the only way to actually accomplish anything of value would be to test it under a load, which would involve the use of a muti-meter, some familiarity with the pin-outs and knowing what you should expect and being able to compare that with what you are actually seeing on the meter. That is a bit outside the scope of this forum and a bit above my pay grade. I am relatively certain that if you believe you have the requisite skill set and equipment, finding a method of doing so is likely available through Google.
You can always do a poor man's test by minimizing the demands on the PSU by disconnecting any and all unnecessary hardware devices (extra optical or hard drives, addin cards, USB peripherals, etc.,) even trying and older less demanding video card if those options are available to you. And then adding them back one at a time and continue testing.
Update these drivers, and while you are at it double check with your MoBo Mfg., for a BIOS update if available as well as anything new and recent regarding chipset drivers.

ASACPI.sys	3/27/2005	From here	ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE	Expand utilities, 12th one down, ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit
Rt64win7.sys	2/26/2009	From here	Realtek
RTL8187B.sys	3/24/2009	From here	Realtek

EDIT: Additionally, I couldn't help but notice that you have two instances of this driver running, with slightly different dates. Not sure how, why or what for, but something you may want to address.
AODDriver2.sys 1/16/2012
AODDriver2.sys 3/6/2012

Code:

fffff880`06b19000 fffff880`06b4a000   AODDriver2 AODDriver2.sys Tue Mar 06 03:55:00 2012 (4F55DEF4)
fffff880`06b4a000 fffff880`06b7c000   AODDriver2_fffff88006b4a000 AODDriver2.sys Mon Jan 16 01:42:46 2012 (4F13D4F6)