I have looked at your seven most recent dmp files. I did not bother with the one from April. The dmps indicate hardware problems. You have six dmps with a stop error of 116 and one with a stop error of 9F.
STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE
Usual causes: Device driver
STOP 0x00000116: VIDEO_TDR_ERROR Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card
Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Minidump(2).zip\062610-21356-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`8078ada4?
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82c3f000 PsLoadedModuleList = 0x82d87810
Debug session time: Sat Jun 26 12:58:04.611 2010 (GMT-4)
System Uptime: 0 days 8:37:10.406
...............................................................
................................................................
.......................................
Loading unloaded module list
........
0: kd> !Analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, 86289b60, 8078adb0, 88c42198}
*** WARNING: Unable to verify timestamp for netw5v32.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v32.sys
Probably caused by : netw5v32.sys
Followup: MachineOwner
---------
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 86289b60, Physical Device Object of the stack
Arg3: 8078adb0, Functional Device Object of the stack
Arg4: 88c42198, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: 88c42198
DEVICE_OBJECT: 869fc028
DRIVER_OBJECT: 8667c1f0
IMAGE_NAME: netw5v32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49cba8fd
MODULE_NAME: netw5v32
FAULTING_MODULE: 9260d000 netw5v32
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: plugin-contain
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 82c7b054 to 82d1bd10
STACK_TEXT:
8078ad64 82c7b054 0000009f 00000003 86289b60 nt!KeBugCheckEx+0x1e
8078add0 82c7a8e8 8078ae70 00000000 88c35cc8 nt!PopCheckIrpWatchdog+0x1f5
8078ae08 82ca904d 82d80a20 00000000 be65f931 nt!PopCheckForIdleness+0x73
8078ae4c 82ca8ff1 82d68d20 8078af78 00000001 nt!KiProcessTimerDpcTable+0x50
8078af38 82ca8eae 82d68d20 8078af78 00000000 nt!KiProcessExpiredTimerList+0x101
8078afac 82ca720e 001e59fb a2984d34 00000000 nt!KiTimerExpiration+0x25c
8078aff4 82ca69dc a2984ce4 00000000 00000000 nt!KiRetireDpcList+0xcb
8078aff8 a2984ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
WARNING: Frame IP not in any known module. Following frames may be wrong.
82ca69dc 00000000 0000001a 00d6850f bb830000 0xa2984ce4
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_IMAGE_netw5v32.sys
BUCKET_ID: 0x9F_IMAGE_netw5v32.sys
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Minidump(2).zip\062510-22557-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82c43000 PsLoadedModuleList = 0x82d8b810
Debug session time: Fri Jun 25 06:46:00.188 2010 (GMT-4)
System Uptime: 0 days 1:45:44.983
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.......
1: kd> !Analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {8889b510, 91a3af40, 0, 2}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+df40 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 8889b510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 91a3af40, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+df40
91a3af40 55 push ebp
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
8d483b74 9198aadb 00000116 8889b510 91a3af40 nt!KeBugCheckEx+0x1e
WARNING: Stack unwind information not available. Following frames may be wrong.
8d483b98 9198b8fa 91a3af40 00000000 00000002 dxgkrnl+0x8cadb
8d483bbc 919bb92c 00000000 00000102 8893a788 dxgkrnl+0x8d8fa
8d483c34 919e5a32 fffffcfb 000633eb 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8d483c5c 919e6153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8d483c98 919c28f0 8d483c90 889ca008 88940618 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8d483d28 919e74b7 8893a788 82c7f3f1 8893a788 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8d483d3c 919e7573 8893a788 00000000 888fda48 dxgmms1!VidSchiRun_PriorityTable+0xf
8d483d50 82e516bb 8893a788 a5f28297 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8d483d90 82d030f9 919e74f4 8893a788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+df40
91a3af40 55 push ebp
SYMBOL_NAME: nvlddmkm+df40
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ac79286
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
Let's address the 116 stop error first since it appeared six consecutive times. The dmps point to nvlddmkm.sys as the probable cause. This is an NVidia display driver.
Go to the Dell website and make sure you have the latest driver installed for your video card. Download the latest driver, uninstall your current driver and install the new driver.
You also have some old drivers on your system. Windows 7 does not like older drivers. Update these drivers or uninstall the software they are associated with. Pay special attention to the one in red.
HpqRemHid.sys with description: HP Remote Control HID Device is a driver file from company Hewlett-Packard Development Company, L.P. belonging to product HP Remote Control HID Device. If you cannot update this software, I recommend that you uninstall it.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Here are your old drivers:
HpqRemHid.sys Wed Jul 11 11:30:21 2007
RTKVHDA.sys Tue Jan 15 06:18:36 2008
SynTP.sys Thu Mar 27 21:14:58 2008
You also have ESET Security Suite running. For the purpose of trouble shooting, I recommend that you uninstall ESET and replace it MSE. After we get you system running smoothly, you can always reinstall ESET, though I recommend you use MSE or Avast and the Windows Firewall.
After you have taken these steps, post back and we will go from there to the next step.
Also, please fill out your system information. Go to your User CP at the top of the page, look in the left column and click on Edit system specs. Filling in your specs will help us help you.
You can make this easier by downloading Speccy.