TechSpot

PC rebooted from a bugcheck- how I fix it?

By AMR4622
Dec 25, 2014
Post New Reply
  1. Specs

    FX 8350 (stockspeed) and H80i watercooler
    Asus M5A78L-M/USB3
    16gb Ram Gskill
    R9 290x XFX DD
    HX 750w Corsair
    SSD 120gb corsair
    HDD 1 TB
    Win 8.1
    -------------------------------------------------------------

    My pc freezes and then it automatically restarts. After a few intents to resolve it I decide to go some support from windows agent but they charge 99$. So I better port it first to see if I can get some last help.

    They told me it was a corruption or maybe an infection but I think I have taken care of it by using Rougue Killer and deleting unwanted programs from regedit.

    After searching ,my event viewer tell me that I has 3 main errors. But 1 error is caused the same time as the other. The event id 20 (whea- logger) and event id 1001 ( Bug check) But I think my main problem is caused by the EVENT ID 1001 that says> The computer has rebooted from a bucheck. Theres a dump saved but I dont know how to read it or what to do next.

    If u need more information regard to something let me know. Thanks!
     
  2. jobeard

    jobeard TS Ambassador Posts: 9,348   +622

    Copy and paste the details on those three events - - -
     
  3. AMR4622

    AMR4622 TS Rookie Topic Starter

    EVENT ID 1001- Bugcheck
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-28T00:19:30.000000000Z" />
    <EventRecordID>17080</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>AMR</Computer>
    <Security />
    </System>
    - <EventData>
    <Data Name="param1">0x00000124 (0x0000000000000000, 0xffffe001a19fe8f8, 0x0000000000000000, 0x0000000000000000)</Data>
    <Data Name="param2">C:\WINDOWS\Minidump\122714-10953-01.dmp</Data>
    <Data Name="param3">122714-10953-01</Data>
    </EventData>
    </Event>

    EVENT ID 20 - Whea-Logger

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">


    - <System>



    <Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{C26C4F3C-3F66-4E99-8F8A-39405CFED220}" />


    <EventID>20</EventID>


    <Version>0</Version>


    <Level>2</Level>


    <Task>0</Task>


    <Opcode>0</Opcode>


    <Keywords>0x8000000000000000</Keywords>


    <TimeCreated SystemTime="2014-12-28T00:19:32.958761800Z" />


    <EventRecordID>17084</EventRecordID>


    <Correlation ActivityID="{3EBFD630-115E-4126-8E8C-C4E6498DC23D}" />


    <Execution ProcessID="1276" ThreadID="2412" />


    <Channel>System</Channel>


    <Computer>AMR</Computer>


    <Security UserID="S-1-5-19" />

    </System>


    - <EventData>



    <Data Name="ErrorSource">3</Data>


    <Data Name="ApicId">0</Data>


    <Data Name="MCABank">4</Data>


    <Data Name="MciStat">0xfe00000000070f0f</Data>


    <Data Name="MciAddr">0xfeac69b8</Data>


    <Data Name="MciMisc">0xc00a0fff01000000</Data>


    <Data Name="ErrorType">7</Data>


    <Data Name="Length">928</Data>


    <Data Name="RawData">435045521002FFFFFFFF03000100000002000000A0030000141300001C0C0E140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB7EC1CAEB3322D00102000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002040000030000200F60000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000200F6000000808000B32983EFFFB8B170000000000000000000000000000000000000000000000000000000000000000B3F8F31CB1C5A249AA595EEF92FFA63C03000000000000009E07C0E607000000B869ACFE000000000000000000000000000000000000000000000000000000000100000002000000DDB50EED3322D0010000000000000000000000000000000000000000040000000F0F0700000000FEB869ACFE0000000000000001FF0F0AC00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>

    </EventData>

    </Event>


    EVENT ID 6008- Event log

    This one tells that the previous shutdown was unexpected


    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="EventLog" />
    <EventID Qualifiers="32768">6008</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-28T00:19:29.000000000Z" />
    <EventRecordID>17058</EventRecordID>
    <Channel>System</Channel>
    <Computer>AMR</Computer>
    <Security />
    </System>
    - <EventData>
    <Data>8:03:35 PM</Data>
    <Data>‎12/‎27/‎2014</Data>
    <Data />
    <Data />
    <Data>2414</Data>
    <Data />
    <Data />
    <Binary>DE070C0006001B001400030023008201DE070C0000001C000000030023008201600900003C000000010000006009000001000000B00400000100000000000000</Binary>
    </EventData>
    </Event>


     
  4. AMR4622

    AMR4622 TS Rookie Topic Starter

    I found a website for uploading the dmp file and this is what it says. Its sas win8 driver fault. But I don't get how, I even used DDU for uninstalling the driver for updating the driver in safe boot mode and all still that happened?



    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
    Online Crash Dump Analysis Service
    See http://www.osronline.com for more information
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.17476.amd64fre.winblue_r5.141029-1500
    Machine Name:
    Kernel base = 0xfffff801`ad085000 PsLoadedModuleList = 0xfffff801`ad35e250
    Debug session time: Sun Dec 28 06:19:59.212 2014 (UTC - 5:00)
    System Uptime: 0 days 0:00:02.912
    *******************************************************************************
    * *
    * 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: ffffe0002c438038, 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:
    ------------------
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    BUGCHECK_STR: 0x124_AuthenticAMD
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    CURRENT_IRQL: 0
    STACK_TEXT:
    ffffd000`ce5e7500 fffff801`ad40bee8 : ffffd000`cddce180 ffffe000`2c438010 ffffe000`2afe7800 fffff801`ad0b8209 : nt!WheapCreateLiveTriageDump+0x81
    ffffd000`ce5e7a30 fffff801`ad24bba4 : ffffe000`2c438010 fffff801`ad36d7a0 ffffe000`2afe7880 fffff801`ad337300 : nt!WheapCreateTriageDumpFromPreviousSession+0x44
    ffffd000`ce5e7a60 fffff801`ad24c9c1 : fffff801`ad36d740 fffff801`ad36d7a0 ffffe000`2afe7880 00000000`00000000 : nt!WheapProcessWorkQueueItem+0x48
    ffffd000`ce5e7aa0 fffff801`ad102acc : fffff801`ad421d00 fffff801`ad24c99c ffffe000`2c2b6a90 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    ffffd000`ce5e7ad0 fffff801`ad186440 : ffffd000`cddda3c0 ffffe000`2afe7880 00000000`00000080 ffffe000`2afe7880 : nt!ExpWorkerThread+0x28c
    ffffd000`ce5e7b80 fffff801`ad1dc0c6 : ffffd000`cddce180 ffffe000`2afe7880 ffffd000`cddda3c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`ce5e7be0 00000000`00000000 : ffffd000`ce5e8000 ffffd000`ce5e1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: AuthenticAMD
    IMAGE_NAME: AuthenticAMD
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Followup: MachineOwner
     

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...