[edisonfloyd]

Whenever I wake my computer up from sleep it seems as if it's powering on rather than waking up. Then it hits a BSOD and restarts normally.

Any clue? I've attached the BSOD's dump file.

Thanks for any help.

 

[makinu1der2]

Hello,

Please take a look at the following thread and perform the requested steps.

http://www.techsupportforum.com/for...ons-windows-8-windows-7-and-vista-452654.html

Once you have the proper reports please post back here.

Also include the make/model of the PC or if custom built post the specs.

From the dump you provided I would suggest that you check for an updated graphics driver. (uninstall the previous version first)

Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
Machine Name:
Kernel base = 0xfffff803`56e11000 PsLoadedModuleList = 0xfffff803`570daa80
Debug session time: Tue Mar 12 11:36:54.830 2013 (UTC - 4:00)
System Uptime: 0 days 11:17:55.653
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
............
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800644ceeb, fffff8800ef2c2a8, fffff8800ef2bae0}

Probably caused by : nvlddmkm.sys ( nvlddmkm+184eeb )

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: fffff8800644ceeb, The address that the exception occurred at
Arg3: fffff8800ef2c2a8, Exception Record Address
Arg4: fffff8800ef2bae0, 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: 
nvlddmkm+184eeb
fffff880`0644ceeb ff93001a0000    call    qword ptr [rbx+1A00h]

EXCEPTION_RECORD:  fffff8800ef2c2a8 -- (.exr 0xfffff8800ef2c2a8)
ExceptionAddress: fffff8800644ceeb (nvlddmkm+0x0000000000184eeb)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000001a00
Attempt to read from address 0000000000001a00

CONTEXT:  fffff8800ef2bae0 -- (.cxr 0xfffff8800ef2bae0)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=fffffa800920e548 rdi=fffffa8006e6b000
rip=fffff8800644ceeb rsp=fffff8800ef2c4e0 rbp=fffff8800ef2c5c0
 r8=0000000000000001  r9=0000000000000001 r10=0000000000000000
r11=000024ff0051db68 r12=fffffa8006e6d920 r13=0000000000000001
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nvlddmkm+0x184eeb:
fffff880`0644ceeb ff93001a0000    call    qword ptr [rbx+1A00h] ds:002b:00000000`00001a00=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_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:  0000000000001a00

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80357166168
GetUlongFromAddress: unable to read from fffff803571661f8
 0000000000001a00 Nonpaged pool

FOLLOWUP_IP: 
nvlddmkm+184eeb
fffff880`0644ceeb ff93001a0000    call    qword ptr [rbx+1A00h]

BUGCHECK_STR:  AV

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800644ceeb

STACK_TEXT:  
fffff880`0ef2c4e0 00000000`00000000 : fffff880`0644cee0 fffffa80`00000000 00000000`00000000 fffffa80`06e6b000 : nvlddmkm+0x184eeb


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+184eeb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5116d804

STACK_COMMAND:  .cxr 0xfffff8800ef2bae0 ; kb

FAILURE_BUCKET_ID:  AV_nvlddmkm+184eeb

BUCKET_ID:  AV_nvlddmkm+184eeb