1. TechSpot is dedicated to computer enthusiasts and power users. Ask a question and give support. Join the community here.
    TechSpot is dedicated to computer enthusiasts and power users.
    Ask a question and give support.
    Join the community here, it only takes a minute.
    Dismiss Notice

Windows 2008 R2 BSOD

By renoux
May 21, 2018
Post New Reply
  1. Hi. I need help with a BSOD.
    It is on a Windows 2008 R2 Standard server.
    I have started receiving the BSOD one month apart for the last 3 months. I am unable to confirm if the error is hardware or software related and would be very happy if someone can confirm what exactly I need to be looking for. Minidump as follows:
    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
    Online Crash Dump Analysis Service
    See OSR Online - The Home Page for Windows Driver Developers for more information
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: LanManNt, suite: TerminalServer SingleUserTS
    Built by: 7601.24117.amd64fre.win7sp1_ldr_escrow.180422-1430
    Machine Name:
    Kernel base = 0xfffff800`01e0e000 PsLoadedModuleList = 0xfffff800`0204dc90
    Debug session time: Thu May 17 22:04:16.551 2018 (UTC - 4:00)
    System Uptime: 9 days 0:29:23.409
    *******************************************************************************
    * *
    * 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: 0000000000000005, Generic Error
    Arg2: fffffa800d46d028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000
    Arg4: 0000000000000000

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

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    BUGCHECK_STR: 0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT_SERVER

    PROCESS_NAME: System

    CURRENT_IRQL: f

    STACK_TEXT:
    fffff880`01f00d38 fffff800`024039ef : 00000000`00000124 00000000`00000005 fffffa80`0d46d028 00000000`00000000 : nt!KeBugCheckEx
    fffff880`01f00d40 fffff800`01fa5c8f : 00000000`00000001 fffffa80`0d470000 00000000`00000000 00000000`00000000 : hal!HalBugCheckSystem+0x1e3
    fffff880`01f00d80 fffff800`023fd716 : fffffa80`00002140 fffffa80`0d27fbf0 fffff880`01f00e70 fffff800`0241a490 : nt!WheaReportHwError+0x26f
    fffff880`01f00de0 fffff800`01f282f4 : fffff880`01f00fb0 00000000`00000001 00000000`00000001 00000000`00000000 : hal!HalHandleNMI+0x66
    fffff880`01f00e10 fffff800`01ebcb02 : fffff880`01ef2180 00000000`00000000 00000000`00000000 00000000`00000003 : nt!KiProcessNMI+0x184
    fffff880`01f00e70 fffff800`01ebc8df : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
    fffff880`01f00fb0 fffff800`0240e762 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x45f
    fffff880`01f21b68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalProcessorIdle+0x2


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: GenuineIntel

    IMAGE_NAME: GenuineIntel

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN

    BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN

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

    Thank you. Any help would be appreciated!
     
  2. Cycloid Torus

    Cycloid Torus Stone age computing. Posts: 3,564   +950

    I'm a 'tinkerer' and here is 'tinkering' advice.

    Just in general, the error indicates that there is something wrong with hardware or driver (thanks, Microsoft for being so explicit). Some folks have found that the cause is heat related (might tie in with a monthly heavy load process). Further helpful advice (which is a lot like look everywhere, check everything) is: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/blue-screen-data

    Device Manager is first stop. Then memtest86 for a nice long run of continuous tests..

    I often find better success checking 'Reliability Monitor' (https://www.howtogeek.com/166911/re...windows-troubleshooting-tool-you-arent-using/) which hopefully is part of your OS. Check Event Viewer as it might disclose a cascading error.
     

Similar Topics

Add your comment to this article

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