Recurrent restarts, shut downs, clock time issues

Hi and thanks for any help. I bought this PC about 6 months ago, and it's been having the same symptoms since I got it. I've restored it to the factory image several times, updated all the drivers, etc... and it continues to do this. It's a laptop, and it seems like it gets very hot. That's usually my first symptom. It then starts running slowly, and sometimes sounds like the HDD won't stop, then inevitably just shuts down. When I try to restart, it will either shut down again, restart unsuccessfully several times, or run startup repair. It has not completed the startup repair successfully that I am aware of. It usually just shuts down again. I usually leave it off for a while, then try a normal reboot, and it will boot back up. Each time this happens, the clock moves forward 1-3 hours when it finally successfully boots back up. I have tried all of the time sync servers, and it does on all of them or if I choose not to sync time at all. It doesn't matter. The time still changes when this happens. The files that are attached are since I restored my computer last.

I know very little about computers, but I can follow directions pretty good if anyone has suggestions. Dell is coming out to look at it next week sometime since it's in warranty. I was hoping for some insight into what the problems are, and see if there is anything I can do before then.

I'm in college, and will be having to take scheduled, timed, proctored exams online later this week. I'm terrified that this will happen when I can't afford for it to happen during my exams (& before Dell gets out here to fix it).

Zip is attached. Thank you.

Beth

bethrn said:

Hi and thanks for any help. I bought this PC about 6 months ago, and it's been having the same symptoms since I got it. I've restored it to the factory image several times, updated all the drivers, etc... and it continues to do this. It's a laptop, and it seems like it gets very hot. That's usually my first symptom. It then starts running slowly, and sometimes sounds like the HDD won't stop, then inevitably just shuts down. When I try to restart, it will either shut down again, restart unsuccessfully several times, or run startup repair. It has not completed the startup repair successfully that I am aware of. It usually just shuts down again. I usually leave it off for a while, then try a normal reboot, and it will boot back up. Each time this happens, the clock moves forward 1-3 hours when it finally successfully boots back up. I have tried all of the time sync servers, and it does on all of them or if I choose not to sync time at all. It doesn't matter. The time still changes when this happens. The files that are attached are since I restored my computer last.

I know very little about computers, but I can follow directions pretty good if anyone has suggestions. Dell is coming out to look at it next week sometime since it's in warranty. I was hoping for some insight into what the problems are, and see if there is anything I can do before then.

I'm in college, and will be having to take scheduled, timed, proctored exams online later this week. I'm terrified that this will happen when I can't afford for it to happen during my exams (& before Dell gets out here to fix it).

Zip is attached. Thank you.

Beth

Beth

Hi and welcome

These all seem to be caused by several different causes which all point to one or two things. First your USBvideo.sys driver (for the webcams) are involved in most of them and needs to be re-installed.

Second, memory seems to be involved so I would test the memory by
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Let us know if you need assistance with this


Ken


Analysis

Code:

