Random BSOD - while Chrome open

mawallace · 20 Apr 2018

I have been having issues over the last week or so with BSOD. Each time it's a different BSOD message -this evening it was CLOCK-WATCHDOGTIMEOUT.

I can't nail down whats happening. It seems to be random. Often it happens once the PC has been on for between 3/4 and and an hour.

The computer will refuse to reboot - even if I unplug the PC and turn it back on. If I leave for 5 mins it springs into life and is fine for the evening.

I'm at a loss as to what may be causingAttachment 185385 it!

zbook · 20 Apr 2018

mawallace said:

I'm at a loss as to what may be causingAttachment 185385 it!

The folder that was posted was blank.
1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) chkdsk /scan
6) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

7) After the above steps run both log collectors.
a) Post a zip into the thread for each of the log collectors.
b) For any recurrent BSOD please use the BETA log collector and paste a zip into the newest post.
c) DM log collector:
BSOD - Posting Instructions - Windows 10 Forums
d) BETA log collector:
See bottom of this web page:
BSOD - Posting Instructions - Windows 10 Forums
For text and images to run the BETA log collector see post #5 in this link:
DM Log tool problem Solved - Windows 10 Forums

8) Update the specs in the "My Computer" section:
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Windows 10 Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)
https://www.tenforums.com/profile.php?do=extra

9) Open file explorer > this PC > C: > in the right upper corner search for C:\windows\memory.dmp > zip > post a one drive or drop box share link into the thread.

mawallace · 23 Apr 2018

Microsoft Windows [Version 10.0.16299.371](c) 2017 Microsoft Corporation. All rights reserved.C:\Windows\system32>sfc/scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\Windows\system32>dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.371[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.C:\Windows\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.371[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\Windows\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 285952 file records processed.File verification completed. 9884 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 9803 reparse records processed. 385126 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 9803 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 49588 data files processed.CHKDSK is verifying Usn Journal... 37738760 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 487819263 KB total disk space. 75990452 KB in 222024 files. 152868 KB in 49589 indexes. 0 KB in bad sectors. 407923 KB in use by the system. 65536 KB occupied by the log file. 411268020 KB available on disk. 4096 bytes in each allocation unit. 121954815 total allocation units on disk. 102817005 allocation units available on disk.C:\Windows\system32>

Attachment 185859 Attachment 185860

zbook · 23 Apr 2018

The log files displayed bugchecks:
A
D1
101
There were no mini dump files.

1) Open file explorer > this PC > C: > in the right upper corner search for: C:\Windows\MEMORY.DMP > zip > post a one drive or drop box share link into this thread.
The size of the file is approximately 880 MB

2) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

3) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

4) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Windows 10 Tutorials

5) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:Speccy - Free Download - Piriform: Speccy - System Information - Free
Download Speccy | Find your computer specs, free!
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

6) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
a) Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 8 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM Windows 10 Tutorials

7) Make sure that there is no over clocking while troubleshooting.

8) Sometimes there are problems in the bios that produce bsod.

9) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

10) To ensure that there are no improper bios settings please reset the bios.
11) Sometimes there can be failure to boot after resetting the bios.
12) Backup the computer files to another drive or to the cloud.
13) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free

14) And please create a brand new restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

15) The BIOS: Version/Date American Megatrends Inc. 1708, 9/11/12
Upgrade the BIOS: 1708 > 2104

Version 2104
2013/09/264.4 MBytes
P8Z77-V PRO/THUNDERBOLT BIOS 2104
Improve system stability.

16) Run HD Tune: (on all drives)
http://www.hdtune.com/
Post images into the thread using one drive or drop box share links for the test results on these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan

17) For any BSOD run the beta log collector and post a new zip into this thread. And post a new memory dump.

Code:

1/3/18 7:51    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1a
P2: 3f
P3: 295fe
P4: a275d080
P5: b95f6bc0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\030118-67359-01.dmp
\\?\C:\Windows\TEMP\WER-921328-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5CE1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D1F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D40.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_3c71539468f19ef9126a0d4e87f67b12c11871a_00000000_cab_02de5d4e

Analysis symbol: 
Rechecking for solution: 0
Report ID: 53aaae4a-b0bd-4315-aee7-dc0f3722859d
Report Status: 4
Hashed bucket:27/11/17 21:45    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 3b
P2: c000001d
P3: fffff80517ff3d43
P4: fffff007fa274840
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\112717-48812-01.dmp
\\?\C:\Windows\TEMP\WER-764531-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF6ED.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF789.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF7A9.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_2ba1f63dd848c88dfa13f860f7739bbec86e803a_00000000_cab_0297f7a8

Analysis symbol: 
Rechecking for solution: 0
Report ID: 8bf0523a-19bd-4030-9628-411569107500
Report Status: 4
Hashed bucket:
31/3/18 12:07    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: a
P2: 4829acbd
P3: ff
P4: 0
P5: fffff8007965dd9e
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\033118-38750-01.dmp
\\?\C:\Windows\TEMP\WER-510906-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2880.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28BE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28EE.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_9660b4fdec214f24a83e359ba6c165fd8e49719f_00000000_cab_02ac28ed

Analysis symbol: 
Rechecking for solution: 0
Report ID: 7b6ecc56-a4dd-464d-a97f-efa813756b1d
Report Status: 4
Hashed bucket:
31/3/18 12:08    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: b0f6c9ed-b6ea-4e2d-a73d-3ccbbaa7b6ba

Problem signature:
P1: a
P2: 4829acbd
P3: ff
P4: 0
P5: fffff8007965dd9e
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\033118-38750-01.dmp
\\?\C:\Windows\TEMP\WER-510906-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2880.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28BE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28EE.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_9660b4fdec214f24a83e359ba6c165fd8e49719f_00000000_cab_02ac28ed

Analysis symbol: 
Rechecking for solution: 0
Report ID: 7b6ecc56-a4dd-464d-a97f-efa813756b1d
Report Status: 4
Hashed bucket:

Code:

31/3/18 12:23    Windows Error Reporting    Fault bucket AV_nt!SMKM_STORE_MGR_SM_TRAITS_::SmPageRead, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: b0f6c9ed-b6ea-4e2d-a73d-3ccbbaa7b6ba

Problem signature:
P1: a
P2: 4829acbd
P3: ff
P4: 0
P5: fffff8007965dd9e
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\033118-38750-01.dmp
\\?\C:\Windows\TEMP\WER-510906-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2880.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28BE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28EE.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_9660b4fdec214f24a83e359ba6c165fd8e49719f_00000000_cab_2e36e0a0

Analysis symbol: 
Rechecking for solution: 0
Report ID: 7b6ecc56-a4dd-464d-a97f-efa813756b1d
Report Status: 268435460
Hashed bucket:3/4/18 15:10    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Fermi_DmaCopy0, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: dcd35749-d056-40d5-b208-fa12a3e36b97

Problem signature:
P1: 141
P2: ffff9d007821d4a0
P3: fffff80bed576b2c
P4: 0
P5: 4
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20180403-1603.dmp
\\?\C:\Windows\TEMP\WER-188240765-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER70EF.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER714C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER716D.tmp.txt
\\?\C:\Windows\Temp\WER7D36.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_369caa3872e0f7172bebc1c6525a55f9edd1aeb4_00000000_cab_2bb9b52d

Analysis symbol: 
Rechecking for solution: 0
Report ID: 96411ea7-206e-4418-be6c-d08e3f1d06f2
Report Status: 268435456
Hashed bucket:
20/4/18 19:44    Windows Error Reporting    Fault bucket LKD_0x144_CONTEXT_ERROR_AFTER_SET_DEQUEUE_USBXHCI!TelemetryData_CreateReport_VEN_8086_DEV_1E31_REV_04, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: a8f4968d-22ef-401c-ae49-cbcc697d4a0a

