• 16.04.2024, 06:23
  • Registrieren
  • Anmelden
  • Sie sind nicht angemeldet.

 

Lieber Besucher, herzlich willkommen bei: Aqua Computer Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.

Aqua Computer Service hold CPU high randomly and crash with bluescreen.

Dienstag, 6. August 2019, 13:08

windows 10 64bit pro.

first,
from the old aquasuite(2017and 2018 version) what I used until today,
Aqua Computer Service randomly hanging CPU resource too high.

CPU temperature being up to 50~60 degree C, from normal 40~45 degree C at IDLE.
it could be solved when I manually restart the service.

second,
I updated aquasuite to X4 today and I remove previous installed service because of reason what I wrote above,
after remove by windows console command, re-install Aqua Computer Service from aquasuite program.
few minutes after the install, suddenly windows bluescreen crash happen.
it only said about IRQL_NOT_LESS_OR_EQUAL.
I got minidump file so analyze by winDBG program.
here is the analyzed result of minidmp file.
in analyzed result, I found PROCESS_NAME: AquaComputerSe
so, this BSOD crash from aquacomputer service

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000000000b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff801342fa6fa, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 4

Key : Analysis.Elapsed.Sec
Value: 4

Key : Analysis.Memory.CommitPeak.Mb
Value: 70

Key : Dump.Attributes.InsufficientDumpfileSize
Value: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.18362.267 (WinBuild.160101.0800)

DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump

DUMP_TYPE: 2

BUGCHECK_P1: b8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff801342fa6fa

READ_ADDRESS: fffff801347713b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
00000000000000b8

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiUnlockPageTableInternal+a
fffff801`342fa6fa 0fb691b8000000 movzx edx,byte ptr [rcx+0B8h]

CPU_COUNT: 10

CPU_MHZ: bb8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3f

CPU_STEPPING: 2

CPU_MICROCODE: 6,3f,2,0 (F,M,S,R) SIG: 43'00000000 (cache) 43'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: AquaComputerSe

ANALYSIS_SESSION_HOST: JIT-CAN

ANALYSIS_SESSION_TIME: 08-06-2019 19:53:54.0219

ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

TRAP_FRAME: ffff8484dabe93f0 -- (.trap 0xffff8484dabe93f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb88000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffb8dc40991438 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801342fa6fa rsp=ffff8484dabe9588 rbp=ffff8484dabe96c0
r8=0000000000000000 r9=ffffb8dc40991438 r10=0000000000000000
r11=0000007ffffffff8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po nc
nt!MiUnlockPageTableInternal+0xa:
fffff801`342fa6fa 0fb691b8000000 movzx edx,byte ptr [rcx+0B8h] ds:00000000`000000b8=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff801343d1ae9 to fffff801343bfcc0

STACK_TEXT:
ffff8484`dabe92a8 fffff801`343d1ae9 : 00000000`0000000a 00000000`000000b8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff8484`dabe92b0 fffff801`343cde2b : ffffb8dc`6e204000 ffff8484`dabe96d0 fffff801`342accf1 ffff8484`dabe96d0 : nt!KiBugCheckDispatch+0x69
ffff8484`dabe93f0 fffff801`342fa6fa : 00000000`00000000 00000003`35072451 000000f6`90610000 ffffd50c`975ad580 : nt!KiPageFault+0x46b
ffff8484`dabe9588 fffff801`3426f106 : ffff8484`dabe96d0 00000264`00000002 fffff801`00000001 ffffb8dc`00000000 : nt!MiUnlockPageTableInternal+0xa
ffff8484`dabe95c8 00000000`00000000 : ffff8484`dabe99e0 ffff8484`dabe9b80 fffff801`347d65d2 00000000`00000000 : nt!MiQueryAddressState+0xc96


THREAD_SHA1_HASH_MOD_FUNC: 6fbecbdf71cc502c076807292ade73cd8b2f4df3

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3a2e2381b35efd32434153bbf61b0d444af67e80

THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84

FOLLOWUP_IP:
nt!MiUnlockPageTableInternal+a
fffff801`342fa6fa 0fb691b8000000 movzx edx,byte ptr [rcx+0B8h]

FAULT_INSTR_CODE: b891b60f

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiUnlockPageTableInternal+a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 74da155a

IMAGE_VERSION: 10.0.18362.267

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: a

FAILURE_BUCKET_ID: AV_nt!MiUnlockPageTableInternal

BUCKET_ID: AV_nt!MiUnlockPageTableInternal

PRIMARY_PROBLEM_CLASS: AV_nt!MiUnlockPageTableInternal

TARGET_TIME: 2019-08-06T10:01:31.000Z

OSBUILD: 18362

OSSERVICEPACK: 267

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2032-02-15 18:16:10

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.18362.267

ANALYSIS_SESSION_ELAPSED_TIME: 126f

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!miunlockpagetableinternal

FAILURE_ID_HASH: {fdd0de49-46dd-5792-449c-2e88bc15a9b1}

Followup: MachineOwner
---------

Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von »JIT« (6. August 2019, 15:18)

Freitag, 30. August 2019, 14:57

Do you have a new Ryzen system? I saw posts, that hardware monitoring programs can pull the processor unnecessarily from idle state. That might be the reason for your cpu temp.

Samstag, 31. August 2019, 08:27

have you other monitoring software active?
When you dont need aqua computer monitoring, deactivate the functions that you do not need (aquasuite->service)