Loading Dump File [C:\Users\K\Desktop\Seven Forums\081210-16848-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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 Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e15000 PsLoadedModuleList = 0xfffff800`03052e50
Debug session time: Thu Aug 12 01:59:40.256 2010 (GMT-4)
System Uptime: 0 days 0:01:29.316
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800645201a, fffff88003170998, fffff88003170200}

Probably caused by : usbvideo.sys ( usbvideo!LoadPowerLineFrequency+2ce )

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

6: 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: fffff8800645201a, The address that the exception occurred at
Arg3: fffff88003170998, Exception Record Address
Arg4: fffff88003170200, 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: 
usbvideo!LoadPowerLineFrequency+2ce
fffff880`0645201a 448b4a44        mov     r9d,dword ptr [rdx+44h]

EXCEPTION_RECORD:  fffff88003170998 -- (.exr 0xfffff88003170998)
ExceptionAddress: fffff8800645201a (usbvideo!LoadPowerLineFrequency+0x00000000000002ce)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003170200 -- (.cxr 0xfffff88003170200)
rax=0049004d00260037 rbx=0000000000000000 rcx=fffff8a0033fe040
rdx=0044004900500026 rsi=fffffa80094efd30 rdi=fffff8a00174a590
rip=fffff8800645201a rsp=fffff88003170bd0 rbp=fffffa800a616c10
 r8=0000000000000002  r9=0000000000000040 r10=fffff80002e15000
r11=fffffa8006b9f040 r12=fffffa8007edd700 r13=0000000000000001
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
usbvideo!LoadPowerLineFrequency+0x2ce:
fffff880`0645201a 448b4a44        mov     r9d,dword ptr [rdx+44h] ds:002b:00440049`0050006a=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_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 fffff800030bd0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
usbvideo!LoadPowerLineFrequency+2ce
fffff880`0645201a 448b4a44        mov     r9d,dword ptr [rdx+44h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8800645563a to fffff8800645201a

STACK_TEXT:  
fffff880`03170bd0 fffff880`0645563a : fffffa80`00000010 fffffa80`00000002 ffffffff`80000f70 fffffa80`094efd30 : usbvideo!LoadPowerLineFrequency+0x2ce
fffff880`03170c50 fffff800`03182827 : 00000000`00000000 fffffa80`094ecf50 fffffa80`06e5b010 fffffa80`06b9f040 : usbvideo!PassiveWakeup+0x26
fffff880`03170c80 fffff800`02e92861 : fffffa80`09505c00 fffff880`03dd8e80 fffff800`0302a5f8 fffffa80`06b9f040 : nt!IopProcessWorkItem+0x23
fffff880`03170cb0 fffff800`0312aa86 : 0000009a`830f1c00 fffffa80`06b9f040 00000000`00000080 fffffa80`06b87b30 : nt!ExpWorkerThread+0x111
fffff880`03170d40 fffff800`02e63b06 : fffff880`02f86180 fffffa80`06b9f040 fffff880`02f910c0 8bf1f700`000fffb9 : nt!PspSystemThreadStartup+0x5a
fffff880`03170d80 00000000`00000000 : fffff880`03171000 fffff880`0316b000 fffff880`031709f0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  usbvideo!LoadPowerLineFrequency+2ce

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbvideo

IMAGE_NAME:  usbvideo.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc24

STACK_COMMAND:  .cxr 0xfffff88003170200 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_usbvideo!LoadPowerLineFrequency+2ce

BUCKET_ID:  X64_0x7E_usbvideo!LoadPowerLineFrequency+2ce

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

Code:

Mpfp.sys        fffff880`03ebd000    fffff880`03efa000    0x0003d000    0x49de3cd5    4/9/2009 14:22:13                        
spldr.sys        fffff880`01400000    fffff880`01408000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
GEARAspiWDM.sys        fffff880`0415f000    fffff880`0416c000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`010c8000    fffff880`010d3000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
CtClsFlt.sys        fffff880`0419e000    fffff880`041c82a0    0x0002a2a0    0x4a35d6e1    6/15/2009 01:06:41                        
PxHlpa64.sys        fffff880`01133000    fffff880`0113ee00    0x0000be00    0x4a416253    6/23/2009 19:16:35                        
SynTP.sys        fffff880`04116000    fffff880`0415f000    0x00049000    0x4a451503    6/26/2009 14:35:47                        
Acceler.sys        fffff880`0416c000    fffff880`04178000    0x0000c000    0x4a453602    6/26/2009 16:56:34                        
stwrt64.sys        fffff880`0663c000    fffff880`066b7000    0x0007b000    0x4a48ff45    6/29/2009 13:52:05                        
risdpe64.sys        fffff880`05128000    fffff880`05141000    0x00019000    0x4a4b2d0d    7/1/2009 05:31:57                        
rimspe64.sys        fffff880`05141000    fffff880`0515a000    0x00019000    0x4a4bf749    7/1/2009 19:54:49                        
rixdpe64.sys        fffff880`0515a000    fffff880`051b0000    0x00056000    0x4a4f2e74    7/4/2009 06:27:00                        
bcmwl664.sys        fffff880`04e73000    fffff880`0511b000    0x002a8000    0x4a53ec10    7/7/2009 20:45:04

Thanks Ken. I'll do those things right now. Appreciate it. :)