Help BSOD!!!

[dango]

Hello!

I have read many threads about kernel power error, but still haven't gotten my problem solved. I have updated drivers, changed graphic card, changed mother board, tested my RAM, tried without soundcard, tried diaable prosessors additional settings and so on. I don't even remember aal the things I've tried. Only thing is that when the graphic card was changed pc won't stun enymore when the BSOD happens, now it boots up clean. It used to make the craphic cards cooler go 100% and black screen. And also now it mostly happens when I play games. So not so bad anymore, but what's the point having expensive pc if you can't play with it? Please help me! any help is appreciated!

thank you!

ps. I'm new here not not sure where I should post this problem, so I posted it here

 

[zigzag3143]

Hello!

I have read many threads about kernel power error, but still haven't gotten my problem solved. I have updated drivers, changed graphic card, changed mother board, tested my RAM, tried without soundcard, tried diaable prosessors additional settings and so on. I don't even remember aal the things I've tried. Only thing is that when the graphic card was changed pc won't stun enymore when the BSOD happens, now it boots up clean. It used to make the craphic cards cooler go 100% and black screen. And also now it mostly happens when I play games. So not so bad anymore, but what's the point having expensive pc if you can't play with it? Please help me! any help is appreciated!

thank you!

ps. I'm new here not not sure where I should post this problem, so I posted it here

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

 

[Shadowjk]

These Links May help you

http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html - Only to be used if you are confused with the Process that Zigzag3143 is Presenting

Josh

 

[dango]

Ok I found the dump files and tried to zip them. If I did something wrong then I'll need more accurate guide...

thank you for you fast replay to my problem

 

[zigzag3143]

Ok I found the dump files and tried to zip them. If I did something wrong then I'll need more accurate guide...

thank you for you fast replay to my problem

These are fine.

They were probably caused by your video driver. Please use this to re-install it with the newest version

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

Or if the above doesnt work for you. Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.

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


Loading Dump File [C:\Users\K\Desktop\030811-19921-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0304b000 PsLoadedModuleList = 0xfffff800`03290e90
Debug session time: Tue Mar  8 11:22:35.858 2011 (GMT-4)
System Uptime: 0 days 0:07:59.794
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 117, {fffffa8004983010, fffff88003f033bc, 0, 0}

Unable to load image 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+73bc )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa8004983010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003f033bc, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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


FAULTING_IP: 
atikmpag+73bc
fffff880`03f033bc ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`023bd490 fffff880`045025f7 : fffffa80`04983010 00000000`00000024 fffffa80`07e9c1f0 fffff880`04502298 : watchdog!WdDbgReportRecreate+0xa3
fffff880`023bd9b0 fffff880`04502a2e : 00000000`00001000 fffff8a0`0825c420 00000000`00000008 00000000`00003a00 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`023bda00 fffff880`04503ce2 : fffffa80`04983010 fffffa80`04983010 fffffa80`07e9c1f0 fffffa80`07de7010 : dxgkrnl!TdrCollectDbgInfoStage1+0x2e6
fffff880`023bdaa0 fffff880`045aaf07 : fffffa80`04983010 00000000`00000000 fffffa80`07e9c1f0 fffffa80`07de7010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`023bdad0 fffff880`045d8d5a : fffffa80`ffffffff 00000000`000074c2 fffff880`023bdc30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`023bdbb0 fffff880`045a629e : fffffa80`07de7010 ffffffff`feced300 fffffa80`07e9c1f0 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`023bdbf0 fffff880`045d2e7a : 00000000`00000000 fffffa80`07e9c1f0 00000000`00000080 fffffa80`07de7010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`023bdd00 fffff800`03368cce : 00000000`037b6606 fffffa80`07dfa060 fffffa80`03ced040 fffffa80`07dfa060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`023bdd40 fffff800`030bcfe6 : fffff880`009ea180 fffffa80`07dfa060 fffff880`009f50c0 54582031`3834522c : nt!PspSystemThreadStartup+0x5a
fffff880`023bdd80 00000000`00000000 : fffff880`023be000 fffff880`023b8000 fffff880`023bc070 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+73bc
fffff880`03f033bc ??              ???

SYMBOL_NAME:  atikmpag+73bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d409c8d

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

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

 

[Shadowjk]

In addition to Zigzag3143

Drivers - Download NVIDIA Drivers

I believe this is where to download your Graphics Card drivers

   Note

You have a 64 Bit OS

 

[dango]

Thanks, but after doing what you told me to do I got another small problem (see the screenshot)

thanks for the help so far

 

[dango]

Ok I cleaned the drivers again and I don't get the message about old drivers anymore but still while playing pc crash and reboot.... any more ideas?

 

[dango]

ok I post here just if somebody has same problem and wants to get it fixed. So I underclocked my graphic card and pc no longer crash while gaming. All I would like to know why I have to underclock the graphic card. And before you say anything about temp, temperature when playing is max 63C and as far as I know it shouldn't crash untill temp goes over 100C. So any ideas why? I would like to use my graphic card with normal clocks....

 

[dango]

Bsod

Hello, I have posted before that I had constantly BSOD and then I was adviced to clean graphic card drivers and install fresh ones. Well I did that and I have tried a lot more. I even uninstalled virus protection bacause when I had avira then "avipbb.sys" had run before crash and it's avira's file (?) then I installed avast and when kernel power error came then "aswSnx.sys" file run before kernel power error and that's avast's file, right???

Well finally I was able to get somekind of information. When yesterday my pc, crashed I had crash report which I don't understand at all...I'll copy it here if somebody could explain what's in it. (BSOD.txt file)

I'll be more than happy to give any more information if needed, please help me! I have struggle with this pc for almost 5 months

I'll add here also new dump file which was mentioned in the crash report

edit: ok I found more information I'll copy paste it here

Description
A problem with your video hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1035

Extra information about the problem
BCCode: 117
BCP1: FFFFFA80045BB110
BCP2: FFFFF8800F20A6E8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Bucket ID: X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys
Server information: 12c57d8b-5a9e-41da-b98a-6ff5ae819dff

does that help???