BSOD-Intermittent

[8ball123]

Every time my son uses my laptop and I get home to use it, I boot up and get the message: Windows has Recovered from an unexpected shutdown. I don't know what he's doing to cause this and he disavows any knowledge. Whatever...

I'm running Vista Home Premium x64 on my Acer Aspire 8730

I ran winDBG and !analyze -v and got the following. Can anyone decipher this and tell me what the problem might be?

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

 
Copyright (c) Microsoft Corporation. All rights reserved.

 
 

 
 

 
Loading Dump File [C:\Windows\Minidump\Mini120811-01.dmp]

 
Mini Kernel Dump File: Only registers and stack trace are available

 
 

 
Symbol search path is: SRV*C:\Symbols*[URL]http://msdl.microsoft.com/download/symbols[/URL]

 
Executable search path is: 

 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 
procs) Free x64

 
Product: WinNt, suite: TerminalServer SingleUserTS Personal

 
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336

 
Machine Name:

 
Kernel base = 0xfffff800`0244a000 PsLoadedModuleList = 
0xfffff800`0260edd0

 
Debug session time: Thu Dec  8 10:13:34.733 2011 (UTC - 8:00)

 
System Uptime: 0 days 5:39:37.643

 
Loading Kernel Symbols

 
...............................................................

 
................................................................

 
................................................................

 
.

 
Loading User Symbols

 
Loading unloaded module list

 
.....

 
*******************************************************************************

 
*                                                                             
*

 
*                        Bugcheck Analysis                                    
*

 
*                                                                             
*

 
*******************************************************************************

 
 

 
Use !analyze -v to get detailed debugging information.

 
 

 
BugCheck 1000007E, {ffffffffc0000005, fffff800024ab9ef, fffffa6018a413c8, 
fffffa6018a40da0}

 
 

 
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiPdoDispatchPower+7c )

 
 

 
Followup: MachineOwner

 
---------

 
 

 
1: 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: fffff800024ab9ef, The address that the exception occurred at

 
Arg3: fffffa6018a413c8, Exception Record Address

 
Arg4: fffffa6018a40da0, 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!ExAcquireResourceExclusiveLite+1f

 
fffff800`024ab9ef f0480fba696000  lock bts qword ptr [rcx+60h],0

 
 

 
EXCEPTION_RECORD:  fffffa6018a413c8 -- (.exr 0xfffffa6018a413c8)

 
Cannot read Exception record @ fffffa6018a413c8

 
 

 
CONTEXT:  fffffa6018a40da0 -- (.cxr 0xfffffa6018a40da0)

 
Unable to read context, Win32 error 0n30

 
 

 
CUSTOMER_CRASH_COUNT:  1

 
 

 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

 
 

 
BUGCHECK_STR:  0x7E

 
 

 
PROCESS_NAME:  System

 
 

 
CURRENT_IRQL:  0

 
 

 
LAST_CONTROL_TRANSFER:  from fffffa6002c33edc to fffff800024ab9ef

 
 

 
STACK_TEXT:  

 
fffffa60`18a41600 fffffa60`02c33edc : fffffa80`08e3c5e0 00000000`00000004 
fffffa80`04898bd0 fffffa80`08e3c5e0 : nt!ExAcquireResourceExclusiveLite+0x1f

 
fffffa60`18a41650 fffffa60`02c9ccaf : fffffa80`04898bd0 fffffa80`06dc63a0 
fffffa80`04898bd0 fffffa80`0908c870 : dxgkrnl!DpiPdoDispatchPower+0x7c

 
fffffa60`18a416b0 fffff800`025564a2 : fffffa80`04898bd0 fffffa80`04898bd0 
fffffa80`08d569a0 fffffa80`04898bd0 : dxgkrnl!DpiDispatchPower+0x11b

 
fffffa60`18a41700 fffffa60`008cc5f3 : fffffa80`08d569a0 fffffa60`18a417f0 
ffff4d5c`43317d56 00000000`0000056f : nt!IopPoHandleIrp+0x32

 
fffffa60`18a41730 fffffa60`008ca405 : fffffa60`008f3b60 fffffa80`040d96b0 
fffffa80`08d84440 00000000`00000010 : acpi!ACPIFilterIrpSetPower+0x167

 
fffffa60`18a41760 fffff800`025564a2 : fffffa80`04898bd0 fffffa60`18a41870 
fffffa80`04898bd0 fffffa60`18a41870 : acpi!ACPIDispatchIrp+0x2b1

 
fffffa60`18a417e0 fffffa60`00884c34 : 00000000`00000000 fffffa80`08d84440 
0b000b34`0b340b68 fffffa60`18a41898 : nt!IopPoHandleIrp+0x32

 
fffffa60`18a41810 fffffa60`008851f3 : fffffa80`08d84440 00000000`00000000 
00000000`00000000 00000000`00000005 : Wdf01000!FxPkgFdo::_PowerPassDown+0x6c

 
fffffa60`18a41840 fffffa60`00879248 : fffffa80`04898bd0 fffffa80`08d84440 
00000000`00000000 00000000`00000000 : 
Wdf01000!FxPkgFdo::PowerReleasePendingDeviceIrp+0x47

 
fffffa60`18a41870 fffffa60`00878f3d : 00000000`00000000 00000000`00000000 
fffffa60`0088d760 00000000`0000031a : 
Wdf01000!FxPkgPnp::PowerGotoDxIoStopped+0x1e8

 
fffffa60`18a418e0 fffffa60`008786eb : 00000000`0000031c 00000000`00000002 
fffffa60`0088d720 00000000`00000000 : 
Wdf01000!FxPkgPnp::PowerGotoDNotZeroIoStopped+0x9

 
fffffa60`18a41910 fffffa60`0087838e : fffffa80`08d84440 00000000`00000002 
fffffa60`0088d720 00000000`00001000 : 
Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db

 
fffffa60`18a41a40 fffffa60`0087806c : 00000000`00000000 00000000`00000002 
00000000`00000000 fffffa80`08d84440 : 
Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e

 
fffffa60`18a41ab0 fffffa60`0088507f : 00000000`00000000 fffffa80`08d84440 
00000000`00000000 00000000`00000000 : 
Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4

 
fffffa60`18a41b40 fffffa60`00884c91 : 00000000`00000002 fffffa60`18a41c08 
00000000`00000004 00000000`00000000 : Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x117

 
fffffa60`18a41b90 fffffa60`00873f38 : fffffa80`08b5fa90 00000000`00000000 
fffffa80`08d79ab0 fffffa80`04898bd0 : 
Wdf01000!FxPkgFdo::_DispatchSetPower+0x21

 
fffffa60`18a41bc0 fffffa60`00843245 : fffffa80`04898bd0 fffffa80`04898bd0 
fffffa80`08d79ab0 fffffa60`18a41d50 : Wdf01000!FxPkgPnp::Dispatch+0x314

 
fffffa60`18a41c30 fffffa60`0084314b : fffffa80`04898bd0 00000000`00000000 
fffffa80`08d79ab0 fffffa80`0534ea30 : Wdf01000!FxDevice::Dispatch+0xa9

 
fffffa60`18a41c60 fffff800`0256614a : 00000000`00000001 00000000`00000000 
fffffa80`08d79ab0 00000000`00000000 : Wdf01000!FxDevice::DispatchWithLock+0x93

 
fffffa60`18a41ca0 fffff800`026aef97 : ffffffff`fa0a1f00 fffffa80`057e3860 
00000000`00000080 00000000`7eebb001 : nt!PopIrpWorker+0x3ca

 
fffffa60`18a41d50 fffff800`024e15c6 : fffffa60`005ec180 fffffa80`057e3860 
fffffa80`08ea9260 fffffa60`005ec7f0 : nt!PspSystemThreadStartup+0x57

 
fffffa60`18a41d80 00000000`00000000 : 00000000`00000000 00000000`00000000 
00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

 
 

 
 

 
FOLLOWUP_IP: 

 
dxgkrnl!DpiPdoDispatchPower+7c

 
fffffa60`02c33edc 8b87c0000000    mov     eax,dword ptr [rdi+0C0h]

 
 

 
SYMBOL_STACK_INDEX:  1

 
 

 
SYMBOL_NAME:  dxgkrnl!DpiPdoDispatchPower+7c

 
 

 
FOLLOWUP_NAME:  MachineOwner

 
 

 
MODULE_NAME: dxgkrnl

 
 

 
IMAGE_NAME:  dxgkrnl.sys

 
 

 
DEBUG_FLR_IMAGE_TIMESTAMP:  4d384226

 
 

 
STACK_COMMAND:  .cxr 0xfffffa6018a40da0 ; kb

 
 

 
FAILURE_BUCKET_ID:  X64_0x7E_dxgkrnl!DpiPdoDispatchPower+7c

 
 

 
BUCKET_ID:  X64_0x7E_dxgkrnl!DpiPdoDispatchPower+7c

 
 

 
Followup: MachineOwner

 
---------

