Blue Screen Error. I have the WinDbg Script


  1. Posts : 2
    windows 7
       #1

    Blue Screen Error. I have the WinDbg Script


    I have recently finished building a new computer and came accross the Bluescreen error message. I wasnt recieving a "stop" message because I'm using win7 I presume?
    But I have followed some steps and I've been told that the next step is to post this script here and hopefully someone will be able to determine my problem (fingers crossed)
    Alot of people keep saying "try remove newly installed hardware and see if the problem persists" but my whole computers new so not really an option. Anyway enough of rambling....

    I'm just copying and pasting this aswel :S hope it displays clear enough


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


    Loading Dump File [C:\Windows\Minidump\041010-18189-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*Symbol information
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e50e50
    Debug session time: Sat Apr 10 11:02:31.265 2010 (GMT+2)
    System Uptime: 0 days 0:00:10.701
    Loading Kernel Symbols
    .................................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa800317f8f8, 0, 0}

    Probably caused by : hardware

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

    1: 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: fffffa800317f8f8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


    BUGCHECK_STR: 0x124_AuthenticAMD

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    STACK_TEXT:
    fffff880`02fb26f0 fffff800`02ecda89 : fffffa80`0317f8d0 fffffa80`018db040 00000000`00000015 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`02fb2c10 fffff800`02daf547 : fffffa80`0317f8d0 fffff800`02e285f8 fffffa80`018db040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`02fb2c40 fffff800`02d17b95 : fffff800`02e8a360 fffffa80`027c11f8 fffffa80`027c11f0 fffffa80`018db040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`02fb2c80 fffff800`02c92161 : fffff880`0104de00 fffff800`02d17b70 fffffa80`018db040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`02fb2cb0 fffff800`02f28166 : 00000000`00000000 fffffa80`018db040 00000000`00000080 fffffa80`0184f9e0 : nt!ExpWorkerThread+0x111
    fffff880`02fb2d40 fffff800`02c63486 : fffff880`009e8180 fffffa80`018db040 fffff880`009f2f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`02fb2d80 00000000`00000000 : fffff880`02fb3000 fffff880`02fad000 fffff880`02fb2560 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

    BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

    ***MiniDump Folder Included now***
    Last edited by Paulj; 09 Apr 2010 at 06:55. Reason: Adding minidump folder
      My Computer


  2. Posts : 11,840
    64-bit Windows 8.1 Pro
       #2

    We will need the actual .dmp file for analysis..

    [1 - Novice] How to ask for help with a BSOD problem
      My Computer


  3. Posts : 2
    windows 7
    Thread Starter
       #3

    Minidump has been added to the bottom of my thread

    Thanks!
      My Computer


  4. Posts : 11,840
    64-bit Windows 8.1 Pro
       #4

    Your .dmp file points to a hardware error...0x124 ...

    [2-Int] Stop 0x124 - what it means and what to try

    Hope this helps..
      My Computer


 

  Related Discussions
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:44.
Find Us