HP Envy 15 BSOD

GEM1n1 said:

Hi,

I'm having a lot of trouble with my laptop lately. I keep getting a BSOD every time that I boot up my laptop. At first after a few tries, it will successfully boot up but now I have to run in safe mode before it will boot. At first I thought it was a problem with my video drivers but after uninstalling them with Driver Cleaner Pro and installing them again, I keep getting the same problem. I've attached the dump file.


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

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA8008FF4010
BCP2: FFFFF88004206F94
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\111110-14554-01.dmp
C:\Users\Nick\AppData\Local\Temp\WER-34101-0.sysdata.xml\


Thank you so much for your time!

This was caused by the video driver taking too long to respond to a reset. Usually a driver, heat, or video card.

I would re-install the driver using these

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\K\Desktop\111110-14554-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c66000 PsLoadedModuleList = 0xfffff800`02ea3e50
Debug session time: Fri Nov 12 00:30:11.472 2010 (GMT-5)
System Uptime: 0 days 0:00:28.532
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8008ff4010, fffff88004206f94, 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+6f94 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008ff4010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004206f94, 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+6f94
fffff880`04206f94 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`067ee9c8 fffff880`0454bef8 : 00000000`00000116 fffffa80`08ff4010 fffff880`04206f94 00000000`00000000 : nt!KeBugCheckEx
fffff880`067ee9d0 fffff880`0454bc02 : fffff880`04206f94 fffffa80`08ff4010 fffffa80`0889ad50 fffffa80`076cf410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`067eea10 fffff880`0440ff07 : fffffa80`08ff4010 00000000`00000000 fffffa80`0889ad50 fffffa80`076cf410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`067eea40 fffff880`04439b75 : 00000000`ffffffff 00000000`000003f5 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`067eeb20 fffff880`044382bb : 00000000`00000102 00000000`00000000 00000000`000003f5 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`067eeb50 fffff880`0440b2c6 : ffffffff`ff676980 fffffa80`076cf410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`067eebf0 fffff880`04437e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`07614578 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`067eed00 fffff800`02f7ac06 : 00000000`01606efe fffffa80`088a1b60 fffffa80`054ec040 fffffa80`088a1b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`067eed40 fffff800`02cb4c26 : fffff800`02e50e80 fffffa80`088a1b60 fffff800`02e5ec40 fffff880`0122b534 : nt!PspSystemThreadStartup+0x5a
fffff880`067eed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6f94
fffff880`04206f94 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+6f94

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ca29309

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

Boot into safe mode, then follow Kens' advice..

You may need to restore you computer to its factory condition...

Restore the PC to its original condition using the f11 key if Windows 7 is not accessible
If the PC cannot launch into Windows, it may still be possible to use the HP Recovery Manager on the hard drive to restore the computer to its original operating condition. The Recovery Manager can be launched during the startup process by following the steps below.
Press the Power button to start the PC, and then press the f11 key when the standard BIOS prompts are displayed on the black screen.
REMARQUE: Pressing the f11 key during startup on a computer with an HP factory image will start the system recovery process even if the prompt is not displayed.
If the HP Recovery Manager can access the recovery partition on the hard drive, a prompt to backup the user files before beginning the recovery is displayed. Follow any on-screen instructions.
If the HP Recovery Manager cannot access the hard drive to fix any system errors, you will need to use the personalized recovery disc that you created to recover the hard drive to its original condition.
If you have not created the personalized recovery disc, or the discs are corrupted, you can order a replacement recovery disc from HP.
When the Recovery Manager starts, follow the step-by-step system recovery instructions shown above.

source