==> Crash/Hang/Block, please come here <==

[cinder]

Many thanks

[Curson]

Hi cinder,

You are very welcome. 

Regards.

[cinder]

Hi Curson,

Any progress with this issue at all?

Thanks,
- Natalie.

[Curson]

Hi Natalie,

RogueKiller was updated lately.
Could you please give this latest version a try ?

Regards.

[cinder]

Hi,
I'm using 10.8.4.0, is there a later version than this?
- Thanks.

[cinder]

I have just run version 10.8.6.0 and it still causes the BSOD. I was watching to see which process it was currently checking and it was taskeng.exe, not sure if that helps. Dump seems to be the same.

I did some of my own 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: 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
_________________________________________________________________________
So is this indicating an issue with my CPU? I'm now worried!

By the way, the BSOD occurs on random process scans, not just the one I mentioned earlier. so that taskeng.exe is unrelated.

[cinder]

I have removed the offending software, which turned out to be Gigabyte utilities for my motherboard. FYI for future reference if anyone else is having this issue.

[Curson]

Hi Natalie,

Thanks for the heads-up.
RogueKiller's driver is currently refactored. We will do our best to ensure compatibility with Gigabyte software in the future.

Thanks again.
Regards.

[fred3]

RK won't run.
procdump failed when trying to capture the RK crash.
Here is the error:[img][img]
NOTE: the failing program is called "anti~mal~ware tool" instead of RogueKiller!!  ??
This on Windows XP Home 32 on AMD 32.  Panda running.

[Curson]

Hi fred3,

Welcome to Adlice.com Forum.
Could you please repost the image showing procdump failling attempt ? You didn't include the link in your previous post.

Regards.

[fred3]

Here they are:

[Curson]

Hi fred3,

That's problematic.
Is your system up-to-date ?

Regards.

[fred3]

Yes, the system is completely up to date....

[fred3]

I'm beginning to think that there's an incompatibility with this hardware and the most recent RogueKiller.
A very similar issue exists with the latest Malwarebytes.
See:
https://forums.malwarebytes.org/index.php?/topic/170525-malwarebytes-anti-malware-version-2181057-is-not-working/
Note that they have developed a workaround (I"ve not tested it yet).

On this system:
Google Chrome (the latest) will not install and the installer says it's incompatible with the hardware.
Firefox will install.  Bitdefender will install.  They both work fine.
Malwarebytes, in an older version will install and run but not the latest version.

[Tigzy]

Hello Fred3, could you say if you see the same crash happening with OLD RogueKiller interface?
Can you tell me what Processor is your machine?