Welcome to SF!
Were you handling the PC while it was running?
If you did you might have shorted something out.
The SystemInfo.txt file is missing, please follow the instructions below.
Download and save Info.bat to the desktop.
Open an elevated command prompt and then type the following command:
Code:
cd C:\Users\<Username>\Desktop
Then type:
The batch file will begin to run, the SystemInfo.txt file will be saved to your C:\ partition,
the MSINFO32 file will simply open, therefore click File and then Save.
Chose the save location as your Desktop, and then copy the two files into a zipped folder.
Upload the zipped folder in your next post.
Attachment 292216
I would first shutdown the PC and disconnect it from the Mains (wall outlet) and re-seat all of the connectors / expansion cards and see if the coloured artifacts still appear after the fact.
Good practice, open up the case and re-seat all types of connection.
- SATA Cables (HDD/SSD/ODD).
- SATA-Power.
- Motherboard 24-pin.
- Motherboard 4/8-pin (CPU).
- Re-seat the RAM.
- Re-seat the GPU.
Make sure that every slot / cable head is free of dust or other obstruction.
Make sure that every connection is seating properly and firmly in-place.
Most of the bug checks were a TDR (Timeout Detection & Recovery) and its not a real crash
in the sense that something wrong occurred in the Kernel.
"Display driver xxxxx stopped responding and was recovered"
Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected.
.
.
.
.
There are numerous reports of hardware solutions to TDR's. The most common are:
- Poor Cooling
- Problems with the power supply
- Overclocking Issues
- Bad System memory or incorrect memory timings
- Defective PC Components
Code:
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008049010
Arg2: fffff88003e08db8
Arg3: 0000000000000000
Arg4: 0000000000000002
Code:
lmvm atikmpag
start end module name
fffff880`03e00000 fffff880`03e76000 atikmpag T (no symbols)
Loaded symbol image file: atikmpag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
Image name: atikmpag.sys
Timestamp: Fri Sep 28 04:12:52 2012
Please update the driver.
No code has to be inserted here.
The more worrying thing is that the latest of the dumps is a 0x124.
Code:
BugCheck 124, {0, fffffa8007ac4028, be200000, 5110a}
Code:
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa8007ac4138
Section @ fffffa8007ac42c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : GCACHEL2_ERR_ERR (Proc 3 Bank 6)
Status : 0xbe2000000005110a
Address : 0x000000016a0bbc40
Misc. : 0x000000d02401c086
You were stressing the PC using Prime95.
Code:
PROCESS_NAME: prime95.exe
This was a generic L2 CACHE error, this could be a thermal issue.
Code:
Error Type : Cache error
Operation : Generic
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. -
H2SO4
The generic nature of the 0x124 (Arg1=0) stop code means we would have to take
the trail & error approach.
What is the make, model and age of you PSU?
Fill out this form and post back the result:
Reset the BIOS back to default:
Note
Write down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.
Note
If any component is overclocked reset it back to stock speeds!
Test for thermals and stability (well you already tried this but we need this information):
- Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
- Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).
Good places to read more:
Post back with the results.
Quote