My PC will freeze and BSOD multiple times a day. Sometimes it will recover from the freeze without a BSOD. It doesnt seem to be triggered by anything specific, just happens randomly. When it does I'll get the Hypervisor_Wachdog_Timeout BSOD but there might have been other names.
Please help.
DM collector logs attached
Hi Renier,
Welcome to Ten Forums BSOD forum.
1) Update the specs in the my computer section:
System Specs - Fill in at Ten Forums | 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.)
2) Open the website for the computer or motherboard manufacturer > support > enter the product or serial number or model > select the operating system > view drivers > post a URL or hyperlink into the thread
3) There are two log collectors: DM and BETA
Please run the BETA log collector and post a zip into this thread.
BSOD - Posting Instructions - Windows 10 Forums
https://www.tenforums.com/attachment...-v2-beta15.zip
(extract > open)
4) Run HD Tune (free edition) (all drives)
https://www.hdtune.com/
Post images into the thread for results on these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan
5) Run Memtest86+ version 5.01 if the RAM is DDR3
Memtest86+ - Advanced Memory Diagnostic Tool
Run Memtest86 if the RAM is DDR4
MemTest86 - Official Site of the x86 Memory Testing Tool
The computer has 64 GB RAM.
Run all test for 8 or more passes.
RAM testing takes approximately 1 - 2 hours /GB RAM
Remove all RAM modules except two and test for 8 or more passes.
If you are able to have a long period of downtime for the RAM testing you can run as many pairs as desired at the same time to completely test all RAM modules.
Use a camera or smartphone camera to take pictures of the test results and post images into the thread using share links (one drive, drop box, or google drive)
The testing can be performed overnight.
Just one error is a test fail and the test can be aborted.
Then test one RAM module at a time to differentiate good from malfunctioning RAM.
6) Make sure that there is no overclocking during the troubleshooting
7) Open administrative command prompt and type or copy and paste:
8) sfc /scannow
9) dism /online /cleanup-image /restorehealth
10) 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
11) chkdsk /r /v B:
Change the drive letter B: to the applicable drive
Run the command on all drives using the syntax: chkdsk /r /v C: or chdsks /r /v /D: changing the drive letter to the applicable drive
This may take many hours so plan to run overnight.
12) Use the text and images in this link to find the chkdsk reports in the event viewer > copy and paste > notepad > post share links into the thread using one drive, drop box, or google drive
Read Chkdsk Log in Event Viewer in Windows 10 | Tutorials
13) For any BSOD > run the BETA log collector and post a new zip into the thread
Code:The device, \Device\Harddisk3\DR5, has a bad block.Code:Windows removed bad memory regions from this PC.Code:The system failed to flush data to the transaction log. Corruption may occur in VolumeId: H:, DeviceName: \Device\HarddiskVolume10. (The I/O device reported an I/O error.)Code:An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Code:Volume H: (\Device\HarddiskVolume11) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.Code:The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.
Quote