Random crashes? :(

Hello, last week I installed windows 7, but for some reason it is just constantly crashing. I already tried installing all drivers, but that did not fix it. It does not seem to happen when I run a certain application as far as I know.

I included all the crash dumps from today in the attached .rar file.

altaria1993 said:

Hello, last week I installed windows 7, but for some reason it is just constantly crashing. I already tried installing all drivers, but that did not fix it. It does not seem to happen when I run a certain application as far as I know.

I included all the crash dumps from today in the attached .rar file.

I took a quick look at the first 3 dumps. they were almost identical. the probable cause is Hardware. Either a device or driver I also notice that some of the drivers are almost 4 years old and should be updated.
\
I would suggest:
Updating the drivers
download a memory test like memtestx86 and run overnight
Run a system filecheck to verify you system files
system file check is run by typing cmd in search>rightclick and run as admin>
type sfc /scannow

Ken

These are the oldest drivers
ASACPI.sys fffff880`04224000 fffff880`0422c000 0x00008000 0x42476c4c 3/27/2005 10:30:36 PM
secdrv.SYS fffff880`05785000 fffff880`05790000 0x0000b000 0x4508052e 9/13/2006 9:18:38 AM
PFC027.SYS fffff880`04400000 fffff880`04491000 0x00091000 0x4574e8c1 12/4/2006 11:34:25 PM
SiWinAcc.sys fffff880`011ed000 fffff880`011f6000 0x00009000 0x4671d6fa 6/14/2007 8:02:02 PM
SiRemFil.sys fffff880`01958000 fffff880`01960000 0x00008000 0x46798312 6/20/2007 3:42:10 PM
SCDEmu.SYS fffff880`03a3e000 fffff880`03a50000 0x00012000 0x46b88d94 8/7/2007 11:19:48 AM
SI3132.sys fffff880`01139000 fffff880`01153000 0x0001a000 0x4703e1e1 10/3/2007 2:39:29 PM
PxHlpa64.sys fffff880`01000000 fffff880`0100bae0 0x0000bae0 0x475dd06d 12/10/2007 7:49:01 PM



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


Loading Dump File [C:\Users\K\Desktop\103009-30466-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a08000 PsLoadedModuleList = 0xfffff800`02c45e50
Debug session time: Fri Oct 30 07:03:56.119 2009 (GMT-4)
System Uptime: 0 days 1:04:24.820
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8003151038, f6470000, 10015}

Probably caused by : hardware

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

0: 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: fffffa8003151038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f6470000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010015, 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: msnmsgr.exe

CURRENT_IRQL: f

STACK_TEXT:
fffff800`040a2ac8 fffff800`02ff7903 : 00000000`00000124 00000000`00000000 fffffa80`03151038 00000000`f6470000 : nt!KeBugCheckEx
fffff800`040a2ad0 fffff800`02b8e513 : 00000000`00000001 fffffa80`027dc620 00000000`00000000 fffffa80`027dc670 : hal!HalBugCheckSystem+0x1e3
fffff800`040a2b10 fffff800`02ff75c8 : 00000000`00000728 fffffa80`027dc620 fffff800`040a2e70 fffffa80`05589c00 : nt!WheaReportHwError+0x263
fffff800`040a2b70 fffff800`02ff6f1a : fffffa80`027dc620 fffff800`040a2e70 fffffa80`027dc620 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`040a2cc0 fffff800`02feae8f : fffffa80`05589b60 00000000`00000001 fffff800`040a2ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`040a2d00 fffff800`02a787ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff800`040a2d30 fffff800`02a78613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`040a2e70 fffff800`02a80fff : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`05b16af0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x17f


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_TLB

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_TLB

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

I already updated those drivers, and it still crashes, so I don't think that's the problem, I think I changed them before the last crashes in those logs, so the last few should say so.

altaria1993 said:

I already updated those drivers, and it still crashes, so I don't think that's the problem, I think I changed them before the last crashes in those logs, so the last few should say so.

Stop 0x124 is a hardware error report being passed along by Windows.

Either one of the hardware drivers is "driving" in a way that gives the hardware component conniptions, or the hardware is actually broken. Either way, dump analysis won't get you much further, other than perhaps yielding a list of older drivers which may need updating. Suggestions:

1) Update your BIOS.
2) Update all hardware-related drivers (NIC, chipset, video...).
3) Don't overclock.
4) Ensure adequate cooling.
5) Take it back to the shop if 0x124 errors persist.