Windows 7 64bit.
No problems until several days ago. One Blue Screen.
Crashed overnight last night. Now will not start (other than safe mode). Blue Screens after typing in login details.
Dump Attached.
Nost of these are memory related. you should
Download memtestx86 and run it overnight.
these drivers are old and need to be updated
\Code:secdrv.SYS fffff880`0897d000 fffff880`08988000 0x0000b000 0x4508052e 9/13/2006 8:18:38 AM WacomVKHid.sys fffff880`04230000 fffff880`04231c80 0x00001c80 0x45d4e87e 2/15/2007 6:10:54 PM wacommousefilter.sys fffff880`044d8000 fffff880`044e0000 0x00008000 0x45d5f401 2/16/2007 1:12:17 PM lmimirr.sys fffff880`043ef000 fffff880`043f6000 0x00007000 0x461c108d 4/10/2007 5:32:45 PM lvpopf64.sys fffff880`03a48000 fffff880`03b92d00 0x0014ad00 0x464502a5 5/11/2007 6:56:21 PM lvuvc64.sys fffff880`06a41000 fffff880`06db1500 0x00370500 0x46450350 5/11/2007 6:59:12 PM LVUSBS64.sys fffff880`045c2000 fffff880`045cc900 0x0000a900 0x464503d0 5/11/2007 7:01:20 PM RaInfo.sys fffff880`085f4000 fffff880`085fb000 0x00007000 0x477e818a 1/4/2008 1:57:14 PM PxHlpa64.sys fffff880`0104e000 fffff880`01059d00 0x0000bd00 0x47d88a39 3/12/2008 8:58:17 PM rdpdispm.sys fffff880`04177000 fffff880`0417e000 0x00007000 0x47e3424e 3/21/2008 12:06:22 AM adfs.SYS fffff880`085cc000 fffff880`085e4000 0x00018000 0x48640195 6/26/2008 3:52:37 PM wacomvhid.sys fffff880`0420b000 fffff880`0420d680 0x00002680 0x4877a389 7/11/2008 1:16:41 PM LMIRfsDriver.sys fffff880`08400000 fffff880`08413000 0x00013000 0x487b7e50 7/14/2008 11:26:56 AM
These are the rest of the dmps
Code:082309-32136-01.dmp 8/23/2009 7:49:26 AM DRIVER_POWER_STATE_FAILURE 0x1000009f 00000000`00000004 00000000`00000258 fffffa80`036f9680 fffff800`04143510 ntoskrnl.exe ntoskrnl.exe+77dda 082409-39795-01.dmp 8/24/2009 12:05:56 PM DRIVER_POWER_STATE_FAILURE 0x1000009f 00000000`00000004 00000000`00000258 fffffa80`036de040 fffff800`04141510 ntoskrnl.exe ntoskrnl.exe+77dda 121909-50684-01.dmp 12/19/2009 6:20:50 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000000 00000000`00000002 00000000`00000001 fffff800`02e719c2 ntoskrnl.exe ntoskrnl.exe+71f00 102309-76690-01.dmp 10/23/2009 6:22:14 AM MEMORY_MANAGEMENT 0x0000001a 00000000`00041790 fffffa80`011dd650 00000000`0000ffff 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 102309-53071-01.dmp 10/23/2009 6:12:54 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffffa83`014168eb 00000000`00000000 fffff800`02e9fdff 00000000`00000005 atapi.sys atapi.sys+1604 121709-36020-01.dmp 12/17/2009 5:20:06 PM REFERENCE_BY_POINTER 0x00000018 fffffa80`036de750 fffffa80`052f3530 00000000`00000001 00000000`00001000 ntoskrnl.exe ntoskrnl.exe+71f00 121909-45926-01.dmp 12/19/2009 6:33:58 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02e5671d fffff880`0ab6a800 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+71f00 121909-45957-01.dmp 12/19/2009 6:14:44 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff960`0014648a fffff880`047d8e20 00000000`00000000 win32k.sys win32k.sys+10648a 101909-56238-01.dmp 10/19/2009 2:18:24 PM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`040661ff fffff880`031a1088 fffff880`031a08e0 ks.sys ks.sys+183f0 121909-30045-01.dmp 12/19/2009 4:47:08 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`00fd11ff fffff880`033cb088 fffff880`033ca8e0 ks.sys ks.sys+183f0 121909-31200-01.dmp 12/19/2009 6:05:10 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff800`0325ebaf fffff880`031a1768 fffff880`031a0fc0 ntoskrnl.exe ntoskrnl.exe+458baf 121909-37019-01.dmp 12/19/2009 4:11:42 AM SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`044361ff fffff880`033c4088 fffff880`033c38e0 ks.sys ks.sys+183f0Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\102309-76690-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02e04000 PsLoadedModuleList = 0xfffff800`03041e50 Debug session time: Fri Oct 23 01:19:28.549 2009 (GMT-5) System Uptime: 0 days 0:07:46.640 Loading Kernel Symbols ............................................................... ................................................................ .......................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41790, fffffa80011dd650, ffff, 0} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33a98 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041790, The subtype of the bugcheck. Arg2: fffffa80011dd650 Arg3: 000000000000ffff Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41790 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: csc.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002ee8328 to fffff80002e75f00 STACK_TEXT: fffff880`0b877058 fffff800`02ee8328 : 00000000`0000001a 00000000`00041790 fffffa80`011dd650 00000000`0000ffff : nt!KeBugCheckEx fffff880`0b877060 fffff800`02e48eee : fffffa80`07d8d730 fffffa80`00000000 fffff8a0`00000085 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x33a98 fffff880`0b877910 fffff800`031587af : fffff8a0`04fe0580 fffff880`0b877c20 00000000`00000000 fffffa80`06563610 : nt!MmCleanProcessAddressSpace+0x96 fffff880`0b877960 fffff800`03132b3d : 00000000`00000001 00000000`00000001 00000000`7efdb000 00000000`00000000 : nt!PspExitThread+0x47f fffff880`0b877a30 fffff800`02e52a43 : 00000000`00000100 fffffa80`065636d0 00000000`00000001 fffff800`02e7d25d : nt!PsExitSpecialApc+0x1d fffff880`0b877a60 fffff800`02e52e80 : 00000000`00000000 fffff880`0b877ae0 fffff800`03133710 00000000`00000001 : nt!KiDeliverApc+0x2eb fffff880`0b877ae0 fffff800`02e751f7 : fffffa80`06563610 00000000`00240000 00000000`00000000 fffffa80`07e6f600 : nt!KiInitiateUserApc+0x70 fffff880`0b877c20 00000000`75152dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c 00000000`0008ebf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75152dd9 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+33a98 fffff800`02ee8328 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33a98 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33a98 BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33a98 Followup: MachineOwner ---------
The last dump file blames epfwwfp.sys - a component of your ESET personal firewall.
Please download a fresh copy of the program, then uninstall the current program from your computer and install the fresh copy.
2 of the other dump files blame ks.sys - a component of the Windows operating system related to video. These dump files also have issues with lvuvc64.sys - a component of your Logitech webcam. So, the same thing goes here - Please download a fresh copy of the program, then uninstall the current program from your computer and install the fresh copy.
Finally, please update these older drivers as you have time:
Here's the summary of the latest BSOD'S:Code:adfs.SYS Thu Jun 26 16:52:37 2008 lmimirr.sys Tue Apr 10 18:32:45 2007 lvpopf64.sys Fri May 11 19:56:21 2007 LVUSBS64.sys Fri May 11 20:01:20 2007 lvuvc64.sys Fri May 11 19:59:12 2007 PxHlpa64.sys Wed Mar 12 21:58:17 2008 rdpdispm.sys Fri Mar 21 01:06:22 2008 wacommousefilter.sys Fri Feb 16 13:12:17 2007 wacomvhid.sys Fri Jul 11 14:16:41 2008 WacomVKHid.sys Thu Feb 15 18:10:54 2007
Code:Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Thu Dec 17 12:17:17.385 2009 (GMT-5) System Uptime: 0 days 19:30:42.101 BugCheck 18, {fffffa80036de750, fffffa80052f3530, 1, 1000} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4660a ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Dec 18 23:45:47.957 2009 (GMT-5) System Uptime: 0 days 0:00:38.658 BugCheck 1000007E, {ffffffffc0000005, fffff88000fd11ff, fffff880033cb088, fffff880033ca8e0} *** WARNING: Unable to verify timestamp for lvuvc64.sys *** ERROR: Module load completed but symbols could not be loaded for lvuvc64.sys Probably caused by : ks.sys ( ks!KspCountSetsAndItems+53 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Dec 19 01:03:04.944 2009 (GMT-5) System Uptime: 0 days 0:01:26.661 BugCheck 1000007E, {ffffffffc0000005, fffff8000325ebaf, fffff880031a1768, fffff880031a0fc0} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption DEFAULT_BUCKET_ID: CODE_CORRUPTION PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Fri Dec 18 21:35:31.548 2009 (GMT-5) System Uptime: 0 days 0:00:40.265 BugCheck 1000007E, {ffffffffc0000005, fffff880044361ff, fffff880033c4088, fffff880033c38e0} *** WARNING: Unable to verify timestamp for lvuvc64.sys *** ERROR: Module load completed but symbols could not be loaded for lvuvc64.sys Probably caused by : ks.sys ( ks!KspCountSetsAndItems+53 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Dec 19 01:22:05.347 2009 (GMT-5) System Uptime: 0 days 0:02:21.064 BugCheck 3B, {c0000005, fffff80002e5671d, fffff8800ab6a800, 0} Probably caused by : ntkrnlmp.exe ( nt!RtlpCreateSplitBlock+329 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: SnagIt32.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Dec 19 01:12:23.500 2009 (GMT-5) System Uptime: 0 days 0:07:59.016 BugCheck 3B, {c0000005, fffff9600014648a, fffff880047d8e20, 0} Probably caused by : win32k.sys ( win32k!xxxDestroyThreadDDEObject+a ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: wisptis.exe -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sat Dec 19 01:17:58.610 2009 (GMT-5) System Uptime: 0 days 0:00:49.701 BugCheck A, {0, 2, 1, fffff80002e719c2} *** WARNING: Unable to verify timestamp for epfwwfp.sys *** ERROR: Module load completed but symbols could not be loaded for epfwwfp.sys Probably caused by : epfwwfp.sys ( epfwwfp+4cb6 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System
Thank you for the advice.
I checked my memory settings with everest and they were set to values which were more aggressive than recommeded. I have remedied this and will look for new drivers to replace those listed.
I've already updated eset.
My machine is currently back to it's (usual) stable self. Fingers crossed.
Quote