I've attached the last BSOD dump. It happened on startup, before I even logged in!
This past week I have reinstalled Dell's webcam software--which I'm guessing installs the driver, which I otherwise wasn't able to find from Creative--as well as nVidia and WiFi driver updates.
Any help is appreciated.
Thanks,
George
George, I am sorry to learn you are still having problems. Anytime you get a crash on startup, you can pretty well figure it is a hardware or driver related.
Error code 3B, SYSTEM_SERVICE_EXCEPTION- usually caused by System service, Device driver, graphics driver, ?memory.
The dump blamed a Windows system driver (very unlikely) and indicated memory corruption. I also looked at the two previous dumps. Both are error code 3B. One directly point s to memory corruption and the other points to a Windows system driver and indicates memory corruption.
Let's test your RAM. Follow the instructions in this excellent tutorial by Johnathan King.Code:Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03088e50 Debug session time: Fri Sep 10 19:54:37.299 2010 (GMT-4) System Uptime: 0 days 0:01:14.437 Loading Kernel Symbols ............................................................... ................................................................ ............................................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002edb436, fffff8800b12ed00, 0} Probably caused by : ntkrnlmp.exe ( nt!WmipIoControl+d6 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80002edb436, Address of the exception record for the exception that caused the bugcheck Arg3: fffff8800b12ed00, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. 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!IopCompleteRequest+c73 fffff800`02edb436 488b09 mov rcx,qword ptr [rcx] CONTEXT: fffff8800b12ed00 -- (.cxr 0xfffff8800b12ed00) rax=fffffa800b173978 rbx=fffffa800b285010 rcx=fefffa800b173978 rdx=fefffa800b173978 rsi=0000000000000000 rdi=fffffa800b301520 rip=fffff80002edb436 rsp=fffff8800b12f6d0 rbp=00000000a000000c r8=0000000fffffffff r9=fffffa8000000008 r10=0000000000000002 r11=0000007ffffffff8 r12=fffffa800b173970 r13=0000000000000000 r14=fffffa800b32a930 r15=fffff880009e9180 iopl=0 nv up ei ng nz na po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287 nt!IopCompleteRequest+0xc73: fffff800`02edb436 488b09 mov rcx,qword ptr [rcx] ds:002b:fefffa80`0b173978=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: WmiPrvSE.exe CURRENT_IRQL: 2 IRP_ADDRESS: ffffffffffffff88 LAST_CONTROL_TRANSFER: from fffff80002ebe0dd to fffff80002edb436 STACK_TEXT: fffff880`0b12f6d0 fffff800`02ebe0dd : 00000000`00000000 fffff800`20206f49 00000000`00010001 fffffa80`00000000 : nt!IopCompleteRequest+0xc73 fffff880`0b12f7a0 fffff800`0314d2f6 : 00000000`0000000c fffff800`02fefb00 fffffa80`0b301520 00000000`00000000 : nt!IopfCompleteRequest+0x75d fffff880`0b12f880 fffff800`031d6707 : fffffa80`0b301520 fffff880`0b12fc60 fffff880`0b12fc60 fffffa80`0b285010 : nt!WmipIoControl+0xd6 fffff880`0b12f9d0 fffff800`031d6f66 : fffff880`0b12fbb8 00000000`00000454 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x607 fffff880`0b12fb00 fffff800`02eba993 : 00000000`00000d41 00000000`0062e638 00000000`00000000 0000007f`ffffffff : nt!NtDeviceIoControlFile+0x56 fffff880`0b12fb70 00000000`73f02dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0062ef38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73f02dd9 FOLLOWUP_IP: nt!WmipIoControl+d6 fffff800`0314d2f6 8bc3 mov eax,ebx SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!WmipIoControl+d6 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff8800b12ed00 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!WmipIoControl+d6 BUCKET_ID: X64_0x3B_nt!WmipIoControl+d6 Followup: MachineOwner --------- Kernel base = 0xfffff800`02e61000 PsLoadedModuleList = 0xfffff800`0309ee50 Debug session time: Wed Sep 1 14:17:12.782 2010 (GMT-4) System Uptime: 0 days 0:31:59.592 Loading Kernel Symbols ............................................................... ................................................................ ............................................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff800031787eb, fffff8800ab35e10, 0} Probably caused by : memory_corruption ( nt!MiUnsecureVirtualMemory+6b ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff800031787eb, Address of the exception record for the exception that caused the bugcheck Arg3: fffff8800ab35e10, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. 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!MiUnsecureVirtualMemory+6b fffff800`031787eb 8b4540 mov eax,dword ptr [rbp+40h] CONTEXT: fffff8800ab35e10 -- (.cxr 0xfffff8800ab35e10) rax=000000000000000a rbx=fffffa800af13060 rcx=fefffa800b5da951 rdx=0000000000000000 rsi=fffffa8006970b30 rdi=fefffa800b5da950 rip=fffff800031787eb rsp=fffff8800ab367e0 rbp=fefffa800b5da910 r8=0000000000000001 r9=0000000000000002 r10=fffffa8006970b30 r11=fffff800030d1b60 r12=fffffa8006970d48 r13=fffffa800a8eb520 r14=fffffa8006970b30 r15=fffff8800ab36930 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 nt!MiUnsecureVirtualMemory+0x6b: fffff800`031787eb 8b4540 mov eax,dword ptr [rbp+40h] ss:0018:fefffa80`0b5da950=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80003179b1b to fffff800031787eb STACK_TEXT: fffff880`0ab367e0 fffff800`03179b1b : fffff800`03049e30 00000000`00000000 fffff8a0`0c2c3490 fffff8a0`0c2c34b0 : nt!MiUnsecureVirtualMemory+0x6b fffff880`0ab36810 fffff800`0316a596 : 00000000`00000000 fffff800`03049e30 fffff8a0`0c2c34b0 fffff8a0`0c282d00 : nt!AlpcpViewDestroyProcedure+0x1fb fffff880`0ab368b0 fffff800`0316b167 : 00000000`00000000 00000000`01b2e3c0 00000000`40000000 fffff880`0ab36a40 : nt!AlpcpCaptureViewAttributeInternal+0x196 fffff880`0ab36910 fffff800`031a0413 : fffff8a0`0bdd27e8 00000000`00000000 fffffa80`0af13060 fffff800`031eb56f : nt!AlpcpCaptureViewAttribute+0x47 fffff880`0ab36960 fffff800`031d11f9 : fffffa80`0a8eb520 00000000`00000000 fffff8a0`0c282d00 fffff8a0`0c282d00 : nt!AlpcpCaptureAttributes+0x320 fffff880`0ab369c0 fffff800`031d2ed9 : fffffa80`00000000 fffff8a0`00000001 00000000`014ff420 00000000`00000701 : nt!AlpcpSendMessage+0x3c7 fffff880`0ab36ac0 fffff800`02ed0993 : fffffa80`0af13060 fffff880`0ab36c60 00000000`014ff3a8 0000007f`ffffffff : nt!NtAlpcSendWaitReceivePort+0xb9 fffff880`0ab36b70 00000000`773a05aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`014ff388 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773a05aa FOLLOWUP_IP: nt!MiUnsecureVirtualMemory+6b fffff800`031787eb 8b4540 mov eax,dword ptr [rbp+40h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiUnsecureVirtualMemory+6b FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff8800ab35e10 ; kb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x3B_nt!MiUnsecureVirtualMemory+6b BUCKET_ID: X64_0x3B_nt!MiUnsecureVirtualMemory+6b Followup: MachineOwner --------- Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030a4e50 Debug session time: Mon Aug 30 17:19:33.405 2010 (GMT-4) System Uptime: 0 days 1:15:03.434 Loading Kernel Symbols ............................................................... ................................................................ .............................................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff800031b374d, fffff8800b599730, 0} Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff800031b374d, Address of the exception record for the exception that caused the bugcheck Arg3: fffff8800b599730, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. 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!CmpKcbCacheLookup+1dd fffff800`031b374d 418b45f4 mov eax,dword ptr [r13-0Ch] CONTEXT: fffff8800b599730 -- (.cxr 0xfffff8800b599730) rax=fffff8a005065000 rbx=0000000000000000 rcx=0000000000000bd9 rdx=00000000073d1409 rsi=fffff8a0007eea18 rdi=fffff8800b59a340 rip=fffff800031b374d rsp=fffff8800b59a100 rbp=fffff8a0007ee420 r8=000000000000000b r9=0000000000000000 r10=0000000000000016 r11=fffff8800b59a298 r12=0000000000000007 r13=fefff8a0000e8268 r14=0000000000000007 r15=0000000000000001 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 nt!CmpKcbCacheLookup+0x1dd: fffff800`031b374d 418b45f4 mov eax,dword ptr [r13-0Ch] ds:002b:fefff8a0`000e825c=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: explorer.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800031b2d08 to fffff800031b374d STACK_TEXT: fffff880`0b59a100 fffff800`031b2d08 : fffff880`0b59a298 fffff880`00000008 fffff880`0b59a688 fffff880`0b59a6a0 : nt!CmpKcbCacheLookup+0x1dd fffff880`0b59a1f0 fffff800`031b0f61 : fffff8a0`02efe960 fffff880`0b59a6a0 fffff880`0b59a6d8 fffff880`0b59a6c0 : nt!CmpBuildHashStackAndLookupCache+0x328 fffff880`0b59a5d0 fffff800`031d0e84 : fffff800`031b0cc0 00000000`00000000 fffffa80`045b6010 fffff880`011dd901 : nt!CmpParseKey+0x2a1 fffff880`0b59a8a0 fffff800`031d5e4d : fffffa80`045b6010 fffff880`0b59aa00 00000000`00000040 fffffa80`03cf7080 : nt!ObpLookupObjectName+0x585 fffff880`0b59a9a0 fffff800`031b4dcc : 00000000`03c67000 00000000`00000000 fffff8a0`02efe901 fffff880`0b59aa68 : nt!ObOpenObjectByName+0x1cd fffff880`0b59aa50 fffff800`031b6f0f : 00000000`1ff8d340 00000000`00020019 00000000`1ff8d3c8 00000000`00000000 : nt!CmOpenKey+0x28a fffff880`0b59aba0 fffff800`02ed6993 : fffffa80`04192b60 fffff880`0b59ac60 00000000`00000000 fffffa80`0aa2bd60 : nt!NtOpenKeyEx+0xf fffff880`0b59abe0 00000000`76d40caa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`1ff8d2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d40caa FOLLOWUP_IP: nt!CmpKcbCacheLookup+1dd fffff800`031b374d 418b45f4 mov eax,dword ptr [r13-0Ch] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!CmpKcbCacheLookup+1dd FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff8800b599730 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!CmpKcbCacheLookup+1dd BUCKET_ID: X64_0x3B_nt!CmpKcbCacheLookup+1dd Followup: MachineOwner ---------
RAM - Test with Memtest86+
This will take some time. Please post the results.
You still have out of date drivers; though I can see that you have updated some of them. You have a few really old drivers that definitely are not helping your system's stability.
Let's try something. This is going break your webcam; but let's see if those drivers are the problem. Navigate to C:\Windows\System32\Drivers and rename the two camera drivers from .sys to .bak. Reboot and lets see what your system does. You can rename to .sys later if this proves not to be the problem.BCM42RLY.sys Tue Jul 07 20:34:55 2009 - Broadcom iLine10(tm) PCI Network Adapter Broadcom.com - Downloads & Support. I know that you have tried to update this driver. It is slightly out of date; but it may work.
nvsmu.sys Mon Jun 29 03:36:37 2009 - nVidia nForce System Management Controller (nVidia nForce chipset driver) Drivers - Download NVIDIA Drivers. This is a chipset driver and slightly out of date. See if you can update this one.
OA001Ufd.sys Tue Jun 03 05:30:37 2008 - Upper Filter Drivers are driver files from Creative Technology Ltd. These must be for your web cam. If you cannot update these drivers, the hardware is obsolete and not compatible with Win 7. Check here: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads If there is no update, I recommend that you uninstall this hardware and upgrade to a camera compatible with Win 7.
OA001Vid.sys Mon Aug 25 09:07:17 2008 - see above
rimmpx64.sys Thu Jun 25 04:04:18 2009 - Ricoh Card Reader driver.
rimspx64.sys Thu Jun 25 03:13:43 2009 - Ricoh Card Reader driver.
rixdpx64.sys Thu Jun 25 03:38:50 2009 - Ricoh Card Reader driver.
Post back and let us know. And don't forget to run Memtest.
Last edited by CarlTR6; 10 Sep 2010 at 21:13.
I let the RAM test run overnight, 8 hrs, a lot of passes with 0 errors.
Dell said if I install the Webcam software, the appropriate drivers will be installed, so I did that and updated the software.
Also, it appears the driver install packages do not automatically update the drivers, as was the case with one of those Broadcom drivers, so I renamed the old driver to .bak and copied the newer .sys into the system folder.
I think the Ricoh install package also failed to load the new drivers, so I'll have to go dig around and check those.
-George
Good job of digging, George. A big plus on working around the Broadcom driver issue. Thanks for the update.
Hi, had another crash on startup (dump attached), even before reaching the login screen.
This crash was probably caused by your usbhub.sys driver. You may need to reinstall the USB driver..Check device and see if it is without a yellow exclamation mark for "universal serial bus controllers", then see generic usb hub, properties,drive, driver details, this should show usbhub.sys. If all seems well you may need to uninstall and then scan for hardware changes, this can be done from the properties.
I would also run a system file check to verify and repair system files
Let us know if you need help with this
Ken J
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\K\Desktop\092010-25568-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 (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e53000 PsLoadedModuleList = 0xfffff800`03090e50 Debug session time: Mon Sep 20 12:37:22.833 2010 (GMT-4) System Uptime: 0 days 0:00:36.643 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff80002ee1c11, fffff88002fbd528, fffff88002fbcd90} Unable to load image usbhub.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for usbhub.sys *** ERROR: Module load completed but symbols could not be loaded for usbhub.sys Probably caused by : usbhub.sys ( usbhub+2618 ) Followup: MachineOwner --------- 1: 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: fffff80002ee1c11, The address that the exception occurred at Arg3: fffff88002fbd528, Exception Record Address Arg4: fffff88002fbcd90, 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!IopQueueThreadIrp+b1 fffff800`02ee1c11 48897808 mov qword ptr [rax+8],rdi EXCEPTION_RECORD: fffff88002fbd528 -- (.exr 0xfffff88002fbd528) ExceptionAddress: fffff80002ee1c11 (nt!IopQueueThreadIrp+0x00000000000000b1) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff88002fbcd90 -- (.cxr 0xfffff88002fbcd90) rax=fefffa8003ce6a68 rbx=fffffa8003ce6680 rcx=0000000002fbda38 rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa800528eb40 rip=fffff80002ee1c11 rsp=fffff88002fbd760 rbp=fffffa8003ce6a68 r8=0000000000000000 r9=0000000000000000 r10=fffffa8003d009e0 r11=0000000000000006 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003 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!IopQueueThreadIrp+0xb1: fffff800`02ee1c11 48897808 mov qword ptr [rax+8],rdi ds:002b:fefffa80`03ce6a70=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 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 fffff800030fb0e0 ffffffffffffffff FOLLOWUP_IP: usbhub+2618 fffff880`04c80618 ?? ??? BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff800031af084 to fffff80002ee1c11 STACK_TEXT: fffff880`02fbd760 fffff800`031af084 : fffff880`02fbda38 fffff880`02fbd970 00000000`00000000 fffffa80`06dba1a0 : nt!IopQueueThreadIrp+0xb1 fffff880`02fbd7c0 fffff880`04c80618 : 00000000`00220013 fffffa80`06d1b060 00000000`00000000 fffffa80`06013870 : nt!IoBuildDeviceIoControlRequest+0x114 fffff880`02fbd830 00000000`00220013 : fffffa80`06d1b060 00000000`00000000 fffffa80`06013870 00000000`00000000 : usbhub+0x2618 fffff880`02fbd838 fffffa80`06d1b060 : 00000000`00000000 fffffa80`06013870 00000000`00000000 fffffa80`00000000 : 0x220013 fffff880`02fbd840 00000000`00000000 : fffffa80`06013870 00000000`00000000 fffffa80`00000000 ffff7412`0d7e1d01 : 0xfffffa80`06d1b060 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: usbhub+2618 FOLLOWUP_NAME: MachineOwner MODULE_NAME: usbhub IMAGE_NAME: usbhub.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4b18b9af STACK_COMMAND: .cxr 0xfffff88002fbcd90 ; kb FAILURE_BUCKET_ID: X64_0x7E_usbhub+2618 BUCKET_ID: X64_0x7E_usbhub+2618 Followup: MachineOwner --------- 1: 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: fffff80002ee1c11, The address that the exception occurred at Arg3: fffff88002fbd528, Exception Record Address Arg4: fffff88002fbcd90, 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!IopQueueThreadIrp+b1 fffff800`02ee1c11 48897808 mov qword ptr [rax+8],rdi EXCEPTION_RECORD: fffff88002fbd528 -- (.exr 0xfffff88002fbd528) ExceptionAddress: fffff80002ee1c11 (nt!IopQueueThreadIrp+0x00000000000000b1) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff88002fbcd90 -- (.cxr 0xfffff88002fbcd90) rax=fefffa8003ce6a68 rbx=fffffa8003ce6680 rcx=0000000002fbda38 rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa800528eb40 rip=fffff80002ee1c11 rsp=fffff88002fbd760 rbp=fffffa8003ce6a68 r8=0000000000000000 r9=0000000000000000 r10=fffffa8003d009e0 r11=0000000000000006 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000003 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!IopQueueThreadIrp+0xb1: fffff800`02ee1c11 48897808 mov qword ptr [rax+8],rdi ds:002b:fefffa80`03ce6a70=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 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: ffffffffffffffff FOLLOWUP_IP: usbhub+2618 fffff880`04c80618 ?? ??? BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff800031af084 to fffff80002ee1c11 STACK_TEXT: fffff880`02fbd760 fffff800`031af084 : fffff880`02fbda38 fffff880`02fbd970 00000000`00000000 fffffa80`06dba1a0 : nt!IopQueueThreadIrp+0xb1 fffff880`02fbd7c0 fffff880`04c80618 : 00000000`00220013 fffffa80`06d1b060 00000000`00000000 fffffa80`06013870 : nt!IoBuildDeviceIoControlRequest+0x114 fffff880`02fbd830 00000000`00220013 : fffffa80`06d1b060 00000000`00000000 fffffa80`06013870 00000000`00000000 : usbhub+0x2618 fffff880`02fbd838 fffffa80`06d1b060 : 00000000`00000000 fffffa80`06013870 00000000`00000000 fffffa80`00000000 : 0x220013 fffff880`02fbd840 00000000`00000000 : fffffa80`06013870 00000000`00000000 fffffa80`00000000 ffff7412`0d7e1d01 : 0xfffffa80`06d1b060 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: usbhub+2618 FOLLOWUP_NAME: MachineOwner MODULE_NAME: usbhub IMAGE_NAME: usbhub.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4b18b9af STACK_COMMAND: .cxr 0xfffff88002fbcd90 ; kb FAILURE_BUCKET_ID: X64_0x7E_usbhub+2618 BUCKET_ID: X64_0x7E_usbhub+2618 Followup: MachineOwner ---------
Thanks, Ken. I reinstalled the usbhub.sys driver. I'll run the system file check.
Cheers,
George
George, in addition to Ken's solid recommendation, I still find some out of date drivers; some are badly out of date. Out of date third party drivers just do not work well with Win 7. They can cause memory corruption and crashes. Your dump indicates memory corruption.
I know that you tried to update the Ricoh card reader drivers and no updates are available. You may have to ditch this card reader and upgrade to one certified to be compatible with Windows 7. However, concentrate on the 2008 drivers first and lets see if that helps your system's stability.facap.sys Wed Sep 24 22:34:31 2008
nvsmu.sys Mon Jun 29 03:36:37 2009
OA001Ufd.sys Tue Jun 03 05:30:37 2008
OA001Vid.sys Mon Aug 25 09:07:17 2008
rimmpx64.sys Thu Jun 25 04:04:18 2009
rimspx64.sys Thu Jun 25 03:13:43 2009
rixdpx64.sys Thu Jun 25 03:38:50 2009
facap.sys - aCap WebCam Capture is a driver file from company Sensible Vision belonging to product faCap WebCam Capture. This software is obsolete. You can try to upgrade it. If there is not an upgrade available, completely uninstall the software. It is not written for Windows 7.
OA001Ufd.sys and OA001Vid.sys - Upper Filter Drivers are driver files from Creative Technology Ltd. These must be for your web cam. If you cannot update these drivers, the hardware is obsolete and not compatible with Win 7. Check here: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads. I know that you could not find updates for these drivers. This webcam is obsolete and not design for Windows 7. Uninstall the hardware and software completely and upgrade to a camera compatible with Win 7. If it is any consolation, I had to do the same thing. These obsolete webcam drivers could be causing the problem with your USB.
Once you uninstall the webcam, if you still have BSOD's, uninstall the card reader and upload the dump files.
nvsmu.sys - nVidia nForce System Management Controller (nVidia nForce chipset driver) Drivers - Download NVIDIA Drivers. See if you can update this chipset driver.
Hi, Dell support suggest I try Vista drivers for my Webcam. I'm wondering if my recent BSOD was related to that particular driver?
Also, if I do disable my Webcam, won't Windows automatically detect it next time I boot, and reinstall drivers? How do I override that?
Thanks!
George
George, you can try the Vista drivers; that does sometimes work. You can disable the webcam permanently by navigating to C:\Windows\System32\Drivers. Locate those two drivers and rename from .sys to .bak. Reboot and these drivers will not load. Of course, you webcam will not work either.
You also need to uninstall Sensible Vision belonging to product faCap WebCam Capture. This software is obsolete. You can try to upgrade it. If there is not an upgrade available, completely uninstall the software. It is not written for Windows 7.
Error code 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED - usually caused by Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.
The dump points out memory corruption, 0xc0000005, and blames a Windows system driver, which is highly unlikely to be the real cause.
Code:Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03040e50 Debug session time: Mon Sep 27 14:43:23.877 2010 (GMT-4) System Uptime: 0 days 0:11:27.562 Loading Kernel Symbols ............................................................... ................................................................ .................................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff80002e8014b, fffff88004059608, fffff88004058e70} Probably caused by : cdd.dll ( cdd!PresentWorkerThread+4b8 ) Followup: MachineOwner --------- 1: 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: fffff80002e8014b, The address that the exception occurred at Arg3: fffff88004059608, Exception Record Address Arg4: fffff88004058e70, 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!KiInsertTimerTable+13b fffff800`02e8014b 488b42f8 mov rax,qword ptr [rdx-8] EXCEPTION_RECORD: fffff88004059608 -- (.exr 0xfffff88004059608) ExceptionAddress: fffff80002e8014b (nt!KiInsertTimerTable+0x000000000000013b) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff88004058e70 -- (.cxr 0xfffff88004058e70) rax=0000000000000001 rbx=fffff88004059a10 rcx=0000000000000001 rdx=fefff880009ebae8 rsi=0000000000000760 rdi=fffff880009e9180 rip=fffff80002e8014b rsp=fffff88004059840 rbp=fffff880009ebae8 r8=ffffffffffffffff r9=000000000000002b r10=fffff880009e9180 r11=fffffa80046a4000 r12=fffff880009ebae8 r13=0000000000000001 r14=0000000000000000 r15=0000000199d44cdf iopl=0 nv up ei ng nz na po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287 nt!KiInsertTimerTable+0x13b: fffff800`02e8014b 488b42f8 mov rax,qword ptr [rdx-8] ds:002b:fefff880`009ebae0=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: csrss.exe CURRENT_IRQL: 2 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 fffff800030ab0e0 ffffffffffffffff FOLLOWUP_IP: cdd!PresentWorkerThread+4b8 fffff960`00745824 488d842420010000 lea rax,[rsp+120h] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff80002e7fde0 to fffff80002e8014b STACK_TEXT: fffff880`04059840 fffff800`02e7fde0 : ffffffff`fffd7501 fffff880`009e9180 fffff880`04059a10 00000000`00000001 : nt!KiInsertTimerTable+0x13b fffff880`040598a0 fffff800`02e7fce4 : ffffffff`fffd7501 ffffffff`fffd7501 00000000`00000000 ffffffff`fffd7501 : nt!KiSetTimerEx+0xf0 fffff880`04059930 fffff960`00745824 : ffffffff`00000004 fffff880`040599b8 00000000`00000001 00000000`00000000 : nt!KeSetTimer+0x14 fffff880`04059970 fffff800`03117c06 : 00000000`02fc864a fffffa80`06f0bb60 00000000`00000080 fffffa80`06f02060 : cdd!PresentWorkerThread+0x4b8 fffff880`04059d00 fffff800`02e51c26 : fffff880`009e9180 fffffa80`06f0bb60 fffffa80`058fe660 00000000`00000283 : nt!PspSystemThreadStartup+0x5a fffff880`04059d40 00000000`00000000 : fffff880`0405a000 fffff880`04054000 fffff880`040594b0 00000000`00000000 : nt!KxStartSystemThread+0x16 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: cdd!PresentWorkerThread+4b8 FOLLOWUP_NAME: MachineOwner MODULE_NAME: cdd IMAGE_NAME: cdd.dll DEBUG_FLR_IMAGE_TIMESTAMP: 4bf4408a STACK_COMMAND: .cxr 0xfffff88004058e70 ; kb FAILURE_BUCKET_ID: X64_0x7E_cdd!PresentWorkerThread+4b8 BUCKET_ID: X64_0x7E_cdd!PresentWorkerThread+4b8 Followup: MachineOwner --------- 1: kd> lmtsmn start end module name fffff880`03c8c000 fffff880`03cca000 1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30) fffff880`00f0e000 fffff880`00f65000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`02cf7000 fffff880`02d81000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`04be2000 fffff880`04bf8000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`01187000 fffff880`01192000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`0b949000 fffff880`0b954000 asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5) fffff880`00e1a000 fffff880`00e23000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00e23000 fffff880`00e4d000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff960`00810000 fffff960`00871000 ATMFD ATMFD.DLL Thu May 27 00:11:31 2010 (4BFDF0F3) fffff880`00fd6000 fffff880`00fe2000 BATTC BATTC.SYS Mon Jul 13 19:31:01 2009 (4A5BC3B5) fffff880`0482a000 fffff880`04b19000 bcmwl664 bcmwl664.sys Thu Jan 21 22:30:58 2010 (4B591BF2) fffff880`01873000 fffff880`0187a000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`03b3e000 fffff880`03b4f000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`098c8000 fffff880`098e6000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`00740000 fffff960`00767000 cdd cdd.dll Wed May 19 15:48:26 2010 (4BF4408A) fffff880`01813000 fffff880`0183d000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00cc7000 fffff880`00d87000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`10ba4000 fffff880`10bb6000 circlass circlass.sys Mon Jul 13 20:06:34 2009 (4A5BCC0A) fffff880`01977000 fffff880`019a7000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00c69000 fffff880`00cc7000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`03a5c000 fffff880`03a60500 CmBatt CmBatt.sys Mon Jul 13 19:31:03 2009 (4A5BC3B7) fffff880`0105e000 fffff880`010d1000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`00fcd000 fffff880`00fd6000 compbatt compbatt.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6) fffff880`04b82000 fffff880`04b92000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`0500c000 fffff880`0501a000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`03a9d000 fffff880`03b20000 csc csc.sys Mon Jul 13 19:24:26 2009 (4A5BC22A) fffff880`043b0000 fffff880`043da3a0 CtClsFlt CtClsFlt.sys Wed Sep 16 04:08:47 2009 (4AB09D0F) fffff880`03b20000 fffff880`03b3e000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`02cbc000 fffff880`02ccb000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`01961000 fffff880`01977000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`05168000 fffff880`0518a000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`05063000 fffff880`05076000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`05024000 fffff880`05063000 dump_nvstor64 dump_nvstor64.sys Mon Mar 08 19:14:12 2010 (4B9592D4) fffff880`0501a000 fffff880`05024000 dump_storport dump_storport.sys Mon Jul 13 20:01:00 2009 (4A5BCABC) fffff880`05000000 fffff880`0500c000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`04233000 fffff880`04327000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`04327000 fffff880`0436d000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`04b92000 fffff880`04bcb000 facap facap.sys Wed Sep 24 22:34:31 2008 (48DAF8B7) fffff880`09eb1000 fffff880`09ee7000 fastfat fastfat.SYS Mon Jul 13 19:23:28 2009 (4A5BC1F0) fffff880`011de000 fffff880`011f2000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`01192000 fffff880`011de000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`013f4000 fffff880`013fe000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`01927000 fffff880`01961000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`0142b000 fffff880`01475000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`033df000 fffff800`03428000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`03c68000 fffff880`03c8c000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`051be000 fffff880`051d7000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`051ad000 fffff880`051be000 hidir hidir.sys Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`051d7000 fffff880`051df080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`10be9000 fffff880`10bf7000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`09800000 fffff880`098c8000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`0191e000 fffff880`01927000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`03b94000 fffff880`03bb2000 i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`03b75000 fffff880`03b8b000 intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`04b26000 fffff880`04b82000 itecir itecir.sys Wed Feb 24 03:59:35 2010 (4B84EA77) fffff880`03bb2000 fffff880`03bc1000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`051e0000 fffff880`051ee000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00bc2000 fffff800`00bcc000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`0436d000 fffff880`043b0000 ks ks.sys Mon Jul 13 20:00:31 2009 (4A5BCA9F) fffff880`013c9000 fffff880`013e3000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`01400000 fffff880`0142b000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`04bdc000 fffff880`04be1200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`0fe6f000 fffff880`0fe84000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`10b73000 fffff880`10b96000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00c11000 fffff880`00c55000 mcupdate mcupdate.dll Mon Jul 13 21:29:10 2009 (4A5BDF66) fffff880`05076000 fffff880`05084000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`03a4d000 fffff880`03a5c000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`051ee000 fffff880`051fb000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00e00000 fffff880`00e1a000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`0183d000 fffff880`0186a000 MpFilter MpFilter.sys Thu Oct 01 22:36:31 2009 (4AC5672F) fffff880`0b954000 fffff880`0b964000 MpNWMon MpNWMon.sys Thu Oct 01 22:36:22 2009 (4AC56726) fffff880`09986000 fffff880`0999e000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`0999e000 fffff880`099cb000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`09eec000 fffff880`09f3a000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`09f3a000 fffff880`09f5d000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`00e4d000 fffff880`00e58000 msahci msahci.sys Fri Nov 13 23:36:50 2009 (4AFE33E2) fffff880`00df3000 fffff880`00dfe000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00f6e000 fffff880`00f78000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`09f5d000 fffff880`09f5ec00 MSPCLOCK MSPCLOCK.sys Mon Jul 13 20:00:17 2009 (4A5BCA91) fffff880`0997a000 fffff880`0997ba80 MSPQM MSPQM.sys Mon Jul 13 20:00:17 2009 (4A5BCA91) fffff880`01000000 fffff880`0105e000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`02cb1000 fffff880`02cbc000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`0190c000 fffff880`0191e000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`014aa000 fffff880`0159c000 ndis ndis.sys Thu Nov 19 22:45:55 2009 (4B0610F3) fffff880`043db000 fffff880`043e7000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`0994f000 fffff880`09962000 ndisuio ndisuio.sys Mon Jul 13 20:09:25 2009 (4A5BCCB5) fffff880`04200000 fffff880`0422f000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`0fe5a000 fffff880`0fe6f000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`02c16000 fffff880`02c25000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`02d81000 fffff880`02dc6000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`0159c000 fffff880`015fc000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`00c00000 fffff880`00c11000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`02ca5000 fffff880`02cb1000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02e03000 fffff800`033df000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`01226000 fffff880`013c9000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`0186a000 fffff880`01873000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`10b1b000 fffff880`10b1c180 nvBridge nvBridge.kmd Fri Jul 09 17:07:54 2010 (4C378FAA) fffff880`0518a000 fffff880`051ad000 nvhda64v nvhda64v.sys Mon Jun 21 18:07:25 2010 (4C1FE29D) fffff880`0fe89000 fffff880`10b1ae00 nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:58 2010 (4C37918E) fffff880`03d6e000 fffff880`03dc1a80 nvmf6264 nvmf6264.sys Thu Mar 04 20:04:39 2010 (4B9058A7) fffff880`03a61000 fffff880`03a6c000 nvsmu nvsmu.sys Mon Jun 29 03:36:37 2009 (4A486F05) fffff880`010e6000 fffff880`01125000 nvstor64 nvstor64.sys Mon Mar 08 19:14:12 2010 (4B9592D4) fffff880`098fc000 fffff880`0994f000 nwifi nwifi.sys Mon Jul 13 20:07:23 2009 (4A5BCC3B) fffff880`03dc2000 fffff880`03de9060 OA001Ufd OA001Ufd.sys Fri Mar 06 02:33:57 2009 (49B0D1E5) fffff880`019a7000 fffff880`019f5160 OA001Vid OA001Vid.sys Sun Mar 08 20:56:25 2009 (49B46939) fffff880`02dcf000 fffff880`02df5000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`00fb8000 fffff880`00fcd000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00f78000 fffff880`00fab000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00de3000 fffff880`00df3000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`013e3000 fffff880`013f4000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`09e00000 fffff880`09ea6000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`0512b000 fffff880`05168000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00c55000 fffff880`00c69000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`04800000 fffff880`04824000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`10b1d000 fffff880`10b38000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`10b38000 fffff880`10b59000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`10b59000 fffff880`10b73000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`02c54000 fffff880`02ca5000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`043f4000 fffff880`043ff000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA) fffff880`010d1000 fffff880`010da000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`010da000 fffff880`010e3000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`011f2000 fffff880`011fb000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`018d2000 fffff880`0190c000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`03cea000 fffff880`03d00000 rimmpx64 rimmpx64.sys Thu Jun 25 04:04:18 2009 (4A432F82) fffff880`03d00000 fffff880`03d17000 rimspx64 rimspx64.sys Thu Jun 25 03:13:43 2009 (4A4323A7) fffff880`03d17000 fffff880`03d6e000 rixdpx64 rixdpx64.sys Thu Jun 25 03:38:50 2009 (4A43298A) fffff880`09962000 fffff880`0997a000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`03cca000 fffff880`03cea000 sdbus sdbus.sys Fri Oct 09 22:41:20 2009 (4ACFF450) fffff880`09ea6000 fffff880`09eb1000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`0a6da000 fffff880`0a791000 Sftfslh Sftfslh.sys Wed Dec 02 19:55:48 2009 (4B170C94) fffff880`0a791000 fffff880`0a7de000 Sftplaylh Sftplaylh.sys Wed Dec 02 19:55:40 2009 (4B170C8C) fffff880`0a6a7000 fffff880`0a6b2000 Sftredirlh Sftredirlh.sys Wed Dec 02 19:55:52 2009 (4B170C98) fffff880`050a1000 fffff880`050ac000 Sftvollh Sftvollh.sys Wed Dec 02 19:55:23 2009 (4B170C7B) fffff880`018ca000 fffff880`018d2000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`0b8d8000 fffff880`0b949000 spsys spsys.sys Mon May 11 13:20:58 2009 (4A085E7A) fffff880`09f5f000 fffff880`09ff5000 srv srv.sys Mon Jun 21 23:21:11 2010 (4C202C27) fffff880`0a63f000 fffff880`0a6a7000 srv2 srv2.sys Mon Jun 21 23:20:47 2010 (4C202C0F) fffff880`0a600000 fffff880`0a62d000 srvnet srvnet.sys Mon Jun 21 23:20:32 2010 (4C202C00) fffff880`01125000 fffff880`01187000 storport storport.sys Mon Jul 13 20:01:18 2009 (4A5BCACE) fffff880`04bcb000 fffff880`04bdbd00 STREAM STREAM.SYS Mon Jul 13 20:06:18 2009 (4A5BCBFA) fffff880`050ac000 fffff880`0512b000 stwrt64 stwrt64.sys Fri Feb 26 03:07:58 2010 (4B87815E) fffff880`04824000 fffff880`04825480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`03a00000 fffff880`03a4b000 SynTP SynTP.sys Mon Aug 24 13:37:05 2009 (4A92CFC1) fffff880`043e7000 fffff880`043f4000 tap0901 tap0901.sys Thu Aug 19 18:07:59 2010 (4C6DAB3F) fffff880`01602000 fffff880`017ff000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`0a62d000 fffff880`0a63f000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`02cea000 fffff880`02cf7000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`02ccc000 fffff880`02cea000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`02c40000 fffff880`02c54000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`005a0000 fffff960`005aa000 TSDDD TSDDD.dll Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`03b4f000 fffff880`03b75000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`10bb6000 fffff880`10bc8000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`05084000 fffff880`050a1000 usbccgp usbccgp.sys Mon Jul 13 20:06:45 2009 (4A5BCC15) fffff880`03a4b000 fffff880`03a4cf00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`03c57000 fffff880`03c68000 usbehci usbehci.sys Fri Dec 04 02:26:02 2009 (4B18B98A) fffff880`0fe00000 fffff880`0fe5a000 usbhub usbhub.sys Fri Dec 04 02:26:39 2009 (4B18B9AF) fffff880`03a6c000 fffff880`03a77000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`03c01000 fffff880`03c57000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`00fab000 fffff880`00fb8000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`01485000 fffff880`01493000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`01200000 fffff880`01225000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`01475000 fffff880`01485000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E) fffff880`00fe2000 fffff880`00ff7000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00d87000 fffff880`00de3000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`0187e000 fffff880`018ca000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`04b19000 fffff880`04b26000 vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39) fffff880`02c00000 fffff880`02c16000 vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A) fffff880`0997c000 fffff880`09986000 vwifimp vwifimp.sys Mon Jul 13 20:07:28 2009 (4A5BCC40) fffff880`02c25000 fffff880`02c40000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`01493000 fffff880`014a3000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00e5b000 fffff880`00eff000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00eff000 fffff880`00f0e000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02dc6000 fffff880`02dcf000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`000a0000 fffff960`003af000 win32k win32k.sys Sat Jun 19 00:31:59 2010 (4C1C483F) fffff880`03b8b000 fffff880`03b94000 wmiacpi wmiacpi.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6) fffff880`00f65000 fffff880`00f6e000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`10bc8000 fffff880`10be9000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) fffff880`03bc1000 fffff880`03bf2000 WUDFRd WUDFRd.sys Mon Jul 13 20:06:06 2009 (4A5BCBEE) Unloaded modules: fffff880`019a7000 fffff880`019b5000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`019b5000 fffff880`019bf000 dump_storpor Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`019bf000 fffff880`019fe000 dump_nvstor6 Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01800000 fffff880`01813000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`10b73000 fffff880`10ba4000 WUDFRd.sys Timestamp: unavailable (00000000) Checksum: 00000000
Last edited by CarlTR6; 27 Sep 2010 at 14:52.
Quote