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.

Resolved System has recovered from a serious error.

Discussion in 'Windows XP' started by Julian57, 2009/02/27.

Page 2 of 3
  1. 2009/04/06
    Julian57

    Julian57 Inactive Thread Starter

    Joined:
    2009/02/08
    Messages:
    75
    Likes Received:
    0
    Pete, I have to admit i´m getting lost. Have the last minidump located but am trying to figure out how to use the tool/tools. In particular the WinDbg:6.11.0001.404 x86
    Could you step by step get me going?
    Much appreciated.

    Jules.
     
    Julian57,
    #21
  2. 2009/04/06
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Jules

    From this page ..... http://www.windowsbbs.com/general-discussions/33471-dump-data-collection-tool-instructions.html

    Download and install the debugging tools from Microsoft - click on the 32 bit link.

    Download debugwiz.zip from the bottom of the page and unzip

    In Windows Explorer - Tools > Folder Options > View - Show hidden files & folders (necessary if the .dmp file is in Docs & Settings)

    Ensure that you are connected to the Internet

    Double click on debugwiz.exe - Window opens (screenshot)

    Use the browse button to navigate to the dump file - highlight > open

    Path of dump file is entered under 'Dump file to be analysed (screenshot)

    Click on Generate log - a DOS window opens followed by Log File Complete message box (screenshot) - click on OK

    When the DOS box exit the wizard - the log file is to be found in C:\
     

    Attached Files:

    PeteC,
    #22


  3. to hide this advert.

  4. 2009/04/11
    Julian57

    Julian57 Inactive Thread Starter

    Joined:
    2009/02/08
    Messages:
    75
    Likes Received:
    0
    I am getting a number of different responses while trying to locate the Dump File.
    Firstly, why am i unable to see the debug wiz. when it is unfolded succesfully?
    How to i get an up to date version of the mini dump file?
    How does the Debugger tool 6.11.0001.404 fit in to all this?
    Also when i locate a minidump file, how do i open it?
    Frustration is getting the better of me. Fancy a trip to DK?

    Jules.
     
    Julian57,
    #23
  5. 2009/04/12
    Julian57

    Julian57 Inactive Thread Starter

    Joined:
    2009/02/08
    Messages:
    75
    Likes Received:
    0
    When clicking on the Debugwiz. i only unpack it, no image as shown in your mail appears!
    Also the debugging tool has so many options i cannot see where i need to place the dumpfiles. Sorry if this is all elementary to you, i just don´t have the necessary nuerons anymore.

    Thanks, Jules.
     
    Julian57,
    #24
  6. 2009/04/14
    Julian57

    Julian57 Inactive Thread Starter

    Joined:
    2009/02/08
    Messages:
    75
    Likes Received:
    0
    "Symbols cannot be loaded" is one of the things mentioned on the minidump file.
    But how do i get your debug wizard to appear? Nothing i do seems to be able to find it.
    Thanks, Jules.
     
    Julian57,
    #25
  7. 2009/04/14
    Julian57

    Julian57 Inactive Thread Starter

    Joined:
    2009/02/08
    Messages:
    75
    Likes Received:
    0
    "The file you have chosen has an executable dump file, or crash dump file extension. "
    As you can see i have found it but now have this to contend with. Sorry about all this but have considered the possibility of other faults having an influence on proceedings. Are my thoughts unfounded?

    Jules.
     
    Julian57,
    #26
  8. 2009/04/16
    Julian57

    Julian57 Inactive Thread Starter

    Joined:
    2009/02/08
    Messages:
    75
    Likes Received:
    0
    Have both "memory" and "Minidump ". Tried to generate log, told where to find log file when DOS window exits. But i don´t get the DOS window?

    Jules.
     
    Julian57,
    #27
  9. 2009/04/16
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Just returned from a few days away over Easter - I'll review where you are and post back later today.
     
    PeteC,
    #28
  10. 2009/04/16
    Julian57

    Julian57 Inactive Thread Starter

    Joined:
    2009/02/08
    Messages:
    75
    Likes Received:
    0
    Thanks a lot. Hope your refreshed!

    Jules.l
     
    Julian57,
    #29
  11. 2009/04/16
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Please read my next post first

    I'm not sure what is going on at your end, but to work through your posts while I was away ......
    You downloaded a .zip file which unpacks to debugwiz.exe - you have that?

    Double clicking on debugwiz.exe opens the debugwiz dialogue as I posted in post #22 - is that not the case?
    If a dump file is created when the computer crashes or restarts the file is found in one of the locations given in Dump Data Collection Tool
    The wizard uses the tool to debug the dump file - from the start of a typical log .....
    I see that my version of the Debugging Tools is quite old 6.8.0004.0 X86 vs 6.11.0001.404 so I'll check out the later version.
    Browse to it using the Browse button in the Debugwiz dialogue - post #22
    Where do you see this - that message would appear in the log file. You have downloaded and installed the debugging tools from MS - Symbols are installed with those tools and you need to be connected to the internet while debugging to allow access to more symbols if required.
    The whole object of the wizard is to remove the need for such decisions - as I noted above use the Browse button in the Wizard dialogue to locate the dump file, highlight it and click on Open and the path will be inserted into the wizard. Then hit the generate log button.
    Not seen that before :confused:
    Strange - one thought - you may need to be logged on as Administrator - I am always - or the wizard/debugging tools may be corrupt. I would uninstall the debugging tools and start over with a fresh install.

    In the meantime feel free to email me a minidump - latest date please. Look in your PM for an email addy.

    I'll check out the latest version of the debugging tools to ensure that they work OK with the wizard.
     
    PeteC,
    #30
  12. 2009/04/16
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    OK - I have found the source of the problem ......

    Versions of the Debugging tools later than 6.8.0004.0 locate a registry key in a different location and the debug wizard does not see that the tools are installed.

    Please uninstall the Debugging Tools and download & install Debugging Tools 6.8.4.0 from the same location as before.

    Sorry about that - I'll see if Admin can get the wizard updated - it was originally written for us by a Microsoft 'code monkey' who is no longer on the BBS.
     
    PeteC,
    #31
  13. 2009/04/18
    Julian57

    Julian57 Inactive Thread Starter

    Joined:
    2009/02/08
    Messages:
    75
    Likes Received:
    0
    Started again using the older version of Debugwizard.
    All working as you stated, saw the log being generated in the DOS window.
    Located the minidump file but how to open it and copy to mail is a problem.
    Getting closer but have a feeling that something else is not right.

    "The file you have chosen has an executable dump file, or crash dump file extension ", as you mentioned this msg. is apparently not normal. Could this have an influence on proceedings?
    Thanks, Jules.
     
    Julian57,
    #32
  14. 2009/04/18
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    The debuglog (debuglog.txt) should be located here .....

    C:\debuglog.txt

    Is the log there? If so open it and copy/paste into a post here.
    Send the .dmp file as an attachment - you do not need to open it and indeed cannot outside of the debugging tools.
    When do you see this?
     
    PeteC,
    #33
  15. 2009/04/18
    Julian57

    Julian57 Inactive Thread Starter

    Joined:
    2009/02/08
    Messages:
    75
    Likes Received:
    0
    Dump Files.



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


    Loading Dump File [C:\WINDOWS\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
    Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 2600.xpsp_sp3_gdr.090206-1234
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
    Debug session time: Fri Apr 17 21:36:39.375 2009 (GMT+2)
    System Uptime: 0 days 0:01:15.953
    Loading Kernel Symbols
    ...........................................................................................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details
    Loading unloaded module list
    ..............................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {3fffebb0, ff, 1, 8984fbce}


    PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details

    PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details
    Probably caused by : ntkrnlpa.exe ( nt!KiTrap0E+233 )

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

    kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * 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: 3fffebb0, memory referenced
    Arg2: 000000ff, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 8984fbce, address which referenced memory

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


    PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details

    PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details

    WRITE_ADDRESS: 3fffebb0

    CURRENT_IRQL: ff

    FAULTING_IP:
    +ffffffff8984fbce
    8984fbce 89440444 mov dword ptr [esp+eax+44h],eax

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: backWeb-8876480

    TRAP_FRAME: b61f5ac8 -- (.trap 0xffffffffb61f5ac8)
    .trap 0xffffffffb61f5ac8
    ErrCode = 00000002
    eax=89e09030 ebx=b61f5c68 ecx=00000001 edx=00000000 esi=89ddb26c edi=89ddb008
    eip=8984fbce esp=b61f5b3c ebp=b61f5b3c iopl=0 nv up di ng nz ac pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010096
    8984fbce 89440444 mov dword ptr [esp+eax+44h],eax ss:0010:3fffebb0=????????
    .trap
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 8984fbce to 80540693

    STACK_TEXT:
    b61f5ac8 8984fbce badb0d00 00000000 00000000 nt!KiTrap0E+0x233
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b61f5b3c 00000000 88cf8da8 b61f5b6c e299f840 0x8984fbce


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiTrap0E+233
    80540693 f7457000000200 test dword ptr [ebp+70h],20000h

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!KiTrap0E+233

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlpa.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3

    FAILURE_BUCKET_ID: 0xD1_W_nt!KiTrap0E+233

    BUCKET_ID: 0xD1_W_nt!KiTrap0E+233

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

    eax=ffdff13c ebx=000000ff ecx=00000000 edx=00000000 esi=8984fbce edi=3fffebb0
    eip=80540693 esp=b61f5ab0 ebp=b61f5ac8 iopl=0 nv up ei ng nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
    nt!KiTrap0E+0x233:
    80540693 f7457000000200 test dword ptr [ebp+70h],20000h ss:0010:b61f5b38=00010096
    ChildEBP RetAddr Args to Child
    b61f5ac8 8984fbce badb0d00 00000000 00000000 nt!KiTrap0E+0x233 (FPO: [0,0] TrapFrame @ b61f5ac8)
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b61f5b3c 00000000 88cf8da8 b61f5b6c e299f840 0x8984fbce
    start end module name
    804d7000 806cf680 nt ntkrnlpa.exe Fri Feb 06 11:32:51 2009 (498C11D3)
    806d0000 806f0300 hal halaacpi.dll Sun Apr 13 20:31:27 2008 (4802517F)
    b645c000 b6470480 wdmaud wdmaud.sys Sun Apr 13 21:17:18 2008 (48025C3E)
    b668d000 b6690b20 aswRdr aswRdr.SYS Thu Feb 05 22:06:09 2009 (498B54C1)
    b68f9000 b694a880 srv srv.sys Thu Dec 11 11:57:07 2008 (4940F203)
    b6993000 b6996700 ubsbm ubsbm.sys Wed Apr 13 11:06:46 2005 (425CE126)
    b699b000 b69dba80 HTTP HTTP.sys Sun Apr 13 20:53:48 2008 (480256BC)
    b6af4000 b6b09500 aswMon2 aswMon2.SYS Thu Feb 05 03:41:46 2009 (498A51EA)
    b6b32000 b6b5e180 mrxdav mrxdav.sys Sun Apr 13 20:32:42 2008 (480251CA)
    b6b6f000 b6b71bc0 CdaC15BA CdaC15BA.SYS Mon Jul 01 10:46:43 2002 (3D2016F3)
    b6cf3000 b6cf6900 ndisuio ndisuio.sys Sun Apr 13 20:55:57 2008 (4802573D)
    b6d17000 b6d27200 Udfs Udfs.SYS Sun Apr 13 20:32:35 2008 (480251C3)
    b6d28000 b6d87380 BsUDF BsUDF.SYS Thu Jun 19 04:44:14 2003 (3EF1237E)
    b6e20000 b6e28e00 ubumapi ubumapi.sys Wed Apr 13 11:05:58 2005 (425CE0F6)
    b6f08000 b6f1f900 dump_atapi dump_atapi.sys Sun Apr 13 20:40:29 2008 (4802539D)
    b6f20000 b6f41000 aswSP aswSP.SYS Thu Feb 05 03:41:01 2009 (498A51BD)
    b7001000 b7070280 mrxsmb mrxsmb.sys Fri Oct 24 13:21:07 2008 (4901AFA3)
    b7071000 b709be80 rdbss rdbss.sys Sun Apr 13 21:28:38 2008 (48025EE6)
    b70c5000 b70ea500 ipnat ipnat.sys Sun Apr 13 20:57:10 2008 (48025786)
    b719d000 b71be000 SASKUTIL SASKUTIL.sys Mon Apr 28 23:17:42 2008 (48163EF6)
    b71be000 b71dfd00 afd afd.sys Thu Aug 14 12:04:35 2008 (48A40333)
    b71e0000 b7207c00 netbt netbt.sys Sun Apr 13 21:20:59 2008 (48025D1B)
    b7208000 b7260480 tcpip tcpip.sys Fri Jun 20 13:51:09 2008 (485B99AD)
    b7261000 b7273600 ipsec ipsec.sys Sun Apr 13 21:19:42 2008 (48025CCE)
    b7f4c000 b7f4e900 Dxapi Dxapi.sys Fri Aug 17 22:53:19 2001 (3B7D843F)
    b91b3000 b9210f00 update update.sys Sun Apr 13 20:39:46 2008 (48025372)
    b9211000 b9221e00 psched psched.sys Sun Apr 13 20:56:36 2008 (48025764)
    b9252000 b9260d80 sysaudio sysaudio.sys Sun Apr 13 21:15:55 2008 (48025BEB)
    b92c2000 b92d8580 ndiswan ndiswan.sys Sun Apr 13 21:20:41 2008 (48025D09)
    b92d9000 b92fca80 portcls portcls.sys Sun Apr 13 21:19:40 2008 (48025CCC)
    b92fd000 b96eb700 ALCXWDM ALCXWDM.SYS Wed Sep 24 04:40:17 2008 (48D9A891)
    b96ec000 b970e700 ks ks.sys Sun Apr 13 21:16:34 2008 (48025C12)
    b970f000 b9729d80 Rtnicxp Rtnicxp.sys Thu Jul 17 08:40:32 2008 (487EE960)
    b972a000 b973f300 UB1394 UB1394.SYS Wed Apr 13 11:05:49 2005 (425CE0ED)
    b9740000 b9752d00 ubohci ubohci.sys Wed Apr 13 11:08:13 2005 (425CE17D)
    b9753000 b9776200 USBPORT USBPORT.SYS Sun Apr 13 20:45:34 2008 (480254CE)
    b9777000 b978af00 VIDEOPRT VIDEOPRT.SYS Sun Apr 13 20:44:39 2008 (48025497)
    b978b000 b9dcbee0 nv4_mini nv4_mini.sys Fri May 16 23:45:57 2008 (482E0095)
    b9df0000 b9df3c80 mssmbios mssmbios.sys Sun Apr 13 20:36:45 2008 (480252BD)
    b9e14000 b9e2db80 Mup Mup.sys Sun Apr 13 21:17:05 2008 (48025C31)
    b9e2e000 b9e5a980 NDIS NDIS.sys Sun Apr 13 21:20:35 2008 (48025D03)
    b9e5b000 b9ee7600 Ntfs Ntfs.sys Sun Apr 13 21:15:49 2008 (48025BE5)
    b9ee8000 b9efe880 KSecDD KSecDD.sys Sun Apr 13 20:31:40 2008 (4802518C)
    b9eff000 b9f10f00 sr sr.sys Sun Apr 13 20:36:50 2008 (480252C2)
    b9f11000 b9f30b00 fltmgr fltmgr.sys Sun Apr 13 20:32:58 2008 (480251DA)
    b9f31000 b9f48900 atapi atapi.sys Sun Apr 13 20:40:29 2008 (4802539D)
    b9f49000 b9f67880 ftdisk ftdisk.sys Fri Aug 17 22:52:41 2001 (3B7D8419)
    b9f68000 b9f78a80 pci pci.sys Sun Apr 13 20:36:43 2008 (480252BB)
    b9f79000 b9fa6d80 ACPI ACPI.sys Sun Apr 13 20:36:33 2008 (480252B1)
    ba0a8000 ba0b1180 isapnp isapnp.sys Sun Apr 13 20:36:40 2008 (480252B8)
    ba0b8000 ba0c7100 ohci1394 ohci1394.sys Sun Apr 13 20:46:18 2008 (480254FA)
    ba0c8000 ba0d5100 1394BUS 1394BUS.SYS Fri Jan 23 14:41:38 2009 (4979C912)
    ba0d8000 ba0e2580 MountMgr MountMgr.sys Sun Apr 13 20:39:45 2008 (48025371)
    ba0e8000 ba0f4c80 VolSnap VolSnap.sys Sun Apr 13 20:41:00 2008 (480253BC)
    ba0f8000 ba100e00 disk disk.sys Sun Apr 13 20:40:46 2008 (480253AE)
    ba108000 ba114180 CLASSPNP CLASSPNP.SYS Sun Apr 13 21:16:21 2008 (48025C05)
    ba118000 ba123580 gagp30kx gagp30kx.sys Sun Apr 13 20:36:40 2008 (480252B8)
    ba148000 ba154880 rasl2tp rasl2tp.sys Sun Apr 13 21:19:43 2008 (48025CCF)
    ba158000 ba162200 raspppoe raspppoe.sys Sun Apr 13 20:57:31 2008 (4802579B)
    ba168000 ba173d00 raspptp raspptp.sys Sun Apr 13 21:19:47 2008 (48025CD3)
    ba178000 ba180900 msgpc msgpc.sys Sun Apr 13 20:56:32 2008 (48025760)
    ba188000 ba191f00 termdd termdd.sys Sun Apr 13 20:38:36 2008 (4802532C)
    ba1a8000 ba1b1e80 NDProxy NDProxy.SYS Sun Apr 13 20:57:28 2008 (48025798)
    ba1b8000 ba1c6880 usbhub usbhub.sys Sun Apr 13 20:45:36 2008 (480254D0)
    ba1c8000 ba1d5e80 ousb2hub ousb2hub.sys Sat Jul 16 00:02:41 2005 (42D83281)
    ba1e8000 ba1f22c0 aswTdi aswTdi.SYS Thu Feb 05 22:06:19 2009 (498B54CB)
    ba1f8000 ba200780 netbios netbios.sys Sun Apr 13 20:56:01 2008 (48025741)
    ba218000 ba220700 wanarp wanarp.sys Sun Apr 13 20:57:20 2008 (48025790)
    ba228000 ba232e00 Fips Fips.SYS Sun Apr 13 20:33:27 2008 (480251F7)
    ba248000 ba253280 ousbehci ousbehci.sys Sat Jul 16 00:02:30 2005 (42D83276)
    ba258000 ba262480 imapi imapi.sys Sun Apr 13 20:40:57 2008 (480253B9)
    ba268000 ba277600 cdrom cdrom.sys Sun Apr 13 20:40:45 2008 (480253AD)
    ba278000 ba286100 redbook redbook.sys Sun Apr 13 20:40:27 2008 (4802539B)
    ba288000 ba294d00 i8042prt i8042prt.sys Sun Apr 13 21:17:59 2008 (48025C67)
    ba298000 ba2a7c00 serial serial.sys Sun Apr 13 21:15:44 2008 (48025BE0)
    ba2a8000 ba2b7900 Cdfs Cdfs.SYS Sun Apr 13 21:14:21 2008 (48025B8D)
    ba2b8000 ba2c6b00 drmk drmk.sys Sun Apr 13 20:45:12 2008 (480254B8)
    ba2c8000 ba2d5000 AmdPPM AmdPPM.sys Mon Apr 16 23:46:33 2007 (4623EEB9)
    ba328000 ba32e180 PCIIDEX PCIIDEX.SYS Sun Apr 13 20:40:29 2008 (4802539D)
    ba330000 ba334d00 PartMgr PartMgr.sys Sun Apr 13 20:40:48 2008 (480253B0)
    ba338000 ba340000 videX32 videX32.sys Tue Nov 20 10:56:52 2007 (4742AF64)
    ba3a0000 ba3a5000 SASENUM SASENUM.SYS Tue Apr 15 20:22:56 2008 (4804F280)
    ba3f8000 ba3fc300 usbohci usbohci.sys Sun Apr 13 20:45:34 2008 (480254CE)
    ba400000 ba407400 DM9PCI5 DM9PCI5.SYS Fri Mar 02 09:56:34 2001 (3A9F6042)
    ba408000 ba40d080 usbuhci usbuhci.sys Sun Apr 13 20:45:34 2008 (480254CE)
    ba410000 ba416000 kbdclass kbdclass.sys Sun Apr 13 20:39:46 2008 (48025372)
    ba418000 ba41da00 mouclass mouclass.sys Sun Apr 13 20:39:47 2008 (48025373)
    ba420000 ba426b00 fdc fdc.sys Sun Apr 13 20:40:25 2008 (48025399)
    ba428000 ba42ca80 TDI TDI.SYS Sun Apr 13 21:00:04 2008 (48025834)
    ba430000 ba434580 ptilink ptilink.sys Fri Aug 17 22:49:53 2001 (3B7D8371)
    ba438000 ba43c080 raspti raspti.sys Fri Aug 17 22:55:32 2001 (3B7D84C4)
    ba440000 ba445000 flpydisk flpydisk.sys Sun Apr 13 20:40:24 2008 (48025398)
    ba450000 ba455200 vga vga.sys Sun Apr 13 20:44:40 2008 (48025498)
    ba458000 ba45ca80 Msfs Msfs.SYS Sun Apr 13 20:32:38 2008 (480251C6)
    ba460000 ba467880 Npfs Npfs.SYS Sun Apr 13 20:32:38 2008 (480251C6)
    ba468000 ba46e000 SASDIFSV SASDIFSV.SYS Mon Mar 23 21:55:36 2009 (49C7F748)
    ba470000 ba474a80 Aavmker4 Aavmker4.SYS Thu Feb 05 22:05:10 2009 (498B5486)
    ba478000 ba47c500 watchdog watchdog.sys Sun Apr 13 20:44:59 2008 (480254AB)
    ba480000 ba488000 aswFsBlk aswFsBlk.sys Thu Feb 05 03:40:50 2009 (498A51B2)
    ba4b8000 ba4bb000 BOOTVID BOOTVID.dll Fri Aug 17 22:49:09 2001 (3B7D8345)
    ba4bc000 ba4be480 BsStor BsStor.sys Thu Jun 06 08:41:41 2002 (3CFF0425)
    ba544000 ba546c00 vulfntr vulfntr.sys Mon Jun 06 11:51:37 2005 (42A41CA9)
    ba55c000 ba55e280 rasacd rasacd.sys Fri Aug 17 22:55:39 2001 (3B7D84CB)
    ba58c000 ba58fb80 cdrbsvsd cdrbsvsd.SYS Fri Jun 13 03:53:05 2003 (3EE92E81)
    ba594000 ba597d80 serenum serenum.sys Sun Apr 13 20:40:12 2008 (4802538C)
    ba598000 ba59a780 ndistapi ndistapi.sys Sun Apr 13 20:57:27 2008 (48025797)
    ba5a8000 ba5a9b80 kdcom kdcom.dll Fri Aug 17 22:49:10 2001 (3B7D8346)
    ba5aa000 ba5ab100 WMILIB WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B)
    ba5ac000 ba5ad500 viaide viaide.sys Sun Apr 13 20:40:30 2008 (4802539E)
    ba5ee000 ba5ef100 swenum swenum.sys Sun Apr 13 20:39:52 2008 (48025378)
    ba5f2000 ba5f3280 USBD USBD.SYS Fri Aug 17 23:02:58 2001 (3B7D8682)
    ba5f8000 ba5f9f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 22:49:37 2001 (3B7D8361)
    ba5fa000 ba5fb080 Beep Beep.SYS Fri Aug 17 22:47:33 2001 (3B7D82E5)
    ba5fc000 ba5fd080 mnmdd mnmdd.SYS Fri Aug 17 22:57:28 2001 (3B7D8538)
    ba5fe000 ba5ff080 RDPCDD RDPCDD.sys Fri Aug 17 22:46:56 2001 (3B7D82C0)
    ba608000 ba609100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B)
    ba689000 ba689860 BANTExt BANTExt.sys Thu May 28 04:43:29 1998 (356CCF51)
    ba713000 ba713d00 dxgthk dxgthk.sys Fri Aug 17 22:53:12 2001 (3B7D8438)
    ba717000 ba717c00 audstub audstub.sys Fri Aug 17 22:59:40 2001 (3B7D85BC)
    ba7ab000 ba7abb80 Null Null.SYS Fri Aug 17 22:47:39 2001 (3B7D82EB)
    bf000000 bf011600 dxg dxg.sys Sun Apr 13 20:38:27 2008 (48025323)
    bf012000 bf5e5700 nv4_disp nv4_disp.dll Fri May 16 23:41:04 2008 (482DFF70)
    bf800000 bf9c2e00 win32k win32k.sys Mon Feb 09 12:13:13 2009 (49900FC9)
    bffa0000 bffe5c00 ATMFD ATMFD.DLL Mon Apr 14 02:09:55 2008 (4802A0D3)

    Unloaded modules:
    ba7a0000 ba7a1000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b63e6000 b6411000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b64e9000 b64f6000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b6509000 b6517000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b6439000 b645c000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba5ce000 ba5d0000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b64b9000 b64c4000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b64d9000 b64e4000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b64f9000 b6504000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b6519000 b6524000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b6831000 b683c000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b6e00000 b6e0b000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b65d9000 b65e4000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b65e9000 b65f4000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    b6af6000 b6b0a000 Parport.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba208000 ba211000 processr.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba448000 ba44d000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba558000 ba55b000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba5ec000 ba5ee000 USBD.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba318000 ba323000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba5e8000 ba5ea000 USBD.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba308000 ba313000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba5e4000 ba5e6000 USBD.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba2f8000 ba303000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba5e0000 ba5e2000 USBD.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba2e8000 ba2f3000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba5dc000 ba5de000 USBD.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba2d8000 ba2e3000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba5d8000 ba5da000 USBD.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ba2a8000 ba2b3000 lvusbsta.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:debuglog.txt
     
    Julian57,
    #34
  16. 2009/04/18
    Julian57

    Julian57 Inactive Thread Starter

    Joined:
    2009/02/08
    Messages:
    75
    Likes Received:
    0
    That is what you get.
    Hope the info can be usefull for someone!

    Jules.
     
    Julian57,
    #35
  17. 2009/04/18
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Great - success :)

    As I posted at the outset .....
    There is nothing blindingly obvious that I can interpret, except possibly
    Do you have a Logitec mouse/keyboard and Logitec Desktop Manager/Messenger loaded?
     
    PeteC,
    #36
  18. 2009/04/18
    Julian57

    Julian57 Inactive Thread Starter

    Joined:
    2009/02/08
    Messages:
    75
    Likes Received:
    0
    The only Logitec products i have are my mouse and webcam.

    Jules.
     
    Julian57,
    #37
  19. 2009/04/18
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Check in Add/Remove Programs for Logitec Desktop Manager - loaded by default with Logitec products AFAIK ....
    It is not necessary for the operation of Logitec equipment - if present uninstall it and see if the problem is resolved.
     
    PeteC,
    #38
  20. 2009/04/18
    Julian57

    Julian57 Inactive Thread Starter

    Joined:
    2009/02/08
    Messages:
    75
    Likes Received:
    0
    Have uninstalled Logitec Desktop Manager.
    Never noticed it before so have no idea as to what it is.

    Jules.
     
    Julian57,
    #39
  21. 2009/04/19
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Any change for the better ?
     
    PeteC,
    #40
Page 2 of 3

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...