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.

DUMP DATA: BSoDs during bootup after installing Mozy Pro

Discussion in 'Windows XP' started by bnt, 2007/10/29.

  1. 2007/10/29
    bnt

    bnt Inactive Thread Starter

    Joined:
    2007/10/08
    Messages:
    8
    Likes Received:
    0
    Hi there!

    We have a number of users experiencing Blue Screens during bootup after installing Mozy Pro. After the BSoD, selecting "Start windows normally" works just fine. However, every reboot or shutdown will predictably cause the blue screen.

    Here is an example bit of dump data. Note that all of the dumps we've collected are virtually identical. Any suggestions? We're in contact with support, but not finding much help as of yet.

    Opened log file 'c:\debuglog.txt'

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


    Loading Dump File [Mini102907-02.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: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_qfe.070227-2300
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805535a0
    Debug session time: Mon Oct 29 09:29:39.000 2007 (GMT-5)
    System Uptime: 0 days 0:00:31.562
    Loading Kernel Symbols
    ....................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007F, {8, 80042000, 0, 0}

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


    Probably caused by : SYMEVENT.SYS ( SYMEVENT+7652 )

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

    kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault). The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
    use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
    use .trap on that value
    Else
    .trap on the appropriate frame will show where the trap was taken
    (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 80042000
    Arg3: 00000000
    Arg4: 00000000

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




    BUGCHECK_STR: 0x7f_8

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    PROCESS_NAME: csrss.exe

    LAST_CONTROL_TRANSFER: from f72a8856 to f72a864d

    STACK_TEXT:
    f4ddd21c f72a8856 f4ddd5e0 e1016d20 00000002 Ntfs!BinarySearchIndex+0x177
    f4ddd244 f72aa35e f4ddd5e0 e1016d20 e40499d0 Ntfs!FindFirstIndexEntry+0x19e
    f4ddd36c f72aa4f4 f4ddd5e0 e177a888 e1016d20 Ntfs!NtfsRestartIndexEnumeration+0x6c
    f4ddd590 f72a90e8 f4ddd5e0 857865e8 85f92738 Ntfs!NtfsQueryDirectory+0x54a
    f4ddd5c4 f72a9053 f4ddd5e0 e1016d20 85f3d870 Ntfs!NtfsCommonDirectoryControl+0xbc
    f4ddd73c 804ee0ef 85f92658 857865e8 857865e8 Ntfs!NtfsFsdDirectoryControl+0xad
    f4ddd74c f733b09e f4ddd7f0 85fdf128 857867e4 nt!IopfCallDriver+0x31
    f4ddd778 804ee0ef 85f3d870 857865e8 85f5c1a0 fltMgr!FltpDispatch+0x152
    f4ddd788 f7325459 f4ddd7b8 804ee0ef 85fc97d8 nt!IopfCallDriver+0x31
    f4ddd790 804ee0ef 85fc97d8 857865e8 804eef72 sr!SrPassThrough+0x31
    f4ddd7a0 f4bfe652 857867e4 85786808 f4ddd7f0 nt!IopfCallDriver+0x31
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f4ddd7b8 f4c05d80 85fc97d8 00000000 f4ddd7f0 SYMEVENT+0x7652
    f4ddd7d4 f4bfe7b9 f4ddd7f0 804eef72 f4bfe880 SYMEVENT+0xed80
    f4ddd814 804ee0ef 85789b68 857865e8 857cbda0 SYMEVENT+0x77b9
    f4ddd860 804ee0ef 8599c020 857865e8 857865e8 nt!IopfCallDriver+0x31
    f4ddd870 f733b09e 857865e8 85fdf128 857a6950 nt!IopfCallDriver+0x31
    f4ddd850 f4aefa6c 8599c020 007865e8 f4ddd89c fltMgr!FltpDispatch+0x152
    f4ddd860 804ee0ef 8599c020 857865e8 857865e8 mozypro+0x3a6c
    f4ddd870 f733b09e 857865e8 85fdf128 857a6950 nt!IopfCallDriver+0x31
    f4ddd89c 804ee0ef 85930ee8 857865e8 806d02d0 fltMgr!FltpDispatch+0x152
    f4ddd8ac 80574032 f4ddd918 f4ddd9bc 8056e426 nt!IopfCallDriver+0x31
    f4ddd8c0 8056e483 85930ee8 857865e8 85e3ec98 nt!IopSynchronousServiceTail+0x60
    f4ddd8e4 8053cbc8 80000fe0 00000000 00000000 nt!NtQueryDirectoryFile+0x5d
    f4ddd8e4 804fe0f5 80000fe0 00000000 00000000 nt!KiFastCallEntry+0xf8
    f4ddd988 f48e5f4b 80000fe0 00000000 00000000 nt!ZwQueryDirectoryFile+0x11
    f4ddd9d4 f48e6451 f4ddd9f8 f4ddda08 f4ddda00 SPBBCDrv+0x2f4b
    f4ddda20 f48f4247 e37be7a4 e40179b0 00000000 SPBBCDrv+0x3451
    f4ddda3c f48f25a4 e40dd16c f4900fda f49011c3 SPBBCDrv+0x11247
    f4ddda60 f4901603 f4dddb90 00000005 0000000b SPBBCDrv+0xf5a4
    f4ddda90 f49012e8 f4dddb84 e3178d08 00000000 SPBBCDrv+0x1e603
    f4dddacc f48f2335 00000002 f4dddb84 e40dd008 SPBBCDrv+0x1e2e8
    f4dddb2c f48f370a f4dddc5c 00dddc30 00000002 SPBBCDrv+0xf335
    f4dddb90 f4dddc5c 85490000 e40179b0 00000000 SPBBCDrv+0x1070a
    f4dddb94 85490000 e40179b0 00000000 00000000 0xf4dddc5c
    f4dddd40 804ee0ef 85789b68 857a6940 857cbda0 0x85490000
    f4dddd8c 804ee0ef 8599c020 857a6940 857a6940 nt!IopfCallDriver+0x31
    f4dddd9c f733ae9b 00000000 857a6940 857a6b3c nt!IopfCallDriver+0x31
    f4ddddc0 f7347448 f4dddde0 85930ee8 00000000 fltMgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20b
    f4ddddfc 804ee0ef 85930ee8 857a6940 857a6940 fltMgr!FltpCreate+0x26a
    f4ddde0c 805778d6 85f3dbf0 8594d0ac f4dddfb4 nt!IopfCallDriver+0x31
    f4dddeec 805b3c2a 85f3dc08 00000000 8594d008 nt!IopParseDevice+0xa12
    f4dddf74 805b010b 00000000 f4dddfb4 00000240 nt!ObpLookupObjectName+0x56a
    f4dddfc8 8056a613 00000000 00000000 dde04000 nt!ObOpenObjectByName+0xeb
    f4dde044 8056af8a f4dde0f0 80100180 f4dde110 nt!IopCreateFile+0x407
    f4dde0a0 f4c5e8c6 f4dde0f0 80100180 f4dde110 nt!IoCreateFile+0x8e
    f4dde138 80544477 e3fe3e48 f4dde130 f4dde110 savrt+0x458c6
    f4dde1a4 805b0cfd 00000068 00000000 f4dde1c4 nt!ExFreePool+0xf
    f4dde1b8 804e7a41 e3fa4680 f4dde22c f4c5d747 nt!NtClose+0x1d
    f4dde1c4 f4c5d747 857e98c0 f4dde23c f4c3037a nt!ExAllocateFromPagedLookasideList+0x13
    f4dde22c 00000000 00000000 00000000 00000000 savrt+0x44747


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    SYMEVENT+7652
    f4bfe652 ?? ???

    SYMBOL_STACK_INDEX: b

    SYMBOL_NAME: SYMEVENT+7652

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: SYMEVENT

    IMAGE_NAME: SYMEVENT.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP: 450f3f43

    FAILURE_BUCKET_ID: 0x7f_8_SYMEVENT+7652

    BUCKET_ID: 0x7f_8_SYMEVENT+7652

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

    eax=00000001 ebx=00000000 ecx=c829e9b8 edx=e1565000 esi=00000001 edi=f4ddd010
    eip=f72a864d esp=f4ddd000 ebp=f4ddd21c iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    Ntfs!BinarySearchIndex+0x177:
    f72a864d 6aff push 0FFFFFFFFh
    ChildEBP RetAddr Args to Child
    f4ddd21c f72a8856 f4ddd5e0 e1016d20 00000002 Ntfs!BinarySearchIndex+0x177 (FPO: [Non-Fpo])
    f4ddd244 f72aa35e f4ddd5e0 e1016d20 e40499d0 Ntfs!FindFirstIndexEntry+0x19e (FPO: [Non-Fpo])
    f4ddd36c f72aa4f4 f4ddd5e0 e177a888 e1016d20 Ntfs!NtfsRestartIndexEnumeration+0x6c (FPO: [Non-Fpo])
    f4ddd590 f72a90e8 f4ddd5e0 857865e8 85f92738 Ntfs!NtfsQueryDirectory+0x54a (FPO: [Non-Fpo])
    f4ddd5c4 f72a9053 f4ddd5e0 e1016d20 85f3d870 Ntfs!NtfsCommonDirectoryControl+0xbc (FPO: [Non-Fpo])
    f4ddd73c 804ee0ef 85f92658 857865e8 857865e8 Ntfs!NtfsFsdDirectoryControl+0xad (FPO: [Non-Fpo])
    f4ddd74c f733b09e f4ddd7f0 85fdf128 857867e4 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
    f4ddd778 804ee0ef 85f3d870 857865e8 85f5c1a0 fltMgr!FltpDispatch+0x152 (FPO: [Non-Fpo])
    f4ddd788 f7325459 f4ddd7b8 804ee0ef 85fc97d8 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
    f4ddd790 804ee0ef 85fc97d8 857865e8 804eef72 sr!SrPassThrough+0x31 (FPO: [Non-Fpo])
    f4ddd7a0 f4bfe652 857867e4 85786808 f4ddd7f0 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f4ddd7b8 f4c05d80 85fc97d8 00000000 f4ddd7f0 SYMEVENT+0x7652
    f4ddd7d4 f4bfe7b9 f4ddd7f0 804eef72 f4bfe880 SYMEVENT+0xed80
    f4ddd814 804ee0ef 85789b68 857865e8 857cbda0 SYMEVENT+0x77b9
    f4ddd860 804ee0ef 8599c020 857865e8 857865e8 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
    f4ddd870 f733b09e 857865e8 85fdf128 857a6950 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
    f4ddd850 f4aefa6c 8599c020 007865e8 f4ddd89c fltMgr!FltpDispatch+0x152 (FPO: [Non-Fpo])
    f4ddd860 804ee0ef 8599c020 857865e8 857865e8 mozypro+0x3a6c
    f4ddd870 f733b09e 857865e8 85fdf128 857a6950 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
    f4ddd89c 804ee0ef 85930ee8 857865e8 806d02d0 fltMgr!FltpDispatch+0x152 (FPO: [Non-Fpo])
    start end module name
    804d7000 806cdc80 nt ntkrnlpa.exe Wed Feb 28 03:15:53 2007 (45E54849)
    806ce000 806ee280 hal halaacpi.dll Mon Nov 15 19:37:02 2004 (419959BE)
    bf000000 bf011580 dxg dxg.sys Wed Aug 04 01:00:51 2004 (41107B93)
    bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 07:47:34 2007 (45F013F6)
    f4766000 f477d480 dump_atapi dump_atapi.sys Wed Aug 04 00:59:41 2004 (41107B4D)
    f477e000 f479d000 EraserUtilRebootDrv EraserUtilRebootDrv.sys Fri Aug 24 20:52:21 2007 (46CF8B55)
    f479d000 f4800000 eeCtrl eeCtrl.sys Fri Aug 24 20:52:21 2007 (46CF8B55)
    f4800000 f486ea00 mrxsmb mrxsmb.sys Fri May 05 04:41:42 2006 (445B1DD6)
    f486f000 f4899a00 rdbss rdbss.sys Fri May 05 04:47:55 2006 (445B1F4B)
    f48c2000 f48e2f00 ipnat ipnat.sys Wed Sep 29 17:28:36 2004 (415B3714)
    f48e3000 f4945000 SPBBCDrv SPBBCDrv.sys Tue Apr 11 18:55:08 2006 (443C41DC)
    f4945000 f4966d00 afd afd.sys Wed Aug 04 01:14:13 2004 (41107EB5)
    f4967000 f498ec00 netbt netbt.sys Wed Aug 04 01:14:36 2004 (41107ECC)
    f498f000 f49ba000 symidsco symidsco.sys Tue Sep 11 22:47:33 2007 (46E76155)
    f49ba000 f49e3000 SYMFW SYMFW.SYS Mon Aug 07 17:52:33 2006 (44D7C431)
    f49e3000 f4a1e000 SYMTDI SYMTDI.SYS Mon Aug 07 17:52:32 2006 (44D7C430)
    f4a1e000 f4a75d80 tcpip tcpip.sys Thu Apr 20 06:51:47 2006 (444775D3)
    f4a76000 f4a91000 RCFOX RCFOX.sys Fri Oct 15 12:46:09 2004 (41700CE1)
    f4a91000 f4aa3400 ipsec ipsec.sys Wed Aug 04 01:14:27 2004 (41107EC3)
    f4aec000 f4afe000 mozypro mozypro.sys Thu Aug 09 15:23:20 2007 (46BB77B8)
    f4afe000 f4b10320 naveng naveng.sys Sat Jun 23 13:23:20 2007 (467D6518)
    f4b11000 f4be2c40 navex15 navex15.sys Sat Jun 23 12:48:39 2007 (467D5CF7)
    f4be3000 f4bf7000 Savrtpel Savrtpel.sys Wed Sep 06 16:26:26 2006 (44FF3D02)
    f4bf7000 f4c19000 SYMEVENT SYMEVENT.SYS Mon Sep 18 19:52:19 2006 (450F3F43)
    f4c19000 f4c71000 savrt savrt.sys Wed Sep 06 16:26:23 2006 (44FF3CFF)
    f4cb1000 f4d10f00 Senfilt Senfilt.sys Mon Mar 13 11:40:28 2006 (4415A07C)
    f4d11000 f4d32700 portcls portcls.sys Tue Mar 16 13:58:17 2004 (40574E49)
    f4d33000 f4d70000 ADIHdAud ADIHdAud.sys Mon May 22 15:40:52 2006 (447221D4)
    f4de0000 f4def900 Cdfs Cdfs.SYS Wed Aug 04 01:14:09 2004 (41107EB1)
    f6e4a000 f6e4c280 rasacd rasacd.sys Fri Aug 17 15:55:39 2001 (3B7D84CB)
    f6e4e000 f6e51a00 kbdhid kbdhid.sys Wed Aug 04 00:58:33 2004 (41107B09)
    f6e52000 f6e54f80 mouhid mouhid.sys Fri Aug 17 15:47:57 2001 (3B7D82FD)
    f6e97000 f6eefe80 update update.sys Mon Apr 23 05:32:54 2007 (462C8B56)
    f6f00000 f6f02900 Dxapi Dxapi.sys Fri Aug 17 15:53:19 2001 (3B7D843F)
    f6f0c000 f6f0e580 hidusb hidusb.sys Fri Aug 17 16:02:16 2001 (3B7D8658)
    f6f18000 f6f48100 rdpdr rdpdr.sys Wed Aug 04 01:01:10 2004 (41107BA6)
    f6f49000 f6f59e00 psched psched.sys Wed Aug 04 01:04:16 2004 (41107C60)
    f6f5a000 f6f70680 ndiswan ndiswan.sys Wed Aug 04 01:14:30 2004 (41107EC6)
    f6f71000 f6f8c9e0 dne2000 dne2000.sys Fri May 14 19:13:12 2004 (40A56098)
    f6f8d000 f6fa0900 parport parport.sys Wed Aug 04 00:59:04 2004 (41107B28)
    f6fa1000 f6fc7000 HDAudBus HDAudBus.sys Thu Aug 12 19:45:52 2004 (411C0F40)
    f6fc7000 f6fe9680 ks ks.sys Wed Aug 04 01:15:20 2004 (41107EF8)
    f6fea000 f700cf00 USBPORT USBPORT.SYS Tue Oct 25 18:39:41 2005 (435EC23D)
    f700d000 f7020f00 VIDEOPRT VIDEOPRT.SYS Thu Aug 03 09:02:07 2006 (44D201DF)
    f7021000 f71e0000 ati2mtag ati2mtag.sys Tue Oct 03 20:43:21 2006 (452311B9)
    f7239000 f7253580 Mup Mup.sys Wed Aug 04 01:15:20 2004 (41107EF8)
    f7254000 f7280a80 NDIS NDIS.sys Wed Aug 04 01:14:27 2004 (41107EC3)
    f7281000 f730d400 Ntfs Ntfs.sys Fri Feb 09 05:10:31 2007 (45CC56A7)
    f730e000 f7324780 KSecDD KSecDD.sys Wed Aug 04 00:59:45 2004 (41107B51)
    f7325000 f7336f00 sr sr.sys Wed Aug 04 01:06:22 2004 (41107CDE)
    f7337000 f7356780 fltMgr fltMgr.sys Mon Aug 21 04:14:57 2006 (44E97991)
    f7357000 f736e480 atapi atapi.sys Wed Aug 04 00:59:41 2004 (41107B4D)
    f736f000 f7394700 dmio dmio.sys Wed Aug 04 01:07:13 2004 (41107D11)
    f7395000 f73b3880 ftdisk ftdisk.sys Fri Aug 17 15:52:41 2001 (3B7D8419)
    f73b4000 f73c4a80 pci pci.sys Wed Aug 04 01:07:45 2004 (41107D31)
    f73c5000 f73f2d80 ACPI ACPI.sys Wed Aug 04 01:07:35 2004 (41107D27)
    f74f4000 f74fcc00 isapnp isapnp.sys Fri Aug 17 15:58:01 2001 (3B7D8559)
    f7504000 f750e500 MountMgr MountMgr.sys Wed Aug 04 00:58:29 2004 (41107B05)
    f7514000 f7520c80 VolSnap VolSnap.sys Wed Aug 04 01:00:14 2004 (41107B6E)
    f7524000 f752ce00 disk disk.sys Wed Aug 04 00:59:53 2004 (41107B59)
    f7534000 f7540200 CLASSPNP CLASSPNP.SYS Wed Aug 04 01:14:26 2004 (41107EC2)
    f7554000 f755cd80 HIDCLASS HIDCLASS.SYS Wed Aug 04 01:08:18 2004 (41107D52)
    f7594000 f759e000 SYMREDRV SYMREDRV.SYS Mon Aug 07 17:52:34 2006 (44D7C432)
    f75a4000 f75af000 SYMNDIS SYMNDIS.SYS Mon Aug 07 17:52:33 2006 (44D7C431)
    f75b4000 f75c0000 SYMIDS SYMIDS.SYS Mon Aug 07 17:52:34 2006 (44D7C432)
    f75c4000 f75cc700 netbios netbios.sys Wed Aug 04 01:03:19 2004 (41107C27)
    f75d4000 f75dc700 wanarp wanarp.sys Wed Aug 04 01:04:57 2004 (41107C89)
    f7604000 f760c880 Fips Fips.SYS Fri Aug 17 20:31:49 2001 (3B7DC585)
    f7634000 f763cd00 intelppm intelppm.sys Wed Aug 04 00:59:19 2004 (41107B37)
    f7664000 f7670180 cdrom cdrom.sys Wed Aug 04 00:59:52 2004 (41107B58)
    f7674000 f7682080 redbook redbook.sys Wed Aug 04 00:59:34 2004 (41107B46)
    f7684000 f7693d80 serial serial.sys Wed Aug 04 01:15:51 2004 (41107F17)
    f7694000 f76a4000 bcm4sbxp bcm4sbxp.sys Wed May 17 13:03:22 2006 (446B656A)
    f76a4000 f76b0880 rasl2tp rasl2tp.sys Wed Aug 04 01:14:21 2004 (41107EBD)
    f76b4000 f76be200 raspppoe raspppoe.sys Wed Aug 04 01:05:06 2004 (41107C92)
    f76c4000 f76cfd00 raspptp raspptp.sys Wed Aug 04 01:14:26 2004 (41107EC2)
    f76d4000 f76dc900 msgpc msgpc.sys Wed Aug 04 01:04:11 2004 (41107C5B)
    f76e4000 f76edf00 termdd termdd.sys Wed Aug 04 00:58:52 2004 (41107B1C)
    f76f4000 f76fd480 NDProxy NDProxy.SYS Fri Aug 17 15:55:30 2001 (3B7D84C2)
    f7734000 f7742100 usbhub usbhub.sys Wed Aug 04 01:08:40 2004 (41107D68)
    f7744000 f7752b80 drmk drmk.sys Wed Aug 04 01:07:54 2004 (41107D3A)
    f7774000 f777a200 PCIIDEX PCIIDEX.SYS Wed Aug 04 00:59:40 2004 (41107B4C)
    f777c000 f7780900 PartMgr PartMgr.sys Fri Aug 17 20:32:23 2001 (3B7DC5A7)
    f77c4000 f77c8500 watchdog watchdog.sys Wed Aug 04 01:07:32 2004 (41107D24)
    f783c000 f7840280 usbohci usbohci.sys Wed Aug 04 01:08:34 2004 (41107D62)
    f7844000 f784aa80 usbehci usbehci.sys Tue Oct 25 18:39:41 2005 (435EC23D)
    f784c000 f7850880 TDI TDI.SYS Wed Aug 04 01:07:47 2004 (41107D33)
    f7854000 f7858580 ptilink ptilink.sys Fri Aug 17 15:49:53 2001 (3B7D8371)
    f785c000 f7860080 raspti raspti.sys Fri Aug 17 15:55:32 2001 (3B7D84C4)
    f7864000 f786a000 kbdclass kbdclass.sys Wed Aug 04 00:58:32 2004 (41107B08)
    f786c000 f7871a00 mouclass mouclass.sys Wed Aug 04 00:58:32 2004 (41107B08)
    f788c000 f7892180 HIDPARSE HIDPARSE.SYS Wed Aug 04 01:08:15 2004 (41107D4F)
    f789c000 f78a1200 vga vga.sys Wed Aug 04 01:07:06 2004 (41107D0A)
    f78a4000 f78a8a80 Msfs Msfs.SYS Wed Aug 04 01:00:37 2004 (41107B85)
    f78ac000 f78b3880 Npfs Npfs.SYS Wed Aug 04 01:00:38 2004 (41107B86)
    f78bc000 f78c3000 SYMDNS SYMDNS.SYS Mon Aug 07 17:52:32 2006 (44D7C430)
    f7904000 f7907000 BOOTVID BOOTVID.dll Fri Aug 17 15:49:09 2001 (3B7D8345)
    f79a0000 f79a3c80 serenum serenum.sys Wed Aug 04 00:59:06 2004 (41107B2A)
    f79a8000 f79aa580 ndistapi ndistapi.sys Fri Aug 17 15:55:29 2001 (3B7D84C1)
    f79b8000 f79baf40 rcvpn rcvpn.sys Tue Nov 05 18:39:49 2002 (3DC864D5)
    f79c4000 f79c7c80 mssmbios mssmbios.sys Wed Aug 04 01:07:47 2004 (41107D33)
    f79f4000 f79f5b80 kdcom kdcom.dll Fri Aug 17 15:49:10 2001 (3B7D8346)
    f79f6000 f79f7100 WMILIB WMILIB.SYS Fri Aug 17 16:07:23 2001 (3B7D878B)
    f79f8000 f79f9700 dmload dmload.sys Fri Aug 17 15:58:15 2001 (3B7D8567)
    f7a1c000 f7a1d100 swenum swenum.sys Wed Aug 04 00:58:41 2004 (41107B11)
    f7a24000 f7a25280 USBD USBD.SYS Fri Aug 17 16:02:58 2001 (3B7D8682)
    f7a28000 f7a2a000 i2omgmt i2omgmt.SYS Wed Aug 04 01:00:50 2004 (41107B92)
    f7a2a000 f7a2bf00 Fs_Rec Fs_Rec.SYS Fri Aug 17 15:49:37 2001 (3B7D8361)
    f7a3c000 f7a3d080 Beep Beep.SYS Fri Aug 17 15:47:33 2001 (3B7D82E5)
    f7a3e000 f7a3f080 mnmdd mnmdd.SYS Fri Aug 17 15:57:28 2001 (3B7D8538)
    f7a40000 f7a41080 RDPCDD RDPCDD.sys Fri Aug 17 15:46:56 2001 (3B7D82C0)
    f7a82000 f7a83100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 16:07:23 2001 (3B7D878B)
    f7abc000 f7abcd00 pciide pciide.sys Fri Aug 17 15:51:49 2001 (3B7D83E5)
    f7abd000 f7abdd80 atiide atiide.sys Thu Sep 07 15:37:20 2006 (45008300)
    f7aee000 f7aeed00 dxgthk dxgthk.sys Fri Aug 17 15:53:12 2001 (3B7D8438)
    f7b40000 f7b40b80 Null Null.SYS Fri Aug 17 15:47:39 2001 (3B7D82EB)
    f7c32000 f7c32c00 audstub audstub.sys Fri Aug 17 15:59:40 2001 (3B7D85BC)

    Unloaded modules:
    f75f4000 f75ff000 imapi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f6ef0000 f6ef4000 kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7584000 f7591000 i8042prt.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f787c000 f7881000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f71f8000 f71fb000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt
     
    bnt,
    #1
  2. 2007/10/29
    bnt

    bnt Inactive Thread Starter

    Joined:
    2007/10/08
    Messages:
    8
    Likes Received:
    0
    Heh, I just noticed the typo in the thread title, sorry about that!

    Corrected - Mod
     
    bnt,
    #2

  3. to hide this advert.

  4. 2007/10/29
    PeteC

    PeteC SuperGeek Staff

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

    First the rider .....

    Unfortunately these logs require expert knowledge to analyze and there are only 2 members (who occasionally visit WindowsBBS.com) that have the depth of knowledge necessary. Other members can make observations and suggestions as to how you might proceed toward finding the cause ....

    From your log .....
    this is part of Norton Symantec software, so I would suspect a clash between the two.
     
  5. 2007/10/29
    ccutrer

    ccutrer Inactive

    Joined:
    2007/10/29
    Messages:
    1
    Likes Received:
    0
    Hi,

    I'm an employee at Mozy, specifically working on the Windows client and our kernel mode filter driver. I'd like to help you with your BSOD problems. First off, I would definitely agree with PeteC that the crash is being caused by Symantec AntiVirus. We've seen several occurrences in the past of navap.sys BSODing when Mozy is installed. Symevent.sys seems a likely first cousin of navap.sys. I'd recommend making sure you have all the latest updates from Symantec. We've looked at crash dumps before, and have seen that Mozy is indeed installed, but is not directly in the call stack for the crash, and so cannot determine the root problem. We have forwarded the issue to Symantec, but have not received a direct response, although upgrading has seemed to work in the past.

    If you would like me to take a look at your specific crash dumps, please PM me, and I'll send you information to e-mail them directly to me. If Mozy is anywhere in the call stack, I have the debugging resources available to look at where it is passing through our code.

    Thanks,

    Cody Cutrer
    Senior Windows Engineer
    Mozy, Inc.
     
  6. 2007/10/29
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Cody - Welcome to the Board :) - and thanks for your input!
     
  7. 2007/10/29
    peterdiva

    peterdiva Inactive

    Joined:
    2007/06/04
    Messages:
    43
    Likes Received:
    0
    It's most likely a stack overflow caused by Norton. You can find out how to extend the stack HERE.
     
  8. 2007/10/29
    bnt

    bnt Inactive Thread Starter

    Joined:
    2007/10/08
    Messages:
    8
    Likes Received:
    0
    Thanks, peterdiva! Excellent find.


    We'll give it a shot.
     
    bnt,
    #7
  9. 2007/10/29
    bnt

    bnt Inactive Thread Starter

    Joined:
    2007/10/08
    Messages:
    8
    Likes Received:
    0
    Thanks for all of the help! It was resolved via a registry variable per the Symantec document linked to above. It turns out to be a problem with SAV only in a kernel stack with low memory. Probably not a Mozy problem, but one that was apparent once Mozy was installed.

    From Symantec (link above):
    Thanks again!
     
    bnt,
    #8
  10. 2007/10/29
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Great effort all round - successful outcome - thanks to all :)
     

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.