The results of this one dump indicate hardware. I would suggest you check your HD carefully. It of course could be any thing that is part of your computer.
I suggest that you test your hard drive and back everything up.
http://www.tacktech.com/display.cfm?ttid=287
If the problem does not occur in safe mode, it would be a driver issue. It appears to be hardware related, however. The meaning of the actual error code 124 is less clear.
In addition these drivers must be replaced, they have outlived their usefulness.
fffff880`04745000 fffff880`04759380 pcouffin pcouffin.sys Tue Dec 05 09:39:30 2006 (457584A2)
fffff880`04783000 fffff880`047bf880 mcdbus mcdbus.sys Tue Feb 24 05:34:07 2009 (49A3CD1F)
fffff880`03af6000 fffff880`03aff000 NuidFltr NuidFltr.sys Fri May 08 04:53:31 2009 (4A03F30B)
fffff880`015da000 fffff880`015e2000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`06b8b000 fffff880`06bfc000 spsys spsys.sys Mon May 11 13:20:58 2009 (4A085E7A)
fffff880`00db9000 fffff880`00dc4000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB)
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Seven%20Forums[1].zip\Seven Forums\Minidumps\060810-20919-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c54000 PsLoadedModuleList = 0xfffff800`02e91e50
Debug session time: Tue Jun 8 09:08:11.208 2010 (GMT-4)
System Uptime: 0 days 0:50:33.190
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8004b07028, b66b4000, 175}
Probably caused by : hardware
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* 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: fffffa8004b07028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b66b4000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000175, 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: firefox.exe
CURRENT_IRQL: f
STACK_TEXT:
fffff880`009b9b08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
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
---------