Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › How do I fix bluescreen???
New Posts  All Forums:Forum Nav:

How do I fix bluescreen??? - Page 4

post #31 of 33
Hi smile.gif Sorry to hear you're still having issues!

Multiple 116 TDR bugchecks, the rest point to core MS files and drivers, so those are incorrect. There are a multitude of things that can cause this specific bugcheck. Before going into that, I should mention this:

NOTE: If overclocking, please reset the system to default values while troubleshooting it. This includes CPU, RAM, GPU overclocking. You're more than welcome to put your stocks back to clock after we've diagnosed your issues!!!!!

The first thing I recommend doing if overclocks aren't the issue is fully uninstalling and reinstalling your AMD video card drivers, as a bad driver installation can cause 116 bugchecks, especially since the culprit is being pointed to the (AMD video card drivers). If these issues started happening after a driver update, rollback the video card drivers you installed to an earlier version that worked previously without issue.

If drivers do not help, your issue may be heat related, inadequate cooling, dust buildup in the fans or pci-e slot, so make sure your rig is being cooled adequately.

Run Furmark to test your video card to ensure that the card(s) itself is running as intended:
Quote:
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

The following hardware issues can cause a TDR event:
Quote:
- Failing overclock on CPU or GPU (stop overclocking)
- Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory) ( MemTest and a video memory stress test: |MG| Video Memory Stress Test 1.7.116 Download )
- Corrupt hard drive/windows install resulting in corruption to the system registry or the page file (Hard drive diagnostics ( HD Diagnostic ), reset your pagefile

Memtest download to test your RAM: http://www.memtest86.com/

To "reset" the pagefile, follow these instructions:
Quote:
Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

Run System File Checker:
Quote:
SFC.EXE /SCANNOW
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

- Over heating of GPU or CPU again resulting in corrupt data being communicated. (Point a house fan at the video card, take temperature readings from the card with an IR detector (or your finger - but be very, very careful!!!)

- GPU failure due to any sort of issue from insufficient power(VERY common) to heat. (check the power leads, use a multimeter to check the power output, try another, more powerful PSU)

The following software issues can cause a TDR event:
Quote:
-Incompatible drivers of any sort (either GPU, sound, etc) ( http://www.microsoft.com/windows/com...s/default.aspx )
-Messy registry (I doubt this and don't approve of registry cleaners)
-Known vista issues resounding around multiple displays, aero, dreamscape, and various display drivers. (none known for this OS)
-Known vista issues that sometimes cause corrupt information to be sent to the video card from system memory (will be addressed completely in SP2, has had various fixes applied since vista's release) (none known for this OS)
-Bad direct x files (uninstall, then reinstall DirectX)
-bad system files (System File Checker - was run above)
-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom) - (remove all 3rd party programs and check to be sure drivers aren't loading. Then install only the necessary 3rd party stuff, and ensure it's the latest version and that it's compatible with Windows 7)

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Cardbox\Downloads\042912-43446-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 Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03656000 PsLoadedModuleList = 0xfffff800`0389a650
Debug session time: Sun Apr 29 21:02:07.969 2012 (UTC - 4:00)
System Uptime: 0 days 0:50:24.499
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80125d74e0, fffff8800462d8b8, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+78b8 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80125d74e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800462d8b8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+78b8
fffff880`0462d8b8 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`091e8a68 fffff880`054e8000 : 00000000`00000116 fffffa80`125d74e0 fffff880`0462d8b8 00000000`00000000 : nt!KeBugCheckEx
fffff880`091e8a70 fffff880`054e7d0a : fffff880`0462d8b8 fffffa80`125d74e0 fffffa80`1211b9a0 fffffa80`0cd80410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`091e8ab0 fffff880`0558ef07 : fffffa80`125d74e0 00000000`00000000 fffffa80`1211b9a0 fffffa80`0cd80410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`091e8ae0 fffff880`055b8b75 : fffffa80`ffffffff 00000000`0002f4cd 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`091e8bc0 fffff880`0558a2d5 : fffffa80`0cd80410 fffffa80`00000002 00000000`0002f4cd 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`091e8bf0 fffff880`055b6e7a : 00000000`00000000 fffffa80`0d40c190 00000000`00000080 fffffa80`0cd80410 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`091e8d00 fffff800`0396cfda : 00000000`fffffc32 fffffa80`0fdedb60 fffffa80`0cd7a040 fffffa80`0fdedb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`091e8d40 fffff800`036c39c6 : fffff800`03847e80 fffffa80`0fdedb60 fffff800`03855cc0 3778302c`13fd4c32 : nt!PspSystemThreadStartup+0x5a
fffff880`091e8d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+78b8
fffff880`0462d8b8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+78b8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ea760b6

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

post #32 of 33
Thread Starter 
Thanks, I quit OCing my CPU and it hasn't bluescreened since, again, Thank You guys!
Blue Skittle
(24 items)
 
  
CPUMotherboardGraphicsRAM
FX 8350 4.6ghz Asus Sabertooth 990FX EVGA GTX 670 FTW Corsair Vengeance Blue 16gb 1600mhz 
Hard DriveHard DriveHard DriveOptical Drive
Seagate 500gb OS Drive Seagate 1TB Internal (2.5" on 5.25" brackets) WD Green Caviar Internal 3TB Sony Blu ray player 
CoolingOSMonitorKeyboard
Corsair H80 Windows 7 Home Premium Asus VE247H Logitech G510 
PowerCaseMouseMouse Pad
Silverstone Decathlon 650w Corsair Vengeance Series C70 A4 Tech XL-750BK Razer Goliathus  
AudioAudioAudioAudio
Sennheiser HD598  Sony Stereo 540w Tritton AX 180  Superlux 668B semi open 
OtherOtherOtherOther
WD Elements 1TB External  Toshiba 500gb USB 3.0 External Xbox 360 wireless controller adapter Logitech MX Anywhere 
  hide details  
Reply
Blue Skittle
(24 items)
 
  
CPUMotherboardGraphicsRAM
FX 8350 4.6ghz Asus Sabertooth 990FX EVGA GTX 670 FTW Corsair Vengeance Blue 16gb 1600mhz 
Hard DriveHard DriveHard DriveOptical Drive
Seagate 500gb OS Drive Seagate 1TB Internal (2.5" on 5.25" brackets) WD Green Caviar Internal 3TB Sony Blu ray player 
CoolingOSMonitorKeyboard
Corsair H80 Windows 7 Home Premium Asus VE247H Logitech G510 
PowerCaseMouseMouse Pad
Silverstone Decathlon 650w Corsair Vengeance Series C70 A4 Tech XL-750BK Razer Goliathus  
AudioAudioAudioAudio
Sennheiser HD598  Sony Stereo 540w Tritton AX 180  Superlux 668B semi open 
OtherOtherOtherOther
WD Elements 1TB External  Toshiba 500gb USB 3.0 External Xbox 360 wireless controller adapter Logitech MX Anywhere 
  hide details  
Reply
post #33 of 33
Good to hear smile.gif
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › How do I fix bluescreen???