Windows 7: New Bsod Today

warshiv · 31 Oct 2010

Ok its been 2 days since the last help seemed to have fixed my Bsod issue, just today this happened tho attached the file hopefully its not the same thing again.

Cyberpower build Preinstalled win 7 x64
did a fresh install from supplied disc
amd phenom x6 t1055
8 gigs ram
2x ati 5770 vid cards
1t hardrive
system is 2 months old and cyberpower wants

**yowanvista** · 31 Oct 2010

BSOD caused by your ATI display driver

As it is the same BSOD error, there is a high probability that your graphic card is faulty

Possible causes:bad RAM/PSU, incorrect RAM timings/voltages, bad Graphics card, overheating, outdated driver

Uninstall the ATI driver then use driver sweeper to remove leftover ATI files
Guru3D - Driver Sweeper

Then reinstall your driver: ATI Radeon

This was likely caused by the following module: atikmpag.sys
Bugcheck code: 0x116 (0xFFFFFA8008021010, 0xFFFFF88006133F94, 0x0, 0x2)
Error: VIDEO_TDR_ERROR

richc46 · 31 Oct 2010

Dont know about last time, but replace your driver
Atikmpag.sys file description
Productname: AMD driver
Company: Advanced Micro Devices, Inc.

Code:

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Documents[1].zip\Windows_NT6_BSOD_jcgriff2\102910-20607-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e56e50
Debug session time: Fri Oct 29 11:46:38.162 2010 (GMT-4)
System Uptime: 0 days 0:20:57.066
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8008021010, fffff88006133f94, 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+6f94 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008021010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006133f94, 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+6f94
fffff880`06133f94 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`07035a58 fffff880`040d2ef8 : 00000000`00000116 fffffa80`08021010 fffff880`06133f94 00000000`00000000 : nt!KeBugCheckEx
fffff880`07035a60 fffff880`040d2c02 : fffff880`06133f94 fffffa80`08021010 fffffa80`06ef6300 fffffa80`06d17010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07035aa0 fffff880`04179f07 : fffffa80`08021010 00000000`00000000 fffffa80`06ef6300 fffffa80`06d17010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`07035ad0 fffff880`041a7d7e : fffffa80`ffffffff 00000000`00013a38 fffff880`07035c30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07035bb0 fffff880`0417529e : fffffa80`06d17010 ffffffff`feced300 fffffa80`06ef6300 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`07035bf0 fffff880`041a1e7a : 00000000`00000000 fffffa80`07014d50 00000000`00000080 fffffa80`06d17010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`07035d00 fffff800`02f2dc06 : 00000000`fffffc32 fffffa80`09ad9770 fffffa80`06cad9e0 fffffa80`09ad9770 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07035d40 fffff800`02c67c26 : fffff880`02dd5180 fffffa80`09ad9770 fffff880`02de0040 fffff880`01656c20 : nt!PspSystemThreadStartup+0x5a
fffff880`07035d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+6f94
fffff880`06133f94 4883ec28        sub     rsp,28h
SYMBOL_NAME:  atikmpag+6f94
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4cbfa04f
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------

It would have helped if you stayed in the same thread. The more pieces we have the more accurate the analysis
It appears that the driver was recently updated. The date is current. What was your last problem?

warshiv · 31 Oct 2010

Quick question other then running furmark and 3dmark on each card individually in each slot individually is there any other test i can perfrom to check the vid cards?

thanks

As yowan noted last time it was the Video driver and sound driver i redid the vid driver and removed the sound driver and it seemed to be fine for 2 days until just when i posted this message.

richc46 · 31 Oct 2010

That is the test that we use. Dont know of others.

warshiv · 31 Oct 2010

crashed one mroe time just posting this to verify that its the card/pcie slot and not the drivers thanks for the info on this matter tho.

CarlTR6 · 31 Oct 2010

This latest dump blames the Windows system Direct X Driver, more than likely not the real cause. It is another video error. Are you overclocking anything? If so, please return everything to default values.

All of your drivers are up to date except this one. I believe there is a later version available.

Quote:

AtiPcie.sys Tue May 05 11:00:22 2009 - ATI PCIE Driver for ATI PCIE chipsetGlobal Provider of Innovative Graphics, Processors and Media Solutions | AMD

warshiv · 01 Nov 2010

Ok no overclocking never made it that far with the comp.
newest BSOD's 2 in a row with a single vid card in atm hoping its this vidcard or the slot its in now so i can finally rma this and get it fixed.

CarlTR6 · 01 Nov 2010

Quote:

Error code 1A, MEMORY_MANAGEMENT. Usual causes: Device driver, memory, kernel.

Error code 3B, SYSTEM_SERVICE_EXCEPTION. Usual causes: System service, Device driver, graphics driver, ?memory.

