new HPz800 BSOD


  1. Posts : 2
    Windows 7 Pro x64
       #1

    new HPz800 BSOD


    OS: new installation of Windows 7 x64 Enterprise loaded from disc
    PC: new HP z800

    Our new Hpz800 is BSODing daily it seems. It is a stock Hpz800 with the exception of a brand new Nvidia Quadro FX 580. I didn't see a spot to plug in the auxilary cable that came with the new gfx card to the power supply so i left it out... dunno if that is causing anything. I've ran windows update and installed the MS debugging tools and windows 7 symbols but I get some "could not find module nt list" error when I run the analyze -v command???


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

    Loading Dump File [C:\Windows\Minidump\112910-31808-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: E:\Symbols
    Executable search path is:
    Unable to load image Unknown_Module_f6493657`e392e63a, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Unknown_Module_f6493657`e392e63a
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_f6493657`e392e63a
    Debugger can not determine kernel base address
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a54000 PsLoadedModuleList = 0xfffff800`02c91e50
    Debug session time: Mon Nov 29 14:26:36.160 2010 (UTC - 7:00)
    System Uptime: 0 days 0:28:26.869
    Unable to load image Unknown_Module_f6493657`e392e63a, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Unknown_Module_f6493657`e392e63a
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_f6493657`e392e63a
    Debugger can not determine kernel base address
    Loading Kernel Symbols
    .
    Loading User Symbols
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {0, fffffa800b739028, be000000, 1009f}
    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
    Probably caused by : Unknown_Image
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800b739028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 000000000001009f, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    ------------------
    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

    BUGCHECK_STR: 0x124_GenuineIntel
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    CURRENT_IRQL: 0
    STACK_TEXT:
    fffff800`041b4c50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`02a61565

    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: Unknown_Module
    IMAGE_NAME: Unknown_Image
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    BUCKET_ID: CORRUPT_MODULELIST
    Followup: MachineOwner
    ---------

    any thoughts??? thanks!
      My Computer


  2. Posts : 17,796
    Windows 10, Home Clean Install
       #2

    Welcome
    BC 124 is one of the most difficult to solve, it is a hardware issue
    Here is our best post on the subject
    Stop 0x124 - what it means and what to try
      My Computer


  3. Posts : 2
    Windows 7 Pro x64
    Thread Starter
       #3

    richc46 said:
    Welcome
    BC 124 is one of the most difficult to solve, it is a hardware issue
    Here is our best post on the subject
    Stop 0x124 - what it means and what to try
    Thanks for the reply I'll give that link a try...
      My Computer


 

Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:04.
Find Us