Random Reboots (WHEA-LOGGER ID 20 win error)

Page 1 of 2 12 LastLast

  1. Posts : 17
    Windows 7 Home Premium 64-bit SP1
       #1

    Random Reboots (WHEA-LOGGER ID 20 win error)


    Hi,

    What i'm experiencing are random reboots (it happened 4 times), BUT while i was navigating in google maps, or watching a video on Youtube. Problem started to happen since the case was swapped by a tech to fit my Sapphire Radeon R9 290 Tri-x, which is pretty big...

    I did several tests, and all went fine (memtest86+ 3 passes; Seagate HD diagnostics; Sfc/scannow). I didn't experience any problems during gaming.

    The error codes are (pasted from Win Event Viewer)

    Error 06/12/2014 17:34:37 WMI 10 None
    Error 06/12/2014 17:33:50 WHEA-Logger 20 None ***
    Error 06/12/2014 17:33:49 Service Control Manager 7009 None
    Error 06/12/2014 17:32:55 Kernel-Processor-Power 35 (2) **
    Error 06/12/2014 17:32:55 Kernel-Processor-Power 35 (2)**
    Error 06/12/2014 17:32:55 Kernel-Processor-Power 35 (2)**
    Error 06/12/2014 17:32:55 Kernel-Processor-Power 35 (2)**
    Error 06/12/2014 17:32:55 Kernel-Processor-Power 35 (2) **
    Error 06/12/2014 17:32:55 Kernel-Processor-Power 35 (2)**
    Critical 06/12/2014 17:32:54 Kernel-Power 41 (63) *

    **:

    Log Name: System
    Source: Kernel-Processor-Power
    Date:
    Event ID: 35
    Task Category: (2)
    Level: Error

    Description:
    Performance power management features on processor 0 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware. <-- note that in every "**" error, the processor is different: from "processor 0 in group 0" to "processor 5 in group 0".

    ***:

    Event ID 20 - WHEA-Logger

    A fatal hardware error has occurred.

    Component: AMD Northbridge

    Error Source: Machine Check Exception

    Error Type: HyperTransport Watchdog Timeout Error

    Processor APIC ID: 0

    The details view of this entry contains further information.



    Note that the "**" errors occur every time i boot up the machine...like this:

    Error 07/12/2014 11:48:38 WMI 10 None
    Error 07/12/2014 11:47:42 Service Control Manager 7009 None
    Error 07/12/2014 11:46:52 Kernel-Processor-Power 35 (2)
    Error 07/12/2014 11:46:52 Kernel-Processor-Power 35 (2)
    Error 07/12/2014 11:46:52 Kernel-Processor-Power 35 (2)
    Error 07/12/2014 11:46:52 Kernel-Processor-Power 35 (2)
    Error 07/12/2014 11:46:52 Kernel-Processor-Power 35 (2)
    Error 07/12/2014 11:46:52 Kernel-Processor-Power 35 (2)

    here are my stats:

    Operating System
    Windows 7 Home Premium 64-bit SP1
    CPU
    AMD FX-6350 19 °C
    Vishera 32nm Technology
    RAM
    8,00GB Dual-Channel DDR3 @ 669MHz (9-9-9-24)
    Motherboard
    Gigabyte Technology Co., Ltd. GA-78LMT-S2P (Socket M2) 30 °C
    Graphics
    VG248 (1920x1080@144Hz)
    4096MB ATI AMD Radeon R9 200 Series (Sapphire/PCPartner) 44 °C
    Storage
    465GB Seagate ST500DM002-1BD142 ATA Device (SATA) 26 °C
    Optical Drives
    ELBY CLONEDRIVE SCSI CdRom Device
    ATAPI iHAS524 B ATA Device
    Audio
    Realtek High Definition Audio
    PSU:
    Corsair VS 650W

    ...it happened recently, and i was browsing on firefox again (searching for a flight on Bing). Here it's "Who Crashed" log:

    On Sat 13/12/2014 11:12:08 GMT your computer crashed

    crash dump file: C:\Windows\Minidump\121314-25864-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)

    Bugcheck code: 0x124 (0x0, 0xFFFFFA80082BA8F8, 0x0, 0x0) Error: WHEA_UNCORRECTABLE_ERROR

    file path: C:\Windows\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System company: Microsoft Corporation

    description: NT Kernel & System

    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    A "Thermal issue" seems a bit strange, because HwMonitor showed low temperatures (between 20-35 °C except for the 43 °C of the graphics card). I really don't know what to say...
    Thanks in advance for your help!
      My Computer


  2. Posts : 17
    Windows 7 Home Premium 64-bit SP1
    Thread Starter
       #2

    Update:
    I accidentaly found this error on the Event Viewer, happened few minutes ago:
    Error 14/12/2014 14:15:30 amdacpusrsvc 0 None
    The description for Event ID 0 from source amdacpusrsvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer
    amdacpusrsvc
    acpusrsvc: GraphicsMemory API Wrapper: Dummy Packet Submission FAILED
    ...another similar:
    Error 14/12/2014 14:15:30 amdacpusrsvc 0 None
    The description for Event ID 0 from source amdacpusrsvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer
    amdacpusrsvc
    acpusrsvc: GraphicsMemory API Wrapper: Dummy Packet Submission FAILED
      My Computer


  3. Posts : 17
    Windows 7 Home Premium 64-bit SP1
    Thread Starter
       #3

    Hi,
    anyone???
    Last edited by Sgaroz; 17 Dec 2014 at 16:50.
      My Computer


  4. Posts : 17
    Windows 7 Home Premium 64-bit SP1
    Thread Starter
       #4

    Anyone had this error before?
      My Computer


  5. Posts : 17
    Windows 7 Home Premium 64-bit SP1
    Thread Starter
       #5

    IT HAPPENED AGAIN... with this log (similar to the past one):
    ..Successo di nuovo, stavolta stavo giocando (ad un gioco diverso). Il log di Who Crashed è il seguente:
    On Mon 22/12/2014 00:08:42 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122214-14398-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
    Bugcheck code: 0x124 (0x0, 0xFFFFFA8008338038, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
    This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    ------
    I opened the case to verify if the NB was really overheating...i could stick my finger on it for all night long with no problems, it was just slightly warm.
    I really don't know what to do at this point...I keep on hoping it's a simple driver issue...
      My Computer


  6. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #6

    There aren't any .dmp files in your ZIP file attachment.

    Re-run, but wait until the file is ready:

    1. Download the DM Log Collector application to your desktop by clicking the link below

    DM Log Collector.exe

    2. Run it by double-clicking the icon on your desktop, and follow the prompts.
    3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

      My Computer


  7. Posts : 17
    Windows 7 Home Premium 64-bit SP1
    Thread Starter
       #7

    Ok, i think i managed to attach it correctly...let me know what you think.
    Thanks in advance
      My Computer


  8. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #8

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa8008338038, 0, 0}
    
    Probably caused by : AuthenticAMD
    
    Followup: MachineOwner
    ---------
    Run Very High Test of IBT and report back with screen capture images:
    CPU - Stress Test Using IntelBurnTest
      My Computer


  9. Posts : 17
    Windows 7 Home Premium 64-bit SP1
    Thread Starter
       #9

    There you go: Very High Test succeeded... as you can see in the screenshot in the attachment:
    1. CPU temp never went over 43° (38-40 average)
    2. TMPIN2 of the mobo (which it should be the Northbridge) went around 60° (too high/strange?)
    ...so the CPU should be ok at this point; the RAM was tested a while ago (3 passes-ok); HDD was tested too a while ago...now?
      My Computer


  10. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #10

    3 passes of MemTest86+ isn't sufficient - run a minumum of 8 consecutive passes. Any less, and RAM has not been tested thoroughly enough.
      My Computer


 
Page 1 of 2 12 LastLast

  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 21:12.
Find Us