Code:

Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e3de50
Debug session time: Mon Nov  1 13:37:04.700 2010 (GMT-4)
System Uptime: 0 days 0:24:47.604
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 38, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000038
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  GoogleToolbarU

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880033088e0 -- (.trap 0xfffff880033088e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8008972dc0 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8a00251fab0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d76817 rsp=fffff88003308a70 rbp=0000000000000000
 r8=fffffa800987000c  r9=fffffa8007388048 r10=fffffa8006cd64b0
r11=fffffa8009ee3720 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiEmptyPageAccessLog+0xe7:
fffff800`02d76817 8b4138          mov     eax,dword ptr [rcx+38h] ds:00000000`00000038=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c1cb7a to fffff80002c70740

STACK_TEXT:  
fffff880`03308778 fffff800`02c1cb7a : 00000000`0000001a 00000000`00041287 00000000`00000038 00000000`00000000 : nt!KeBugCheckEx
fffff880`03308780 fffff800`02c6e82e : 00000000`00000000 00000000`00a6240c 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42ba5
fffff880`033088e0 fffff800`02d76817 : 00000000`00000000 fffffa80`06cd64f0 fffffa80`0987e060 fffffa80`0987e060 : nt!KiPageFault+0x16e
fffff880`03308a70 fffff800`02cf2aac : fffffa80`0987e060 00000003`00000000 00000000`00000000 fffffa80`08972dc0 : nt!MiEmptyPageAccessLog+0xe7
fffff880`03308ae0 fffff800`02c84ee2 : 00000000`000005d0 00000000`00000000 fffffa80`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x4972b
fffff880`03308b80 fffff800`02c85173 : 00000000`00000008 fffff880`03308c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03308bd0 fffff800`02f14c06 : fffffa80`06d258e0 00000000`00000080 fffffa80`06cad890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03308d40 fffff800`02c4ec26 : fffff880`02f64180 fffffa80`06d258e0 fffff880`02f6f040 89480000`0228249c : nt!PspSystemThreadStartup+0x5a
fffff880`03308d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42ba5
fffff800`02c1cb7a cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42ba5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002fb7d90, fffff8800bb8c090, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObDereferenceSecurityDescriptor+20 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002fb7d90, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800bb8c090, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ObDereferenceSecurityDescriptor+20
fffff800`02fb7d90 8b4610          mov     eax,dword ptr [rsi+10h]

CONTEXT:  fffff8800bb8c090 -- (.cxr 0xfffff8800bb8c090)
rax=fffff8800bb8ca88 rbx=0000000000000000 rcx=0000000000000100
rdx=0000000000000001 rsi=00000000000000e0 rdi=0000000000000000
rip=fffff80002fb7d90 rsp=fffff8800bb8ca60 rbp=fffffa800a4871d0
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff8800bb8cb38 r12=0000000000000001 r13=fffffa800a462060
r14=00000000770a8b00 r15=fffff8a0025325f0
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ObDereferenceSecurityDescriptor+0x20:
fffff800`02fb7d90 8b4610          mov     eax,dword ptr [rsi+10h] ds:002b:00000000`000000f0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  SearchProtocol

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f822c4 to fffff80002fb7d90

STACK_TEXT:  
fffff880`0bb8ca60 fffff800`02f822c4 : 00000000`00000000 fffffa80`0a4871d0 fffffa80`06d2b410 00000000`00000000 : nt!ObDereferenceSecurityDescriptor+0x20
fffff880`0bb8ca90 fffff800`02cc08ee : 00000000`00000000 fffffa80`0a462060 fffffa80`06d2b410 fffff880`0bb8cbc0 : nt!SeDefaultObjectMethod+0xa8
fffff880`0bb8cae0 fffff800`02fd1514 : fffffa80`0a462060 00000000`00000000 fffffa80`0a463060 00000000`00000000 : nt!ObfDereferenceObject+0x10e
fffff880`0bb8cb40 fffff800`02fd1414 : 00000000`000003d4 fffffa80`0a462060 fffff8a0`025325f0 00000000`000003d4 : nt!ObpCloseHandleTableEntry+0xc4
fffff880`0bb8cbd0 fffff800`02cba993 : fffffa80`0a463060 fffff880`0bb8cca0 000007fe`fb800000 00000000`00000001 : nt!ObpCloseHandle+0x94
fffff880`0bb8cc20 00000000`76fbfe4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0020fa08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fbfe4a


FOLLOWUP_IP: 
nt!ObDereferenceSecurityDescriptor+20
fffff800`02fb7d90 8b4610          mov     eax,dword ptr [rsi+10h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ObDereferenceSecurityDescriptor+20

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff8800bb8c090 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ObDereferenceSecurityDescriptor+20

BUCKET_ID:  X64_0x3B_nt!ObDereferenceSecurityDescriptor+20

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

I recommend that you test your RAM with Memetest following the instructions in this tutorial: RAM - Test with Memtest86+. Run Memetest for at least seven passes from both a warm boot and a cold boot after your computer has been off for a while. Each run will take 6-8 hours. Errors will show on you screen in red. Post your results.

If Memetest shows no errors, enable Driver Verifier following the instructions in this tutorial: Driver Verifier - Enable and Disable. Use your computer normally while Driver Verifier is running. Upload any and all dumps generated by Driver Verifier.

warshiv · 01 Nov 2010

Ok will do, already ran verifier once but didnt save the logs so ill run it again.
and ill run memtest as well thanks......

Windows 7: New Bsod Today

New Bsod Today problems?