Any help would be appreciated.

Thanks in advance.

 

[Lottiemansion]

Hi,

Try updating the graphics drivers: -

NVIDIA Driver Downloads - Automatically Detect NVIDIA Products

 

[8ball123]

I've already updated my graphics drivers but the BSOD keeps occurring. It's strange...I never get the BSOD but every time my son get's on my laptop he gets it. When I ask him what he was doing at the moment it occurred, he denies it even happened. I ask him if he thinks I'm stupid and show him the message on-screen and he says "Windows made a mistake, I never got a Blue Screen". I'm at my wits end.

 

[Lottiemansion]

OK,

Follow the instructions for posting a BSOD: -

http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html

 

[8ball123]

Ok...here is the zip file for my BSOD. Hope this helps. Thank you.

Vista Home Premium x64 (OEM pre-installed)
Acer Aspire 8730 (purchased new on June 23, 2009)

 

[Lottiemansion]

Hi,

You get one answer & I get "Memory corruption".

This must be down to the the difference in OS (32 bit v 64 bit), So have a look here & try it: -

Download: Update for Windows Vista for x64-based Systems (KB953026) - Microsoft Download Center - Download Details

 

[8ball123]

I followed the download/installation instructions per your suggestion and get the following message: "The update does not apply to your system".

 

[richc46]

Welcome
I checked out your Dump Reports and most seem to indicate a graphics problem.
Try to download the previous graphics driver. The most up to date is not always the best.
If that does not work, go to search by the start button and type event viewer. In event viewer go to adminstrative and look at the errors that are shown about the time of the problem.