Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after reboot for program install. BSOD @ Win 7 splash screen

31 Dec 2012   #1

Windows 7 Ultimate x64
 
 
BSOD after reboot for program install. BSOD @ Win 7 splash screen

I installed an antivirus program and Adobe Acrobat on Win 7 64 bit ultimate. It requested a system restart. Upon restart, I had a BSOD immediately after the Windows 7 splash screen (before Win requests my user password). Upon BSOD, it auto-restarted my PC and automatically brought me in to Windows repair. After waiting 45 minutes and seeing Windows repair wasn't doing anything, I just turned off and turned on my PC. I got another BSOD. Then, I rebooted again, and it was able to load into Windows.

I've attached my dump file. Any what's causing this and how I can fix?

Thanks.


My System SpecsSystem Spec
.

31 Dec 2012   #2

Windows 8 Professional x64
 
 

Your ati driver is causing the BSOD
Code:
Loading User Symbols
Loading unloaded module list
.....
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002c010f3, fffff88002fd22b8, fffff88002fd1b20}

Probably caused by : atikmpag.sys ( atikmpag+10aec )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c010f3, The address that the exception occurred at
Arg3: fffff88002fd22b8, Exception Record Address
Arg4: fffff88002fd1b20, Context Record Address

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!ExFreePoolWithTag+43
fffff800`02c010f3 418b45f0        mov     eax,dword ptr [r13-10h]

EXCEPTION_RECORD:  fffff88002fd22b8 -- (.exr 0xfffff88002fd22b8)
ExceptionAddress: fffff80002c010f3 (nt!ExFreePoolWithTag+0x0000000000000043)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88002fd1b20 -- (.cxr 0xfffff88002fd1b20)
rax=0000000000000000 rbx=fffffa800692d880 rcx=0069007200750063
rdx=000000005958504b rsi=0000000000000000 rdi=fffffa800692d880
rip=fffff80002c010f3 rsp=fffff88002fd24f0 rbp=fffffa8006362b10
 r8=0000000000006680  r9=00000000000000c0 r10=fffff80002a5d000
r11=0000000000000290 r12=fffffa80049e6d40 r13=0069007200750063
r14=fffff88004857110 r15=fffffa8004780a20
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExFreePoolWithTag+0x43:
fffff800`02c010f3 418b45f0        mov     eax,dword ptr [r13-10h] ds:002b:00690072`00750053=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d040e0
GetUlongFromAddress: unable to read from fffff80002d04198
 ffffffffffffffff 

FOLLOWUP_IP: 
atikmpag+10aec
fffff880`043b7aec ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880043b7aec to fffff80002c010f3

STACK_TEXT:  
fffff880`02fd24f0 fffff880`043b7aec : fffffa80`049e6d40 fffffa80`06362b10 00000000`00000000 fffffa80`06362b10 : nt!ExFreePoolWithTag+0x43
fffff880`02fd25a0 fffffa80`049e6d40 : fffffa80`06362b10 00000000`00000000 fffffa80`06362b10 fffffa80`0692d880 : atikmpag+0x10aec
fffff880`02fd25a8 fffffa80`06362b10 : 00000000`00000000 fffffa80`06362b10 fffffa80`0692d880 fffff880`043b00f2 : 0xfffffa80`049e6d40
fffff880`02fd25b0 00000000`00000000 : fffffa80`06362b10 fffffa80`0692d880 fffff880`043b00f2 00000000`00000001 : 0xfffffa80`06362b10


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  atikmpag+10aec

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d409c8d

STACK_COMMAND:  .cxr 0xfffff88002fd1b20 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atikmpag+10aec

BUCKET_ID:  X64_0x7E_atikmpag+10aec

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c010f3, The address that the exception occurred at
Arg3: fffff88002fd22b8, Exception Record Address
Arg4: fffff88002fd1b20, Context Record Address

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!ExFreePoolWithTag+43
fffff800`02c010f3 418b45f0        mov     eax,dword ptr [r13-10h]

EXCEPTION_RECORD:  fffff88002fd22b8 -- (.exr 0xfffff88002fd22b8)
ExceptionAddress: fffff80002c010f3 (nt!ExFreePoolWithTag+0x0000000000000043)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88002fd1b20 -- (.cxr 0xfffff88002fd1b20)
rax=0000000000000000 rbx=fffffa800692d880 rcx=0069007200750063
rdx=000000005958504b rsi=0000000000000000 rdi=fffffa800692d880
rip=fffff80002c010f3 rsp=fffff88002fd24f0 rbp=fffffa8006362b10
 r8=0000000000006680  r9=00000000000000c0 r10=fffff80002a5d000
r11=0000000000000290 r12=fffffa80049e6d40 r13=0069007200750063
r14=fffff88004857110 r15=fffffa8004780a20
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExFreePoolWithTag+0x43:
fffff800`02c010f3 418b45f0        mov     eax,dword ptr [r13-10h] ds:002b:00690072`00750053=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff 

FOLLOWUP_IP: 
atikmpag+10aec
fffff880`043b7aec ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880043b7aec to fffff80002c010f3

STACK_TEXT:  
fffff880`02fd24f0 fffff880`043b7aec : fffffa80`049e6d40 fffffa80`06362b10 00000000`00000000 fffffa80`06362b10 : nt!ExFreePoolWithTag+0x43
fffff880`02fd25a0 fffffa80`049e6d40 : fffffa80`06362b10 00000000`00000000 fffffa80`06362b10 fffffa80`0692d880 : atikmpag+0x10aec
fffff880`02fd25a8 fffffa80`06362b10 : 00000000`00000000 fffffa80`06362b10 fffffa80`0692d880 fffff880`043b00f2 : 0xfffffa80`049e6d40
fffff880`02fd25b0 00000000`00000000 : fffffa80`06362b10 fffffa80`0692d880 fffff880`043b00f2 00000000`00000001 : 0xfffffa80`06362b10


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  atikmpag+10aec

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d409c8d

STACK_COMMAND:  .cxr 0xfffff88002fd1b20 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atikmpag+10aec

BUCKET_ID:  X64_0x7E_atikmpag+10aec

Followup: MachineOwner
---------
Driver Reference Table

Update this ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)

http://support.amd.com/us/Pages/AMDSupportHub.aspx
My System SpecsSystem Spec
Reply

 BSOD after reboot for program install. BSOD @ Win 7 splash screen




Thread Tools



Similar help and support threads for2: BSOD after reboot for program install. BSOD @ Win 7 splash screen
Thread Forum
Solved BSOD on splash screen everytime BSOD Help and Support
Solved Slow startup to splash screen then a BSOD BSOD Help and Support
BSOD after boot splash screen 0x1000007E BSOD Help and Support
Solved BSOD on boot up - can't get past Windows splash screen BSOD Help and Support
Solved BSOD crash right after Windows splash screen BSOD Help and Support
BSOD after splash OxOOOOOO7B after New OS install BSOD Help and Support
Dragon Age: Origins BSOD after Splash Screen BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 03:27 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33