More System Crashes

On three or four occasions, my video card has seemingly caused problems with my system. Two of those times, the screen locked up and distorted.


I have already ensured that I have the latest drivers and BIOS and I have even uninstalled and reinstalled the driver for the video card. I have run memory and hard disk checks using the built-in Windows 7 tools and they did not report any errors.


I have had some other issues with the system which you can see in the thread listed below. The last issue listed here I was told had to do with my CPU and/or motherboard. Could those be the culprit here as well?
Previous Thread


Can someone look at the attached dump files and help me figure out what is going on? I have heard everything from my CPU is bad to my video card driver is bad. I really need to figures out what is going on here. I have included every dump file from every crash.


Thanks very much in advance!

rebelagentm said:

On three or four occasions, my video card has seemingly caused problems with my system. Two of those times, the screen locked up and distorted.


I have already ensured that I have the latest drivers and BIOS and I have even uninstalled and reinstalled the driver for the video card. I have run memory and hard disk checks using the built-in Windows 7 tools and they did not report any errors.


I have had some other issues with the system which you can see in the thread listed below. The last issue listed here I was told had to do with my CPU and/or motherboard. Could those be the culprit here as well?
Previous Thread


Can someone look at the attached dump files and help me figure out what is going on? I have heard everything from my CPU is bad to my video card driver is bad. I really need to figures out what is going on here. I have included every dump file from every crash.


Thanks very much in advance!

In an effort to respond quickly I have only done the most recent DMP. It was caused by hardware.
Please use these instructions to find out what These crashes were caused by several things but they all point to hardware. Please use these instructions to find out what that means and to figure out what to try.

https://www.sevenforums.com/crash-loc...-what-try.html

Thanks

Ken

Code:

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


Loading Dump File [C:\Users\K\Desktop\070910-25178-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c56000 PsLoadedModuleList = 0xfffff800`02e93e50
Debug session time: Fri Jul  9 10:10:24.080 2010 (GMT-4)
System Uptime: 0 days 0:00:10.219
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, fffffa800baf1038, 0, 0}

Probably caused by : hardware

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

3: 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: fffffa800baf1038, 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`033626f0 fffff800`02f10a79 : fffffa80`0baf1010 fffffa80`09d6d040 00000000`00000011 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03362c10 fffff800`02df25a7 : fffffa80`0baf1010 fffff800`02e6b5f8 fffffa80`09d6d040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03362c40 fffff800`02d5ab85 : fffff800`02ecd360 fffffa80`0ba12148 fffffa80`0ba12140 fffffa80`09d6d040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03362c80 fffff800`02cd3861 : fffff880`011b4e00 fffff800`02d5ab60 fffffa80`09d6d040 3c6e3c6e`23012301 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03362cb0 fffff800`02f6ba86 : 2cca2cca`28c928c9 fffffa80`09d6d040 00000000`00000080 fffffa80`09d51040 : nt!ExpWorkerThread+0x111
fffff880`03362d40 fffff800`02ca4b06 : fffff880`0316a180 fffffa80`09d6d040 fffff880`031750c0 6f7d6f7d`a081a081 : nt!PspSystemThreadStartup+0x5a
fffff880`03362d80 00000000`00000000 : fffff880`03363000 fffff880`0335d000 fffff880`03fdd540 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_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

3: 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: fffffa800baf1038, 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`033626f0 fffff800`02f10a79 : fffffa80`0baf1010 fffffa80`09d6d040 00000000`00000011 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03362c10 fffff800`02df25a7 : fffffa80`0baf1010 fffff800`02e6b5f8 fffffa80`09d6d040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03362c40 fffff800`02d5ab85 : fffff800`02ecd360 fffffa80`0ba12148 fffffa80`0ba12140 fffffa80`09d6d040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03362c80 fffff800`02cd3861 : fffff880`011b4e00 fffff800`02d5ab60 fffffa80`09d6d040 3c6e3c6e`23012301 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03362cb0 fffff800`02f6ba86 : 2cca2cca`28c928c9 fffffa80`09d6d040 00000000`00000080 fffffa80`09d51040 : nt!ExpWorkerThread+0x111
fffff880`03362d40 fffff800`02ca4b06 : fffff880`0316a180 fffffa80`09d6d040 fffff880`031750c0 6f7d6f7d`a081a081 : nt!PspSystemThreadStartup+0x5a
fffff880`03362d80 00000000`00000000 : fffff880`03363000 fffff880`0335d000 fffff880`03fdd540 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_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

I have tried the things mentioned in the article. I ran the Windows tool to test the RAM and had no errors. I also checked the hard drives for errors and nothing there either. I have not stress tested the CPU, motherboard, or video card and I'm not sure how to do that.

From what I'm seeing so far, I either have a problem with the CPU and/or motherboard, and possibly a problem with the video card. Or maybe all three. I'm just trying to figure out which it is.

Would you mind looking at all the files when you have a chance and let me know what you think?

Thanks for your help so far! It is much appreciated!

Anyone?

O.K. I will look at trying out MemTest86 and FurMark as soon as I get a chance.

Per Intel's suggestion, I was going to have someone test out my CPU in their system. Would running Prime95 do the same thing for me and single out the CPU if it is the problem?

Anything for testing out the motherboard?

I'm ready to try MemTest, Prime, and FurMark. Before doing so though, are these things safe to run overnight or are they something I need to keep a constant eye on?

Thanks!

Besides running them overnight, are they safe at all? Sorry for the noob questions, but I was watching a video of FurMark stressing a card and it really gets the fan spinning. Just don't want to damage any of my hardware.

Should the case be open or anything like that to prevent heat build-up from damaging other hardware?