Frequent blue screen of death

By funkad
Aug 25, 2009
Topic Status:
Not open for further replies.
  1. Need help with bsod, wich happened twice today:

    This is from the Event Viewer

    -System Error (102), Error code 1000008e, parameter1 c0000005, parameter2 eb8300b, parameter3 ba8fca74, parameter4 00000000

    Dump file info:

    Loading Dump File [C:\WINDOWS\Minidump\Mini082509-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    WARNING: Inaccessible path: 'ImagePath'
    WARNING: Inaccessible path: 'SymbolPath'
    Symbol search path is: SymbolPath
    Executable search path is: ImagePath
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
    Debug session time: Tue Aug 25 16:39:47.880 2009 (GMT-7)
    System Uptime: 0 days 3:37:11.450
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    ...................
    Unable to load image SYMTDI.SYS, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SYMTDI.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMTDI.SYS
    Unable to load image vsdatant.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for vsdatant.sys
    *** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, eb8b300b, ba8fca74, 0}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** 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 ***
    *** ***
    *************************************************************************
    Probably caused by : SYMTDI.SYS ( SYMTDI+400b )

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

    Hope somebody can make some sense of this...thanks in advance
  2. raybay

    raybay TechSpot Evangelist Posts: 10,716   +6

    Correct brand and model, please, along with configuration.
  3. funkad

    funkad Newcomer, in training Topic Starter

    vaio vgn-a190, pentium M, 1.70GHz, 512 MB of RAM, XP home Service Pack 3
    Never had a single problem with it, except those BSOD since a week or so and haven't change anything on system prior to errors.
    Thanks
  4. raybay

    raybay TechSpot Evangelist Posts: 10,716   +6

    Memory will help... two modules of DDR333 PC2700... then check your case for too much lint, fiber and cooling blockage...
    Then look at the Sony site for upgraded drivers for the video graphics as that is the usual cause.
  5. funkad

    funkad Newcomer, in training Topic Starter

    dust free, and drivers updated already( a while back) no more update for ATI Mobility Radeon 9700...haven't upgraded memory though
    Thanks
  6. Yonniman

    Yonniman Newcomer, in training

    I called microsoft about this problem

    It was an issue caused by an automatic update last night

    Go into safe mode, uninstall the updates from last night, and disable automatic update for a while until this problem is fixed
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.