BSOD then restart.

cs2091 · 20 Apr 2011

Hello people, this is my first post here, and unfortunately it all has to start with a crash issue

It is a BSOD and I've copied the log and i'm attaching the minidump file to this thread. I would really appreciate your help in analyzing the problem =)

Code:

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    3b
  BCP1:    00000000C0000005
  BCP2:    FFFFF88005AAE817
  BCP3:    FFFFF8800B5178F0
  BCP4:    0000000000000000
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

JMH · 20 Apr 2011

cs2091 said:

Hello people, this is my first post here, and unfortunately it all has to start with a crash issue

It is a BSOD and I've copied the log and i'm attaching the minidump file to this thread. I would really appreciate your help in analyzing the problem =)

Code:

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    1033

Additional information about the problem:
  BCCode:    3b
  BCP1:    00000000C0000005
  BCP2:    FFFFF88005AAE817
  BCP3:    FFFFF8800B5178F0
  BCP4:    0000000000000000
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    768_1

Hi CS and welcome.

While it is difficult to give a definative answer from a single minidump your points towards a memory fault caused by your video driver.

Re-installing your driver with the newest version available using the below instructions should help

Code:

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


Loading Dump File [C:\Users\JMH\Desktop\042011-13244-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`02e58000 PsLoadedModuleList = 0xfffff800`0309de90
Debug session time: Wed Apr 20 14:45:20.655 2011 (GMT-4)
System Uptime: 0 days 4:44:18.686
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88005aae817, fffff8800b5178f0, 0}

Probably caused by : atikmdag.sys ( atikmdag+90817 )

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

2: 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: fffff88005aae817, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800b5178f0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

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

Let us know if you need further assistance.

cs2091 · 20 Apr 2011

Super helpful sir!

I would definitely do that. But before i get my hand dirty (not), I attached several other minidumps, as you can see, all in the last 1-2 weeks, during which I installed SSD (switching from a faulty HHD).

Would you also take a quick look at them and see if it was the same issue or are there several issues together, so i could take care of them all at once

Again, super fast response and helpful forum -- i truly appreciate that!

cs2091 · 01 May 2011

Had to bump the thread

This time the BCcode changed..

JMH · 01 May 2011

cs2091 said:

Had to bump the thread

This time the BCcode changed..

Hi CS and welcome

You are correct this time it is a classic video card reset (BC116). Basically it means that your computer attempted to reset the video card and failed. A driver re-install using these directions should help

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

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

Code:

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


Loading Dump File [C:\Users\JMH\Desktop\050111-13275-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`02e51000 PsLoadedModuleList = 0xfffff800`03096e90
Debug session time: Sun May  1 07:34:36.639 2011 (GMT-4)
System Uptime: 3 days 5:10:14.254
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80080604e0, fffff88000c58008, 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+7008 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80080604e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88000c58008, 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:
-----------------

cs2091 · 02 May 2011

Thank you! I upgraded to the newest version after a clean wipe yesterday. I'll report back if anything wrong remains!