1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

BSOD and freezes

Discussion in 'Windows XP' started by Patonb, 2008/03/17.

  1. 2008/03/17
    Patonb

    Patonb Inactive Thread Starter

    Joined:
    2008/03/17
    Messages:
    32
    Likes Received:
    0
    Built my Rig in Dec, XP Pro SP2. Bout a week in I started having random BSOD when I relog onto the puter, after the screen saver kicks in. WinDbg says its KMW_Sys, which is the Kensington Mouse program.

    Reinstalled it a few times, and nothing.
    WinDbg isnow also giving
    usbehci.sys (usbehci ! EHCI_POLLActiveASyncEndpoint+37)

    And

    AswMon2.sys (asmon2+6a1e)

    It's crashed 25 times in bout 2 months with, with the first 15 being the kmw_sys, 7 being usbehci and 2 the aswmon, and 1 saying corrupt memmory.

    I just uninstalled avast to see if that helps. And i do have my mouse as usb.

    As I had 4G's of RAM in, I removed 2G's and ran it, but within a week it started again. Switched back the other 2G's in different slots, but that too id nothing.
    However, It has now also freezng when I use, IE7, Firefox or Explorer. Which is new since decreasint RAM. Sometimes is a 5 second freeze, but it also goes completely frooze.

    I tried a format and reinstall, but nope, didn't work... lost my minidumps too.

    I'm hoping someone can help me, I'm leaning towards a faulty MB.. which blows as it's 4mo old.

    Systems in my sig, but in addition, I was running a USB 2 hub connecting my external HD, but got rid of it and still no go. When I plug it directly into a usb port, the computer doesn't always recognized it. However my Lappy does recognize it.

    I can cause a crash if I run Tversity, utorrent, and a Voice command program using a USB mic.

    I'm hoping someone can help me out, I'm adding minidumps, 3 of them as the format nuked the others, and would appreciate someone looking at them....

    Thanks.

    Can't seem to add the minidumps.... Any suggestions how?

    Dumps can be found at my Tech-forums Post here.
     
    Last edited: 2008/03/17
  2. 2008/03/17
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    Patonb - Welcome to the Board :)

    You cannot make attachments unless you are a Contributing Member . However what we want you to do is debug the dumps and post the dump data here - instructions .....

    http://www.windowsbbs.com/showthread.php?t=33471

    There is a caveat ....
     

  3. to hide this advert.

  4. 2008/03/17
    Patonb

    Patonb Inactive Thread Starter

    Joined:
    2008/03/17
    Messages:
    32
    Likes Received:
    0
    log 1

    Thanks Pete.


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


    Loading Dump File [C:\WINDOWS\Minidump\Mini031208-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 XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Wed Mar 12 15:50:38.234 2008 (GMT-4)
    System Uptime: 0 days 4:27:20.225
    Loading Kernel Symbols
    ............................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck FE, {5, 89ae80e0, 10de036c, 8830ab00}

    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 : usbohci.sys ( usbohci!OHCI_PollIsoEndpoint+38 )

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

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

    BUGCODE_USB_DRIVER (fe)
    USB Driver bugcheck, first parameter is USB bugcheck code.
    Arguments:
    Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
    using a physical memory address that was not allocated by
    the USBport driver.
    Arg2: 89ae80e0, Device extension pointer of the host controller
    Arg3: 10de036c, PCI Vendor,Product id for the controller
    Arg4: 8830ab00, Pointer to Endpoint data structure

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




    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xFE

    PROCESS_NAME: Idle

    LAST_CONTROL_TRANSFER: from b9cf7cc3 to 804f9deb

    STACK_TEXT:
    8055028c b9cf7cc3 000000fe 00000005 89ae80e0 nt!KeBugCheckEx+0x1b
    805502ac b9d04516 89ae8028 00002fd0 b4fbe000 USBPORT!USBPORT_BugCheck+0x2d
    805502e8 babf0ba6 00000000 89ae89dc 8830ab00 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x126
    80550308 babf2bd4 89ae89dc 8830ab00 80550338 usbohci!OHCI_PollIsoEndpoint+0x38
    80550318 b9cf12ba 89ae89dc 8830ab00 80545d0c usbohci!OHCI_PollEndpoint+0x2a
    80550338 b9cf2578 026c6f50 89ae80e0 8830a988 USBPORT!USBPORT_PollEndpoint+0xe8
    80550360 b9cf5ed0 89ae8028 50457270 80545d0c USBPORT!USBPORT_CoreEndpointWorker+0x2be
    80550390 b9d03fb0 89ae8028 80545d0c 89ae8028 USBPORT!USBPORT_DpcWorker+0x18a
    805503cc b9d04128 89ae8028 00000001 89af152c USBPORT!USBPORT_IsrDpcWorker+0x37e
    805503e8 ba6bba9e 89ae864c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
    WARNING: Stack unwind information not available. Following frames may be wrong.
    80550428 805450bf 89ae864c 89ae8028 00000000 sptd+0x11a9e
    80550450 80544fa4 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
    80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    usbohci!OHCI_PollIsoEndpoint+38
    babf0ba6 ff7038 push dword ptr [eax+38h]

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: usbohci!OHCI_PollIsoEndpoint+38

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: usbohci

    IMAGE_NAME: usbohci.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62

    FAILURE_BUCKET_ID: 0xFE_usbohci!OHCI_PollIsoEndpoint+38

    BUCKET_ID: 0xFE_usbohci!OHCI_PollIsoEndpoint+38

    Followup: MachineOwner
    ---------
     
  5. 2008/03/17
    Patonb

    Patonb Inactive Thread Starter

    Joined:
    2008/03/17
    Messages:
    32
    Likes Received:
    0
    log 2

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini031208-02.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 XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Wed Mar 12 16:17:13.156 2008 (GMT-4)
    System Uptime: 0 days 0:26:13.147
    Loading Kernel Symbols
    ............................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .............
    Unable to load image aswTdi.SYS, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for aswTdi.SYS
    *** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {fdf7fe07, 2, 0, baa3b234}

    Unable to load image NVENETFD.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for NVENETFD.sys
    *** ERROR: Module load completed but symbols could not be loaded for NVENETFD.sys
    *** WARNING: Unable to verify timestamp for NVNRM.SYS
    *** ERROR: Module load completed but symbols could not be loaded for NVNRM.SYS


    Probably caused by : aswTdi.SYS ( aswTdi+3234 )

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

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




    READ_ADDRESS: fdf7fe07

    CURRENT_IRQL: 2

    FAULTING_IP:
    aswTdi+3234
    baa3b234 8b5014 mov edx,dword ptr [eax+14h]

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: Idle

    LAST_CONTROL_TRANSFER: from b70ec733 to baa3b234

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8054ffa0 b70ec733 89c34ed8 88479628 00000e20 aswTdi+0x3234
    80550000 b70e13a2 88479628 00001850 89c089b8 tcpip!IndicateData+0x98
    80550088 b70deef5 89a72118 6801a8c0 aa578151 tcpip!TCPRcv+0xb55
    805500e8 b70deb19 00000020 89a72118 b70e1076 tcpip!DeliverToUser+0x18e
    80550164 b70de836 b711e4f0 89a72118 8888ba18 tcpip!DeliverToUserEx+0x95e
    8055021c b70dd922 89a72118 8888ba2c 00000036 tcpip!IPRcvPacket+0x6cb
    8055025c b70dd84d 00000000 88922e68 8888ba0a tcpip!ARPRcvIndicationNew+0x149
    80550298 ba4fbf45 892a86d0 00000000 b9a83b40 tcpip!ARPRcvPacket+0x68
    805502ec b9a7e01d 0092c1e0 898f44c8 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x307
    80550300 b9a7e1b4 899d0a28 898f44c8 00000001 psched!PsFlushReceiveQueue+0x15
    80550324 b9a7e5f9 88c3cae8 00000000 899d0a28 psched!PsEnqueueReceivePacket+0xda
    8055033c ba4fbd40 88c3cae0 89b785bc 89b78000 psched!ClReceiveComplete+0x13
    8055038c ba9ed35c 0092c1e0 89b785bc 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4
    805503d4 b9ba0de0 00000001 89a58634 00000000 NVENETFD+0x535c
    80550410 b9ba35f4 b9c17170 ffdff000 8055b0a0 NVNRM+0xdde0
    80550428 805450bf 89a585e4 00000000 00000000 NVNRM+0x105f4
    80550450 80544fa4 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
    80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    aswTdi+3234
    baa3b234 8b5014 mov edx,dword ptr [eax+14h]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: aswTdi+3234

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: aswTdi

    IMAGE_NAME: aswTdi.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP: 47556986

    FAILURE_BUCKET_ID: 0xD1_aswTdi+3234

    BUCKET_ID: 0xD1_aswTdi+3234

    Followup: MachineOwner
    ---------
     
  6. 2008/03/17
    Patonb

    Patonb Inactive Thread Starter

    Joined:
    2008/03/17
    Messages:
    32
    Likes Received:
    0
    log 3

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini031208-03.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 XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Wed Mar 12 16:18:43.000 2008 (GMT-4)
    System Uptime: 0 days 0:00:29.984
    Loading Kernel Symbols
    .........................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck FE, {5, 89adf0e0, 10de036c, 895298a8}

    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 : usbohci.sys ( usbohci!OHCI_PollAsyncEndpoint+41 )

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

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

    BUGCODE_USB_DRIVER (fe)
    USB Driver bugcheck, first parameter is USB bugcheck code.
    Arguments:
    Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
    using a physical memory address that was not allocated by
    the USBport driver.
    Arg2: 89adf0e0, Device extension pointer of the host controller
    Arg3: 10de036c, PCI Vendor,Product id for the controller
    Arg4: 895298a8, Pointer to Endpoint data structure

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




    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xFE

    PROCESS_NAME: services.exe

    LAST_CONTROL_TRANSFER: from b9cf7cc3 to 804f9deb

    STACK_TEXT:
    baccbe24 b9cf7cc3 000000fe 00000005 89adf0e0 nt!KeBugCheckEx+0x1b
    baccbe44 b9d04516 89adf028 00001fd0 88652000 USBPORT!USBPORT_BugCheck+0x2d
    baccbe80 babf18f3 fffffff0 89adf9dc 895298a8 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x126
    baccbeac babf2bc9 89adf9dc 895298a8 baccbedc usbohci!OHCI_PollAsyncEndpoint+0x41
    baccbebc b9cf12ba 89adf9dc 895298a8 80545d0c usbohci!OHCI_PollEndpoint+0x1f
    baccbedc b9cf2578 026c6f50 89adf0e0 89529730 USBPORT!USBPORT_PollEndpoint+0xe8
    baccbf04 b9cf5ed0 89adf028 50457270 80545d0c USBPORT!USBPORT_CoreEndpointWorker+0x2be
    baccbf34 b9d03fb0 89adf028 80545d0c 89adf028 USBPORT!USBPORT_DpcWorker+0x18a
    baccbf70 b9d04128 89adf028 00000001 89ae552c USBPORT!USBPORT_IsrDpcWorker+0x37e
    baccbf8c ba6bba9e 89adf64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
    WARNING: Stack unwind information not available. Following frames may be wrong.
    baccbfcc 805450bf 89adf64c 89adf028 00000000 sptd+0x11a9e
    baccbff4 80544c2b b64bf8f8 00000000 00000000 nt!KiRetireDpcList+0x61
    baccbff8 b64bf8f8 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
    80544c2b 00000000 00000009 0081850f bb830000 0xb64bf8f8


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    usbohci!OHCI_PollAsyncEndpoint+41
    babf18f3 ff7038 push dword ptr [eax+38h]

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: usbohci!OHCI_PollAsyncEndpoint+41

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: usbohci

    IMAGE_NAME: usbohci.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62

    FAILURE_BUCKET_ID: 0xFE_usbohci!OHCI_PollAsyncEndpoint+41

    BUCKET_ID: 0xFE_usbohci!OHCI_PollAsyncEndpoint+41

    Followup: MachineOwner
    ---------
     
  7. 2008/03/17
    Patonb

    Patonb Inactive Thread Starter

    Joined:
    2008/03/17
    Messages:
    32
    Likes Received:
    0
    log 4

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini031708-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 XP Kernel Version 2600 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Mon Mar 17 19:22:05.437 2008 (GMT-4)
    System Uptime: 0 days 2:00:11.430
    Loading Kernel Symbols
    .......................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck FE, {5, 89afa0e0, 10de036c, 892f3820}

    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 : usbohci.sys ( usbohci!OHCI_PollAsyncEndpoint+41 )

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

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

    BUGCODE_USB_DRIVER (fe)
    USB Driver bugcheck, first parameter is USB bugcheck code.
    Arguments:
    Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
    using a physical memory address that was not allocated by
    the USBport driver.
    Arg2: 89afa0e0, Device extension pointer of the host controller
    Arg3: 10de036c, PCI Vendor,Product id for the controller
    Arg4: 892f3820, Pointer to Endpoint data structure

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




    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xFE

    PROCESS_NAME: Idle

    LAST_CONTROL_TRANSFER: from b9869cc3 to 804f9deb

    STACK_TEXT:
    80550280 b9869cc3 000000fe 00000005 89afa0e0 nt!KeBugCheckEx+0x1b
    805502a0 b9876516 89afa028 00001fd0 885b6000 USBPORT!USBPORT_BugCheck+0x2d
    805502dc bac618f3 fffffff0 89afa9dc 892f3820 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x126
    80550308 bac62bc9 89afa9dc 892f3820 80550338 usbohci!OHCI_PollAsyncEndpoint+0x41
    80550318 b98632ba 89afa9dc 892f3820 80545d0c usbohci!OHCI_PollEndpoint+0x1f
    80550338 b9864578 026c6f50 89afa0e0 892f36a8 USBPORT!USBPORT_PollEndpoint+0xe8
    80550360 b9867ed0 89afa028 50457270 80545d0c USBPORT!USBPORT_CoreEndpointWorker+0x2be
    80550390 b9875fb0 89afa028 80545d0c 89afa028 USBPORT!USBPORT_DpcWorker+0x18a
    805503cc b9876128 89afa028 00000001 89aff52c USBPORT!USBPORT_IsrDpcWorker+0x37e
    805503e8 ba6bba9e 89afa64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
    WARNING: Stack unwind information not available. Following frames may be wrong.
    80550428 805450bf 89afa64c 89afa028 00000000 sptd+0x11a9e
    80550450 80544fa4 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
    80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    usbohci!OHCI_PollAsyncEndpoint+41
    bac618f3 ff7038 push dword ptr [eax+38h]

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: usbohci!OHCI_PollAsyncEndpoint+41

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: usbohci

    IMAGE_NAME: usbohci.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62

    FAILURE_BUCKET_ID: 0xFE_usbohci!OHCI_PollAsyncEndpoint+41

    BUCKET_ID: 0xFE_usbohci!OHCI_PollAsyncEndpoint+41

    Followup: MachineOwner
    ---------
     
  8. 2008/03/18
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    Log #2 the source of the BSOD would appear to be the Avast filter driver ....

    Probably caused by : aswTdi.SYS ( aswTdi+3234 )


    The other 3 logs show usbohci.sys - OHCI USB Miniport Driver as the culprit as you have noted.

    The problem is clearly USB related - you have removed some USB devices and found problems when connecting others.

    The fact that you have formatted and reinstalled without any inprovement does suggest that the problem is hardware related.

    Did you load the chipset drivers after the reformat? Check for updates at the mobo manufacturer's web site.

    While you are there see if there is a BIOS update, but only install if it points to resolving your specific problem.

    Have you removed all USB controllers and Root Hubs through Device Manager and rebooted to re-install them?
     
  9. 2008/03/18
    Patonb

    Patonb Inactive Thread Starter

    Joined:
    2008/03/17
    Messages:
    32
    Likes Received:
    0
    Thanks for looking at those.

    As for the Avast thing, I had uninstalled Avast, and the issue just changed to the usb problem.

    As I breifly noted in my first post, I had a minihub connecting my USB external and web cam. I removed that, and directly connected the external to my tower, and it no longer always recognized. Also, the blue light has turned red.. Can't find out what that means though. It's a PHR-100su, it has no fan, but it is used as a storage drive mainly for music and video.

    I know all drivers are updated, and I think so is the BIOS.

    Removed the external and will run it like that and see what happens.

    Thanks again for looking at the dumps.

    ***********EDIT**********

    Well lasted bout 4 hours. It's not crashing, but total lock up, requireing a manual renboot.

    All thats now plugged in, are keyboard, mouse (kensingten trackball) and a headset.

    Is it possible for the usb on the board to be buggered, with no Windows warnnings?

    Anyway to test my motherboard? Freak'n thing is starten to P me off.
     
    Last edited: 2008/03/18
  10. 2008/03/19
    Patonb

    Patonb Inactive Thread Starter

    Joined:
    2008/03/17
    Messages:
    32
    Likes Received:
    0
    Removed all USB devices, and have pluged my mouse and keyboard into the PS/2 ports, and so far so good.

    Is/could this be a defective USB/motherboard?

    thanks
     
  11. 2008/03/19
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    A strong possibility - as I posted earlier the problem was not resolved by a reformat and fresh install which tends to rule out software and this is backed up by the lack of problems running PS/2. If that situation continues it points to a problem with the motherboard (USB).

    If you now connect the external drive is it recognised?
     
  12. 2008/03/19
    Patonb

    Patonb Inactive Thread Starter

    Joined:
    2008/03/17
    Messages:
    32
    Likes Received:
    0
    Good question... I'll have to check later.

    However, When I fresh installed last, I had only my keyboard plugged in via USB, and my mouse PS/2, as one of the dumps pointed to its software, the problem was still happening.

    Ugh, hopefully i've found the cause.

    Thank you.
     
  13. 2008/03/28
    Patonb

    Patonb Inactive Thread Starter

    Joined:
    2008/03/17
    Messages:
    32
    Likes Received:
    0
    Just a week latrer update..

    Updated the BIOS, and it went bad... system woukldn't boot, BUT gave long repeated beeps... Yay memmory errors.

    Further reading pointed to.......... Get this......... Low voltage on my RAM.

    Pulled a stick, rebooted, got my BIOS, bumped my RAM voltage, and have been stable for a week.

    Turns out crucial tracer RAM needs high V's. As i never had played with it, never though of it.

    Anyway, thanks for the help.
     
  14. 2008/03/28
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    Good bit of sleuthing :) Thanks for the update - and fingers crossed!!
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.