Solved More System Crashes

[rebelagentm]

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!

 

[zigzag3143]

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.

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

Thanks

Ken

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
---------

 

[rebelagentm]

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!

 

[rebelagentm]

Anyone?

 

[CarlTR6]

The windows tool to test the RAM is not as thorough as I like. [FONT=&quot]Download a copy of Memtest86+ - Advanced Memory Diagnostic Tool[FONT=&quot] and burn the ISO to a CD using [/FONT]http://isorecorder.alexfeinman.com/W7[FONT=&quot]. [/FONT][FONT=&quot]Boot from the CD, and leave it running for at least 7 passes. Post back with your results.

Next, [/FONT][/FONT]use this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net Post back and let us know the results.

Then go to the Western Digital site and use their testing tool to test your hard drive. Let us know the results of this.

You can test your CPU as well, using Prime95.

 

[rebelagentm]

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?

 

[CarlTR6]

Prime should tell you if your CPU is the problem. I don't know of anything for testing the motherboard except a bench in the tech shop.

Let us know the results of Memtest, FurMark and Prime.

 

[rebelagentm]

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!

 

[ttran]

Among the 3 test, Memtest is supposed to run overnight because it take quite long time. Hopefully the system won't crash or reboot while doing that. You will get the result after about 9 hours. In the morning, if the screen is still nicely blue screen color from the begining, you are fine

 

[rebelagentm]

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?

 

[ttran]

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html



Try this free video stress test: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

More visual: http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

 

[CarlTR6]

Yes, the tests are safe; but run them one at at a time.

With Memtest, errors, if any, will show in red.

With FurMark, you need to be watching your GPU temps. If your receive an error and/or if your GPU reaches its maximum operating temp, you need to stop the test. http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

 

[rebelagentm]

O.K. Thanks for the info and tutorial link!

I ran MemTest86+ overnight. It made it through five full passes without any errors and was about 81% complete on a sixth run without any errors thus far.

So, I'm guessing memory is not to blame here?

Unless someone here says otherwise, I'll proceed with the next test.

 

[rebelagentm]

One more thing: When running FurMark, does it show the temp of the GPU or do I need a separate utility for this?

Thanks!

 

[CarlTR6]

I would say that your RAM is good as far as Memtest can determine. After the seventh pass, stop it and move on to the next test.

It has been a long time since I have run FurMark. and I don't remember. You can down load Speedfan or CPUZ for temp monitoring. Both are free.

 

[rebelagentm]

I ran FurMark and it didn't take long before my entire screen distorted. Probably less than one minute. I had to force the PC off because I couldn't see the "Quit" button on the app.

The temp got up around 75 degrees Celcius before it distorted.

According to SpeedFan, my GPU sits around 49 degrees.

Is this normal? If all GPUs will eventually max out with this program, how does this tell you whether your graphics card is bad?

 

[rebelagentm]

Anyone?

 

[CarlTR6]

At a good bit under max temperature of your GPU, your display distorted and quit functioning properly. With a good graphics card, that should not have happened. FurMark stresses the graphics card to see if there are any faults. Apparently there are. I suggest that you should replace it.

 

[rebelagentm]

I ran Prime95 for 8.5 hrs. and it had no errors. The CPU's temp never exceeded 80 degrees celcius. Some cores hit 92, but the average temp never went over 80. I also had a co-worker run it in his machine with my CPU and same thing, no errors.

So, is it safe to say that all of these problems are the result of a faulty graphics card?

 

[rebelagentm]

Here is what I have tried so far in terms of troubleshooting:

• When these problems started last year, I ran FurMark to test the GPU. The test didn't even last a minute before the screen distorted and the system locked up. The temp got up to around 75 C.
• I ran the FurMark test again today. The temp reached 94 C within about 1-1.5 mins. I ran the test for about nine minutes total. The temp never exceeded 95 C, the system never locked up, and the screen showed no artifacts.
• I ran Prime95 for 8.5 hours and had no errors. According to SpeedFan, the temp never exceeded 80 C. Some cores did hit 92. I also had a co-worker run Prime95 with my proc in his machine and it did not report any errors either.
• I ran MemTest86+ for nearly six full passes and no errors were reported. I also ran the Windows memory testing tool and again, no errors.
• I have had both the motherboard and the graphics card RMA'd, and the manufactures said in both cases that they were fine.
• I tried installing a different graphics card in my system (an NVIDIA GeForce 9600 XT), but I could never get the card to work. During the reboot of the driver installation, the system would always lock up at the Windows 7 screen.

I reseated the processor as there did seem to be too much thermal paste applied. This did drop the CPU's average temp about 5 degrees while idling. I have not tested it again under Prime95, but given that the idle temp didn't drop much, I wouldn't expect it to do good enough on Prime95.

I contacted Intel and they are going to send me a new processor. They did however tell me that the memory I am using is not compatible with the i7 930. It runs at 1.65v, but the Intel rep told me that it should not exceed 1.5v give or take 5% and that using anything over that could possibly damage the processor or greatly reduce its life.
Processors — Intel® Core™ i7 desktop processors frequently asked questions

Interestingly though, OCZ says that the memory I have is specifically for the i7 family, even though it runs at 1.65v.
OCZ DDR3 PC3-10666 Reaper CL9 Edition Low-Voltage Triple Channel - OCZ

Even though Intel specifies DDR3-800/1066, I also saw a post on NewEgg from OCZ that said this: "This memory will run 1333 on i7, but you must increase your memory multiplier, or overclock your buss speed. We sell that as enthusiast memory, and it does require some tweaking to get there."
Newegg.com - OCZ Reaper Edition 12GB (3 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Low Voltage Desktop Memory Model OCZ3RPR1333C9LV12GK (Post is at the bottom)

What does everyone think? Do I need to buy new RAM that is 1066? Do I need to change the memory multiplier as OCZ suggests? Has this been the cause of my problems all along? I certainly don't want to damage my new processor once it arrives.