- Nov 14, 2015
- 23
- 0
- 4,510
Hello community.
Recently I've been having a lot of issues with my PC, in fact I had to buy a new one because I didn't have the time or energies to fix it myself. It's been more likely just constant shutdowns and BlueScreens without any weird hot temperatures and stuff... I formatted my PC, installed windows 7 again and all the drivers. I suspected it was the AMD HDMI audio and Realtek HD audio drivers conflicting again as they used to do, but I have uninstalled/disabled them in various combinations most of the times and it still shutdowns or bluescreens (saying "a clock interrupt was not received on a secondary processor within the allocated time interval").
So I have now the curiosity about what can you do with the bluescreen dump info... Can you really have any benefit with this? I read long time ago that most of the times, the codes of the error itself doesn't help. But there are some tools like BlueScreenViewer and Windows Driver Kit help (someone said that the first one is useless and that the second one works perfectly).
I also read about someone saying that he solved the problem by disabling the power management software, but I guess that's only for the notebooks and is not my case as it's a desktop PC (I guess...? correct me if I'm wrong, which probably am).
For the record
Motherboard: Asus m5a78l-m lx3
CPU: AMD FX6300 six core
GPU: AMD Radeon HD 7770
Memory: 2 x Kingston (I guess) HyperX 4gb Memory (which Windows Memory Diagnostic said there were no errors detected)
PSU: Spektra 650W
My bios is as updated as it can, I also reseted the CMOS (because I read that it may be the solution).
I suspect that it still may be the sound drivers conflicting again, I downloaded the most recent updates I could find on the internet on the official website (at least the realtek one, the AMD HDMI audio one I couldn't find it on "his official website", it is supposed to be installed with the rest of the AMD stuff like the chipset or the GPU driver but the installation failed for some reason) but I still feel insecure if they are ok or if they are conflicting. In my local PC store, the repair guy said he just updated the drivers and voila... Because he was using some automatic driver tools software or that kind of stuff, but I still feel really insecure if I'm doing it right or wrong.
I need help please! (Sorry for bad english)
Thanks!
edit: from 3 dump files, with the BluescreenViewer it says that there are 3 malfunctioning files:
-ntoskrnl.exe (NT Kernel & system) appeared on the three dump files
-atapi.sys (ATAPI IDE Miniport driver) appeared on the 3rd dump file
-atikmdag.sys (ATI Radeon Kernel mode driver) on the 2nd dump file
Any ideas?
edit 2: New crash while I was checking the BlueScreenViewer, so 4th dump file.
Also, I uploaded the dumps on a website that analyses it, but I can't tell anything from it, maybe it may help you guys
1st dump file analysis
2nd dump file analysis
3rd dump file analysis
4th dump file analysis
Hope it may help!
Recently I've been having a lot of issues with my PC, in fact I had to buy a new one because I didn't have the time or energies to fix it myself. It's been more likely just constant shutdowns and BlueScreens without any weird hot temperatures and stuff... I formatted my PC, installed windows 7 again and all the drivers. I suspected it was the AMD HDMI audio and Realtek HD audio drivers conflicting again as they used to do, but I have uninstalled/disabled them in various combinations most of the times and it still shutdowns or bluescreens (saying "a clock interrupt was not received on a secondary processor within the allocated time interval").
So I have now the curiosity about what can you do with the bluescreen dump info... Can you really have any benefit with this? I read long time ago that most of the times, the codes of the error itself doesn't help. But there are some tools like BlueScreenViewer and Windows Driver Kit help (someone said that the first one is useless and that the second one works perfectly).
I also read about someone saying that he solved the problem by disabling the power management software, but I guess that's only for the notebooks and is not my case as it's a desktop PC (I guess...? correct me if I'm wrong, which probably am).
For the record
Motherboard: Asus m5a78l-m lx3
CPU: AMD FX6300 six core
GPU: AMD Radeon HD 7770
Memory: 2 x Kingston (I guess) HyperX 4gb Memory (which Windows Memory Diagnostic said there were no errors detected)
PSU: Spektra 650W
My bios is as updated as it can, I also reseted the CMOS (because I read that it may be the solution).
I suspect that it still may be the sound drivers conflicting again, I downloaded the most recent updates I could find on the internet on the official website (at least the realtek one, the AMD HDMI audio one I couldn't find it on "his official website", it is supposed to be installed with the rest of the AMD stuff like the chipset or the GPU driver but the installation failed for some reason) but I still feel insecure if they are ok or if they are conflicting. In my local PC store, the repair guy said he just updated the drivers and voila... Because he was using some automatic driver tools software or that kind of stuff, but I still feel really insecure if I'm doing it right or wrong.
I need help please! (Sorry for bad english)
Thanks!
edit: from 3 dump files, with the BluescreenViewer it says that there are 3 malfunctioning files:
-ntoskrnl.exe (NT Kernel & system) appeared on the three dump files
-atapi.sys (ATAPI IDE Miniport driver) appeared on the 3rd dump file
-atikmdag.sys (ATI Radeon Kernel mode driver) on the 2nd dump file
Any ideas?
edit 2: New crash while I was checking the BlueScreenViewer, so 4th dump file.
Also, I uploaded the dumps on a website that analyses it, but I can't tell anything from it, maybe it may help you guys
1st dump file analysis
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19160.amd64fre.win7sp1_gdr.160211-0600
Machine Name:
Kernel base = 0xfffff800`0281d000 PsLoadedModuleList = 0xfffff800`02a64730
Debug session time: Wed Jun 7 17:59:40.242 2017 (UTC - 4:00)
System Uptime: 0 days 0:00:06.382
***************************
* *
* 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: fffffa8007c6f038, 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:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
BUGCHECK_STR: 0x124_AuthenticAMD
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`031a95b0 fffff800`02ae1cb9 : fffffa80`07c6f010 fffffa80`06a88040 fffff8a0`00000004 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a9ad0 fffff800`029c0c07 : fffffa80`07c6f010 fffff800`02a3b2d8 fffffa80`06a88040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a9b00 fffff800`02927c55 : fffff800`02a9dba0 00000000`00000001 fffffa80`07c51500 fffffa80`06a88040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a9b40 fffff800`0289a065 : fffff880`010dde00 fffff800`02927c30 fffffa80`06a88000 fffffa80`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a9b70 fffff800`02b2bc6a : 00000000`00000000 fffffa80`06a88040 00000000`00000080 fffffa80`069ea040 : nt!ExpWorkerThread+0x111
fffff880`031a9c00 fffff800`02882086 : fffff880`009b3180 fffffa80`06a88040 fffff880`009be040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a9c40 00000000`00000000 : fffff880`031aa000 fffff880`031a4000 fffff880`031a8f60 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19160.amd64fre.win7sp1_gdr.160211-0600
Machine Name:
Kernel base = 0xfffff800`0281d000 PsLoadedModuleList = 0xfffff800`02a64730
Debug session time: Wed Jun 7 17:59:40.242 2017 (UTC - 4:00)
System Uptime: 0 days 0:00:06.382
***************************
* *
* 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: fffffa8007c6f038, 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:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
BUGCHECK_STR: 0x124_AuthenticAMD
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`031a95b0 fffff800`02ae1cb9 : fffffa80`07c6f010 fffffa80`06a88040 fffff8a0`00000004 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a9ad0 fffff800`029c0c07 : fffffa80`07c6f010 fffff800`02a3b2d8 fffffa80`06a88040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a9b00 fffff800`02927c55 : fffff800`02a9dba0 00000000`00000001 fffffa80`07c51500 fffffa80`06a88040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a9b40 fffff800`0289a065 : fffff880`010dde00 fffff800`02927c30 fffffa80`06a88000 fffffa80`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a9b70 fffff800`02b2bc6a : 00000000`00000000 fffffa80`06a88040 00000000`00000080 fffffa80`069ea040 : nt!ExpWorkerThread+0x111
fffff880`031a9c00 fffff800`02882086 : fffff880`009b3180 fffffa80`06a88040 fffff880`009be040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a9c40 00000000`00000000 : fffff880`031aa000 fffff880`031a4000 fffff880`031a8f60 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
2nd dump file analysis
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23796.amd64fre.win7sp1_ldr.170427-1518
Machine Name:
Kernel base = 0xfffff800`02e11000 PsLoadedModuleList = 0xfffff800`03053730
Debug session time: Wed Jun 7 21:49:03.789 2017 (UTC - 4:00)
System Uptime: 0 days 0:48:42.913
***************************
* *
* Bugcheck Analysis *
* *
***************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b3180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_6_PROC
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: d
STACK_TEXT:
fffff880`0317f3e8 fffff800`02edac99 : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`009b3180 : nt!KeBugCheckEx
fffff880`0317f3f0 fffff800`02e8ace7 : 00000000`00000000 fffff800`00000004 00000000`00002711 fffff880`111319eb : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0317f480 fffff800`03401895 : fffff800`03427460 fffff880`0317f630 fffff800`03427460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0317f580 fffff800`02e7ca13 : 00000000`0f096505 fffff800`02fffe80 00000000`00000000 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0317f5b0 fffff800`02e85fe0 : fffff800`02fffe80 00000000`00000001 00000000`00000000 fffff880`0317f838 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0317f740 fffff800`02ec5c8c : fffff880`0317fb18 00000000`00000000 00000000`00000000 fffff800`02ec3fa1 : nt!KeFlushMultipleRangeTb+0x260
fffff880`0317f810 fffff800`02ec2ac1 : fffffa80`06adb040 00000000`00000000 fffff880`0317fb18 00000000`00000000 : nt!MmSetAddressRangeModified+0x2b0
fffff880`0317f910 fffff800`02ec6416 : fffffa80`07a0eb90 fffffa80`00000001 fffff880`00000001 00000000`00001000 : nt!CcFlushCache+0x561
fffff880`0317fa10 fffff800`02ec6de4 : fffff880`00000000 fffff880`0317fb18 fffffa80`0987a8c0 fffffa80`08f95bf0 : nt!CcWriteBehind+0x1c6
fffff880`0317fac0 fffff800`02e8a849 : fffffa80`06a486e0 fffff800`0317d201 fffff800`0308c980 fffff800`00000003 : nt!CcWorkerThread+0x1c8
fffff880`0317fb70 fffff800`0311be66 : 00000000`00000000 fffffa80`06adb040 00000000`00000080 fffffa80`069db040 : nt!ExpWorkerThread+0x111
fffff880`0317fc00 fffff800`02e726e6 : fffff880`009b3180 fffffa80`06adb040 fffff880`009be040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0317fc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23796.amd64fre.win7sp1_ldr.170427-1518
Machine Name:
Kernel base = 0xfffff800`02e11000 PsLoadedModuleList = 0xfffff800`03053730
Debug session time: Wed Jun 7 21:49:03.789 2017 (UTC - 4:00)
System Uptime: 0 days 0:48:42.913
***************************
* *
* Bugcheck Analysis *
* *
***************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b3180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_6_PROC
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: d
STACK_TEXT:
fffff880`0317f3e8 fffff800`02edac99 : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`009b3180 : nt!KeBugCheckEx
fffff880`0317f3f0 fffff800`02e8ace7 : 00000000`00000000 fffff800`00000004 00000000`00002711 fffff880`111319eb : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0317f480 fffff800`03401895 : fffff800`03427460 fffff880`0317f630 fffff800`03427460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0317f580 fffff800`02e7ca13 : 00000000`0f096505 fffff800`02fffe80 00000000`00000000 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0317f5b0 fffff800`02e85fe0 : fffff800`02fffe80 00000000`00000001 00000000`00000000 fffff880`0317f838 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0317f740 fffff800`02ec5c8c : fffff880`0317fb18 00000000`00000000 00000000`00000000 fffff800`02ec3fa1 : nt!KeFlushMultipleRangeTb+0x260
fffff880`0317f810 fffff800`02ec2ac1 : fffffa80`06adb040 00000000`00000000 fffff880`0317fb18 00000000`00000000 : nt!MmSetAddressRangeModified+0x2b0
fffff880`0317f910 fffff800`02ec6416 : fffffa80`07a0eb90 fffffa80`00000001 fffff880`00000001 00000000`00001000 : nt!CcFlushCache+0x561
fffff880`0317fa10 fffff800`02ec6de4 : fffff880`00000000 fffff880`0317fb18 fffffa80`0987a8c0 fffffa80`08f95bf0 : nt!CcWriteBehind+0x1c6
fffff880`0317fac0 fffff800`02e8a849 : fffffa80`06a486e0 fffff800`0317d201 fffff800`0308c980 fffff800`00000003 : nt!CcWorkerThread+0x1c8
fffff880`0317fb70 fffff800`0311be66 : 00000000`00000000 fffffa80`06adb040 00000000`00000080 fffffa80`069db040 : nt!ExpWorkerThread+0x111
fffff880`0317fc00 fffff800`02e726e6 : fffff880`009b3180 fffffa80`06adb040 fffff880`009be040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0317fc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
3rd dump file analysis
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23796.amd64fre.win7sp1_ldr.170427-1518
Machine Name:
Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`0304f730
Debug session time: Wed Jun 7 22:13:49.720 2017 (UTC - 4:00)
System Uptime: 0 days 0:23:10.499
***************************
* *
* Bugcheck Analysis *
* *
***************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b3180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_6_PROC
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: d
STACK_TEXT:
fffff880`07aaa328 fffff800`02ed6c99 : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`009b3180 : nt!KeBugCheckEx
fffff880`07aaa330 fffff800`02e86ce7 : 00000000`00000000 fffff800`00000004 00000000`00002711 fffff880`00e02a10 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`07aaa3c0 fffff800`033fd895 : fffff800`03423460 fffff880`07aaa570 fffff800`03423460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`07aaa4c0 fffff800`02e78a13 : fffff800`02ffbe80 00000000`00000001 00000000`00000001 fffff800`02e0d000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`07aaa4f0 fffff800`02e52e6d : fffffa80`09084310 00000000`00000000 fffff800`02e87095 00000000`000406f8 : nt!KiInterruptDispatchNoLock+0x163
fffff880`07aaa680 fffff800`0318df1f : 00000000`00000000 fffff880`07aaab60 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x65
fffff880`07aaa6f0 fffff800`0318e57d : 00000000`03440d80 fffff800`03178d6e 00000000`00000000 00000000`00000246 : nt!ExpQuerySystemInformation+0x13af
fffff880`07aaaaa0 fffff800`02e7b753 : 00000000`00000000 fffff880`07aaab60 ffffffff`fffe7960 000007fe`fabe0b48 : nt!NtQuerySystemInformation+0x4d
fffff880`07aaaae0 00000000`7734c09a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`039cf698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7734c09a
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23796.amd64fre.win7sp1_ldr.170427-1518
Machine Name:
Kernel base = 0xfffff800`02e0d000 PsLoadedModuleList = 0xfffff800`0304f730
Debug session time: Wed Jun 7 22:13:49.720 2017 (UTC - 4:00)
System Uptime: 0 days 0:23:10.499
***************************
* *
* Bugcheck Analysis *
* *
***************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000021, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b3180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_6_PROC
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: d
STACK_TEXT:
fffff880`07aaa328 fffff800`02ed6c99 : 00000000`00000101 00000000`00000021 00000000`00000000 fffff880`009b3180 : nt!KeBugCheckEx
fffff880`07aaa330 fffff800`02e86ce7 : 00000000`00000000 fffff800`00000004 00000000`00002711 fffff880`00e02a10 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`07aaa3c0 fffff800`033fd895 : fffff800`03423460 fffff880`07aaa570 fffff800`03423460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`07aaa4c0 fffff800`02e78a13 : fffff800`02ffbe80 00000000`00000001 00000000`00000001 fffff800`02e0d000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`07aaa4f0 fffff800`02e52e6d : fffffa80`09084310 00000000`00000000 fffff800`02e87095 00000000`000406f8 : nt!KiInterruptDispatchNoLock+0x163
fffff880`07aaa680 fffff800`0318df1f : 00000000`00000000 fffff880`07aaab60 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x65
fffff880`07aaa6f0 fffff800`0318e57d : 00000000`03440d80 fffff800`03178d6e 00000000`00000000 00000000`00000246 : nt!ExpQuerySystemInformation+0x13af
fffff880`07aaaaa0 fffff800`02e7b753 : 00000000`00000000 fffff880`07aaab60 ffffffff`fffe7960 000007fe`fabe0b48 : nt!NtQuerySystemInformation+0x4d
fffff880`07aaaae0 00000000`7734c09a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`039cf698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7734c09a
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_6_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
4th dump file analysis
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23796.amd64fre.win7sp1_ldr.170427-1518
Machine Name:
Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`03044730
Debug session time: Thu Jun 8 01:31:05.148 2017 (UTC - 4:00)
System Uptime: 0 days 0:00:06.428
***************************
* *
* 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: fffffa8004d218f8, 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:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`031845b0 fffff800`030c1cb9 : fffffa80`04d218d0 fffffa80`03a28b50 00000000`00000009 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03184ad0 fffff800`02fa13f7 : fffffa80`04d218d0 fffff800`0301b2d8 fffffa80`03a28b50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03184b00 fffff800`02f08ce5 : fffff800`0307dba0 00000000`00000001 fffffa80`04da60e0 fffffa80`03a28b50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03184b40 fffff800`02e7b849 : fffff880`00c30e00 fffff800`02f08cc0 fffffa80`03a28b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03184b70 fffff800`0310ce66 : 00000000`00000000 fffffa80`03a28b50 00000000`00000080 fffffa80`039bc040 : nt!ExpWorkerThread+0x111
fffff880`03184c00 fffff800`02e636e6 : fffff880`009b2180 fffffa80`03a28b50 fffff880`009bd040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03184c40 00000000`00000000 : fffff880`03185000 fffff880`0317f000 fffff880`03b2f720 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23796.amd64fre.win7sp1_ldr.170427-1518
Machine Name:
Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`03044730
Debug session time: Thu Jun 8 01:31:05.148 2017 (UTC - 4:00)
System Uptime: 0 days 0:00:06.428
***************************
* *
* 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: fffffa8004d218f8, 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:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`031845b0 fffff800`030c1cb9 : fffffa80`04d218d0 fffffa80`03a28b50 00000000`00000009 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03184ad0 fffff800`02fa13f7 : fffffa80`04d218d0 fffff800`0301b2d8 fffffa80`03a28b50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03184b00 fffff800`02f08ce5 : fffff800`0307dba0 00000000`00000001 fffffa80`04da60e0 fffffa80`03a28b50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03184b40 fffff800`02e7b849 : fffff880`00c30e00 fffff800`02f08cc0 fffffa80`03a28b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03184b70 fffff800`0310ce66 : 00000000`00000000 fffffa80`03a28b50 00000000`00000080 fffffa80`039bc040 : nt!ExpWorkerThread+0x111
fffff880`03184c00 fffff800`02e636e6 : fffff880`009b2180 fffffa80`03a28b50 fffff880`009bd040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03184c40 00000000`00000000 : fffff880`03185000 fffff880`0317f000 fffff880`03b2f720 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
Hope it may help!
Facebook
Twitter
Instagram