Author Topic: ==> Crash/Hang/Block, please come here <==  (Read 64396 times)

0 Members and 1 Guest are viewing this topic.

Reply #30June 20, 2015, 03:54:29 am

cinder

  • Newbie

  • Offline
  • *

  • 14
  • Reputation:
    0
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #30 on: June 20, 2015, 03:54:29 am »
Many thanks :)

Reply #31June 21, 2015, 05:57:06 pm

Curson

  • Global Moderator
  • Hero Member

  • Offline
  • *****

  • 2332
  • Reputation:
    82
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #31 on: June 21, 2015, 05:57:06 pm »
Hi cinder,

You are very welcome.  ;)

Regards.

Reply #32June 24, 2015, 01:27:24 am

cinder

  • Newbie

  • Offline
  • *

  • 14
  • Reputation:
    0
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #32 on: June 24, 2015, 01:27:24 am »
Hi Curson,

Any progress with this issue at all?

Thanks,
- Natalie.

Reply #33June 24, 2015, 10:53:38 pm

Curson

  • Global Moderator
  • Hero Member

  • Offline
  • *****

  • 2332
  • Reputation:
    82
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #33 on: June 24, 2015, 10:53:38 pm »
Hi Natalie,

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

Regards.

Reply #34June 25, 2015, 05:09:11 am

cinder

  • Newbie

  • Offline
  • *

  • 14
  • Reputation:
    0
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #34 on: June 25, 2015, 05:09:11 am »
Hi,
I'm using 10.8.4.0, is there a later version than this?
- Thanks.

Reply #35June 25, 2015, 05:22:19 am

cinder

  • Newbie

  • Offline
  • *

  • 14
  • Reputation:
    0
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #35 on: June 25, 2015, 05:22:19 am »
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.
« Last Edit: June 25, 2015, 07:12:27 am by cinder »

Reply #36June 25, 2015, 09:01:08 am

cinder

  • Newbie

  • Offline
  • *

  • 14
  • Reputation:
    0
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #36 on: June 25, 2015, 09:01:08 am »
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.

Reply #37June 25, 2015, 10:21:25 pm

Curson

  • Global Moderator
  • Hero Member

  • Offline
  • *****

  • 2332
  • Reputation:
    82
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #37 on: June 25, 2015, 10:21:25 pm »
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.

Reply #38July 16, 2015, 09:23:10 pm

fred3

  • Newbie

  • Offline
  • *

  • 7
  • Reputation:
    0
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #38 on: July 16, 2015, 09:23:10 pm »
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.
« Last Edit: July 17, 2015, 01:24:29 am by fred3 »

Reply #39July 16, 2015, 10:20:55 pm

Curson

  • Global Moderator
  • Hero Member

  • Offline
  • *****

  • 2332
  • Reputation:
    82
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #39 on: July 16, 2015, 10:20:55 pm »
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.

Reply #40July 17, 2015, 01:44:04 am

fred3

  • Newbie

  • Offline
  • *

  • 7
  • Reputation:
    0
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #40 on: July 17, 2015, 01:44:04 am »
Here they are:

Reply #41July 18, 2015, 12:54:27 am

Curson

  • Global Moderator
  • Hero Member

  • Offline
  • *****

  • 2332
  • Reputation:
    82
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #41 on: July 18, 2015, 12:54:27 am »
Hi fred3,

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

Regards.

Reply #42July 18, 2015, 05:20:46 am

fred3

  • Newbie

  • Offline
  • *

  • 7
  • Reputation:
    0
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #42 on: July 18, 2015, 05:20:46 am »
Yes, the system is completely up to date....

Reply #43July 19, 2015, 05:36:27 pm

fred3

  • Newbie

  • Offline
  • *

  • 7
  • Reputation:
    0
    • View Profile
Re: ==> Crash/Hang/Block, please come here <==
« Reply #43 on: July 19, 2015, 05:36:27 pm »
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.

Reply #44July 21, 2015, 09:36:53 am

Tigzy

  • Administrator
  • Hero Member

  • Offline
  • *****

  • 829
  • Reputation:
    91
  • Personal Text
    Owner, Adlice Software
    • View Profile
    • Adlice Software
Re: ==> Crash/Hang/Block, please come here <==
« Reply #44 on: July 21, 2015, 09:36:53 am »
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?