BSOD HELP! (Sorry for starting another)


  1. Aks
    Posts : 7
    Windows 7
       New #1

    BSOD HELP! (Sorry for starting another)


    Hello,

    Only yesterday did I start getting this BSOD. I don't think it is the memory as I've got two 2gb sticks in place but I could be fun and in due course I can run some tests.

    I built this computer at xmas so its fairly new and I can include my specs if required. All the brands I used are reputable though.

    But heres the error and the zip.

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.48
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 109
    BCP1: A3A039D895C64BA5
    BCP2: 0000000000000000
    BCP3: 64F8CC221906A8AB
    BCP4: 0000000000000101
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\033010-19936-01.dmp
    C:\Users\Aks\AppData\Local\Temp\WER-9632359-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt



    Thank you in advance for your help :)
      My Computer
    Quote Quote

  3. Jonathan_King
    Posts : 13,354
    Windows 7 Professional x64
       New #2

    Welcome!

    Looks like your ATI Video card driver atikmdag.sys is causing the trouble. I suggest updating your video card drivers.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\032310-21964-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030a4e50
Debug session time: Tue Mar 23 11:13:45.653 2010 (GMT-4)
System Uptime: 10 days 14:54:43.464
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
...................
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8004eac210, fffff88003c4def0, 0, 2}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+12ef0 )

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: fffffa8004eac210, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003c4def0, 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: 
atikmdag+12ef0
fffff880`03c4def0 48895c2408      mov     qword ptr [rsp+8],rbx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02186988 fffff880`042cdef8 : 00000000`00000116 fffffa80`04eac210 fffff880`03c4def0 00000000`00000000 : nt!KeBugCheckEx
fffff880`02186990 00000000`00000116 : fffffa80`04eac210 fffff880`03c4def0 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8
fffff880`02186998 fffffa80`04eac210 : fffff880`03c4def0 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116
fffff880`021869a0 fffff880`03c4def0 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`04eac210
fffff880`021869a8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`042cdc02 : atikmdag+0x12ef0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+12ef0
fffff880`03c4def0 48895c2408      mov     qword ptr [rsp+8],rbx

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  atikmdag+12ef0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b0ca832

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys

Followup: MachineOwner
---------
      My Computer
    Quote Quote

  4. Aks
    Posts : 7
    Windows 7
    Thread Starter
       New #3

    Jonathan_King said:
    Welcome!

    Looks like your ATI Video card driver atikmdag.sys is causing the trouble. I suggest updating your video card drivers.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\032310-21964-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030a4e50
Debug session time: Tue Mar 23 11:13:45.653 2010 (GMT-4)
System Uptime: 10 days 14:54:43.464
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
...................
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8004eac210, fffff88003c4def0, 0, 2}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+12ef0 )

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: fffffa8004eac210, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003c4def0, 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: 
atikmdag+12ef0
fffff880`03c4def0 48895c2408      mov     qword ptr [rsp+8],rbx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02186988 fffff880`042cdef8 : 00000000`00000116 fffffa80`04eac210 fffff880`03c4def0 00000000`00000000 : nt!KeBugCheckEx
fffff880`02186990 00000000`00000116 : fffffa80`04eac210 fffff880`03c4def0 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8
fffff880`02186998 fffffa80`04eac210 : fffff880`03c4def0 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116
fffff880`021869a0 fffff880`03c4def0 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`04eac210
fffff880`021869a8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`042cdc02 : atikmdag+0x12ef0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmdag+12ef0
fffff880`03c4def0 48895c2408      mov     qword ptr [rsp+8],rbx

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  atikmdag+12ef0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b0ca832

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys

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

    Thank you,

    I've updated everything, just hope its done correctly!

    I'll leave it for a bit and then if there is any more problems I shall reply.

    Thanks for your help again it is much appreciated.


    Aks
      My Computer
    Quote Quote

  6. Aks
    Posts : 7
    Windows 7
    Thread Starter
       New #4

    My computer is still dumping but its appeared to change its dump type. I've attached the files again.

    Any help again would be appreciated please.


    Thanks
      My Computer
    Quote Quote

  7. Jonathan_King
    Posts : 13,354
    Windows 7 Professional x64
       New #5

    Now you might want to run a system files check and test your RAM.

    Open an elevated command prompt and enter sfc /scannow.

    Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\040110-20857-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03040e50
Debug session time: Thu Apr  1 06:37:49.817 2010 (GMT-4)
System Uptime: 0 days 0:10:30.643
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8001747680, ffff, 0}

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

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

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

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

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WmiPrvSE.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ee726e to fffff80002e74f00

STACK_TEXT:  
fffff880`083fe878 fffff800`02ee726e : 00000000`0000001a 00000000`00041790 fffffa80`01747680 00000000`0000ffff : nt!KeBugCheckEx
fffff880`083fe880 fffff800`02e48487 : ffffffff`00000000 00000000`014bffff fffffa80`00000000 fffffa80`05b38a80 : nt! ?? ::FNODOBFM::`string'+0x339d6
fffff880`083fea40 fffff800`031577af : fffff8a0`03f6c060 00000000`00000001 00000000`00000000 fffffa80`05b38a80 : nt!MmCleanProcessAddressSpace+0x62f
fffff880`083fea90 fffff800`03130cb8 : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x47f
fffff880`083feb60 fffff800`02e74153 : fffffa80`064ee260 00000000`00000000 fffffa80`05b38a80 fffffa80`00000001 : nt!NtTerminateProcess+0x138
fffff880`083febe0 00000000`778f017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001afa78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778f017a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+339d6
fffff800`02ee726e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+339d6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

Followup: MachineOwner
---------
      My Computer
    Quote Quote

  8. Aks
    Posts : 7
    Windows 7
    Thread Starter
       New #6

    Thank you.

    Could this be related to the last fault?
    Also, it states Vista driver fault... I'm on Windows 7, would that have something to do with it?
      My Computer
    Quote Quote

  10. Aks
    Posts : 7
    Windows 7
    Thread Starter
       New #7

    I ran the scan and it came up with this...

    Windows Resource Protection found corrupt files but was unable to fix some of them.
    Details are included in CBS.LOG windir\Logs\CBS\CBS.log. For example
    C:\Windows\Logs\CBS\CBS.log

    I've attached the log.

    Thanks again
      My Computer
    Quote Quote

 

  Related Discussions
It all starts if i'm not wrong is when i updated my laptop using Windows Update after then i accidentally shut my computer down at the time in its installing restart process. Then tomorrow after that i open my laptop. then when i noticed my amd radeon HD 6630 and ati catalyst manager are gone. ...
BSOD When Starting PC but not always
in BSOD Help and Support

Hello Folks (crash = bsod) Since a couple of days, my PC always gets a BSOD when it started and remained about 5-10 seconds on the desktop. When I restart the PC, it either crashes there again, or already crashes on the First Windows7 Loading screen. Here is the data I got by...
hi I have learnt my neighbour my lap top to do his school work. he gave it back to me with a starting up problem. he calms he did nothing. I really need my stuff on my laptop. the starting up repair doesnt not work. neither does putting it back to a earlier stage. I have windows 7 ultimate....
BSOD starting to act up again..
in BSOD Help and Support

Windows 7 x64 Professional currently None windows preinstalled when bought Around a year ago was the last time I installed windows All hardware except for the grafic card is around 2 years old. System spec: GTX 580 I7 940 2,93Ghz Gigabyte EX58-UD3R 6 GB ram dont remember what
Hello All, I've been getting consistent BSODs while trying to start Windows Virtual PC (not Microsoft Virtual PC 2007) machines on my computer. I've tried various driver updates and a bios update and several system restores along the way, but to no avail. In the attached dump files, the last...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 15:27.
Find Us