defeater
12-02-2018, 23:35
Ciao a tutti è da un po di tempo che casualmente il pc si riavvia. Non compare nessuna BSOD ma dopo ho un file .dmp
Mi è capitato alcune volte giocando ed altre volte semplicemente usando Word
Allego il dmp analizzato con windbg.
Vedo alcune riferimenti che mi fanno pensare al processore FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
PRIMARY_PROBLEM_CLASS: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Cosa ne pensate?
Configurazione hw:
CPU AMD PHENOM X2 1055T
GPU AMD R9 270X 2 GB
SSD 840 EVO 120 GB
HDD 1.5TB
10GB RAM
Microsoft (R) Windows Debugger Version 10.0.17074.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\andre\Desktop\021318-16500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 16299 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`67284000 PsLoadedModuleList = 0xfffff800`675eafd0
Debug session time: Tue Feb 13 00:09:08.948 2018 (UTC + 1:00)
System Uptime: 0 days 0:00:02.685
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
.........
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, ffff89817d1ef8f8, 0, 0}
Probably caused by : AuthenticAMD
Followup: MachineOwner
---------
nt!WheapCreateLiveTriageDump+0x7b:
fffff800`679e2b33 48895c2438 mov qword ptr [rsp+38h],rbx ss:0018:fffff20d`b01a1728=ffff898100000910
4: kd> !analyze -v
*******************************************************************************
* *
* 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: ffff89817d1ef8f8, 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:
------------------
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.16299.214 (WinBuild.160101.0800)
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: ffff89817d1ef8f8
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BUGCHECK_STR: 0x124_AuthenticAMD
CPU_COUNT: 6
CPU_MHZ: afd
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 10
CPU_MODEL: a
CPU_STEPPING: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: BOSS-PC
ANALYSIS_SESSION_TIME: 02-13-2018 00:28:41.0319
ANALYSIS_VERSION: 10.0.17074.1002 amd64fre
STACK_TEXT:
fffff20d`b01a16f0 fffff800`676bab15 : ffff8981`7c198040 ffff8981`7d1ef8d0 ffff8981`7b71dcb0 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x7b
fffff20d`b01a1c20 fffff800`67509d98 : ffff8981`7d1ef8d0 00000000`00001000 fffff803`00000000 ffff8981`7d3a0040 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
fffff20d`b01a1c50 fffff800`6750a8bb : fffff800`675dbe20 fffff800`675dbe20 ffff8981`7b71dcb0 fffff803`882271e0 : nt!WheapProcessWorkQueueItem+0x48
fffff20d`b01a1c90 fffff800`672a5145 : ffff8981`7b71dcb0 ffff8981`7c198040 fffff803`00000000 ffff8981`00000200 : nt!WheapWorkQueueWorkerRoutine+0x2b
fffff20d`b01a1cc0 fffff800`6739b6e7 : ffff8981`7c198040 00000000`00000080 ffff8981`7b6d3440 ffff8981`7c198040 : nt!ExpWorkerThread+0xf5
fffff20d`b01a1d50 fffff800`67401036 : fffff800`65fef180 ffff8981`7c198040 fffff800`6739b6a0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
fffff20d`b01a1da0 00000000`00000000 : fffff20d`b01a2000 fffff20d`b019c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
THREAD_SHA1_HASH_MOD_FUNC: 26acd050bd9f055d0a04825d57b9e0e6be9c1a07
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e1ca14ad460db17fee32f4b133c79439b72309bb
THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
PRIMARY_PROBLEM_CLASS: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
TARGET_TIME: 2018-02-12T23:09:08.000Z
OSBUILD: 16299
OSSERVICEPACK: 214
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: 2018-01-17 21:38:31
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.16299.214
ANALYSIS_SESSION_ELAPSED_TIME: 770
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_bus_prv
FAILURE_ID_HASH: {6fd7875b-9a1b-9e09-d6d6-816026a875c8}
Followup: MachineOwner
---------
Mi è capitato alcune volte giocando ed altre volte semplicemente usando Word
Allego il dmp analizzato con windbg.
Vedo alcune riferimenti che mi fanno pensare al processore FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
PRIMARY_PROBLEM_CLASS: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Cosa ne pensate?
Configurazione hw:
CPU AMD PHENOM X2 1055T
GPU AMD R9 270X 2 GB
SSD 840 EVO 120 GB
HDD 1.5TB
10GB RAM
Microsoft (R) Windows Debugger Version 10.0.17074.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\andre\Desktop\021318-16500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 16299 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`67284000 PsLoadedModuleList = 0xfffff800`675eafd0
Debug session time: Tue Feb 13 00:09:08.948 2018 (UTC + 1:00)
System Uptime: 0 days 0:00:02.685
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
.........
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, ffff89817d1ef8f8, 0, 0}
Probably caused by : AuthenticAMD
Followup: MachineOwner
---------
nt!WheapCreateLiveTriageDump+0x7b:
fffff800`679e2b33 48895c2438 mov qword ptr [rsp+38h],rbx ss:0018:fffff20d`b01a1728=ffff898100000910
4: kd> !analyze -v
*******************************************************************************
* *
* 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: ffff89817d1ef8f8, 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:
------------------
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.16299.214 (WinBuild.160101.0800)
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: ffff89817d1ef8f8
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BUGCHECK_STR: 0x124_AuthenticAMD
CPU_COUNT: 6
CPU_MHZ: afd
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 10
CPU_MODEL: a
CPU_STEPPING: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: BOSS-PC
ANALYSIS_SESSION_TIME: 02-13-2018 00:28:41.0319
ANALYSIS_VERSION: 10.0.17074.1002 amd64fre
STACK_TEXT:
fffff20d`b01a16f0 fffff800`676bab15 : ffff8981`7c198040 ffff8981`7d1ef8d0 ffff8981`7b71dcb0 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x7b
fffff20d`b01a1c20 fffff800`67509d98 : ffff8981`7d1ef8d0 00000000`00001000 fffff803`00000000 ffff8981`7d3a0040 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
fffff20d`b01a1c50 fffff800`6750a8bb : fffff800`675dbe20 fffff800`675dbe20 ffff8981`7b71dcb0 fffff803`882271e0 : nt!WheapProcessWorkQueueItem+0x48
fffff20d`b01a1c90 fffff800`672a5145 : ffff8981`7b71dcb0 ffff8981`7c198040 fffff803`00000000 ffff8981`00000200 : nt!WheapWorkQueueWorkerRoutine+0x2b
fffff20d`b01a1cc0 fffff800`6739b6e7 : ffff8981`7c198040 00000000`00000080 ffff8981`7b6d3440 ffff8981`7c198040 : nt!ExpWorkerThread+0xf5
fffff20d`b01a1d50 fffff800`67401036 : fffff800`65fef180 ffff8981`7c198040 fffff800`6739b6a0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
fffff20d`b01a1da0 00000000`00000000 : fffff20d`b01a2000 fffff20d`b019c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
THREAD_SHA1_HASH_MOD_FUNC: 26acd050bd9f055d0a04825d57b9e0e6be9c1a07
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e1ca14ad460db17fee32f4b133c79439b72309bb
THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
PRIMARY_PROBLEM_CLASS: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
TARGET_TIME: 2018-02-12T23:09:08.000Z
OSBUILD: 16299
OSSERVICEPACK: 214
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: 2018-01-17 21:38:31
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.16299.214
ANALYSIS_SESSION_ELAPSED_TIME: 770
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_bus_prv
FAILURE_ID_HASH: {6fd7875b-9a1b-9e09-d6d6-816026a875c8}
Followup: MachineOwner
---------