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.

Explorer Crash on RMB

Discussion in 'Windows XP' started by paulbristow, 2004/07/25.

Thread Status:
Not open for further replies.
Page 1 of 2
  1. 2004/07/25
    paulbristow

    paulbristow Well-Known Member Thread Starter

    Joined:
    2002/01/11
    Messages:
    246
    Likes Received:
    0
    Whenever I use the RMB (Right Mouse Button) on a system drive I get a crash, the type that asks you to send a report to Microsoft, I have tried the following:

    sfc /scannow
    qfecheck /v (checks windows hotfixes)

    I have also incuded below the error report:

    <?xml version= "1.0" encoding= "UTF-16 "?>
    <DATABASE>
    <EXE NAME= "SYSTEM INFO" FILTER= "GRABMI_FILTER_SYSTEM ">
    <MATCHING_FILE NAME= "advapi32.dll" SIZE= "558080" CHECKSUM= "0x7B6E5DDA" BIN_FILE_VERSION= "5.1.2600.1106" BIN_PRODUCT_VERSION= "5.1.2600.1106" PRODUCT_VERSION= "5.1.2600.1106" FILE_DESCRIPTION= "Advanced Windows 32 Base API" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "5.1.2600.1106 (xpsp1.020828-1920)" ORIGINAL_FILENAME= "advapi32.dll" INTERNAL_NAME= "advapi32.dll" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x9315E" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "5.1.2600.1106" UPTO_BIN_PRODUCT_VERSION= "5.1.2600.1106" LINK_DATE= "08/29/2002 10:40:40" UPTO_LINK_DATE= "08/29/2002 10:40:40" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "gdi32.dll" SIZE= "257536" CHECKSUM= "0xB0D6141C" BIN_FILE_VERSION= "5.1.2600.1346" BIN_PRODUCT_VERSION= "5.1.2600.1346" PRODUCT_VERSION= "5.1.2600.1346" FILE_DESCRIPTION= "GDI Client DLL" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "5.1.2600.1346 (xpsp2.040109-1800)" ORIGINAL_FILENAME= "gdi32" INTERNAL_NAME= "gdi32" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x4CFC1" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "5.1.2600.1346" UPTO_BIN_PRODUCT_VERSION= "5.1.2600.1346" LINK_DATE= "03/30/2004 01:48:36" UPTO_LINK_DATE= "03/30/2004 01:48:36" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "kernel32.dll" SIZE= "930304" CHECKSUM= "0xCBCCF8A9" BIN_FILE_VERSION= "5.1.2600.1106" BIN_PRODUCT_VERSION= "5.1.2600.1106" PRODUCT_VERSION= "5.1.2600.1106" FILE_DESCRIPTION= "Windows NT BASE API Client DLL" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "5.1.2600.1106 (xpsp1.020828-1920)" ORIGINAL_FILENAME= "kernel32" INTERNAL_NAME= "kernel32" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0xE7ED3" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "5.1.2600.1106" UPTO_BIN_PRODUCT_VERSION= "5.1.2600.1106" LINK_DATE= "08/29/2002 10:40:40" UPTO_LINK_DATE= "08/29/2002 10:40:40" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "ntdll.dll" SIZE= "654336" CHECKSUM= "0xC568C00F" BIN_FILE_VERSION= "5.1.2600.1217" BIN_PRODUCT_VERSION= "5.1.2600.1217" PRODUCT_VERSION= "5.1.2600.1217" FILE_DESCRIPTION= "NT Layer DLL" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "5.1.2600.1217 (xpsp2.030429-2131)" ORIGINAL_FILENAME= "ntdll.dll" INTERNAL_NAME= "ntdll.dll" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0xA5841" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "5.1.2600.1217" UPTO_BIN_PRODUCT_VERSION= "5.1.2600.1217" LINK_DATE= "05/01/2003 23:56:10" UPTO_LINK_DATE= "05/01/2003 23:56:10" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "ole32.dll" SIZE= "1183744" CHECKSUM= "0x7BA6A54E" BIN_FILE_VERSION= "5.1.2600.1362" BIN_PRODUCT_VERSION= "5.1.2600.1362" PRODUCT_VERSION= "5.1.2600.1362" FILE_DESCRIPTION= "Microsoft OLE for Windows" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "5.1.2600.1362 (xpsp2.040109-1800)" ORIGINAL_FILENAME= "OLE32.DLL" INTERNAL_NAME= "OLE32.DLL" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x12ED04" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "5.1.2600.1362" UPTO_BIN_PRODUCT_VERSION= "5.1.2600.1362" LINK_DATE= "03/06/2004 02:16:11" UPTO_LINK_DATE= "03/06/2004 02:16:11" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "oleaut32.dll" SIZE= "569344" CHECKSUM= "0x276CFFB1" BIN_FILE_VERSION= "3.50.5016.0" BIN_PRODUCT_VERSION= "3.50.5016.0" PRODUCT_VERSION= "3.50.5016.0" FILE_DESCRIPTION= "Microsoft OLE 3.50 for Windows NT(TM) and Windows 95(TM) Operating Systems" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft OLE 3.50 for Windows NT(TM) and Windows 95(TM) Operating Systems" FILE_VERSION= "3.50.5016.0" INTERNAL_NAME= "OLEAUT32.DLL" LEGAL_COPYRIGHT= "Copyright © Microsoft Corp. 1993-1999." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x999AF" LINKER_VERSION= "0x0" UPTO_BIN_FILE_VERSION= "3.50.5016.0" UPTO_BIN_PRODUCT_VERSION= "3.50.5016.0" LINK_DATE= "08/29/2002 10:40:34" UPTO_LINK_DATE= "08/29/2002 10:40:34" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "shell32.dll" SIZE= "8350720" CHECKSUM= "0x93F88D32" BIN_FILE_VERSION= "6.0.2800.1556" BIN_PRODUCT_VERSION= "6.0.2800.1556" PRODUCT_VERSION= "6.00.2800.1556" FILE_DESCRIPTION= "Windows Shell Common Dll" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "6.00.2800.1556 (xpsp2_gdr.040517-1325)" ORIGINAL_FILENAME= "SHELL32.DLL" INTERNAL_NAME= "SHELL32" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x80069B" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "6.0.2800.1556" UPTO_BIN_PRODUCT_VERSION= "6.0.2800.1556" LINK_DATE= "06/10/2004 19:51:26" UPTO_LINK_DATE= "06/10/2004 19:51:26" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "user32.dll" SIZE= "560128" CHECKSUM= "0xA1CBF84" BIN_FILE_VERSION= "5.1.2600.1255" BIN_PRODUCT_VERSION= "5.1.2600.1255" PRODUCT_VERSION= "5.1.2600.1255" FILE_DESCRIPTION= "Windows XP USER API Client DLL" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "5.1.2600.1255 (xpsp2.030804-1745)" ORIGINAL_FILENAME= "user32" INTERNAL_NAME= "user32" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x8AFFF" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "5.1.2600.1255" UPTO_BIN_PRODUCT_VERSION= "5.1.2600.1255" LINK_DATE= "09/25/2003 16:49:01" UPTO_LINK_DATE= "09/25/2003 16:49:01" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "WININET.DLL" SIZE= "588288" CHECKSUM= "0x8E2417C3" BIN_FILE_VERSION= "6.0.2800.1405" BIN_PRODUCT_VERSION= "6.0.2800.1405" PRODUCT_VERSION= "6.00.2800.1405" FILE_DESCRIPTION= "Internet Extensions for Win32" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "6.00.2800.1405" ORIGINAL_FILENAME= "wininet.dll" INTERNAL_NAME= "wininet.dll" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0x974A2" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "6.0.2800.1405" UPTO_BIN_PRODUCT_VERSION= "6.0.2800.1405" LINK_DATE= "02/07/2004 02:05:03" UPTO_LINK_DATE= "02/07/2004 02:05:03" VER_LANGUAGE= "English (United States) [0x409]" />
    <MATCHING_FILE NAME= "winsock.dll" SIZE= "2864" CHECKSUM= "0x73AE8088" BIN_FILE_VERSION= "3.10.0.103" BIN_PRODUCT_VERSION= "3.10.0.103" PRODUCT_VERSION= "3.10" FILE_DESCRIPTION= "Windows Socket 16-Bit DLL" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows(TM) Operating System" FILE_VERSION= "3.10" ORIGINAL_FILENAME= "WINSOCK.DLL" INTERNAL_NAME= "WINSOCK" LEGAL_COPYRIGHT= "Copyright © Microsoft Corp. 1981-1996" VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x10001" VERFILETYPE= "0x2" MODULE_TYPE= "WIN16" S16BIT_DESCRIPTION= "BSD Socket API for Windows" S16BIT_MODULE_NAME= "WINSOCK" UPTO_BIN_FILE_VERSION= "3.10.0.103" UPTO_BIN_PRODUCT_VERSION= "3.10.0.103" VER_LANGUAGE= "English (United States) [0x409]" />
    </EXE>
    <EXE NAME= "ntdll.dll" FILTER= "GRABMI_FILTER_THISFILEONLY ">
    <MATCHING_FILE NAME= "ntdll.dll" SIZE= "654336" CHECKSUM= "0xC568C00F" BIN_FILE_VERSION= "5.1.2600.1217" BIN_PRODUCT_VERSION= "5.1.2600.1217" PRODUCT_VERSION= "5.1.2600.1217" FILE_DESCRIPTION= "NT Layer DLL" COMPANY_NAME= "Microsoft Corporation" PRODUCT_NAME= "Microsoft® Windows® Operating System" FILE_VERSION= "5.1.2600.1217 (xpsp2.030429-2131)" ORIGINAL_FILENAME= "ntdll.dll" INTERNAL_NAME= "ntdll.dll" LEGAL_COPYRIGHT= "© Microsoft Corporation. All rights reserved." VERFILEDATEHI= "0x0" VERFILEDATELO= "0x0" VERFILEOS= "0x40004" VERFILETYPE= "0x2" MODULE_TYPE= "WIN32" PE_CHECKSUM= "0xA5841" LINKER_VERSION= "0x50001" UPTO_BIN_FILE_VERSION= "5.1.2600.1217" UPTO_BIN_PRODUCT_VERSION= "5.1.2600.1217" LINK_DATE= "05/01/2003 23:56:10" UPTO_LINK_DATE= "05/01/2003 23:56:10" VER_LANGUAGE= "English (United States) [0x409]" />
    </EXE>
    </DATABASE>

    I anybody can make sense of this I would be grateful for a fix ?

    Paul
     
    paulbristow,
    #1
  2. 2004/07/25
    LDTate

    LDTate Inactive

    Joined:
    2004/06/29
    Messages:
    284
    Likes Received:
    0
    LDTate,
    #2


  3. to hide this advert.

  4. 2004/07/25
    paulbristow

    paulbristow Well-Known Member Thread Starter

    Joined:
    2002/01/11
    Messages:
    246
    Likes Received:
    0
    same issue it seems but not a double post

    Paul
     
    paulbristow,
    #3
  5. 2004/07/25
    LDTate

    LDTate Inactive

    Joined:
    2004/06/29
    Messages:
    284
    Likes Received:
    0
    Third one like this in last couple days! Have you tried a AV scan, AdAware and Spybot? Maybe the start of some new virus going around :eek:
     
    LDTate,
    #4
  6. 2004/07/25
    paulbristow

    paulbristow Well-Known Member Thread Starter

    Joined:
    2002/01/11
    Messages:
    246
    Likes Received:
    0
    Yes, checked for AdAware and Virus all okay

    Paul
     
    paulbristow,
    #5
  7. 2004/07/25
    LDTate

    LDTate Inactive

    Joined:
    2004/06/29
    Messages:
    284
    Likes Received:
    0
    You might want to do a HijackThis log and have someone experienced with the logs look at it.
    Was the AV scan you did online? If not you might want to use the link.
    HouseCall
     
    LDTate,
    #6
  8. 2004/07/25
    paulbristow

    paulbristow Well-Known Member Thread Starter

    Joined:
    2002/01/11
    Messages:
    246
    Likes Received:
    0
    Used my McAfee Virus Scan I also have a McAffee Firewall, so my Explorer issues are not AdAware or Virus related

    Paul
     
    paulbristow,
    #7
  9. 2004/07/25
    paulbristow

    paulbristow Well-Known Member Thread Starter

    Joined:
    2002/01/11
    Messages:
    246
    Likes Received:
    0
    paulbristow,
    #8
  10. 2004/07/25
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Have you tried another mouse? uninstalled/reinstalled mouse software?
     
    PeteC,
    #9
  11. 2004/07/25
    paulbristow

    paulbristow Well-Known Member Thread Starter

    Joined:
    2002/01/11
    Messages:
    246
    Likes Received:
    0
    Could be an idea as I have recently installed a Microsoft Keyboard and Mouse the only thing is in device manager it stills shows an HP keyboard (HP PS2 Keyboard (2k-3)) and if I update the selection to show Microsoft from HP by updating the driver some of the the keys do not work (ctrl and alt keys) and I thought I had cracked it ..........

    Uninstalled the HP keyboard before installing Microsoft (well I thought I had until now) it looks like I need to look in this area, what makes you think it is the mouse drivers?

    Paul
     
    paulbristow,
    #10
  12. 2004/07/25
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Standard practice - any hardware problem - uninstall thro' Device Manager, reboot & let Windows find it again. If specific drivers/software are involved - uninstall/reinstall. For you - Intellipoint?
     
    PeteC,
    #11
  13. 2004/07/25
    JoeHobart

    JoeHobart Inactive Alumni

    Joined:
    2004/05/19
    Messages:
    919
    Likes Received:
    1
    I beleive that you are crashing due to a misbehaving shell extension (a programmer can register something that gets called every time you RMB), either causing heap corruption, or just outright running bad code. We should be able to tell from a user.dmp what the malfunctioning component is.

    In order to determine whats blowing up, i need you to collect the user dump from a crash and run this stuff

    Its possible that i will need some extra data beyond that, so please copy the dump to a safe place to run followup tests on.

    Also, seems to be a rash of corrupted files going around. have you tried an SFC /scannow?
     
    Last edited: 2004/07/25
    JoeHobart,
    #12
  14. 2004/07/26
    paulbristow

    paulbristow Well-Known Member Thread Starter

    Joined:
    2002/01/11
    Messages:
    246
    Likes Received:
    0
    Thank you to everyone that contributed to this post.

    I have managed (hopefully) to cure the explorer problem, it was my new keyboard (Microsoft Elite Optical Desktop Set) that conflicted with some of the HP (Hewlet Packard) drivers, although I had uninstalled the HP keyboard every time I rebooted, the HP drivers were automaticaly re-installed but if I unticked the "PS2" in HLKM / Run using StatUp CPL (http://www.mlin.net/) the conflict went away.

    My computer is brand new (1Gb of memory, Pentinum4 3 GHz, 200 GB hard drive) and as it is an OEM machine it does make fault finding the easiest of tasks.

    Thanks again BBS :)
    Paul
     
    paulbristow,
    #13
  15. 2004/07/26
    paulbristow

    paulbristow Well-Known Member Thread Starter

    Joined:
    2002/01/11
    Messages:
    246
    Likes Received:
    0
    Guess what? its back a whole morning of no trouble then explorer crash, trying the Dr Watson route "I will be back "

    Paul
     
    paulbristow,
    #14
  16. 2004/07/26
    paulbristow

    paulbristow Well-Known Member Thread Starter

    Joined:
    2002/01/11
    Messages:
    246
    Likes Received:
    0
    Joe

    Carried out your instructions and the results are as follows:

    Opened log file 'c:\debug.txt'

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


    Loading Dump File [c:\documents and settings\all users\application data\microsoft\dr watson\user.dmp]
    User Mini Dump File: Only registers, stack and portions of memory are available

    Comment: 'Dr. Watson generated MiniDump'
    Windows XP Version 2600 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: SingleUserTS Personal
    Debug session time: Mon Jul 26 14:24:42 2004
    System Uptime: not available
    Process Uptime: 0 days 0:03:42.000
    Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    .........................................................................................................................
    (654.c34): Access violation - code c0000005 (!!! second chance !!!)
    eax=01720bf8 ebx=00000003 ecx=00c62eec edx=00000003 esi=00000000 edi=00177f80
    eip=77416983 esp=00f4edf8 ebp=00f4ee14 iopl=0 nv up ei pl zr na po nc
    cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246


    Does not mean a lot to me! any chance of a cipher into real words

    Paul
     
    paulbristow,
    #15
  17. 2004/07/26
    JoeHobart

    JoeHobart Inactive Alumni

    Joined:
    2004/05/19
    Messages:
    919
    Likes Received:
    1
    Ahh, a minidump
    Code:
    kd -y SRV*c:\symbols*http://msdl.microsoft.com/download/symbols  -i c:\winnt;c:\winnt\system32;c:\winnt\system32\drivers -z c:\winnt\minidump\Mini071304-04.dmp
    NO SPACES in system32\drivers

    rerun the command to look like that. Please paste the entire spew from the script. its all important.
     
    JoeHobart,
    #16
  18. 2004/07/26
    paulbristow

    paulbristow Well-Known Member Thread Starter

    Joined:
    2002/01/11
    Messages:
    246
    Likes Received:
    0
    I tried the information you sent as used as STEP2 as per original directions but will not go as "kd not reconised as an internal or external command "
    what should I put in for STEP2?

    Paul
     
    paulbristow,
    #17
  19. 2004/07/26
    JoeHobart

    JoeHobart Inactive Alumni

    Joined:
    2004/05/19
    Messages:
    919
    Likes Received:
    1
    the above is a modified Step5. everything else will remain the same.
     
    JoeHobart,
    #18
  20. 2004/07/26
    In_A_Rut

    In_A_Rut Inactive

    Joined:
    2004/07/25
    Messages:
    11
    Likes Received:
    0
    well i'm having the exact same problem, even after reformatting my drives grrrr. could this be some kind of new virus?
     
    In_A_Rut,
    #19
  21. 2004/07/26
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,315
    Likes Received:
    252
    There is a "known" issue (known to microsoft that is) with right clicking. I'll see if I can find it again when I have the time. Can't remember if it's a "call us we've got a patch just for you" or a "so so very sorry" type solution. It's in the MS knowledgebase...
     
    Steve R Jones,
    #20
Page 1 of 2
Thread Status:
Not open for further replies.

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.
    Accept Learn More...