BSOD - Computer shutting down

Discussion in 'Software' started by mlydell, Feb 12, 2009.

  1. mlydell

    mlydell Private First Class

    My computer started running slow recently and then it started shutting down on me. When it restarts I get a message that Windows has recovered from a serious error.

    Today I got a Driver_Not_Less_Or_Equal error.

    Below is what WinDbg generated.

    Any thoughts and help would be appreciated. One thought I had - am I running too many USB devices? I have all the ports used as well as a hub from one that goes to 4 other devices.

    I also have a lot of drives attached. (3 internal, 1 external) a 4 bay memory card reader, a webcam. I also installed a 1GB LAN card. Not sure if I needed to do something to the old one - I just disabled it in the network settings.

    The reason I asked is I unplugged ALL the usb devices except for the keyboard/mouse and it seems to be running smoother, but it's hard to tell. The BSOD always comes out of nowhere...

    If there is another type of report I should run let me know!

    This is my biz computer and I need to get it up and running where I can depend on it again...

    =======================================

    Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini021209-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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_gdr.080814-1236
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Thu Feb 12 08:18:28.921 2009 (GMT-8)
    System Uptime: 0 days 14:14:09.522
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................................
    Loading User Symbols
    Loading unloaded module list
    ................................................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {2c, 2, 0, b6683d7f}

    Unable to load image sptd.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for sptd.sys
    Probably caused by : sptd.sys ( sptd+11d54 )

    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: 0000002c, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: b6683d7f, address which referenced memory

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


    READ_ADDRESS: 0000002c

    CURRENT_IRQL: 2

    FAULTING_IP:
    USBPORT!USBPORT_CompleteTransfer+1d
    b6683d7f 8b4e2c mov ecx,dword ptr [esi+2Ch]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: Idle

    LAST_CONTROL_TRANSFER: from b6684d47 to b6683d7f

    STACK_TEXT:
    805512fc b6684d47 88c23200 00000000 8a6647d8 USBPORT!USBPORT_CompleteTransfer+0x1d
    8055132c b6685944 026e6f44 8a6640e0 8a6640e0 USBPORT!USBPORT_DoneTransfer+0x137
    80551364 b668713a 8a664028 80546acc 8a664230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
    80551390 b669524b 8a664028 80546acc 8a664028 USBPORT!USBPORT_DpcWorker+0x224
    805513cc b66953c2 8a664028 00000001 8a6d452c USBPORT!USBPORT_IsrDpcWorker+0x38f
    805513e8 ba6b8d54 8a66464c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
    WARNING: Stack unwind information not available. Following frames may be wrong.
    80551428 80545e7f 8a66464c 8a664028 00000000 sptd+0x11d54
    80551450 80545d64 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
    80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    sptd+11d54
    ba6b8d54 ?? ???

    SYMBOL_STACK_INDEX: 6

    SYMBOL_NAME: sptd+11d54

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: sptd

    IMAGE_NAME: sptd.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 47cf3bb9

    FAILURE_BUCKET_ID: 0xD1_sptd+11d54

    BUCKET_ID: 0xD1_sptd+11d54

    Followup: MachineOwner
    ---------
     
    mlydell, Feb 12, 2009
    #1
  2. mlydell

    mlydell Private First Class

    FOLLOW_UP:

    I used WinDbg to open up another dump file from today. It seems to have a different problem, but I'm not an expert on reading these:

    ==========================================

    Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini021109-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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_gdr.080814-1236
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Wed Feb 11 16:38:58.308 2009 (GMT-8)
    System Uptime: 0 days 8:35:25.600
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................................
    Loading User Symbols
    Loading unloaded module list
    ................................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck FE, {2, 8993b430, 88d493c0, 88fc25a8}

    *** WARNING: Unable to verify timestamp for hppausb0.sys
    *** ERROR: Module load completed but symbols could not be loaded for hppausb0.sys
    Probably caused by : hppausb0.sys ( hppausb0+3083 )

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

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

    BUGCODE_USB_DRIVER (fe)
    USB Driver bugcheck, first parameter is USB bugcheck code.
    Arguments:
    Arg1: 00000002, BAD_URB The USB client driver has submitted a URB that is
    still attached to another IRP still pending in the bus
    driver.
    Arg2: 8993b430, Address of pending IRP.
    Arg3: 88d493c0, Address of IRP passed in.
    Arg4: 88fc25a8, Address URB that caused the error.

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


    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xFE

    PROCESS_NAME: spoolsv.exe

    LAST_CONTROL_TRANSFER: from b83885a5 to 804f9f43

    STACK_TEXT:
    ab387670 b83885a5 000000fe 00000002 8993b430 nt!KeBugCheckEx+0x1b
    ab3876a0 b838e362 8a73a028 8a7047f8 586b6b66 USBPORT!USBPORT_FindUrbInIrpTable+0x115
    ab387708 b838f3c6 00d9e470 ffffffff 80546acc USBPORT!USBPORT_FlushPendingList+0x43a
    ab387738 b8396350 8a7508a8 ab387770 b8395f14 USBPORT!USBPORT_QueueTransferUrb+0x248
    ab387744 b8395f14 8a73a028 88d493c0 88fc25a8 USBPORT!USBPORT_AsyncTransfer+0x30
    ab387770 b839b088 8a62b618 8a73a028 00000090 USBPORT!USBPORT_ProcessURB+0x3f4
    ab387790 b83843d2 8a62b618 88d493c0 88d493c0 USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x7e
    ab3877b4 804ef19f 88d4949c 8a62b770 88fc25a8 USBPORT!USBPORT_Dispatch+0x148
    ab3877c4 b874059c ab3877ec b874482d 88d493c0 nt!IopfCallDriver+0x31
    ab3877cc b874482d 88d493c0 8a62b618 88d493c0 usbhub!USBH_PassIrp+0x18
    ab3877ec b87450ae 8a71bd50 88d493c0 88d493c0 usbhub!USBH_PdoUrbFilter+0xbd
    ab387808 b87425e4 88fc25a8 88d493c0 89f0a648 usbhub!USBH_PdoDispatch+0x202
    ab387818 804ef19f 89df8ba0 88d493c0 88fc25a8 usbhub!USBH_HubDispatch+0x48
    ab387828 babd3083 892b7a00 89f0a648 89f0a590 nt!IopfCallDriver+0x31
    WARNING: Stack unwind information not available. Following frames may be wrong.
    ab387860 804f12d7 891c7860 8904a500 00000000 hppausb0+0x3083
    ab387894 804ef19f 89f0a590 892b7a00 89f0a590 nt!IoBuildAsynchronousFsdRequest+0xd9
    ab3878b4 00000000 00000000 00000000 ab047800 nt!IopfCallDriver+0x31


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    hppausb0+3083
    babd3083 ?? ???

    SYMBOL_STACK_INDEX: e

    SYMBOL_NAME: hppausb0+3083

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: hppausb0

    IMAGE_NAME: hppausb0.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 3a64ced3

    FAILURE_BUCKET_ID: 0xFE_hppausb0+3083

    BUCKET_ID: 0xFE_hppausb0+3083

    Followup: MachineOwner
    ---------
     
    Last edited: Feb 12, 2009
    mlydell, Feb 12, 2009
    #2
  3. mlydell

    mlydell Private First Class

    POST UPDATE:

    MiniDump from a few days ago:

    ======================================

    Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini020809-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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp3_gdr.080814-1236
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Sun Feb 8 08:57:50.031 2009 (GMT-8)
    System Uptime: 3 days 20:17:04.750
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................................
    Loading User Symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {c, 1c, 0, 804fc4c5}

    Unable to load image 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+23c9 )

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

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000c, memory referenced
    Arg2: 0000001c, IRQL
    Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 804fc4c5, address which referenced memory

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


    READ_ADDRESS: 0000000c

    CURRENT_IRQL: 1c

    FAULTING_IP:
    nt!KeInsertQueueApc+3b
    804fc4c5 8b450c mov eax,dword ptr [ebp+0Ch]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: OneTouch.exe

    LAST_CONTROL_TRANSFER: from 804f17f6 to 804fc4c5

    STACK_TEXT:
    8bd6ebe0 804f17f6 88fa6c28 88d60028 00000000 nt!KeInsertQueueApc+0x3b
    8bd6ec14 b06df3c9 88d60028 8a6d4440 88fa6be8 nt!IopfCompleteRequest+0x1d8
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8bd6ec34 b06df412 8a70ece0 8a70edac 804ef19f mxopswd+0x23c9
    8bd6ec64 805807f7 8a70ece0 88fa6be8 88d60028 mxopswd+0x2412
    8bd6ed00 80579274 000001cc 00000000 00000000 nt!IopXxxControlFile+0x5c5
    8bd6ed34 8054162c 000001cc 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
    8bd6ed34 7c90e4f4 000001cc 00000000 00000000 nt!KiFastCallEntry+0xfc
    00eed54c 00000000 00000000 00000000 00000000 0x7c90e4f4


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    mxopswd+23c9
    b06df3c9 ?? ???

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: mxopswd+23c9

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: mxopswd

    IMAGE_NAME: mxopswd.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 42545d23

    FAILURE_BUCKET_ID: 0xA_mxopswd+23c9

    BUCKET_ID: 0xA_mxopswd+23c9

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

    1: kd> lmvm mxopswd
    start end module name
    b06dd000 b06e0c00 mxopswd T (no symbols)
    Loaded symbol image file: mxopswd.sys
    Image path: mxopswd.sys
    Image name: mxopswd.sys
    Timestamp: Wed Apr 06 15:05:23 2005 (42545D23)
    CheckSum: 0000EF57
    ImageSize: 00003C00
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
    1: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000c, memory referenced
    Arg2: 0000001c, IRQL
    Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 804fc4c5, address which referenced memory

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


    READ_ADDRESS: 0000000c

    CURRENT_IRQL: 1c

    FAULTING_IP:
    nt!KeInsertQueueApc+3b
    804fc4c5 8b450c mov eax,dword ptr [ebp+0Ch]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: OneTouch.exe

    LAST_CONTROL_TRANSFER: from 804f17f6 to 804fc4c5

    STACK_TEXT:
    8bd6ebe0 804f17f6 88fa6c28 88d60028 00000000 nt!KeInsertQueueApc+0x3b
    8bd6ec14 b06df3c9 88d60028 8a6d4440 88fa6be8 nt!IopfCompleteRequest+0x1d8
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8bd6ec34 b06df412 8a70ece0 8a70edac 804ef19f mxopswd+0x23c9
    8bd6ec64 805807f7 8a70ece0 88fa6be8 88d60028 mxopswd+0x2412
    8bd6ed00 80579274 000001cc 00000000 00000000 nt!IopXxxControlFile+0x5c5
    8bd6ed34 8054162c 000001cc 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
    8bd6ed34 7c90e4f4 000001cc 00000000 00000000 nt!KiFastCallEntry+0xfc
    00eed54c 00000000 00000000 00000000 00000000 0x7c90e4f4


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    mxopswd+23c9
    b06df3c9 ?? ???

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: mxopswd+23c9

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: mxopswd

    IMAGE_NAME: mxopswd.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 42545d23

    FAILURE_BUCKET_ID: 0xA_mxopswd+23c9

    BUCKET_ID: 0xA_mxopswd+23c9

    Followup: MachineOwner
    ---------
     
    mlydell, Feb 12, 2009
    #3
  4. plodr

    plodr MajorGeek Super Extraordinaire Moderator Staff Member

    I know very little about crash dumps but I look through (omitting most of the numbers) and look for anything that I can sort of understand. ;)

    First post: Probably caused by : sptd.sys
    has something to do with Daemon tools
    FAULTING_IP:
    USBPORT!USBPORT_CompleteTransfer+1d
    FOLLOWUP_IP:
    sptd+11d54

    Second post: Probably caused by : hppausb0.sys
    has to do with your HP printer
    FAULTING_IP:
    nt!KeInsertQueueApc+3b
    FOLLOWUP_IP:
    hppausb0+3083
    Arg1: 00000002, BAD_URB The USB client driver has submitted a URB that is
    still attached to another IRP still pending in the bus
    driver.

    Third post: Probably caused by : mxopswd.sys
    has to do with Maxtor hd and backup utility
    FAULTING_IP:
    nt!KeInsertQueueApc+3b
    FOLLOWUP_IP:
    mxopswd+23c9
    PROCESS_NAME: OneTouch.exe

    Do you have or did you ever have Daemon tools installed? It's my understanding that the program creates virtual drives. This uses up some of your drive letters. If your USB devices expect to be on a certain drive letter and Daemon is using it, maybe that's where the conflict comes in. It might also be that Daemon is using so many, combined with the card reader and hub that you run out of drive letters for things like your printer and external Maxtor with OneTouch backup.
     
    plodr, Feb 12, 2009
    #4
  5. mlydell

    mlydell Private First Class

    Thanks for getting back to me - I know so many people post, so I know how hard it is to take the time and read through all this stuff..

    I hacve a couple more questions now...

    Daemon Tools:
    I used to have that, but thought it was uninstalled. I do have a program called NoteBurner that lets me create a virtual drive to burn files to. AM I correct in assuming that anything like this is similar to Daemon? I don't use it that often, so I'll uninstall it.

    HP Printer:
    How do I clear this out?

    Maxtor:
    I just hooked up a Maxtor external drive. I installed their backup program, but will prob not be using it - I just need it to be storage, so I'll uninstall that.


    Any other thoughts?


     
    mlydell, Feb 13, 2009
    #5
  6. mlydell

    mlydell Private First Class

    The latest is that tonight Outlook "encountered a problem" and needed to close. The error signature said:

    AppName: outlook.exe AppVer: 11.0.8217.0 AppStamp:480f95d9
    ModName: msmapi32.dll ModVer: 11.0.8200.0 ModStamp:472f94b0
    fDebug: 0 Offset: 0002cd5c

    Is this connected to my other problems?
     
    mlydell, Feb 13, 2009
    #6
  7. plodr

    plodr MajorGeek Super Extraordinaire Moderator Staff Member

    It might help to run CCleaner. http://majorgeeks.com/download4191.html
    Make a restore point just in case something breaks. Note: CCleaner is very safe. I've run it on all my windows computers for many years but this is a slight chance that some time something will go wrong.
    When you run it, it will help to do three things:
    a) in the screen that first pops up Cleaner is selected. Click tha analyze button after making sue what you want cleaned in Internet Explorer, Windows Explorer and System is checked. Do not touch Advanced.
    Then click Run Cleaner. It will remove all those old huge log files, browser cache and other unnecessary item.
    b) Click next on the registry icon. I have everything checked here - I want a thorough cleaning. Click the scan for Issues button. It will work and find all the things in the registry that should no longer be there. Then click Fix selected issues. It will ask if you want to make a backup. Always select YES. That way if something goes wrong, it is very easy to put everything back in the registry.
    c)Click on Tools, then in the next column click on Startup. If you see anything in there that you do not think belongs, click the disable button. This is safer than deleting it. If you find out a week later that you do not need what you have disabled, you can always go back in and delete it.

    I know nothing about NoteBurner so I won't venture a guess until I have a chance to look at how it works.

    HP Printer with its USB problem might be fixed once the USB drive letters are worked out properly.
    Currently, when you click on your printer, where does it show it is located?

    Good idea to uninstall software you won't use. I have an external WesternDigital and I never installed the software because I use Acronis True Image to make images and TI can put my images on my external with no problem.

    Sorry, I can't tell from the few details what outlook.exe had a problem with. We know it wasn't a USB drive.
     
    plodr, Feb 13, 2009
    #7
  8. mlydell

    mlydell Private First Class

    Thanks! I ran CCleaner as suggested.

    As for finding out my printers location, I'm not sure what I'm looking for. Where do I find it's location? Are yo asking what port it's on?

    The port list is confusing - it looks like there are references to old printers, etc. I've deleted the ports that reference something no longer in use.

    my hp printer is on a port named DOT4_002. There is a port called DOT4_001 with the same printer name as the description but no printer attached. It won't let me delete that port.

    Do I need to clean these ports up and get the printer attached to something different in here?

    I noticed something else this morning as well. I have to LAN cards - the one that came with the computer which I don't use, and a 1GB card I installed last year.

    I noticed the regular 10/100 card was still enabled, so I tried to disable it today and the system told me that I couldn't disable it was something was still using it. Is this something to worry about?

    Thanks again.
     
    Last edited: Feb 14, 2009
    mlydell, Feb 14, 2009
    #8
  9. voodoo3rd

    voodoo3rd Corporal

    Whenever I come across a blue screening machine I normally run MEMTEST first as faulty memory can cause all sorts of problems, just burn the ISO file to disk and boot your machine from CDrom. It maybe a software related problem but if it is the memory at fault this will save you a lot of time. Also disable things like serial ports and parallel ports in the CMOS set-up if you don't use them as its pointless getting your OS to load up drivers that are not needed.
     
    voodoo3rd, Feb 14, 2009
    #9
  10. plodr

    plodr MajorGeek Super Extraordinaire Moderator Staff Member

    Go to start and open your printers folder. (In 2K, it is under the control panel folder). If you don't see it there, there is probably a printer icon in control panel. Is there more than your current printer listed? If so, delete the "extra" printers.

    I wasn't sure what a DOT port was so I did a little investigating and that is normal for HP multifunction devices connected by a USB port. So I think you are okay there.

    As for the LAN cards, open Device manager (rt-click My Computer, select Properties then the Hardware tab) and see what is listed under network adapters. You should be able to right click the unused card and select uninstall from the menu.
     
    plodr, Feb 14, 2009
    #10

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds