Blue screen while playing games like (Dota 2, CS:GO, Apex Legends)

invoker90 · May 20, 2019

Hello,

I've been getting this blue screen only when playing games.

I've attached the log files as well.

Thanks in advance.

axe0 · May 20, 2019

Please do the following

Open an admin command prompt
Copy & paste the code below in the command prompt
Go to your desktop
Right click CollectedFiles folder and choose sent to and select compressed (zipped) folder
Upload the zip.

Code:

md "%USERPROFILE%\Desktop\CollectedFiles"&wmic /output:"%USERPROFILE%\Desktop\CollectedFiles\hotfix.txt" qfe list full /format:table&copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\CollectedFiles"&dxdiag /t %temp%\dxdiag.txt&copy %temp%\dxdiag.txt "%USERPROFILE%\Desktop\CollectedFiles\dxdiag.txt"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\CollectedFiles\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\CollectedFiles\systeminfo.tmp"&findstr /v "Owner." "%USERPROFILE%\Desktop\CollectedFiles\systeminfo.tmp" > "%USERPROFILE%\Desktop\CollectedFiles\systeminfo.txt"&del "%USERPROFILE%\Desktop\CollectedFiles\systeminfo.tmp"&driverquery /v > "%USERPROFILE%\Desktop\CollectedFiles\drivers.txt"&msinfo32 /nfo "%USERPROFILE%\Desktop\CollectedFiles\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\CollectedFiles\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\CollectedFiles\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\CollectedFiles\installed.txt"

invoker90 · May 20, 2019

axe0 said:
Please do the following

Open an admin command prompt

Copy & paste the code below in the command prompt

Go to your desktop

Right click CollectedFiles folder and choose sent to and select compressed (zipped) folder

Upload the zip.

Code:

Here you go.

axe0 · May 22, 2019

It looks like the Asmedia USB controller drivers are causing issues. Could you uninstall it in device manager, reboot your system and check Windows Update for updates.

invoker90 · May 23, 2019

axe0 said:
It looks like the Asmedia USB controller drivers are causing issues. Could you uninstall it in device manager, reboot your system and check Windows Update for updates.

I've uninstalled it, should i not install it anymore? because i cannot seem to make my other USB flash drives to work anymore. some USB slots are not working due to the fact that i don't have the driver installed

axe0 · May 23, 2019

Commonly Windows Update automatically installs drivers for it if you haven't installed any other drivers. Looking at the logs I assumed Windows Update was the one who had installed the drivers you removed, because the date of the drivers are years more recent than the onces ASUS provides for your motherboard.

If Windows Update hasn't installed drivers for it, and the device is not present in device manager, then install the drivers via device manager. Sometimes Windows installs the drivers upon a reboot.

invoker90 · May 23, 2019

axe0 said:
Commonly Windows Update automatically installs drivers for it if you haven't installed any other drivers. Looking at the logs I assumed Windows Update was the one who had installed the drivers you removed, because the date of the drivers are years more recent than the onces ASUS provides for your motherboard.

If Windows Update hasn't installed drivers for it, and the device is not present in device manager, then install the drivers via device manager. Sometimes Windows installs the drivers upon a reboot.

Still getting blue screen :/

invoker90 · May 24, 2019

axe0 said:
Commonly Windows Update automatically installs drivers for it if you haven't installed any other drivers. Looking at the logs I assumed Windows Update was the one who had installed the drivers you removed, because the date of the drivers are years more recent than the onces ASUS provides for your motherboard.

If Windows Update hasn't installed drivers for it, and the device is not present in device manager, then install the drivers via device manager. Sometimes Windows installs the drivers upon a reboot.

here is latest two dumps

MrPepka · May 24, 2019

1. Stop CPU overclocking
2. Update CPU-Z (or use a zip version that does not require installation)

invoker90 · May 24, 2019

MrPepka said:
1. Stop CPU overclocking
2. Update CPU-Z (or use a zip version that does not require installation)

Tried it.... Didn't work. still getting BSOD

any other suggestions? :/

invoker90 · May 27, 2019

invoker90 said:
tried it.... Didn't work. Still getting bsod

any other suggestions? :/

bump :/

axe0 · May 27, 2019

I just got back from traveling.

I noticed you had reuploaded the same zip file when I asked you to run commands, I asked you to run commands to generate files because the uploaded zip file does not contain all requested files.

invoker90 · May 28, 2019

axe0 said:
I just got back from traveling.

I noticed you had re uploaded the same zip file when I asked you to run commands, I asked you to run commands to generate files because the uploaded zip file does not contain all requested files.

it is absolutely not the same zip files. i uploaded the latest 2 dumps I've been getting. But here is another new Zip file due to the act that i had just experienced now a BSOD.

axe0 · May 29, 2019

You're right, I'm sorry. The names of the zip files are a bit misguiding.

Your latest uploaded zip file is empty (22 bytes).

invoker90 · May 31, 2019

axe0 said:
You're right, I'm sorry. The names of the zip files are a bit misguiding.

Your latest uploaded zip file is empty (22 bytes).

Okay i have reinstalled windows, and tried to play again, got 2 blue screens back to back...

I've attached new files as well. and i am sure that this time it is NOT empty ;P

axe0 · May 31, 2019

Could you upload the kernel dump in C:\Windows\MEMORY.dmp to onedrive, google drive, dropbox or a similar service and post a share link. One of the dumps requires a kernel dump to have a look at, because the minidump doesn't have relevant information.

invoker90 · May 31, 2019

axe0 said:
Could you upload the kernel dump in C:\Windows\MEMORY.dmp to onedrive, google drive, dropbox or a similar service and post a share link. One of the dumps requires a kernel dump to have a look at, because the minidump doesn't have relevant information.

https://www.**************/file/56rs8spi2re0ae2/MEMORY.DMP/file

NOTE: i do not know why it blanks the link, but i uploaded it on mediafire

mediafire . com/file/56rs8spi2re0ae2/MEMORY.DMP/file

MrPepka · May 31, 2019

"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."

Code:

Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\michal01\Downloads\MEMORY (1).DMP]
Kernel Summary Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*
Symbol search path is: SRV*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24444.amd64fre.win7sp1_ldr_escrow.190429-1700
Machine Name:
Kernel base = 0xfffff800`0e800000 PsLoadedModuleList = 0xfffff800`0ea39c90
Debug session time: Fri May 31 10:54:52.168 2019 (UTC + 2:00)
System Uptime: 0 days 0:15:27.964
Loading Kernel Symbols
..Page 200000bfb too large to be in the dump file.
.............Page 20000f32d too large to be in the dump file.
................................................
................................................................
.....................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88004fb1180, 7}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88004fb1180, The PRCB address of the hung processor.
Arg4: 0000000000000007, The index of the hung processor.

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  7601.24444.amd64fre.win7sp1_ldr_escrow.190429-1700

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  3603

BIOS_DATE:  11/09/2012

BASEBOARD_MANUFACTURER:  ASUSTeK Computer INC.

BASEBOARD_PRODUCT:  P8Z68-V

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  1

BUGCHECK_P1: 19

BUGCHECK_P2: 0

BUGCHECK_P3: fffff88004fb1180

BUGCHECK_P4: 7

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CPU_COUNT: 8

CPU_MHZ: dae

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2a

CPU_STEPPING: 7

CPU_MICROCODE: 6,2a,7,0 (F,M,S,R)  SIG: 28'00000000 (cache) 28'00000000 (init)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  RzSDKService.exe

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  MICHAL

ANALYSIS_SESSION_TIME:  05-31-2019 14:28:43.0412

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

STACK_TEXT:  
fffff880`0a0641d8 fffff800`0e8ab0ee : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`04fb1180 : nt!KeBugCheckEx
fffff880`0a0641e0 fffff800`0e87bff7 : fffffa80`00000000 fffff800`00000007 00000000`00026160 fffffa80`14d1f000 : nt! ?? ::FNODOBFM::`string'+0x4c6e
fffff880`0a064270 fffff800`0ede78e9 : fffff800`0ee0c360 fffff880`0a064420 fffff800`0ee0c360 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0a064370 fffff800`0e8949ef : fffff800`0e9e4180 00000000`00000001 00000000`00000000 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0a0643a0 fffff800`0e863ba1 : fffffa80`16202660 00000000`00000000 00000000`00000000 fffff800`0eb77bef : nt!KiInterruptDispatchNoLock+0xaf
fffff880`0a064530 fffff800`0eaf101f : 00000000`00000000 fffff880`0a064b60 00000000`00000000 fffff800`0e837333 : nt!KeFlushProcessWriteBuffers+0x65
fffff880`0a0645a0 fffff800`0ecd54a4 : 00000000`000d3d30 00000000`00008400 fffff880`0a064730 00000000`00000000 : nt!ExpGetProcessInformation+0x7f
fffff880`0a0646f0 fffff800`0eb4ab55 : 00000000`000d3d30 fffff800`0eb106b1 00000000`00000005 00000000`00000000 : nt!ExpQuerySystemInformation+0x1274
fffff880`0a064aa0 fffff800`0e8a1ad3 : fffffa80`164f55c0 fffff880`0a064b60 ffffffff`fe363c80 00000000`015dfb40 : nt!NtQuerySystemInformation+0x4d
fffff880`0a064ae0 00000000`77b59bea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00b5e138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b59bea


THREAD_SHA1_HASH_MOD_FUNC:  0bf6ab374f5908864d0c16dff9ffba22ce7c694f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  c3e8b3705d61e9f5be26dba2b58caf21080059d5

THREAD_SHA1_HASH_MOD:  692dc177616b23b31c5615392ac069be10b8455d

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

PRIMARY_PROBLEM_CLASS:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

TARGET_TIME:  2019-05-31T08:54:52.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:  2019-04-30 03:35:34

BUILDDATESTAMP_STR:  190429-1700

BUILDLAB_STR:  win7sp1_ldr_escrow

BUILDOSVER_STR:  6.1.7601.24444.amd64fre.win7sp1_ldr_escrow.190429-1700

ANALYSIS_SESSION_ELAPSED_TIME:  65b

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_clock_watchdog_timeout_8_proc_analysis_inconclusive

FAILURE_ID_HASH:  {b37a9ee0-e89a-8796-d6e1-c509c7ba4f05}

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

0: kd> .load pde
=========================================================================================
 PDE v11.3 - Copyright 2017 Andrew Richards
=========================================================================================
0: kd> !dpx
Start memory scan  : 0xfffff8800a0641d8 ($csp)
End memory scan    : 0xfffff8800a065000 (Kernel Stack Base)

0xfffff8800a064240 : 0xfffff8800a0643a0 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180
0xfffff8800a064250 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180
0xfffff8800a064268 : 0xfffff8000e87bff7 : nt!KeUpdateSystemTime+0x377
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
0xfffff8800a064368 : 0xfffff8000ede78e9 : hal!HalpHpetClockInterrupt+0x8d
0xfffff8800a064370 : 0xfffff8000ee0c360 : hal!HalpKInterruptHeap+0x360
0xfffff8800a064380 : 0xfffff8000ee0c360 : hal!HalpKInterruptHeap+0x360
0xfffff8800a064390 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180
0xfffff8800a064398 : 0xfffff8000e8949ef : nt!KiInterruptDispatchNoLock+0xaf
0xfffff8800a0643a0 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180 Trap @ fffff8800a0643a0
0xfffff8800a064408 : 0xfffff8000e84df31 : nt!KiIpiSendRequest+0x2c1
0xfffff8800a0644c8 : 0xfffff8000e863b2f : nt!KiIpiSendPacket+0x4f
0xfffff8800a0644d0 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180
0xfffff8800a0644e0 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180
0xfffff8800a064508 : 0xfffff8000e863ba1 : nt!KeFlushProcessWriteBuffers+0x65
0xfffff8800a064588 : 0xfffff8000e88c4f4 : nt!KiSetAddressPolicy+0xc
0xfffff8800a064598 : 0xfffff8000eaf101f : nt!ExpGetProcessInformation+0x7f
0xfffff8800a0645b8 : 0xfffff8000e837333 : nt!KeStackAttachProcess+0x283
0xfffff8800a064638 : 0xfffff8000eadfd23 : nt!MmCopyVirtualMemory+0x317
0xfffff8800a064738 : 0xfffff8000e840000 : nt!ExpReleaseResourceForThreadLite+0x2b0
0xfffff8800a064768 : 0xfffff8000eb0cb8f : nt!SePrivilegedServiceAuditAlarm+0x47
0xfffff8800a064828 : 0xfffff8000e896344 : nt!SwapContext_PatchXSave+0xd4
0xfffff8800a064848 : 0xfffff8000eae9b59 : nt!SeDeleteAccessState+0x79
0xfffff8800a064868 : 0xfffff8000e895f4a : nt!KiSwapContext+0x7a
0xfffff8800a064878 : 0xfffff8000eb10a12 : nt!PsOpenProcess+0x1da
0xfffff8800a064978 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180
0xfffff8800a0649a8 : 0xfffff8000e840722 : nt!KiCommitThreadWait+0x1d2
0xfffff8800a064a38 : 0xfffff8000e851fee : nt!KeDelayExecutionThread+0x186
0xfffff8800a064a58 : 0xfffff8000eafc326 : nt!ExMapHandleToPointer+0x26
0xfffff8800a064a98 : 0xfffff8000eb4ab55 : nt!NtQuerySystemInformation+0x4d
0xfffff8800a064aa8 : 0xfffff8000eb106b1 : nt!NtDelayExecution+0x59
0xfffff8800a064ad8 : 0xfffff8000e8a1ad3 : nt!KiSystemServiceCopyEnd+0x13
0xfffff8800a064ae0 : 0xfffffa80164f55c0 :  Trap @ fffff8800a064ae0

It looks like the processor 7 has hung:

Code:

0: kd> !prcb 7
PRCB for Processor 7 at fffff88004fb1180:
Current IRQL -- 0
Threads--  Current fffffa8012ba2b50 Next fffffa80167761a0 Idle fffff88004fc0240
Processor Index 7 Number (0, 7) GroupSetMember 80
Interrupt Count -- 000ce098
Times -- Dpc    00000000 Interrupt 00000000 
         Kernel 0000d971 User      00000ca4

Let's look at IDT:

Code:

0: kd> !idt

Dumping IDT: fffff8000f001000

00:	fffff8000e9d1100 nt!KiDivideErrorFaultShadow
01:	fffff8000e9d1180 nt!KiDebugTrapOrFaultShadow	Stack = 0xFFFFF8000F0049E0
02:	fffff8000e9d1200 nt!KiNmiInterruptShadow	Stack = 0xFFFFF8000F0047E0
03:	fffff8000e9d1280 nt!KiBreakpointTrapShadow
04:	fffff8000e9d1300 nt!KiOverflowTrapShadow
05:	fffff8000e9d1380 nt!KiBoundFaultShadow
06:	fffff8000e9d1400 nt!KiInvalidOpcodeFaultShadow
07:	fffff8000e9d1480 nt!KiNpxNotAvailableFaultShadow
08:	fffff8000e9d1500 nt!KiDoubleFaultAbortShadow	Stack = 0xFFFFF8000F0043E0
09:	fffff8000e9d1580 nt!KiNpxSegmentOverrunAbortShadow
0a:	fffff8000e9d1600 nt!KiInvalidTssFaultShadow
0b:	fffff8000e9d1680 nt!KiSegmentNotPresentFaultShadow
0c:	fffff8000e9d1700 nt!KiStackFaultShadow
0d:	fffff8000e9d1780 nt!KiGeneralProtectionFaultShadow
0e:	fffff8000e9d1800 nt!KiPageFaultShadow
10:	fffff8000e9d1880 nt!KiFloatingErrorFaultShadow
11:	fffff8000e9d1900 nt!KiAlignmentFaultShadow
12:	fffff8000e9d1980 nt!KiMcheckAbortShadow	Stack = 0xFFFFF8000F0045E0
13:	fffff8000e9d1a00 nt!KiXmmExceptionShadow
1f:	fffff8000e9d1a80 nt!KiApcInterruptShadow
2c:	fffff8000e9d1b00 nt!KiRaiseAssertionShadow
2d:	fffff8000e9d1b80 nt!KiDebugServiceTrapShadow
2f:	fffff8000e9d1c00 nt!KiDpcInterruptShadow
37:	fffff8000e9d1f38 hal!PicSpuriousService37 (KINTERRUPT fffff8000ee0c000)

3f:	fffff8000e9d1f78 hal!PicSpuriousService37 (KINTERRUPT fffff8000ee0c090)

50:	fffff8000e9d2000 hal!HalpCmciService (KINTERRUPT fffff8000ee0c1b0)

61:	fffff8000e9d2088 SCSIPORT!ScsiPortInterrupt (KINTERRUPT fffffa80133d0e40)

	                 ataport!IdePortInterrupt (KINTERRUPT fffffa80133d0d80)

	                 ataport!IdePortInterrupt (KINTERRUPT fffffa80133d0cc0)

71:	fffff8000e9d2108 *** ERROR: Module load completed but symbols could not be loaded for HECIx64.sys
HECIx64+0x1008 (KINTERRUPT fffffa80133d0c00)

	                 USBPORT!USBPORT_InterruptService (KINTERRUPT fffffa80133d0a80)

	                 dxgkrnl!DpiFdoLineInterruptRoutine (KINTERRUPT fffffa80133d0780)

92:	fffff8000e9d2210 HDAudBus!HdaController::Isr (KINTERRUPT fffffa80133d0840)

a2:	fffff8000e9d2290 HDAudBus!HdaController::Isr (KINTERRUPT fffffa80133d0900)

b0:	fffff8000e9d2300 NDIS!ndisMiniportMessageIsr (KINTERRUPT fffffa80133d0b40)

b1:	fffff8000e9d2308 ACPI!ACPIInterruptServiceRoutine (KINTERRUPT fffffa80133d0f00)

b2:	fffff8000e9d2310 USBPORT!USBPORT_InterruptService (KINTERRUPT fffffa80133d09c0)

d1:	fffff8000e9d2408 hal!HalpHpetClockInterrupt (KINTERRUPT fffff8000ee0c360)

d2:	fffff8000e9d2410 hal!HalpHpetRolloverInterrupt (KINTERRUPT fffff8000ee0c3f0)

df:	fffff8000e9d2478 hal!HalpApicRebootService (KINTERRUPT fffff8000ee0c2d0)

e1:	fffff8000e9d1c80 nt!KiIpiInterruptShadow
e2:	fffff8000e9d2490 hal!HalpDeferredRecoveryService (KINTERRUPT fffff8000ee0c240)

e3:	fffff8000e9d2498 hal!HalpLocalApicErrorService (KINTERRUPT fffff8000ee0c120)

fd:	fffff8000e9d2568 hal!HalpProfileInterrupt (KINTERRUPT fffff8000ee0c480)

fe:	fffff8000e9d2570 hal!HalpPerfInterrupt (KINTERRUPT fffff8000ee0c510)

Here I would update the Intel Management Engine Interface driver (check in SDI Download)

Code:

0: kd> lmvm hecix64
Browse full module list
start             end                 module name
fffff880`10e00000 fffff880`10e11000   HECIx64    (no symbols)           
    Loaded symbol image file: HECIx64.sys
    Image path: \SystemRoot\system32\DRIVERS\HECIx64.sys
    Image name: HECIx64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Oct 19 16:33:43 2010 (4CBE2AD7)
    CheckSum:         0001B15F
    ImageSize:        00011000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Among the pending IRPs, I found the VMWare driver:

Code:

7: kd> !irp fffffa8016736100
Irp is active with 1 stacks 1 is current (= 0xfffffa80167361d0)
 No Mdl: System buffer=fffffa80167bdb00: Thread fffffa80165bab50:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
>[IRP_MJ_DEVICE_CONTROL(e), N/A(0)]
            5  1 fffffa8015486060 fffffa80165ba810 00000000-00000000    pending
	       \Driver\hcmon
			Args: 000003d4 00000078 0x8101235c 00000000

Update VMWare (check updates in program)

Code:

7: kd> lmvm hcmon
Browse full module list
start             end                 module name
fffff880`09872000 fffff880`09884000   hcmon      (no symbols)           
    Loaded symbol image file: hcmon.sys
    Image path: \??\C:\Windows\system32\drivers\hcmon.sys
    Image name: hcmon.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Mar 10 08:02:49 2016 (56E19AA9)
    CheckSum:         00018156
    ImageSize:        00012000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I almost forgot. If the mouse software (Razer Chroma SDK) is unnecessary, it can be turned off

invoker90 · May 31, 2019

MrPepka said:

"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."

Code:

Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\michal01\Downloads\MEMORY (1).DMP]
Kernel Summary Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*
Symbol search path is: SRV*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24444.amd64fre.win7sp1_ldr_escrow.190429-1700
Machine Name:
Kernel base = 0xfffff800`0e800000 PsLoadedModuleList = 0xfffff800`0ea39c90
Debug session time: Fri May 31 10:54:52.168 2019 (UTC + 2:00)
System Uptime: 0 days 0:15:27.964
Loading Kernel Symbols
..Page 200000bfb too large to be in the dump file.
.............Page 20000f32d too large to be in the dump file.
................................................
................................................................
.....................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff88004fb1180, 7}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88004fb1180, The PRCB address of the hung processor.
Arg4: 0000000000000007, The index of the hung processor.

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  7601.24444.amd64fre.win7sp1_ldr_escrow.190429-1700

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  3603

BIOS_DATE:  11/09/2012

BASEBOARD_MANUFACTURER:  ASUSTeK Computer INC.

BASEBOARD_PRODUCT:  P8Z68-V

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  1

BUGCHECK_P1: 19

BUGCHECK_P2: 0

BUGCHECK_P3: fffff88004fb1180

BUGCHECK_P4: 7

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CPU_COUNT: 8

CPU_MHZ: dae

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2a

CPU_STEPPING: 7

CPU_MICROCODE: 6,2a,7,0 (F,M,S,R)  SIG: 28'00000000 (cache) 28'00000000 (init)

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  RzSDKService.exe

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  MICHAL

ANALYSIS_SESSION_TIME:  05-31-2019 14:28:43.0412

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

STACK_TEXT:  
fffff880`0a0641d8 fffff800`0e8ab0ee : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`04fb1180 : nt!KeBugCheckEx
fffff880`0a0641e0 fffff800`0e87bff7 : fffffa80`00000000 fffff800`00000007 00000000`00026160 fffffa80`14d1f000 : nt! ?? ::FNODOBFM::`string'+0x4c6e
fffff880`0a064270 fffff800`0ede78e9 : fffff800`0ee0c360 fffff880`0a064420 fffff800`0ee0c360 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0a064370 fffff800`0e8949ef : fffff800`0e9e4180 00000000`00000001 00000000`00000000 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0a0643a0 fffff800`0e863ba1 : fffffa80`16202660 00000000`00000000 00000000`00000000 fffff800`0eb77bef : nt!KiInterruptDispatchNoLock+0xaf
fffff880`0a064530 fffff800`0eaf101f : 00000000`00000000 fffff880`0a064b60 00000000`00000000 fffff800`0e837333 : nt!KeFlushProcessWriteBuffers+0x65
fffff880`0a0645a0 fffff800`0ecd54a4 : 00000000`000d3d30 00000000`00008400 fffff880`0a064730 00000000`00000000 : nt!ExpGetProcessInformation+0x7f
fffff880`0a0646f0 fffff800`0eb4ab55 : 00000000`000d3d30 fffff800`0eb106b1 00000000`00000005 00000000`00000000 : nt!ExpQuerySystemInformation+0x1274
fffff880`0a064aa0 fffff800`0e8a1ad3 : fffffa80`164f55c0 fffff880`0a064b60 ffffffff`fe363c80 00000000`015dfb40 : nt!NtQuerySystemInformation+0x4d
fffff880`0a064ae0 00000000`77b59bea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00b5e138 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b59bea


THREAD_SHA1_HASH_MOD_FUNC:  0bf6ab374f5908864d0c16dff9ffba22ce7c694f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  c3e8b3705d61e9f5be26dba2b58caf21080059d5

THREAD_SHA1_HASH_MOD:  692dc177616b23b31c5615392ac069be10b8455d

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

PRIMARY_PROBLEM_CLASS:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

TARGET_TIME:  2019-05-31T08:54:52.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:  2019-04-30 03:35:34

BUILDDATESTAMP_STR:  190429-1700

BUILDLAB_STR:  win7sp1_ldr_escrow

BUILDOSVER_STR:  6.1.7601.24444.amd64fre.win7sp1_ldr_escrow.190429-1700

ANALYSIS_SESSION_ELAPSED_TIME:  65b

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_clock_watchdog_timeout_8_proc_analysis_inconclusive

FAILURE_ID_HASH:  {b37a9ee0-e89a-8796-d6e1-c509c7ba4f05}

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

0: kd> .load pde
=========================================================================================
 PDE v11.3 - Copyright 2017 Andrew Richards
=========================================================================================
0: kd> !dpx
Start memory scan  : 0xfffff8800a0641d8 ($csp)
End memory scan    : 0xfffff8800a065000 (Kernel Stack Base)

