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 when updating]

Discussion in 'Windows XP' started by Sminky, 2007/03/17.

  1. 2007/03/17
    Sminky

    Sminky Inactive Thread Starter

    Joined:
    2007/03/17
    Messages:
    5
    Likes Received:
    0
    Hi.

    This is the first time ive posted on your forum. So thanks fro reading, and any help would be greatly appreciated!

    My PC crashes every time I get an auto update from my internet service provider or windows. I get the big blue screen business and then the "your computer has recovered form as serious error" message. The error message is as:

    BCCode : 1000008e BCP1 : C0000005 BCP2 : F1F09609 BCP3 : F17B8A20 BCP4 : 00000000 OSVER : 5_1_2600 SP : 2_0 Product : 768_1

    I hope this means somthing to someone, as it's complete gobbledygook to me???

    Thanks
     
  2. 2007/03/17
    charlesvar

    charlesvar Inactive Alumni

    Joined:
    2002/02/18
    Messages:
    7,024
    Likes Received:
    0
    Hello Sminky and welcome to the Board,

    Right click on My Computer, then Manage.
    On the left you will see Event Viewer. Expand that (click on the plus sign).

    Then click on System. See if there are any errors being logged by the system when the problem occurs.

    Right clicking on a line and then clicking on Properties will give you a window with more info concerning that line. You'll see in the top section right below the down arrow, a text graphic symbol. Clicking on that will place the error info text into your clipboard (memory). Bring up Notepad and right click and paste, that will transfer it to Notepad. You can then paste the text into your next post here.

    Two tests to perform:

    Test your physical memory with this MS diagnostic tool: http://oca.microsoft.com/en/windiag.asp

    Do a chkdsk: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx Use the /r switch

    Also, I've changed your thread title - please use meaningfull titles.

    Regards - Charles
     

  3. to hide this advert.

  4. 2007/03/17
    Sminky

    Sminky Inactive Thread Starter

    Joined:
    2007/03/17
    Messages:
    5
    Likes Received:
    0
    Thankyou Charles. Apologies for my nievety and the incorrect title! I have managed to dig up the following information/data? =

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 16/03/2007
    Time: 20:00:07
    User: N/A
    Computer: BLACKBIRD
    Description:
    Error code 1000008e, parameter1 c0000005, parameter2 f1f09609,
    parameter3 f0bf1a20, parameter4 00000000.

    For more information,
    see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 53 79 73 74 65 6d 20 45 System E
    0008: 72 72 6f 72 20 20 45 72 rror Er
    0010: 72 6f 72 20 63 6f 64 65 ror code
    0018: 20 31 30 30 30 30 30 38 1000008
    0020: 65 20 20 50 61 72 61 6d e Param
    0028: 65 74 65 72 73 20 63 30 eters c0
    0030: 30 30 30 30 30 35 2c 20 000005,
    0038: 66 31 66 30 39 36 30 39 f1f09609
    0040: 2c 20 66 30 62 66 31 61 , f0bf1a
    0048: 32 30 2c 20 30 30 30 30 20, 0000
    0050: 30 30 30 30 0000




    I also have this error:


    Event Type: Error
    Event Source: W32Time
    Event Category: None
    Event ID: 29
    Date: 17/03/2007
    Time: 19:48:07
    User: N/A
    Computer: BLACKBIRD
    Description:
    The time provider NtpClient is configured to acquire time from one or more time sources,
    however none of the sources are currently accessible. No attempt to contact a source will
    be made for 14 minutes. NtpClient has no source of accurate time.

    For more information, see
    Help and Support Center at http://go.microsoft.com/fwlink/events.asp.




    And I have this warning?


    Event Type: Warning
    Event Source: Dhcp
    Event Category: None
    Event ID: 1007
    Date: 17/03/2007
    Time: 13:26:37
    User: N/A
    Computer: BLACKBIRD
    Description:
    Your computer has automatically configured the IP address for the Network Card with network
    address 009096791AAC.The IP address being used is 169.254.220.93.

    For more information, see
    Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 00 00 00 00 ....


    I hope that i've done this right, please forgive my incompitence my Jedi master.

    Thanks... Simon:D
     
  5. 2007/03/17
    charlesvar

    charlesvar Inactive Alumni

    Joined:
    2002/02/18
    Messages:
    7,024
    Likes Received:
    0
    Hello Sminky,

    Please confirm that you have run the diagnostic tools linked to.

    Is this system on a LAN or connected to a router?

    Research points to hardware - either memory or a peripheral device.

    Regards - Charles
     
  6. 2007/03/17
    Sminky

    Sminky Inactive Thread Starter

    Joined:
    2007/03/17
    Messages:
    5
    Likes Received:
    0
    I've just finished running the tests, and both came up with no faults or problems!

    I've just had a look in my device manager and my SCSI/RAID Host Controller is showing an error = "Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39) "

    I'm still experiencing software glitches and system crashes?????
     
  7. 2007/03/17
    Sminky

    Sminky Inactive Thread Starter

    Joined:
    2007/03/17
    Messages:
    5
    Likes Received:
    0
    I'm not on a network (LAN) or connected to a router. I've a ADSL Broadband modem connecting me to the Net!

    Heres my vital statistics:

    MS Win XP Home 2002 SP2
    Intel Pentium 4 2.0GHz
    384 MB RAM
    80Gig HD of which 20Gig is being used!

    I defrag weekly and run Adaware, Spybot, Window Washer, and CCleaner once a week.

    I have recently changed from Norton Systemworks to Macafee Security Centre!

    Eeeermm:confused: :confused: ....Thats about as technical as I get!!!

    Thanks for the help by the way. Simon
     
  8. 2007/03/17
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Arie,
    #7
  9. 2007/03/17
    Sminky

    Sminky Inactive Thread Starter

    Joined:
    2007/03/17
    Messages:
    5
    Likes Received:
    0
    Dump Data Log

    Opened log file 'c:\debuglog.txt'

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini031707-03.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
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 2600.xpsp_sp2_gdr.050301-1519
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
    Debug session time: Sat Mar 17 13:20:36.625 2007 (GMT+0)
    System Uptime: 0 days 0:04:26.203
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
    Loading Kernel Symbols
    ........................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    Unable to load image system32:lzx32.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for lzx32.sys
    *** ERROR: Module load completed but symbols could not be loaded for lzx32.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, f1f09609, f165ca20, 0}

    ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
    ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,213F80,42250FF9
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : system32:lzx32.sys ( lzx32+2609 )

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

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

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: f1f09609, The address that the exception occurred at
    Arg3: f165ca20, Trap Frame
    Arg4: 00000000

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

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************

    MODULE_NAME: lzx32

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 45abe5f0

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

    FAULTING_IP:
    lzx32+2609
    f1f09609 8a1401 mov dl,byte ptr [ecx+eax]

    TRAP_FRAME: f165ca20 -- (.trap fffffffff165ca20)
    .trap fffffffff165ca20
    ErrCode = 00000000
    eax=00000000 ebx=f1f0f535 ecx=0101d000 edx=804dd2ad esi=00001000 edi=0101c000
    eip=f1f09609 esp=f165ca94 ebp=f165caa0 iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
    lzx32+0x2609:
    f1f09609 8a1401 mov dl,byte ptr [ecx+eax] ds:0023:0101d000=??
    .trap
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    BUGCHECK_STR: 0x8E

    LAST_CONTROL_TRANSFER: from f1f0b465 to f1f09609

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f165caa0 f1f0b465 0101c000 0000001e f1f0f535 lzx32+0x2609
    f165caf4 f1f0b575 82893280 01000000 01000210 lzx32+0x4465
    f165cb58 f1f0b66e 82893280 e17fe558 826fbda8 lzx32+0x4575
    f165cb78 805f9351 00000d90 82893280 00000001 lzx32+0x466e
    f165ccc4 8057b2a3 00c8ecbc 001f03ff 00000000 nt!IoCheckFunctionAccess+0x1942a
    f165cd3c 804de7ec 00c8ecbc 001f03ff 00000000 nt!PsSetThreadWin32Thread+0x70d
    f165cd64 7c90eb94 badb0d00 00c8e8f4 00000000 nt!ZwYieldExecution+0xb78
    f165cd68 badb0d00 00c8e8f4 00000000 00000000 0x7c90eb94
    f165cd6c 00c8e8f4 00000000 00000000 00000000 0xbadb0d00
    f165cd70 00000000 00000000 00000000 00000000 0xc8e8f4


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    lzx32+2609
    f1f09609 8a1401 mov dl,byte ptr [ecx+eax]

    SYMBOL_STACK_INDEX: 0

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: system32:lzx32.sys

    SYMBOL_NAME: lzx32+2609

    BUCKET_ID: WRONG_SYMBOLS

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

    eax=00000000 ebx=f1f0f535 ecx=0101d000 edx=804dd2ad esi=00001000 edi=0101c000
    eip=f1f09609 esp=f165ca94 ebp=f165caa0 iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
    lzx32+0x2609:
    f1f09609 8a1401 mov dl,byte ptr [ecx+eax] ds:0023:0101d000=??
    ChildEBP RetAddr Args to Child
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f165caa0 f1f0b465 0101c000 0000001e f1f0f535 lzx32+0x2609
    f165caf4 f1f0b575 82893280 01000000 01000210 lzx32+0x4465
    f165cb58 f1f0b66e 82893280 e17fe558 826fbda8 lzx32+0x4575
    f165cb78 805f9351 00000d90 82893280 00000001 lzx32+0x466e
    f165ccc4 8057b2a3 00c8ecbc 001f03ff 00000000 nt!IoCheckFunctionAccess+0x1942a
    f165cd3c 804de7ec 00c8ecbc 001f03ff 00000000 nt!PsSetThreadWin32Thread+0x70d
    f165cd64 7c90eb94 badb0d00 00c8e8f4 00000000 nt!ZwYieldExecution+0xb78
    f165cd68 badb0d00 00c8e8f4 00000000 00000000 0x7c90eb94
    f165cd6c 00c8e8f4 00000000 00000000 00000000 0xbadb0d00
    f165cd70 00000000 00000000 00000000 00000000 0xc8e8f4
    start end module name
    804d7000 806eaf80 nt ntoskrnl.exe Wed Mar 02 00:59:37 2005 (42250FF9)
    806ec000 8070c380 hal halaacpi.dll Wed Aug 04 06:59:05 2004 (41107B29)
    bf800000 bf9c1180 win32k win32k.sys Thu Oct 06 01:05:44 2005 (43446A58)
    bf9c2000 bf9d3580 dxg dxg.sys Wed Aug 04 07:00:51 2004 (41107B93)
    bf9d4000 bfcb8c60 nv4_disp nv4_disp.dll Sat Sep 15 02:41:46 2001 (3BA2B1DA)
    f11f0000 f11f8080 ipfltdrv ipfltdrv.sys Fri Aug 17 21:55:07 2001 (3B7D84AB)
    f12b6000 f12ca400 wdmaud wdmaud.sys Wed Jun 14 10:00:44 2006 (448FD03C)
    f13bb000 f13de000 Fastfat Fastfat.SYS Wed Aug 04 07:14:15 2004 (41107EB7)
    f1496000 f14a4d80 sysaudio sysaudio.sys Wed Aug 04 07:15:54 2004 (41107F1A)
    f14ce000 f151f480 srv srv.sys Mon Aug 14 11:34:39 2006 (44E051BF)
    f1570000 f159c400 mrxdav mrxdav.sys Wed Aug 04 07:00:49 2004 (41107B91)
    f1941000 f1944280 ndisuio ndisuio.sys Wed Aug 04 07:03:10 2004 (41107C1E)
    f1c57000 f1c6e480 dump_atapi dump_atapi.sys Wed Aug 04 06:59:41 2004 (41107B4D)
    f1d0f000 f1d4eb60 glausb glausb.sys Mon Apr 28 16:09:20 2003 (3EAD4420)
    f1d4f000 f1dbda00 mrxsmb mrxsmb.sys Fri May 05 10:41:42 2006 (445B1DD6)
    f1de6000 f1e10a00 rdbss rdbss.sys Fri May 05 10:47:55 2006 (445B1F4B)
    f1e11000 f1e31f00 ipnat ipnat.sys Wed Sep 29 23:28:36 2004 (415B3714)
    f1e32000 f1e53d00 afd afd.sys Wed Aug 04 07:14:13 2004 (41107EB5)
    f1e54000 f1e7bc00 netbt netbt.sys Wed Aug 04 07:14:36 2004 (41107ECC)
    f1e7c000 f1ed3d80 tcpip tcpip.sys Thu Apr 20 12:51:47 2006 (444775D3)
    f1ed4000 f1ee6400 ipsec ipsec.sys Wed Aug 04 07:14:27 2004 (41107EC3)
    f1f07000 f1f1a000 lzx32 lzx32.sys Mon Jan 15 20:37:04 2007 (45ABE5F0)
    f6f72000 f6f74900 Dxapi Dxapi.sys Fri Aug 17 21:53:19 2001 (3B7D843F)
    f6f7a000 f6fad200 update update.sys Wed Aug 04 06:58:32 2004 (41107B08)
    f6fae000 f6fc6bc0 PPPoEWin PPPoEWin.SYS Thu Sep 25 14:52:45 2003 (3F72F32D)
    f7067000 f7077e00 psched psched.sys Wed Aug 04 07:04:16 2004 (41107C60)
    f7078000 f708e680 ndiswan ndiswan.sys Wed Aug 04 07:14:30 2004 (41107EC6)
    f70d0000 f70e3900 parport parport.sys Wed Aug 04 06:59:04 2004 (41107B28)
    f70e4000 f7106e80 USBPORT USBPORT.SYS Wed Aug 04 07:08:34 2004 (41107D62)
    f7107000 f719b1c0 ltmdmnt ltmdmnt.sys Mon Mar 31 19:29:40 2003 (3E888914)
    f719c000 f71be680 ks ks.sys Wed Aug 04 07:15:20 2004 (41107EF8)
    f71bf000 f71e2980 portcls portcls.sys Wed Aug 04 07:15:47 2004 (41107F13)
    f71e3000 f72a0b80 emu10k1f emu10k1f.sys Thu Sep 13 11:09:45 2001 (3BA085E9)
    f72a1000 f72b4780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 07:07:04 2004 (41107D08)
    f72b5000 f7389920 nv4_mini nv4_mini.sys Sat Sep 15 02:37:30 2001 (3BA2B0DA)
    f738a000 f738c280 rasacd rasacd.sys Fri Aug 17 21:55:39 2001 (3B7D84CB)
    f73ae000 f73b1f00 MODEMCSA MODEMCSA.sys Fri Aug 17 21:57:37 2001 (3B7D8541)
    f73d6000 f73d9c80 mssmbios mssmbios.sys Wed Aug 04 07:07:47 2004 (41107D33)
    f740b000 f7425580 Mup Mup.sys Wed Aug 04 07:15:20 2004 (41107EF8)
    f7426000 f7452a80 NDIS NDIS.sys Wed Aug 04 07:14:27 2004 (41107EC3)
    f7453000 f74df480 Ntfs Ntfs.sys Wed Aug 04 07:15:06 2004 (41107EEA)
    f74e0000 f74f6780 KSecDD KSecDD.sys Wed Aug 04 06:59:45 2004 (41107B51)
    f74f7000 f7508f00 sr sr.sys Wed Aug 04 07:06:22 2004 (41107CDE)
    f7509000 f7528780 fltmgr fltmgr.sys Mon Aug 21 10:14:57 2006 (44E97991)
    f7529000 f7540480 atapi atapi.sys Wed Aug 04 06:59:41 2004 (41107B4D)
    f7541000 f755f880 ftdisk ftdisk.sys Fri Aug 17 21:52:41 2001 (3B7D8419)
    f7560000 f7570a80 pci pci.sys Wed Aug 04 07:07:45 2004 (41107D31)
    f7571000 f759ed80 ACPI ACPI.sys Wed Aug 04 07:07:35 2004 (41107D27)
    f759f000 f75b6800 SPTD3581 SPTD3581.SYS Wed Aug 04 06:59:39 2004 (41107B4B)
    f75b7000 f7688000 sptd sptd.sys Sat Jun 24 10:18:51 2006 (449D037B)
    f76a9000 f76b1c00 isapnp isapnp.sys Fri Aug 17 21:58:01 2001 (3B7D8559)
    f76b9000 f76c7e80 ohci1394 ohci1394.sys Wed Aug 04 07:10:05 2004 (41107DBD)
    f76c9000 f76d6000 1394BUS 1394BUS.SYS Wed Aug 04 07:10:03 2004 (41107DBB)
    f76d9000 f76e3500 MountMgr MountMgr.sys Wed Aug 04 06:58:29 2004 (41107B05)
    f76e9000 f76f5c80 VolSnap VolSnap.sys Wed Aug 04 07:00:14 2004 (41107B6E)
    f76f9000 f7701e00 disk disk.sys Wed Aug 04 06:59:53 2004 (41107B59)
    f7709000 f7715200 CLASSPNP CLASSPNP.SYS Wed Aug 04 07:14:26 2004 (41107EC2)
    f7719000 f7723580 agp440 agp440.sys Wed Aug 04 07:07:40 2004 (41107D2C)
    f7739000 f7747100 usbhub usbhub.sys Wed Aug 04 07:08:40 2004 (41107D68)
    f7749000 f7752480 NDProxy NDProxy.SYS Fri Aug 17 21:55:30 2001 (3B7D84C2)
    f7779000 f7786a80 MpFirewall MpFirewall.sys Fri Dec 06 15:21:21 2002 (3DF0C071)
    f7789000 f7791700 netbios netbios.sys Wed Aug 04 07:03:19 2004 (41107C27)
    f77a9000 f77b1700 wanarp wanarp.sys Wed Aug 04 07:04:57 2004 (41107C89)
    f77c9000 f77d1880 Fips Fips.SYS Sat Aug 18 02:31:49 2001 (3B7DC585)
    f77e9000 f77f8900 Cdfs Cdfs.SYS Wed Aug 04 07:14:09 2004 (41107EB1)
    f7859000 f7861d00 intelppm intelppm.sys Wed Aug 04 06:59:19 2004 (41107B37)
    f7869000 f7877b80 drmk drmk.sys Wed Aug 04 07:07:54 2004 (41107D3A)
    f7879000 f7882080 sfman sfman.sys Fri Aug 31 06:37:56 2001 (3B8F22B4)
    f7889000 f7895e00 i8042prt i8042prt.sys Wed Aug 04 07:14:36 2004 (41107ECC)
    f7899000 f78a8d80 serial serial.sys Wed Aug 04 07:15:51 2004 (41107F17)
    f78a9000 f78b3380 imapi imapi.sys Wed Aug 04 07:00:12 2004 (41107B6C)
    f78b9000 f78c5180 cdrom cdrom.sys Wed Aug 04 06:59:52 2004 (41107B58)
    f78c9000 f78d7080 redbook redbook.sys Wed Aug 04 06:59:34 2004 (41107B46)
    f78d9000 f78e5880 rasl2tp rasl2tp.sys Wed Aug 04 07:14:21 2004 (41107EBD)
    f78e9000 f78f3200 raspppoe raspppoe.sys Wed Aug 04 07:05:06 2004 (41107C92)
    f78f9000 f7904d00 raspptp raspptp.sys Wed Aug 04 07:14:26 2004 (41107EC2)
    f7909000 f7911900 msgpc msgpc.sys Wed Aug 04 07:04:11 2004 (41107C5B)
    f7919000 f7922f00 termdd termdd.sys Wed Aug 04 06:58:52 2004 (41107B1C)
    f7929000 f792f200 PCIIDEX PCIIDEX.SYS Wed Aug 04 06:59:40 2004 (41107B4C)
    f7931000 f7935900 PartMgr PartMgr.sys Sat Aug 18 02:32:23 2001 (3B7DC5A7)
    f7939000 f793de20 PxHelp20 PxHelp20.sys Mon Apr 25 20:48:02 2005 (426D4972)
    f79a9000 f79aeb00 NaiFiltr NaiFiltr.sys Mon Aug 13 20:14:37 2001 (3B78271D)
    f79c1000 f79c8580 Modem Modem.SYS Wed Aug 04 07:08:04 2004 (41107D44)
    f79c9000 f79ce000 usbuhci usbuhci.sys Wed Aug 04 07:08:34 2004 (41107D62)
    f79d1000 f79d7800 usbehci usbehci.sys Wed Aug 04 07:08:34 2004 (41107D62)
    f79d9000 f79da000 fdc fdc.sys unavailable (00000000)
    f79e1000 f79e7000 kbdclass kbdclass.sys Wed Aug 04 06:58:32 2004 (41107B08)
    f79e9000 f79eea00 mouclass mouclass.sys Wed Aug 04 06:58:32 2004 (41107B08)
    f79f1000 f79f5880 TDI TDI.SYS Wed Aug 04 07:07:47 2004 (41107D33)
    f79f9000 f79fd580 ptilink ptilink.sys Fri Aug 17 21:49:53 2001 (3B7D8371)
    f7a01000 f7a05080 raspti raspti.sys Fri Aug 17 21:55:32 2001 (3B7D84C4)
    f7a09000 f7a0e020 wanatw4 wanatw4.sys Tue Jul 16 16:23:14 2002 (3D343A62)
    f7a11000 f7a16000 flpydisk flpydisk.sys Wed Aug 04 06:59:24 2004 (41107B3C)
    f7a21000 f7a26200 vga vga.sys Wed Aug 04 07:07:06 2004 (41107D0A)
    f7a29000 f7a2da80 Msfs Msfs.SYS Wed Aug 04 07:00:37 2004 (41107B85)
    f7a31000 f7a38880 Npfs Npfs.SYS Wed Aug 04 07:00:38 2004 (41107B86)
    f7a51000 f7a57780 USBSTOR USBSTOR.SYS Wed Aug 04 07:08:44 2004 (41107D6C)
    f7a59000 f7a5f500 usbprint usbprint.sys Wed Aug 04 07:01:23 2004 (41107BB3)
    f7a61000 f7a65500 watchdog watchdog.sys Wed Aug 04 07:07:32 2004 (41107D24)
    f7ab9000 f7abc000 BOOTVID BOOTVID.dll Fri Aug 17 21:49:09 2001 (3B7D8345)
    f7b79000 f7b7b600 OMCI OMCI.SYS Tue May 15 00:15:38 2001 (3B00671A)
    f7b95000 f7b97980 gameenum gameenum.sys Wed Aug 04 07:08:20 2004 (41107D54)
    f7b99000 f7b9cc80 serenum serenum.sys Wed Aug 04 06:59:06 2004 (41107B2A)
    f7ba1000 f7ba3580 ndistapi ndistapi.sys Fri Aug 17 21:55:29 2001 (3B7D84C1)
    f7ba9000 f7baab80 kdcom kdcom.dll Fri Aug 17 21:49:10 2001 (3B7D8346)
    f7bab000 f7bac100 WMILIB WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
    f7bad000 f7bae580 intelide intelide.sys Wed Aug 04 06:59:40 2004 (41107B4C)
    f7bc1000 f7bc2b00 ctlface ctlface.sys Wed Jul 11 04:34:51 2001 (3B4BC95B)
    f7bc3000 f7bc4100 swenum swenum.sys Wed Aug 04 06:58:41 2004 (41107B11)
    f7bc5000 f7bc6280 USBD USBD.SYS Fri Aug 17 22:02:58 2001 (3B7D8682)
    f7bcd000 f7bcef00 Fs_Rec Fs_Rec.SYS Fri Aug 17 21:49:37 2001 (3B7D8361)
    f7bcf000 f7bd0080 Beep Beep.SYS Fri Aug 17 21:47:33 2001 (3B7D82E5)
    f7bd1000 f7bd2080 mnmdd mnmdd.SYS Fri Aug 17 21:57:28 2001 (3B7D8538)
    f7bd3000 f7bd4080 RDPCDD RDPCDD.sys Fri Aug 17 21:46:56 2001 (3B7D82C0)
    f7bdf000 f7be0100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
    f7c0d000 f7c0ea80 ParVdm ParVdm.SYS Fri Aug 17 21:49:49 2001 (3B7D836D)
    f7c13000 f7c14100 PfModNT PfModNT.sys Thu Dec 16 04:14:08 1999 (38586710)
    f7c88000 f7c88c00 audstub audstub.sys Fri Aug 17 21:59:40 2001 (3B7D85BC)
    f7d8d000 f7d8dd00 dxgthk dxgthk.sys Fri Aug 17 21:53:12 2001 (3B7D8438)
    f7db9000 f7db9b80 Null Null.SYS Fri Aug 17 21:47:39 2001 (3B7D82EB)
    f7dfb000 f7dfbe80 ctljystk ctljystk.sys Thu Jul 19 23:28:02 2001 (3B575EF2)

    Unloaded modules:
    f1268000 f1293000 kmixer.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7d04000 f7d05000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f1293000 f12b6000 aec.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f1476000 f1483000 DMusic.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f1486000 f1494000 swmidi.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7c39000 f7c3b000 splitter.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7799000 f77a2000 processr.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7a19000 f7a1e000 Cdaudio.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    f7392000 f7395000 Sfloppy.SYS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:\debuglog.txt
     

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.