TechSpot

Frequeny BSODs on new computer

By Prauss123
Nov 17, 2009
  1. Hi,

    I recently built my computer, around 2 months ago. Just about a month ago, I've been receiving frequency BSODs (around 4 - 5 times per week now). I've ran Prime95, Memtest and other checks on my computer, they all seem to be fine.

    Here are the components of my computer if it helps. I am using Windows XP Professional SP2 for my OS:

    Processor: AMD Phenom II X3 2.6Ghz
    Video card: Sapphire Radeon HD 4850 512Mb GDDR3
    HDD: Seagate Barracuda 7200.12 500Gb SATA2 OEM
    RAM: OCZ DDR3-10666+ 2048Mb (2 x 1024Mb)

    The crash time is normally right after I log into windows, when all the processes are initiating.

    Here's my most recent minidump log:

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


    Loading Dump File [C:\Documents and Settings\Stan\My Documents\Debugging Info\Mini111709-02.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 2) MP (3 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Tue Nov 17 17:49:32.375 2009 (GMT-5)
    System Uptime: 0 days 0:00:51.187
    *********************************************************************
    * 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 7F, {0, 0, 0, 0}

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

    *** WARNING: Unable to verify timestamp for ACPI.sys
    *** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
    *** WARNING: Unable to verify timestamp for wmiacpi.sys
    *** ERROR: Module load completed but symbols could not be loaded for wmiacpi.sys
    *** WARNING: Unable to verify timestamp for WMILIB.SYS
    *** ERROR: Module load completed but symbols could not be loaded for WMILIB.SYS
    *************************************************************************
    *** ***
    *** ***
    *** 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 : wmiacpi.sys ( wmiacpi+bc6 )

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

    0: kd> !analyze -v


    Any comment, suggestions, insights, solutions and help is appreciated! Thank you!
     
  2. raybay

    raybay TS Evangelist Posts: 7,241   +9

    Did you run MemTest86 on only one module at a time and for at least four hours or seven passes, whichever is longer.

    Is your memory full strength, or is it value ram?

    What is the brand and model of your power supply?
     
  3. Prauss123

    Prauss123 TS Rookie Topic Starter

    Hi rabay,

    Yes I ran MemTest86 on both modules for over 100% testing, no errors.

    My memory I would probably classify as full strength since it is DDR3 and it operates at 533Mhz. Plus it's OCZ :D

    My power supply is a OCZ ModXStream Pro 600W ATX 20/24PIN Active PFC Power supply. It's a modular power supply so I can change the different wires to accomodate from different components, which is kinda neat. I should also mention that my PSU runs at like 80 degrees idle!

    Thanks
     
  4. raybay

    raybay TS Evangelist Posts: 7,241   +9

    I am assuming that by "both modues" you mean one at a time for the full four hours each.


    Don't have a clue, but my cynical self finds the problem is usually in the video graphics card or the video graphics drivers...

    We never consider memory "full strength" and OCZ is no better than any other brand.

    But my guess it you will find the problem is in video card or driver, or a memory module... unless your CPU is getting too hot from too much thermal past. What do your temps show? Or what are you running at the times the BSOD's shut you down?
     
  5. Prauss123

    Prauss123 TS Rookie Topic Starter

    I am assuming that by "both modues" you mean one at a time for the full four hours each.


    Yeah it miiight be the my video card or drivers since ATI has a record of producing...unstable...hardware. However, if my video card were to be faulty, I think I would've seen symptoms as soon as I started using it. My video drivers are all updated, but then again some parts might be corrupted.

    I normally get BSODs about 10 seconds after I log into my account. So basically, I get a BSOD when I just begin to use my computer and had not opened any programs.

    Could it just be an ACPI driver problem? But then again theres that ntskrnl error..

    Thanks for the reply :D
     
  6. Prauss123

    Prauss123 TS Rookie Topic Starter

    UPDATE: New error message! I left my computer idle for around 20 minutes and I got a fatal system error!

    STOP: c000021a (Fatal system error) 0xc0000005 (0x16f000e8 0x033ff1ec)

    Any more help / suggestions about either errors is appreciated!
     
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...