0xfffff8800a064240 : 0xfffff8800a0643a0 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180
0xfffff8800a064250 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180
0xfffff8800a064268 : 0xfffff8000e87bff7 : nt!KeUpdateSystemTime+0x377
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
0xfffff8800a064368 : 0xfffff8000ede78e9 : hal!HalpHpetClockInterrupt+0x8d
0xfffff8800a064370 : 0xfffff8000ee0c360 : hal!HalpKInterruptHeap+0x360
0xfffff8800a064380 : 0xfffff8000ee0c360 : hal!HalpKInterruptHeap+0x360
0xfffff8800a064390 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180
0xfffff8800a064398 : 0xfffff8000e8949ef : nt!KiInterruptDispatchNoLock+0xaf
0xfffff8800a0643a0 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180 Trap @ fffff8800a0643a0
0xfffff8800a064408 : 0xfffff8000e84df31 : nt!KiIpiSendRequest+0x2c1
0xfffff8800a0644c8 : 0xfffff8000e863b2f : nt!KiIpiSendPacket+0x4f
0xfffff8800a0644d0 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180
0xfffff8800a0644e0 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180
0xfffff8800a064508 : 0xfffff8000e863ba1 : nt!KeFlushProcessWriteBuffers+0x65
0xfffff8800a064588 : 0xfffff8000e88c4f4 : nt!KiSetAddressPolicy+0xc
0xfffff8800a064598 : 0xfffff8000eaf101f : nt!ExpGetProcessInformation+0x7f
0xfffff8800a0645b8 : 0xfffff8000e837333 : nt!KeStackAttachProcess+0x283
0xfffff8800a064638 : 0xfffff8000eadfd23 : nt!MmCopyVirtualMemory+0x317
0xfffff8800a064738 : 0xfffff8000e840000 : nt!ExpReleaseResourceForThreadLite+0x2b0
0xfffff8800a064768 : 0xfffff8000eb0cb8f : nt!SePrivilegedServiceAuditAlarm+0x47
0xfffff8800a064828 : 0xfffff8000e896344 : nt!SwapContext_PatchXSave+0xd4
0xfffff8800a064848 : 0xfffff8000eae9b59 : nt!SeDeleteAccessState+0x79
0xfffff8800a064868 : 0xfffff8000e895f4a : nt!KiSwapContext+0x7a
0xfffff8800a064878 : 0xfffff8000eb10a12 : nt!PsOpenProcess+0x1da
0xfffff8800a064978 : 0xfffff8000e9e4180 : nt!KiInitialPCR+0x180
0xfffff8800a0649a8 : 0xfffff8000e840722 : nt!KiCommitThreadWait+0x1d2
0xfffff8800a064a38 : 0xfffff8000e851fee : nt!KeDelayExecutionThread+0x186
0xfffff8800a064a58 : 0xfffff8000eafc326 : nt!ExMapHandleToPointer+0x26
0xfffff8800a064a98 : 0xfffff8000eb4ab55 : nt!NtQuerySystemInformation+0x4d
0xfffff8800a064aa8 : 0xfffff8000eb106b1 : nt!NtDelayExecution+0x59
0xfffff8800a064ad8 : 0xfffff8000e8a1ad3 : nt!KiSystemServiceCopyEnd+0x13
0xfffff8800a064ae0 : 0xfffffa80164f55c0 :  Trap @ fffff8800a064ae0

It looks like the processor 7 has hung:

Code:

0: kd> !prcb 7
PRCB for Processor 7 at fffff88004fb1180:
Current IRQL -- 0
Threads--  Current fffffa8012ba2b50 Next fffffa80167761a0 Idle fffff88004fc0240
Processor Index 7 Number (0, 7) GroupSetMember 80
Interrupt Count -- 000ce098
Times -- Dpc    00000000 Interrupt 00000000 
         Kernel 0000d971 User      00000ca4

Let's look at IDT:

Code:

0: kd> !idt

Dumping IDT: fffff8000f001000

00:	fffff8000e9d1100 nt!KiDivideErrorFaultShadow
01:	fffff8000e9d1180 nt!KiDebugTrapOrFaultShadow	Stack = 0xFFFFF8000F0049E0
02:	fffff8000e9d1200 nt!KiNmiInterruptShadow	Stack = 0xFFFFF8000F0047E0
03:	fffff8000e9d1280 nt!KiBreakpointTrapShadow
04:	fffff8000e9d1300 nt!KiOverflowTrapShadow
05:	fffff8000e9d1380 nt!KiBoundFaultShadow
06:	fffff8000e9d1400 nt!KiInvalidOpcodeFaultShadow
07:	fffff8000e9d1480 nt!KiNpxNotAvailableFaultShadow
08:	fffff8000e9d1500 nt!KiDoubleFaultAbortShadow	Stack = 0xFFFFF8000F0043E0
09:	fffff8000e9d1580 nt!KiNpxSegmentOverrunAbortShadow
0a:	fffff8000e9d1600 nt!KiInvalidTssFaultShadow
0b:	fffff8000e9d1680 nt!KiSegmentNotPresentFaultShadow
0c:	fffff8000e9d1700 nt!KiStackFaultShadow
0d:	fffff8000e9d1780 nt!KiGeneralProtectionFaultShadow
0e:	fffff8000e9d1800 nt!KiPageFaultShadow
10:	fffff8000e9d1880 nt!KiFloatingErrorFaultShadow
11:	fffff8000e9d1900 nt!KiAlignmentFaultShadow
12:	fffff8000e9d1980 nt!KiMcheckAbortShadow	Stack = 0xFFFFF8000F0045E0
13:	fffff8000e9d1a00 nt!KiXmmExceptionShadow
1f:	fffff8000e9d1a80 nt!KiApcInterruptShadow
2c:	fffff8000e9d1b00 nt!KiRaiseAssertionShadow
2d:	fffff8000e9d1b80 nt!KiDebugServiceTrapShadow
2f:	fffff8000e9d1c00 nt!KiDpcInterruptShadow
37:	fffff8000e9d1f38 hal!PicSpuriousService37 (KINTERRUPT fffff8000ee0c000)

3f:	fffff8000e9d1f78 hal!PicSpuriousService37 (KINTERRUPT fffff8000ee0c090)

50:	fffff8000e9d2000 hal!HalpCmciService (KINTERRUPT fffff8000ee0c1b0)

61:	fffff8000e9d2088 SCSIPORT!ScsiPortInterrupt (KINTERRUPT fffffa80133d0e40)

	                 ataport!IdePortInterrupt (KINTERRUPT fffffa80133d0d80)

	                 ataport!IdePortInterrupt (KINTERRUPT fffffa80133d0cc0)

71:	fffff8000e9d2108 *** ERROR: Module load completed but symbols could not be loaded for HECIx64.sys
HECIx64+0x1008 (KINTERRUPT fffffa80133d0c00)

	                 USBPORT!USBPORT_InterruptService (KINTERRUPT fffffa80133d0a80)

	                 dxgkrnl!DpiFdoLineInterruptRoutine (KINTERRUPT fffffa80133d0780)

92:	fffff8000e9d2210 HDAudBus!HdaController::Isr (KINTERRUPT fffffa80133d0840)

a2:	fffff8000e9d2290 HDAudBus!HdaController::Isr (KINTERRUPT fffffa80133d0900)

b0:	fffff8000e9d2300 NDIS!ndisMiniportMessageIsr (KINTERRUPT fffffa80133d0b40)

b1:	fffff8000e9d2308 ACPI!ACPIInterruptServiceRoutine (KINTERRUPT fffffa80133d0f00)

b2:	fffff8000e9d2310 USBPORT!USBPORT_InterruptService (KINTERRUPT fffffa80133d09c0)

d1:	fffff8000e9d2408 hal!HalpHpetClockInterrupt (KINTERRUPT fffff8000ee0c360)

d2:	fffff8000e9d2410 hal!HalpHpetRolloverInterrupt (KINTERRUPT fffff8000ee0c3f0)

df:	fffff8000e9d2478 hal!HalpApicRebootService (KINTERRUPT fffff8000ee0c2d0)

e1:	fffff8000e9d1c80 nt!KiIpiInterruptShadow
e2:	fffff8000e9d2490 hal!HalpDeferredRecoveryService (KINTERRUPT fffff8000ee0c240)

e3:	fffff8000e9d2498 hal!HalpLocalApicErrorService (KINTERRUPT fffff8000ee0c120)

fd:	fffff8000e9d2568 hal!HalpProfileInterrupt (KINTERRUPT fffff8000ee0c480)

fe:	fffff8000e9d2570 hal!HalpPerfInterrupt (KINTERRUPT fffff8000ee0c510)

Here I would update the Intel Management Engine Interface driver (check in SDI Download)

Code:

0: kd> lmvm hecix64
Browse full module list
start             end                 module name
fffff880`10e00000 fffff880`10e11000   HECIx64    (no symbols)           
    Loaded symbol image file: HECIx64.sys
    Image path: \SystemRoot\system32\DRIVERS\HECIx64.sys
    Image name: HECIx64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Oct 19 16:33:43 2010 (4CBE2AD7)
    CheckSum:         0001B15F
    ImageSize:        00011000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Among the pending IRPs, I found the VMWare driver:

Code:

7: kd> !irp fffffa8016736100
Irp is active with 1 stacks 1 is current (= 0xfffffa80167361d0)
 No Mdl: System buffer=fffffa80167bdb00: Thread fffffa80165bab50:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
>[IRP_MJ_DEVICE_CONTROL(e), N/A(0)]
            5  1 fffffa8015486060 fffffa80165ba810 00000000-00000000    pending
	       \Driver\hcmon
			Args: 000003d4 00000078 0x8101235c 00000000

Update VMWare (check updates in program)

Code:

7: kd> lmvm hcmon
Browse full module list
start             end                 module name
fffff880`09872000 fffff880`09884000   hcmon      (no symbols)           
    Loaded symbol image file: hcmon.sys
    Image path: \??\C:\Windows\system32\drivers\hcmon.sys
    Image name: hcmon.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Mar 10 08:02:49 2016 (56E19AA9)
    CheckSum:         00018156
    ImageSize:        00012000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I almost forgot. If the mouse software (Razer Chroma SDK) is unnecessary, it can be turned off

so what i need to do is uninstall VMware, Chroma SDK driver, and update the intel management driver. What else?

MrPepka · May 31, 2019

That's all. So:
1. Uninstall VMWare
2. Uninsatll Chroma SDK driver
3. Update Intel management engine driver

Blue screen while playing games like (Dota 2, CS:GO, Apex Legends)

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer