solodeed
asked on
Need a fujitsu full hardware check software
HI,
I have a desktop PC in the office that is randomly shutting itself down at times. After a lot of troubleshooting i started to look at the dump files i started to question the memory in the PC.
I really need a full hardware check on my PC. It is a Fujitsu esprimo E510. I looked on the website (Fujitsu) but i cant see anything to really help. I have many lenovo PC's in the office and there is a utility that does a full hardware check and reports back.
I want the same for this fujitsu model
Please can someone help.
I have a desktop PC in the office that is randomly shutting itself down at times. After a lot of troubleshooting i started to look at the dump files i started to question the memory in the PC.
I really need a full hardware check on my PC. It is a Fujitsu esprimo E510. I looked on the website (Fujitsu) but i cant see anything to really help. I have many lenovo PC's in the office and there is a utility that does a full hardware check and reports back.
I want the same for this fujitsu model
Please can someone help.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
nobus
post the dmp file here plse
ASKER
Hello Sorry for the late responses.
Firstly Rindi i have run the mem tests from the links. This is a x64 bit PC and the mem tests seem to relate to the x86. The tests ran fine though. I did the thorough test and also the short test and it passed.
This is a really good cd! Cant beileve i never knew about it.
I did run Windbg X64 a few days ago. This is why i was thinking it was memory. The system also freezes with no mini dumps. I have lots of minidump files and they seem to all point to this: WHEA_UNCORRECTABLE error. There is mention of a driver issue or mem hardware issue. What do you giuys think?
....
Firstly Rindi i have run the mem tests from the links. This is a x64 bit PC and the mem tests seem to relate to the x86. The tests ran fine though. I did the thorough test and also the short test and it passed.
This is a really good cd! Cant beileve i never knew about it.
I did run Windbg X64 a few days ago. This is why i was thinking it was memory. The system also freezes with no mini dumps. I have lots of minidump files and they seem to all point to this: WHEA_UNCORRECTABLE error. There is mention of a driver issue or mem hardware issue. What do you giuys think?
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80093bc028, be200000, 1117a}
Probably caused by : GenuineIntel
---------
1: 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: fffffa80093bc028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000001117a, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
SYSTEM_MANUFACTURER: FUJITSU
SYSTEM_PRODUCT_NAME: ESPRIMO E510
SYSTEM_VERSION:
BIOS_VENDOR: FUJITSU // American Megatrends Inc.
BIOS_VERSION: V4.6.5.3 R1.23.0 for D3171-A1x
BIOS_DATE: 01/17/2013
BASEBOARD_MANUFACTURER: FUJITSU
BASEBOARD_PRODUCT: D3171-A1
BASEBOARD_VERSION: S26361-D3171-A1
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: fffffa80093bc028
BUGCHECK_P3: be200000
BUGCHECK_P4: 1117a
BUGCHECK_STR: 0x124_GenuineIntel
CPU_COUNT: 4
CPU_MHZ: c78
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3a
CPU_STEPPING: 9
CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 15'00000000 (cache) 15'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
ANALYSIS_SESSION_TIME: 04-13-2016 09:31:21.0805
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
STACK_TEXT:
fffff880`009c8a58 fffff800`03013a3b : 00000000`00000124 00000000`00000000 fffffa80`093bc028 00000000`be200000 : nt!KeBugCheckEx
fffff880`009c8a60 fffff800`031d7c33 : 00000000`00000001 fffffa80`093ff490 00000000`00000000 fffffa80`093ff4e0 : hal!HalBugCheckSystem+0x1e3
fffff880`009c8aa0 fffff800`03013700 : 00000000`00000728 fffffa80`093ff490 fffff880`009c8e30 fffff880`009c8e00 : nt!WheaReportHwError+0x263
fffff880`009c8b00 fffff800`03013052 : fffffa80`093ff490 fffff880`009c8e30 fffffa80`093ff490 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009c8c50 fffff800`03012f0d : 00000000`00000004 00000000`00000001 fffff880`009c8eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009c8c90 fffff800`03006e88 : 00000000`00000001 fffff880`009c0180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009c8cc0 fffff800`030bd1ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009c8cf0 fffff800`030bd013 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009c8e30 fffff880`05f45c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`009e8b58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x19
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 1f6e9d63c9e8422ee46cdc5371eb990aab5a3e15
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 5475986b89250031f3afb584a172d53895f73199
THREAD_SHA1_HASH_MOD: 646c5386aef6f8ecb46de814405509fdb98174e3
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN
BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN
PRIMARY_PROBLEM_CLASS: X64_0x124_GenuineIntel_MEMORY__UNKNOWN
TARGET_TIME: 2016-04-06T16:01:20.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2015-05-25 18:07:52
BUILDDATESTAMP_STR: 150525-0603
BUILDLAB_STR: win7sp1_gdr
BUILDOSVER_STR: 6.1.7601.18869.amd64fre.win7sp1_gdr.150525-0603
ANALYSIS_SESSION_ELAPSED_TIME: 3e2
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_memory__unknown
FAILURE_ID_HASH: {088c9428-4ac2-3e7d-d26a-c93dd222fd73}
---------
1: 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: fffffa80093bc028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000001117a, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
SYSTEM_MANUFACTURER: FUJITSU
SYSTEM_PRODUCT_NAME: ESPRIMO E510
SYSTEM_SKU: S26361-Kxxx-Vyyy
SYSTEM_VERSION:
BIOS_VENDOR: FUJITSU // American Megatrends Inc.
BIOS_VERSION: V4.6.5.3 R1.23.0 for D3171-A1x
BIOS_DATE: 01/17/2013
BASEBOARD_MANUFACTURER: FUJITSU
BASEBOARD_PRODUCT: D3171-A1
BASEBOARD_VERSION: S26361-D3171-A1
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: fffffa80093bc028
BUGCHECK_P3: be200000
BUGCHECK_P4: 1117a
BUGCHECK_STR: 0x124_GenuineIntel
CPU_COUNT: 4
CPU_MHZ: c78
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3a
CPU_STEPPING: 9
CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 15'00000000 (cache) 15'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
ANALYSIS_SESSION_TIME: 04-13-2016 09:31:22.0801
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
STACK_TEXT:
fffff880`009c8a58 fffff800`03013a3b : 00000000`00000124 00000000`00000000 fffffa80`093bc028 00000000`be200000 : nt!KeBugCheckEx
fffff880`009c8a60 fffff800`031d7c33 : 00000000`00000001 fffffa80`093ff490 00000000`00000000 fffffa80`093ff4e0 : hal!HalBugCheckSystem+0x1e3
fffff880`009c8aa0 fffff800`03013700 : 00000000`00000728 fffffa80`093ff490 fffff880`009c8e30 fffff880`009c8e00 : nt!WheaReportHwError+0x263
fffff880`009c8b00 fffff800`03013052 : fffffa80`093ff490 fffff880`009c8e30 fffffa80`093ff490 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009c8c50 fffff800`03012f0d : 00000000`00000004 00000000`00000001 fffff880`009c8eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009c8c90 fffff800`03006e88 : 00000000`00000001 fffff880`009c0180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009c8cc0 fffff800`030bd1ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009c8cf0 fffff800`030bd013 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009c8e30 fffff880`05f45c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`009e8b58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x19
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 1f6e9d63c9e8422ee46cdc5371eb990aab5a3e15
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 5475986b89250031f3afb584a172d53895f73199
THREAD_SHA1_HASH_MOD: 646c5386aef6f8ecb46de814405509fdb98174e3
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN
BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN
PRIMARY_PROBLEM_CLASS: X64_0x124_GenuineIntel_MEMORY__UNKNOWN
TARGET_TIME: 2016-04-06T16:01:20.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2015-05-25 18:07:52
BUILDDATESTAMP_STR: 150525-0603
BUILDLAB_STR: win7sp1_gdr
BUILDOSVER_STR: 6.1.7601.18869.amd64fre.win7sp1_gdr.150525-0603
ANALYSIS_SESSION_ELAPSED_TIME: 3d2
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_memory__unknown
FAILURE_ID_HASH: {088c9428-4ac2-3e7d-d26a-c93dd222fd73}
Can you please upload one of the recent minidump files?
Memtest86+ doesn't have a short and long test, it only has one test, and when you run it allow it to do at least 3 passes. The Architecture (x86 or x64) doesn't matter.
You are probably talking about the disk manufacturer's diagnostics. Those usually have short and long tests. Always run the long tests...
You are probably talking about the disk manufacturer's diagnostics. Those usually have short and long tests. Always run the long tests...
ASKER
HI, This is the latest mini dump file. is slightly different i think. Thanks.
1: 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: fffffa80092b7028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000001117a, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
SYSTEM_MANUFACTURER: FUJITSU
SYSTEM_PRODUCT_NAME: ESPRIMO E510
SYSTEM_VERSION:
BIOS_VENDOR: FUJITSU // American Megatrends Inc.
BIOS_VERSION: V4.6.5.3 R1.23.0 for D3171-A1x
BIOS_DATE: 01/17/2013
BASEBOARD_MANUFACTURER: FUJITSU
BASEBOARD_PRODUCT: D3171-A1
BASEBOARD_VERSION: S26361-D3171-A1
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: fffffa80092b7028
BUGCHECK_P3: be200000
BUGCHECK_P4: 1117a
BUGCHECK_STR: 0x124_GenuineIntel
CPU_COUNT: 4
CPU_MHZ: c78
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3a
CPU_STEPPING: 9
CPU_MICROCODE: 6,3a,9,0 (F,M,S,R) SIG: 15'00000000 (cache) 15'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: f
ANALYSIS_SESSION_TIME: 04-13-2016 10:28:43.0507
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
STACK_TEXT:
fffff880`009c8a58 fffff800`035ffa3b : 00000000`00000124 00000000`00000000 fffffa80`092b7028 00000000`be200000 : nt!KeBugCheckEx
fffff880`009c8a60 fffff800`0318ec33 : 00000000`00000001 fffffa80`076fd960 00000000`00000000 fffffa80`076fd9b0 : hal!HalBugCheckSystem+0x1e3
fffff880`009c8aa0 fffff800`035ff700 : 00000000`00000728 fffffa80`076fd960 fffff880`009c8e30 fffff880`009c8e00 : nt!WheaReportHwError+0x263
fffff880`009c8b00 fffff800`035ff052 : fffffa80`076fd960 fffff880`009c8e30 fffffa80`076fd960 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009c8c50 fffff800`035fef0d : 00000000`00000004 00000000`00000001 fffff880`009c8eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009c8c90 fffff800`035f2e88 : 00000000`00000001 fffff880`009c0180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009c8cc0 fffff800`030741ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009c8cf0 fffff800`03074013 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009c8e30 fffff880`05952c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`009e8b58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x19
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 1f6e9d63c9e8422ee46cdc5371eb990aab5a3e15
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 5475986b89250031f3afb584a172d53895f73199
THREAD_SHA1_HASH_MOD: 646c5386aef6f8ecb46de814405509fdb98174e3
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN
BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN
PRIMARY_PROBLEM_CLASS: X64_0x124_GenuineIntel_MEMORY__UNKNOWN
TARGET_TIME: 2016-04-13T08:47:37.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2015-05-25 18:07:52
BUILDDATESTAMP_STR: 150525-0603
BUILDLAB_STR: win7sp1_gdr
BUILDOSVER_STR: 6.1.7601.18869.amd64fre.win7sp1_gdr.150525-0603
ANALYSIS_SESSION_ELAPSED_TIME: 3c0
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_memory__unknown
FAILURE_ID_HASH: {088c9428-4ac2-3e7d-d26a-c93dd222fd73}
---------ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
it refers to the intel processor - maybe it's over heating
install speedfan to check the temperatures : http://www.almico.com/speedfan.php
install speedfan to check the temperatures : http://www.almico.com/speedfan.php
ASKER
Hi guys,
Well i think i eventually found the culprit. It seemed to be the onboard graphics chip. Well at least after i disabled all 'hardware acceleration' on the PC the PC seemed fine.
I noticed the users system always froze when in google maps. zooming in or out was a guarantee for the PC to freeze. quick Google search suggested disabling hardware acceleration. This worked great.
I then disabled this on the entire PC and the user has not complained for over a week so im happy.
Thanks for all your help
Well i think i eventually found the culprit. It seemed to be the onboard graphics chip. Well at least after i disabled all 'hardware acceleration' on the PC the PC seemed fine.
I noticed the users system always froze when in google maps. zooming in or out was a guarantee for the PC to freeze. quick Google search suggested disabling hardware acceleration. This worked great.
I then disabled this on the entire PC and the user has not complained for over a week so im happy.
Thanks for all your help