Receiving crashes more and more frequent

[grandkai]

Thank you for the tutorial. I have been receiving crashes more and more frequent and hoped to get it corrected. When viewing the dump file as you show the error or cause is so vague that I can not tell where to start to diagnose the problem. Can someone help me with this? I have worked with computers since back when punch cards were going out of fashion and only Win 3.0 crashed as much as windows 7 is doing now for me. The report states the cause is hardware, well I kind of figured that out and was a 50/50 was that or the software.

Thanks in advance for any help.


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\051310-20109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e42e50
Debug session time: Thu May 13 11:17:49.625 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:07.906
Loading Kernel Symbols
.................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80050cc8f8, 0, 0}

Probably caused by : hardware

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

1: 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: fffffa80050cc8f8, 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.

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


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`02fe06f0 fffff800`02ebfa79 : fffffa80`050cc8d0 fffffa80`03cfc040 00000000`00000006 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fe0c10 fffff800`02da15a7 : fffffa80`050cc8d0 fffff800`02e1a5f8 fffffa80`03cfc040 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fe0c40 fffff800`02d09b85 : fffff800`02e7c360 fffffa80`050e25b8 fffffa80`050e25b0 fffffa80`03cfc040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fe0c80 fffff800`02c82861 : fffff880`010fae00 fffff800`02d09b60 fffffa80`03cfc040 67005e6a`072400e2 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fe0cb0 fffff800`02f1aa86 : a7c0d36e`870cb0da fffffa80`03cfc040 00000000`00000080 fffffa80`03c6f890 : nt!ExpWorkerThread+0x111
fffff880`02fe0d40 fffff800`02c53b06 : fffff880`009e8180 fffffa80`03cfc040 fffff880`009f2f40 ff0100ef`00a071c3 : nt!PspSystemThreadStartup+0x5a
fffff880`02fe0d80 00000000`00000000 : fffff880`02fe1000 fffff880`02fdb000 fffff880`03773590 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_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

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

As a side note I did use the BlueScreenView program also and it reported that the cause was ntoskrnl.exe at address ntoskrnl.exe+4a5f3c and the description is NT Kernel & System. This contradicts the other report as this is software the other 50% chance of being right or wrong. Any help is appreciated.

 

[jcgriff2]

Hi -

Bugcheck 0x124 = WHEA = Windows Hardware Error Architecture

Information on 0x124 --> http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

There's always the chance that software is to blame. See if Driver Verifier can help.

Run Driver Verifier --> Driver Verifier - jcgriff2.com

Regards. . .

jcgriff2

.

 

[grandkai]

thank you for your response. I am currently running the Driver Verifier and will let it run for 24 hours. I am not sure what to look for when it is done but once it is done will look for anything that stands out. I have updated all drivers and the system is not running hot as well as not overclocked.

I will post back after I get the results from the driver verifier.

Thanks again,

 

[grandkai]

I have finally got the system to crash again. I looked at the driver verifier output and can not make heads or tails of it. I have attached a text file that shows the dump and after shows the output of the verifier.

Appreciate all your help with this.

 

[jcgriff2]

The attachment was a Driver Verifier status report showing D/V in progress..... did D/V BSOD the system? If so - it is the dump from the VERIFIER_ENABLED BSOD that is needed.

 

[grandkai]

Thank you for your response. No, the verifier did not BSOD the system. It actually ran for just over 36 hours before the system BSOD'd. If there is a different dump or a different option besides /query that I am not aware of can you let me know where I can find it and I will post it. As a side note I have done full disk check, several different online virus checks, defraged and all came up clean. Last month I ran the MS memory check and it ran for over 24 hours without a fail.

Any other ideas on where to go from here I appreciate it.

 

[Max Peck]

Grandkai,

Back in November I bought a new Dell machine (Inspiron 1545). Decided against my better judgement to just use the OEM install of the system. Removed some of the crap that came with it and installed my stuff. The system seemed to run OK for awhile but started getting Explorer crashes. Microsoft helped me diagnose to the point where we found I had a 32-bit driver installed where a 64-bit one was needed. That seemed to correct the problem for a little while but the problem soon came back. It eventually got so bad that I couldn't run the system for 5 minutes without an Explorer crash. Clearly something major was hosed.

I decided to go ahead and rebuild the machine from scratch this time, avoiding installing McAffee and the other junk that Dell ships with the system. Installed all my utilities, development tools and the works. Upgraded the system to Win7 Ultimate (in-place upgrade). Since that time have had no issues.

I know a system rebuild is a pain, but I keep finding that using the OEM installation can be problematic. You might want to consider this instead of wasting a lot of time trying to track a bad driver. It can be like the proverbial "needle-in-a-haystack" in systems this involved.

Since getting the machine up and stable, I take a snapshot (image) of the machine from time-to-time so I can always return to a stable installation without doing a rebuild again.

HTH,

-max

 

[grandkai]

Hi Max, when I first installed windows 7 ulitmate the machine it was a complete/full install wiping everything off the drive as the version I purchased being the full version would not let me upgrade only full install. I am using 64-bit version as well and MS direct purchase not OEM. I never really like going with Dell/Gateway or other big name manufacturers. Guess I am one of those against the norm. I swim upstream if everyone is swimming downstream. I built my own machine MSI with onboard video, network, etc. The only add on is the CPU and memory of course. Nothing is OEM all direct manufacturer purchased and the drivers/BIOS are updated to current version. I do understand what you are saying as I have had problems similar when going from 95 to 2000. Any other ideas would be appreciated.

Thanks again,
Albert