BSOD/SAM-Related

Hey guys , I'm having a BSOD everytime I start up. The message said "Security accounts manager initialization failed because of the following error: The media is write protected." I have upload the Minidump Files (A RAR File , to be exact) to be check. Please reply as soon as possible, Thanks!

gabranthx33 said:

Hey guys , I'm having a BSOD everytime I start up. The message said "Security accounts manager initialization failed because of the following error: The media is write protected." I have upload the Minidump Files (A RAR File , to be exact) to be check. Please reply as soon as possible, Thanks!

All of these point to your video driver. A typical BC 116 (or video reset). I would re-install the video driver using these instructions first. RE: the "SAM" issue, lets fix one thing at a time


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 Phyxion.net - 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\K\Desktop\030211-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;srv*e:\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.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a5e000 PsLoadedModuleList = 0xfffff800`02c9be50
Debug session time: Wed Mar  2 16:55:29.033 2011 (GMT-4)
System Uptime: 0 days 8:17:01.376
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80073894e0, fffff88003ca93bc, 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+73bc )

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: fffffa80073894e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003ca93bc, 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+73bc
fffff880`03ca93bc 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`040fc898 fffff880`03d4d000 : 00000000`00000116 fffffa80`073894e0 fffff880`03ca93bc 00000000`00000000 : nt!KeBugCheckEx
fffff880`040fc8a0 fffff880`03d4cd0a : fffff880`03ca93bc fffffa80`073894e0 fffffa80`03c73850 fffffa80`05682410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`040fc8e0 fffff880`051bef07 : fffffa80`073894e0 00000000`00000000 fffffa80`03c73850 fffffa80`05682410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`040fc910 fffff880`051ecd5a : 00000000`ffffffff 00000000`001d2a14 fffff880`040fca70 00000000`00000102 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`040fc9f0 fffff880`051e86af : fffffa80`05682410 ffffffff`feced300 00000000`00000002 fffffa80`06993980 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`040fca30 fffff880`051e7023 : fffffa80`05682410 00000000`00000002 fffff880`051e6dc0 00000000`00000000 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`040fcb20 fffff880`051e72fe : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`040fcb50 fffff880`051ba2c6 : ffffffff`ff676980 fffffa80`05682410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`040fcbf0 fffff880`051e6e7a : 00000000`00000000 fffffa80`05db0950 00000000`00000080 fffffa80`05682410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`040fcd00 fffff800`02d717c6 : 00000000`fffffc32 fffffa80`05db4a10 fffffa80`03973b30 fffffa80`05db4a10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`040fcd40 fffff800`02aacc26 : fffff880`030a3180 fffffa80`05db4a10 fffff880`030ae040 007d6d36`00776938 : nt!PspSystemThreadStartup+0x5a
fffff880`040fcd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+73bc
fffff880`03ca93bc 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+73bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d409c8d

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

Hey there, I couldn't uninstall the driver through the default uninstaller which means i can't proceed to uninstall the driver through Driver Sweeper in Safe Mode, so i go to Normal Mode , when i do , the SAM issue that I previous stated occurs. Is there a way to fix this?

gabranthx33 said:

Hey there, I couldn't uninstall the driver through the default uninstaller which means i can't proceed to uninstall the driver through Driver Sweeper in Safe Mode, so i go to Normal Mode , when i do , the SAM issue that I previous stated occurs. Is there a way to fix this?

Give us your system specs and we will see if we can help

OS: Windows 7 64-Bit
RAM: 4 GB
Processor: AMD Phenom II X6 1055T Processor 2.81
Motherboard: Gigabyte GA-880GM-UD2H
Graphic Card: ATI HD Radeon 4650

I was able to use the system restore and going into safe mode , but I'm still having this issue.
P.S I'm new here lol

SledgeDG said:

then you either have to go back further or use a recent backup. Unless the registry is fixed your driver issue is a no go as it seems

Should i try disable my current graphic card using device manager, and use my integrated graphic card to see if it helps , then follow zigzag's instruction (If this work).