BSOD's

[Watson]

2 ones today

 

[CarlTR6]

Error code 116 VIDEO_TDR_FAILURE - usually caused by Video driver, overheating, bad video card, ?BIOS, ?Power to card

Error code 1A MEMORY_MANAGEMENT - usually caused by Device driver, memory, kernel

The first dump blames atikmpag.sys; Attempt to reset the display driver and recover from timeout failed. The second dump points to memory corruption.

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_082010-19640-01.zip\082010-19640-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0281f000 PsLoadedModuleList = 0xfffff800`02a5ce50
Debug session time: Fri Aug 20 12:22:42.861 2010 (GMT-4)
System Uptime: 0 days 8:05:41.391
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80025e5290, fffff88003c3bc80, 0, 2}

*** 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+6c80 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80025e5290, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003c3bc80, 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+6c80
fffff880`03c3bc80 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`02ec29c8 fffff880`03cd7ef8 : 00000000`00000116 fffffa80`025e5290 fffff880`03c3bc80 00000000`00000000 : nt!KeBugCheckEx
fffff880`02ec29d0 fffff880`03cd7c02 : fffff880`03c3bc80 fffffa80`025e5290 fffffa80`03f5e950 fffffa80`041d2410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02ec2a10 fffff880`04fc7f07 : fffffa80`025e5290 00000000`00000000 fffffa80`03f5e950 fffffa80`041d2410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02ec2a40 fffff880`04ff1b75 : 00000000`ffffffff 00000000`001c805c 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02ec2b20 fffff880`04ff02bb : 00000000`00000102 00000000`00000000 00000000`001c805c 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02ec2b50 fffff880`04fc32c6 : ffffffff`ff676980 fffffa80`041d2410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02ec2bf0 fffff880`04fefe7a : 00000000`00000000 fffffa80`040b2170 00000000`00000080 fffffa80`041d2410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02ec2d00 fffff800`02b33c06 : 00000000`fffffc32 fffffa80`042fcb60 fffffa80`01843b30 fffffa80`042fcb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02ec2d40 fffff800`0286dc26 : fffff800`02a09e80 fffffa80`042fcb60 fffff800`02a17c40 fffff880`01261534 : nt!PspSystemThreadStartup+0x5a
fffff880`02ec2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6c80
fffff880`03c3bc80 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+6c80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c33d53e

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_082010-19640-01.zip\082010-19562-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0284d000 PsLoadedModuleList = 0xfffff800`02a8ae50
Debug session time: Thu Aug 19 21:59:14.691 2010 (GMT-4)
System Uptime: 0 days 12:19:25.221
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8886, fffffa80015d0440, fffffa8000bf9070, 500}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+298 )

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

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

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

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


BUGCHECK_STR:  0x1a_8886

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800028de8c8 to fffff800028bd740

STACK_TEXT:  
fffff880`0280b888 fffff800`028de8c8 : 00000000`0000001a 00000000`00008886 fffffa80`015d0440 fffffa80`00bf9070 : nt!KeBugCheckEx
fffff880`0280b890 fffff800`028ef587 : 00000000`06cd72ae fffff680`00000000 0000007f`06cd72ae fffff680`000366b8 : nt!MiUnlinkPageFromLockedList+0x298
fffff880`0280b920 fffff800`028d9d26 : 00000000`00000001 00000000`06cd72ae fffff880`0280bc20 fffffa80`0433dec8 : nt!MiResolveTransitionFault+0x167
fffff880`0280b9b0 fffff800`028d7743 : ffffffff`ffffffff fffff880`0280bb40 0001dab6`00000080 fffff880`0280bb40 : nt!MiDispatchFault+0x946
fffff880`0280bac0 fffff800`028bb82e : 00000000`00000001 00000000`02895550 00000000`00000001 fffffa80`0189ed80 : nt!MmAccessFault+0x343
fffff880`0280bc20 00000000`778a2b7f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`00f4e120 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778a2b7f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUnlinkPageFromLockedList+298
fffff800`028de8c8 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+298

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+298

BUCKET_ID:  X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+298

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

You video driver is up to date. You can try to reinstall atikmpag.sys it on the offchance is is corrupted. I am wondering if your video card is bad?

Something is definitely corrupting memory. You can re enable Driver Verifier for about 36 hours and see what happens. Maybe one of the other BSOD team members can spot something I have missed.

 

[Watson]

Ok had another one. I actually moved my case the other day to put the ethernet cable back in after I had taken it out to use with my Xbox. Maybe I dislodged something. I'll check it out now.

 

[Watson]

I have the thing running atm with the case open on the floor and am running everything fine so far. The graphics card felt looser than normal and i gave it a few nudges and it seems to fit a bit better. lets hope thats all it was :S.

Cheers for pointing me in that direction and I'll report back

 

[CarlTR6]

I have the thing running atm with the case open on the floor and am running everything fine so far. The graphics card felt looser than normal and i gave it a few nudges and it seems to fit a bit better. lets hope thats all it was :S.

Cheers for pointing me in that direction and I'll report back

Good diagnosing! I hope that is the cure. Let us know.

 

[Watson]

Ok after going afk again and the computer going into sleep. I got this blue screen almost as soon as I came back. Something must have changed again during the past few days. Before now I was absolutely fine for days while playing games quite a lot.

 

[ttran]

Test your RAM again, I turned to previous page and saw that Carl suggested you to check RAM but I've not seen your response. The DMP point to memory corruption with stop code 1A which is memory management.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

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


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.466\082110-18782-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02805000 PsLoadedModuleList = 0xfffff800`02a42e50
Debug session time: Sat Aug 21 18:52:13.395 2010 (UTC + 7:00)
System Uptime: 0 days 1:28:46.800
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {8886, fffffa8000bf90a0, fffffa8000000210, 600}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+298 )

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

Regard,

Tuan

 

[Watson]

I have got that on CD but I'll dl it and do it again. It kept freezing after a few hours before while I left it overnight. Maybe a fresh cd burn will help.

Got another one after going afk and coming back almost instantly. i'm sure that it's something to do with it going into sleep. So I'm gonna disable that.

 

[CarlTR6]

Watson, check your power saving settings. Something is not waking up properly. Control Panel > Power Options > Balanced > Change plan settings. I have mine set for Put the computer to sleep - Never. I put mine to sleep via the Start > Shutdown button.

Now click on Change advanced power settings and review what you have. I have my Wireless adapter setting set to Maximum performance. This resolved the sleep issue I was having. Under Sleep, I have mine set to never and Allow wake timers enabled. PCI Express is set to Moderate power savings. Under Multimedia and When sharing media, I have mine set to Prevent idling to sleep.

Let us know if this helps the problem.

 

[Watson]

I changed it to never and all my settings apart from that were already the same as you specified. On the memtest point. I ran one overnight last night and had 8 passes with no errors.

Yesterday I did blue screen twice, both while playing Mount and Blade Warband. Thing is there is no dump files as on the blue screen it froze at about 65% of the dump. Unfortunately I ddin't write the error message down :S.

 

[CarlTR6]

Glad to hear your RAM is OK; but sorry to hear about the freezes. If you get a dump file, be sure to upload it. If I had to guess, I would say a video or network adapter error.

 

[Watson]

Another one while playing M&B. This time the dump completed so i have something to upload.

 

[CarlTR6]

Unfortunately, it does not tell us much.

Bugcheck A IRQL_NOT_LESS_OR_EQUAL - BSOD Index

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff880027a29f8, 2, 1, fffff800028df3f2}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+f2 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff880027a29f8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800028df3f2, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b0b0e0
 fffff880027a29f8 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerExpiration+f2
fffff800`028df3f2 48894808        mov     qword ptr [rax+8],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9caa0 -- (.trap 0xfffff80000b9caa0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880027a29f0 rbx=0000000000000000 rcx=fffff80002a52048
rdx=00000000000000ee rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028df3f2 rsp=fffff80000b9cc30 rbp=00000000001aa1ee
 r8=fffffa800272e9d0  r9=00000000000000c0 r10=00000000000000ee
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!KiTimerExpiration+0xf2:
fffff800`028df3f2 48894808        mov     qword ptr [rax+8],rcx ds:fffff880`027a29f8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800028d2ca9 to fffff800028d3740

STACK_TEXT:  
fffff800`00b9c958 fffff800`028d2ca9 : 00000000`0000000a fffff880`027a29f8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c960 fffff800`028d1920 : 00000000`00000000 0000003f`654efa77 fffffa80`02f5b900 fffffa80`02f71de0 : nt!KiBugCheckDispatch+0x69
fffff800`00b9caa0 fffff800`028df3f2 : 0000003f`6547593b fffff800`00b9cc58 00000000`001aa1ea fffff800`02a51fc8 : nt!KiPageFault+0x260
fffff800`00b9cc30 fffff800`028decb7 : 00000012`922da9c0 00000012`001aa1ee 00000012`922da94a 00000000`000000ee : nt!KiTimerExpiration+0xf2
fffff800`00b9ccd0 fffff800`028dbeea : fffff800`02a4de80 fffff800`02a5bc40 00000000`00000000 fffff880`04599480 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerExpiration+f2
fffff800`028df3f2 48894808        mov     qword ptr [rax+8],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerExpiration+f2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+f2

BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+f2

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

I am stumped. Something is interfering with memory; but I cannot find it.

 

[Jonathan_King]

Try some hardware diagnostics.

Test CPU: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Test temps with Speedfan: SpeedFan - Access temperature sensor in your computer

Test hard drive: HD Diagnostic

 

[Watson]

Cheers Jonny I'll check those out.

 

[Watson]

Something is telling me my graphics has got something to do with it. Am getting really screwed up graphics when I run mount and blade at certain parts of the screen. These normally just went away after about 2 minutes and the game ran fine. Recently noticed that it has got worse though. Afew characters have not appeared with faces on some instances and now the armour of some of the men has turned from a blue like colour to green, although blue seems fine on the rest of the pc. I downloaded the latest stuff from the ATI website and I'm gonna have to try other games see what happens. On the plus side I haven't had a blue screen for a while.

 

[Jonathan_King]

Glad to hear no BSODs, but I suspect they will return.

Do you have another GFX card you can try? Perhaps borrow one from a friend, or rob one off another computer.

Do the Furmark test: http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

 

[Watson]

Nope no spare card.

The test apears to be going Ok, but what ar the temp limits for the gpu? I have absolutely no idea.

 

[Watson]

Mine hits a max of 80.

 

[Watson]

Keep ketting dodgy graphics on M and B even on lower settings. Annoying me now. I need to keep investigating. Ths blue screen happened yesterday while playing.