Vista - Windows restarts when laptop is closed

hi, im having a problem with my hibernation mode when my laptop is shut.

when i close the laptop, windows restarts and leaves an error code when started up again. the computer runs fine besides this, and is days old i might add. i have recently updated through microsoft, 'a shut down update' standard procedure. before this update hibernation worked fine. i dont know if this could have anything to do with it, but regardless i am new with vista.

my computer specs:

dell studio 15'
windows vista home premium 64 bit
service pack 1


the problem signature is specified:

"Windows has recovered from an unexpected shutdown"

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

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80001FD7B81
BCP3: FFFFFA60015D5798
BCP4: FFFFFA60015D5170
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini082609-07.dmp
C:\Users\Kyle\AppData\Local\Temp\WER-51246-0.sysdata.xml
C:\Users\Kyle\AppData\Local\Temp\WER78E.tmp.version.txt

i am going to college in a few days and this needs to be fixed! please help in whatever way possible. thank you

Do us a favor go into C:\windows\minidump zip the dump file (*.dmp) and upload it for us to look at

Thanks

Ken

okay. the minidump files are attached.

Debug is here:

*******************************************************************************
* *
* 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: fffff80001fd7b81, The address that the exception occurred at
Arg3: fffffa60015d5798, Exception Record Address
Arg4: fffffa60015d5170, 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!IopFreeRelationList+21
fffff800`01fd7b81 488b3e mov rdi,qword ptr [rsi]
EXCEPTION_RECORD: fffffa60015d5798 -- (.exr 0xfffffa60015d5798)
ExceptionAddress: fffff80001fd7b81 (nt!IopFreeRelationList+0x0000000000000021)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000010
Attempt to read from address 0000000000000010
CONTEXT: fffffa60015d5170 -- (.cxr 0xfffffa60015d5170)
rax=fffffa80054d7701 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80054d7701 rsi=0000000000000010 rdi=0000000000000000
rip=fffff80001fd7b81 rsp=fffffa60015d59d0 rbp=0000000000000000
r8=fffffa80067a4590 r9=50013e076c000000 r10=0000000000000000
r11=00000000000007ff r12=fffff80001e09b20 r13=fffffa8007cc11e0
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!IopFreeRelationList+0x21:
fffff800`01fd7b81 488b3e mov rdi,qword ptr [rsi] ds:002b:00000000`00000010=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 7
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: 0000000000000010
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e36080
0000000000000010
FOLLOWUP_IP:
nt!IopFreeRelationList+21
fffff800`01fd7b81 488b3e mov rdi,qword ptr [rsi]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffff80002041417 to fffff80001fd7b81
STACK_TEXT:
fffffa60`015d59d0 fffff800`02041417 : fffffa80`067a4590 00000000`00000001 fffffa80`09037ae0 fffff800`01e7538c : nt!IopFreeRelationList+0x21
fffffa60`015d5a10 fffff800`02041555 : fffffa80`067a4590 fffffa80`07cc11e0 fffffa80`07cc11e0 00000000`00000000 : nt!PnpDelayedRemoveWorker+0x97
fffffa60`015d5a60 fffff800`01d3cc69 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`058ce500 : nt!PnpChainDereferenceComplete+0x115
fffffa60`015d5aa0 fffff800`02045d79 : 00000000`00000000 fffffa80`09037a00 fffffa80`0843f5b0 00000000`00000001 : nt!PnpIsChainDereferenced+0xc9
fffffa60`015d5b20 fffff800`02045ffc : fffffa60`015d5cf8 00000000`00000000 fffff880`0b8c3300 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xf99
fffffa60`015d5c70 fffff800`01f466c7 : 00000000`00000001 fffffa80`05ff4140 fffff880`0b7c7c30 00000000`4b706e50 : nt!PnpProcessTargetDeviceEvent+0x4c
fffffa60`015d5ca0 fffff800`01c6ae4a : fffff800`01e72494 fffff880`0b7c7c30 fffff800`01da08f8 fffffa80`054d7720 : nt! ?? ::NNGAKEGL::`string'+0x4a314
fffffa60`015d5cf0 fffff800`01e82573 : fffffa80`05ff4140 00000000`00000000 fffffa80`054d7720 00000000`00000080 : nt!ExpWorkerThread+0x11a
fffffa60`015d5d50 fffff800`01c99ff6 : fffffa60`005ec180 fffffa80`054d7720 fffffa60`005f5d40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`015d5d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!IopFreeRelationList+21
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a67e1a0
STACK_COMMAND: .cxr 0xfffffa60015d5170 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!IopFreeRelationList+21
BUCKET_ID: X64_0x7E_nt!IopFreeRelationList+21
Followup: MachineOwner
---------

For that 0x7E exception code means a breakpoint was triggered in a target, so I would run a memory diagnostic, followed by updating video and if possible BIOS drivers. Do you have enough free disk space? Upgrade to SP2 too.

okay, im not sure what any of that means.. but i fixed it. got on with dell chat. they told me to do a system restore. i went back about 5 days, and everything is good n working again. thanks anyways for the help