Problem signature:
P1: 144
P2: 100a
P3: ffff818ff13d9970
P4: 0
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\USBXHCI\USBXHCI-20180420-2042.dmp
\\?\C:\Windows\TEMP\WER-714265-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER71DE.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER71EE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER71FF.tmp.txt
\\?\C:\Windows\Temp\WER73AF.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_b64be2ebd5f5dd77c68cd3d383dc4ea81920e2_00000000_cab_2ffc7739

Analysis symbol: 
Rechecking for solution: 0
Report ID: 98951342-e3e5-48a9-951b-3da9a5f4fb24
Report Status: 268435456
Hashed bucket:
1/3/18 7:51    Windows Error Reporting    Fault bucket PAGE_HASH_ERRORS_0x1a_3f, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: b29206ea-941f-4568-931c-238335ab325e

Problem signature:
P1: 1a
P2: 3f
P3: 295fe
P4: a275d080
P5: b95f6bc0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\030118-67359-01.dmp
\\?\C:\Windows\TEMP\WER-921328-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5CE1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D1F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D40.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_3c71539468f19ef9126a0d4e87f67b12c11871a_00000000_cab_378eaeca

Analysis symbol: 
Rechecking for solution: 0
Report ID: 53aaae4a-b0bd-4315-aee7-dc0f3722859d
Report Status: 268435456
Hashed bucket:

Code:

Event[2123]:  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2018-04-23T20:13:26.338
  Event ID: 19
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: mark-pc-nov2017
  Description: 
A corrected hardware error has occurred.


Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 0


The details view of this entry contains further information.

Code:

Event[609]:
  Log Name: System
  Source: Display
  Date: 2018-04-03T16:04:51.819
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: mark-pc-nov2017
  Description: 
Display driver nvlddmkm stopped responding and has successfully recovered.


Event[610]:
  Log Name: System
  Source: Display
  Date: 2018-04-03T16:04:51.957
  Event ID: 4101
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: mark-pc-nov2017
  Description: 
Display driver nvlddmkm stopped responding and has successfully recovered.

Code:

Event[2042]:  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2018-04-23T18:51:07.831
  Event ID: 29
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: mark-pc-nov2017
  Description: 
Windows failed fast startup with error status 0xC00000D4.

Code:

Event[2015]:  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2018-04-20T20:35:18.988
  Event ID: 1005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: mark-pc-nov2017
  Description: 
Unable to produce a minidump file from the full dump file.

mawallace · 23 Apr 2018

1) Open file explorer > this PC > C: > in the right upper corner search for: C:\Windows\MEMORY.DMP > zip > post a one drive or drop box share link into this thread.
The size of the file is approximately 880 MB

https://1drv.ms/u/s!AsLz3n_lNFaRgY0aA6lTPAPTiv8iMg

Please note I have zipped it.

2) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

Sorry I do not have CCcleaner

3) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.

Attachment 185866
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

Attachment 185867

zbook · 23 Apr 2018

1) For startup and recovery system failure:
un-check automatically restart

When automatically restart is unchecked and there is a BSOD you will see a BSOD window.
The BSOD window has a counter and rises to 100%.
Please allow this to rise to 100% before rebooting.
On the BSOD window you will see : ( with a bugcheck.
Sometimes you may see the misbehaving driver in the form *.sys.
If you see the misbehaving driver please record it and post it into the thread.
When there is a Windows upgrade or an in place upgrade repair this setting is typically set with the default automatically restart.
When is displays automatically restart there may be crashes that are unknown unless there were open software applications that were no longer open. So the un-checking will give you information about BSOD crashes. The rise to 100% is necessary so that there is sufficient time to create the dump files.

2) For Virtual memory:
a) un-check automatically manage paging file size for all drives
b) place the dot into no paging file
c) reboot
d) check automatically manage paging file size for all drives
e) place the dot into System managed size

3) After the above steps please post new images of the startup and recovery system failure and virtual memory windows into the thread using one drive or drop box share links.

The memory dump file debugging displayed:

Code:

THIS DUMP FILE IS PARTIALLY CORRUPT.

Code:

BugCheck 101, {18, 0, fffff8025b8a5180, 0}GetContextState failed, 0xD0000147Unable to get current machine context, NTSTATUS 0xC0000147***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.