BSOD when running RogueKiller (same point every time)


  1. Posts : 8
    Windows 7 Ultimate x64
       #1

    BSOD when running RogueKiller (same point every time)


    I'll start off by saying I also have a thread open with Rogue Killer support and am currently awaiting their assistance. In the meantime I want to rule out a hardware or driver error.

    Basically upon initialisation of Rogue Killer (process checking) the PC will BSOD at approximately 80% though the process it's currently scanning appears to be random.

    Here is what I have been able to determine from analysing the crash dump:

    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: fffffa8011fbe8f8, 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_GenuineIntel

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

    STACK_TEXT:
    fffff880`039935b0 fffff800`03912cb9 : fffffa80`11fbe8d0 fffffa80`0ca53040 00000000`00000001 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`03993ad0 fffff800`037f3157 : fffffa80`11fbe8d0 fffff800`0386d2d8 fffffa80`0ca53040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`03993b00 fffff800`0375a505 : fffff800`038ced00 00000000`00000001 00000000`00000000 fffffa80`0ca53040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`03993b40 fffff800`036cfa95 : fffff880`01850400 fffff800`0375a4e0 fffffa80`0ca53000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`03993b70 fffff800`03964b8a : 00000000`00000000 fffffa80`0ca53040 00000000`00000080 fffffa80`0ca1a9e0 : nt!ExpWorkerThread+0x111
    fffff880`03993c00 fffff800`036b78e6 : fffff880`03774180 fffffa80`0ca53040 fffff880`0377f0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03993c40 00000000`00000000 : fffff880`03994000 fffff880`0398e000 fffff880`03993560 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND: kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: GenuineIntel

    IMAGE_NAME: GenuineIntel

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    IMAGE_VERSION:

    FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

    BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae_prv

    FAILURE_ID_HASH: {435e2195-e498-1e77-0526-f8d7450275e5}

    Followup: MachineOwner
    ___

    ===============================================================================
    Common Platform Error Record @ fffffa8011fbe8f8
    -------------------------------------------------------------------------------
    Record Id : 01d0683f2e8df525
    Severity : Fatal (1)
    Length : 928
    Creator : Microsoft
    Notify Type : Machine Check Exception
    Timestamp : 3/27/2015 3:36:20 (UTC)
    Flags : 0x00000002 PreviousError

    ===============================================================================
    Section 0 : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor @ fffffa8011fbe978
    Section @ fffffa8011fbea50
    Offset : 344
    Length : 192
    Flags : 0x00000001 Primary
    Severity : Fatal

    Proc. Type : x86/x64
    Instr. Set : x64
    Error Type : Micro-Architectural Error
    Flags : 0x00
    CPU Version : 0x00000000000306c3
    Processor ID : 0x0000000000000000

    ===============================================================================
    Section 1 : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor @ fffffa8011fbe9c0
    Section @ fffffa8011fbeb10
    Offset : 536
    Length : 128
    Flags : 0x00000000
    Severity : Fatal

    Local APIC Id : 0x0000000000000000
    CPU Id : c3 06 03 00 00 08 10 00 - ff fb fa 7f ff fb eb bf
    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

    Proc. Info 0 @ fffffa8011fbeb10

    ===============================================================================
    Section 2 : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor @ fffffa8011fbea08
    Section @ fffffa8011fbeb90
    Offset : 664
    Length : 264
    Flags : 0x00000000
    Severity : Fatal

    Error : Internal unclassified (Proc 0 Bank 1)
    Status : 0xbf80000000200401
    Address : 0x00000000fee00000
    Misc. : 0x0000000000000086
    _________________________________________________________________________

    I am not convinced this is a hardware issue, but I need some help to confirm. I have monitored the CPU temp whilst running Rogue Killer and it doesn't hit above 39 degrees. It is not overclocked (in fact, non overclockable CPU). I gave Prime95 a quick run but I was worried seeing the temps hit 85 degrees so I stopped it, as I didn't want to risk the CPU (it's Haswell and I know they run hot). I need some further assistance trying to determine the culprit. Many thanks!

    Motherboard BIOS is up to date.
    Last edited by cinder; 25 Jun 2015 at 20:00. Reason: Attachment removed
      My Computer


  2. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #2

    After doing some searching on Google I was able to resolve this by removing the Gigabyte software from my machine (2 other threads on your site indicating this was the problem). RogueKiller now scans without a BSOD. My question is, I was unable to determine that Gigabyte software was responsible from my analysis - how can you determine which driver is causing the dump?

    For example my analysis only came up with:
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    PROCESS_NAME: System

    Whereas in your other threads you were able to see:
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    PROCESS_NAME: thermald.exe
    which is the Gigabyte related file. Was mine different or I hadn't debugged in the same way?

    Many thanks (this would help me for next time I have a problem).
      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 10:17.
Find Us