TechSpot

BSOD with Windows XP SP3 and nero Express or Daemon tools

By commanderapocal
Sep 28, 2008
  1. Hello friends,

    im asking for help, because I can´t solve this problem alone.

    Everytime, EVERY i try to install nero express 7.2.7.0 or Daemon Tools 3.47, my computer freezes with a BSOD.

    The system is stable, but if I try to install those programas, he will give me the crash. I already changed my memory module, disconnected both my video card and Combo DVD-ROM drive and SATA HD, but the error persists.

    Im in dire need of help. Thanks a lot for any help!


    this is the crash dump:

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

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    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) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Sun Sep 28 14:36:27.093 2008 (GMT-3)
    System Uptime: 0 days 0:00:52.828
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    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
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 805620ee, f4105ce4, 0}

    ***** 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 ***
    *** ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : ntoskrnl.exe ( nt+8b0ee )

    Followup: MachineOwner
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    1. Run chkdsk.

    2. 0x8E errors are hardware issues. Run a diagnostics on your harddrive.

    3. You may need to do a Windows repair.
     
  3. commanderapocal

    commanderapocal TS Rookie Topic Starter

    Ok, here are the current news.

    1-Chkdsk found no errors.
    2- I´ve run in my system Spinrite in level 2. No problem in windows partition was found.
    3- Windows repair done, no sucess.

    here is what I tried - Installed new version of daemon tools, and it installed without problems. But as I need SPTD to use new version of daemon, it is causing problems with my windows xp (ie., cd-rom TOO slow).

    Any suggestions? Should I reinstall windows SP2 to test?

    thanks a lot
     
  4. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    I think it is more of a daemons tool issue than XP. Are you getting any problems from anywhere else other than with this software?

    What does the manufacture have to say about possible issues?
     
  5. commanderapocal

    commanderapocal TS Rookie Topic Starter

    friend, definitively my hardware has a problem.

    I changed my cd-rom drive, and hard disk (swaped sata and IDE), and reinstalled windows sp3 and tried installing sp2 too, and still i am getting those annoying freezes.

    I am unable to use/install CD-ROM or HD devices softwares. Everytime I try to install any of them, i got a BSOD. I´ve noted, i got sometimes different bsods.

    here are some of the programs that my computer simply won´t install.
    Daemon tools 3.47
    Nero Express
    Alcohol Burning Rom
    Partition Magic 8.0



    Im getting sometimes different errors codes. Im starting to suspect two pieces: Or my motherboard has a problem, or my power supply.

    BugCheck 1000008E, {c0000005, 805620ee, f4105ce4, 0}
    BugCheck 10000050, {cd987a89, 8, cd987a89, 0}
    BugCheck 1000008E, {c000001d, f40e7843, ba3bece0, 0}

    Any suggestions? Anything would be helpful..

    thanks a lot
     
  6. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Have you overclocked anything?

    The thing is those error codes are pointing to hardware issues as you said.

    I know you have used Spinrite, but have you scanned your harddrive with your harddrive manudfacture's own diagnostic utility?
     
  7. commanderapocal

    commanderapocal TS Rookie Topic Starter

    No, I don´t overclock (it´s against my religion :stickout: )

    No, the fact is I can´t burn a cd-rom to test it.

    But, i´ve tested it with three different hard disks (all samsungs, two IDE SP0802N and one sata SP1614C), and all of them gave me those errors (installed windows XP in all of them, a lot boring :dead: ).

    Im gonna try disabling everything I can in bios.
     
  8. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    LOL!

    Anyway, Seagate Tools is a very good utility that you don't need to burn to a CD and it works on many models.

    I am just wondering if it isn't the SATA/IDE controllers
     
  9. commanderapocal

    commanderapocal TS Rookie Topic Starter

    Okay.

    All tests in sea tools done, no errors found.

    Deleted Windows XP drive Partitions Controllers, and still got BSODS.

    I think i´ve tried everything, and I believe in two solutions:
    1) Buy a new motherboard
    2) Await for a new Driver for it

    Any test before I ask for a refund?
     
  10. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    I was thinking if if it might not be your motherboard as I was writing my last reply. I am wondering if it is the onboard controllers.

    One other shot: How are the cables? Have you tried to switch your cables?
     
  11. commanderapocal

    commanderapocal TS Rookie Topic Starter

    yes. Both IDE and sata cables.

    =/:monkey:

    Im almost giving up :(
     
  12. kimsland

    kimsland Ex-TechSpotter Posts: 14,524

    I'd strongly suggest un-installing daemon tools
    Then testing again

    daemon tools has been the cause of many varied MiniDumps
     
  13. commanderapocal

    commanderapocal TS Rookie Topic Starter

    I give up.

    Magic Iso is working, just like image burn. I will use them both to substitute daemon tools and nero express.

    Im starting installing heavy-programs, and my games. If I see any problem, I will post here. Any solution, Im still watching this thread, at least to the end of year.

    I aprecciated your help, thanks a lot guys.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...