Random Restarts, Log File Enclosed

I've been having problems with random restarts. Sometimes they occur immediately after restarting the PC; other times it is hours later.

My specs:


2.3GHz AMD X2 Dual Core
Two 1GB Corsair brand DDR800 modules
M3A Asus MB
eVGA GeForce 7300 GS GPU
Audigy 2 soundcard
150GB Maxtor SATA-2 HD on MB controller
550W Corsair ATX power supply

I have tried removing one RAM module then the other and still had problems with restarts. I replaced the power supply already. I did a full reformat and reinstalled Windows. All connections are secure. The problem continues.

EDIT: CPU/BM temp hovers around 95-100F. It is cool to the touch. The case is open.
EDIT2: When using CPUStabTest in Troubleshoot mode, when I select Peripheral, I get an intermittent buzzing noise from my DVD drive. I do not have the knowledge to interpret the results further. The DVD drive is functioning normally.

I am at my wit's end. Help would be much appreciated.




The error log is as follows:


Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Ethan Farber\Local Settings\Temp\WERc06f.dir00\Mini030208-08.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sun Mar 2 22:16:19.875 2008 (GMT-8)
System Uptime: 0 days 0:32:52.478
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
............................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*** WARNING: Unable to verify timestamp for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {2, bab3c050, f6002000, 17a}



Probably caused by : hardware ( nt!KeForceResumeThread+1 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 00000002
Arg2: bab3c050
Arg3: f6002000
Arg4: 0000017a

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

NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
----------------------------------------------------------------
1111011000000000001000000000000000000000000000000000000101111010


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

OVER - Error Overflow
Indicates that a machine check error occurred while the results of a
previous error were still in the error-reporting register bank (that
is, the VAL bit was already set in the IA32_MCi_STATUS register).
the processor sets the OVER flag and software is responsible for
clearing it. Enabled errors are written over disabled errors, and
uncorrected errors are written over corrected errors. Uncorrected
errors are not written over previous valid uncorrected errors.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.

ADDRV - IA32_MCi_ADDR register valid
Indicates that the IA32_MCi_ADDR register contains the address where
the error occurred.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

MEMHIRERR - Memory Hierarchy Error {TT}CACHE{LL}_{RRRR}_ERR
These errors match the format 0000 0001 RRRR TTLL



Concatenated Error Code:
--------------------------
_VAL_OVER_UC_EN_ADDRV_PCC_MEMHIRERR_7A

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.



BUGCHECK_STR: 0x9C_AuthenticAMD

CUSTOMER_CRASH_COUNT: 8

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: Idle

MISALIGNED_IP:
nt!KeForceResumeThread+1
804f9deb 5d pop ebp

LAST_CONTROL_TRANSFER: from 806e7bff to 804f9deb

STACK_TEXT:
bab3c028 806e7bff 0000009c 00000002 bab3c050 nt!KeForceResumeThread+0x1
bab3c154 806e2c52 bab38d70 00000002 00000007 hal!KeRevertToUserAffinityThread+0x5
00000000 00000000 00000000 00000000 00000000 hal!HalpWriteCmosTime+0xce


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KeForceResumeThread+1
804f9deb 5d pop ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KeForceResumeThread+1

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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

 

Hi, nucleokinesis. Welcome to Windows BBS!

Please carefully follow all the instructions in this link and then paste DebugWiz-generated BSOD dump log analysis reports for a few of your most recent crashes in this thread. The DebugWiz-generated reports will include more details (such as module lists) than the log you posted.

Sometimes seeing a few dump logs helps us determine whether there is any pattern to the crashes or not. The additional information the DebugWiz-generated reports provide might help us narrow down the culprit more quickly.

The DebugWiz application should be run while connected to the Internet so your Windows Debugging Tools can retrieve the proper "symbols ".

NOTE:

 

• AumHa: Troubleshooting Windows STOP Messages