BSOD - Videocard ! Maybe !

p1tcho0 · Apr 28, 2012

Is Windows 7 . . .
- x86 (32-bit) or x64 ?x64
- the original installed OS on the system?yes
- an OEM or full retail version? OEM
This setup is an original by microsoft network for student !
- OEM = came pre-installed on system N
- Full Retail = you purchased it from retailer N

- What is the age of system (hardware)?2 year Max
- What is the age of OS installation (have you re-installed the OS?) 2012/03/11

Files that help describe the problem:
Every game we start the computer freeze and last time windows sent a warning about BSOD, so i would like to know
if these bsod is just an hardware fail of my video card ...

p1tcho0 · Apr 28, 2012

I did Video Stress test and i did all feature to find out an error and no errour found !

writhziden · Apr 29, 2012

What did you do a video stress test with? What software?

Security Software: ??? I recommend either of these two setups:

Download and install the security setup of your choice, update the software, and then run a full scan of your system for viruses and malware. If you only install MSE, I would also suggest installing and updating Malwarebytes : Free anti-malware, anti-virus and spyware removal download, but do not start the free trial/full version of Malwarebytes. Run a full scan with Malwarebytes after updating it. Post back the results.

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\p1tcho0\Windows_NT6_BSOD_jcgriff2\042812-15453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02818000 PsLoadedModuleList = 0xfffff800`02a5c650
Debug session time: Sat Apr 28 09:17:37.687 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:10.171
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, fffffa8003ee9038, 0, 0}

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: fffffa8003ee9038, 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`0316b6f0 fffff800`02ad9cb9 : fffffa80`03ee9010 fffffa80`024e6b60 00000000`00000007 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0316bc10 fffff800`029ba687 : fffffa80`03ee9010 fffff800`02a342b8 fffffa80`024e6b60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0316bc40 fffff800`02921a35 : fffff800`02a95ac0 00000000`00000001 fffffa80`03e65160 fffffa80`024e6b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0316bc80 fffff800`0289e471 : fffff880`01103e00 fffff800`02921a10 fffffa80`024e6b00 004f0049`ffffffd8 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0316bcb0 fffff800`02b2ef7a : 6f687465`4d6d754e fffffa80`024e6b60 00000000`00000080 fffffa80`024589e0 : nt!ExpWorkerThread+0x111
fffff880`0316bd40 fffff800`028859c6 : fffff880`02f63180 fffffa80`024e6b60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0316bd80 00000000`00000000 : fffff880`0316c000 fffff880`03166000 fffff880`037ac540 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
---------

The above crash was a 0x124 hardware crash. See http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html for more information, and use the following steps to supplement that link.

If you are overclocking any hardware, please stop.
Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
- Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
- Follow the steps for doing a CPU stress test using IntelBurnTest
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.

Remove the following software after disabling any overclocking it provides:

Code:

Start Menu\Programs\RivaTuner v2.24 MSI Master Overclocking Arena 2009 edition	Mike-PC\Mike:Start Menu\Programs\RivaTuner v2.24 MSI Master Overclocking Arena 2009 edition	Mike-PC\Mike

Make sure to read through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html carefully.

p1tcho0 · Apr 30, 2012

The tool from ultimatebootcd Video memory stress test

Gpu idle is 55 (normal for gtx260) Confirm by GPU-Z (tool asked by XFX)

Riva tuner was on the computer cauz i just adjust like 3 5 % the fan speed for the overheating.
These card got the trouble about fan speed
They adjust "default" it at 60 percent and these card are overheating

But after couple year, we have to or the card doesnt work While i was gaming
. This is just what I got when XFX swapped my card ... (SAme gtx)
I already owned this same card from xfx and i been like 2 3 month on 80% & + and more

and the lifetime warranty allowed me new card cauz she blown ( not for real but near )

So, i suppose it hardware fail

PS`: This setup *installation is new since 11 march has no virus on computer ...
This is a secondary computer when we use its for league of legend and we dont browse much with him we dont live on our mother house...

p1tcho0 · Apr 30, 2012

We did also 24 pass for memory !

And no we are not overclocker just normal gamer

writhziden · Apr 30, 2012

Instead of Riva Tuner, you could try SpeedFan - Access temperature sensor in your computer after uninstalling Riva Tuner. I have controlled my graphics card fan with SpeedFan myself.

BSOD - Videocard ! Maybe !

p1tcho0

New member

My Computer

p1tcho0

New member

My Computer

writhziden

Closed by request.

My Computer

p1tcho0

New member

My Computer

p1tcho0

New member

My Computer

writhziden

Closed by request.

My Computer