4 BSOD in a week please help

Hello VSellar.

All of your dumps are caused by the mxopswd.sys driver, which is the Maxtor OneTouch driver. This needs to be updated or removed.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\David\AppData\Local\Temp\Temp1_Dump-1.zip\Dump\062510-23743-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82e50000 PsLoadedModuleList = 0x82f98810
Debug session time: Fri Jun 25 07:25:50.651 2010 (UTC - 7:00)
System Uptime: 1 days 1:00:57.789
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {93c596e6, 2, 8, 93c596e6}

Unable to load image \SystemRoot\system32\DRIVERS\mxopswd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mxopswd.sys
*** ERROR: Module load completed but symbols could not be loaded for mxopswd.sys
Probably caused by : mxopswd.sys ( mxopswd+56e6 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 93c596e6, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 93c596e6, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from 82fb8718
Unable to read MiSystemVaType memory at 82f98160
 93c596e6 

CURRENT_IRQL:  2

FAULTING_IP: 
mxopswd+56e6
93c596e6 8bff            mov     edi,edi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  8078ad64 -- (.trap 0xffffffff8078ad64)
ErrCode = 00000010
eax=828de250 ebx=a11d8d48 ecx=0000000f edx=87cbf270 esi=828de030 edi=828edfe0
eip=93c596e6 esp=8078add8 ebp=8078adec iopl=0         nv up ei ng nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
mxopswd+0x56e6:
93c596e6 8bff            mov     edi,edi
Resetting default scope

LAST_CONTROL_TRANSFER:  from 93c596e6 to 82e9682b

FAILED_INSTRUCTION_ADDRESS: 
mxopswd+56e6
93c596e6 8bff            mov     edi,edi

STACK_TEXT:  
8078ad64 93c596e6 badb0d00 87cbf270 8922b6ad nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
8078add4 82e8c4bc 828de030 87cbf270 86a461b8 mxopswd+0x56e6
8078adec 893c85a4 8078ae70 00000000 8078ae08 nt!IofCallDriver+0x63
8078adfc 893d25ec 828de030 8078ae4c 82eba04d CLASSPNP!SubmitTransferPacket+0x103
8078ae08 82eba04d 86a46200 86a461b8 4fb89815 CLASSPNP!TransferPacketRetryTimerDpc+0xd
8078ae4c 82eb9ff1 82f79d20 8078af78 00000001 nt!KiProcessTimerDpcTable+0x50
8078af38 82eb9eae 82f79d20 8078af78 00000000 nt!KiProcessExpiredTimerList+0x101
8078afac 82eb820e 00581662 c15ac9ec 00000000 nt!KiTimerExpiration+0x25c
8078aff4 82eb79dc c15ac99c 00000000 00000000 nt!KiRetireDpcList+0xcb
8078aff8 c15ac99c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
82eb79dc 00000000 0000001a 00d6850f bb830000 0xc15ac99c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mxopswd+56e6
93c596e6 8bff            mov     edi,edi

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  mxopswd+56e6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mxopswd

IMAGE_NAME:  mxopswd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  459efd59

FAILURE_BUCKET_ID:  0xD1_CODE_AV_BAD_IP_mxopswd+56e6

BUCKET_ID:  0xD1_CODE_AV_BAD_IP_mxopswd+56e6

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

~Lordbob

EDIT: Jan beat me to it. Same conclusion, which is good.

VSellar said:

Any idea why I can't find Maxtor when I go to unistall it clicking on programs in the control panel?

There should be Maxtor something listed under Programs and Features.

Also, go to start menu, all programs, and find Maxtor folder there. Then use the uninstall shortcut.
If it is not there, go to C:\program files\Maxtor and look there.

~Lordbob