Application Hangs (result in complete system hang)

Kyle · 30 Oct 2019

(Not a BSOD related issue)

So for some reason after clean installing Windows 10 Pro 1903 I get random application hangs and then my system just hangs entirely and forces me to manually reboot. The only errors that get logged is in Event Viewer which I've saved to a .RAR. My CPU isn't OC'd anymore, memory test/stress test was perfectly fine, no errors. (Even did a memory test with Memtest and using Microsoft's tool. I'm at a loss.

CRASH.zip DESKTOP-7TCEB6N-(2019-10-30_21-29-12).zip

Ztruker · 30 Oct 2019

Kyle, as the Attention block at the top of the forum and now at the top of your thread states:

Please do not post anything other than Windows 10 Blue Screen Of Death problems in this section.

I recommend posting this in General Support | Windows 10 Forumsor Installation & Upgrade

zbook · 30 Oct 2019

Hi Kyle,

Welcome to Ten Forum's BSOD forum.

There were no dump files collected.

The computer has been having BSOD with bugcheck 7F.

It can be easy to miss BSOD when automatically restart is checked.
The automatic restart will be modified later in the post.

The RAM is mismatched.

When were each of the modules added?

Code:

Location     : DIMM3
BankLabel    : BANK3
Manufacturer : Corsair      
MemoryType   : DDR3
FormFactor   : DIMM
Capacity     : 2GB
Speed        : 1333
Serial       : 0000000
PartNumber   : CMZ4GX3M2A1600C9  
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

Code:

Location     : DIMM1
BankLabel    : BANK1
Manufacturer : Corsair      
MemoryType   : DDR3
FormFactor   : DIMM
Capacity     : 4GB
Speed        : 1333
Serial       : 0000017
PartNumber   : CMZ12GX3M3A1600C9 
ECC          : False
TypeDetail   : {Synchronous, Unbuffered (Unregistered)}

Please perform the following steps:

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) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) bcdedit /enum {badmemory}

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) Make sure that there is no over clocking while troubleshooting.

12) Uninstall Driver Easy and any driver installed by this software

13) For all drivers please use the motherboard or component manufacturer's websites

14) 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 window into the thread

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

15) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan

16) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
How to use SeaTools for Windows | Seagate Support US

17) Post a share link for: PoW32kWatchdog-20191012-0218.dmp

Code:

Name                             LastWriteTime          Size (MB)
----                             -------------          ---------
PoW32kWatchdog-20191012-0218.dmp 12/10/2019 02:19:04 AM    533.65

18) In case there is any problem finding the file use: Everything
voidtools

19) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

z3r010 · 31 Oct 2019

Not a BSOD so moved from the BSOD section to general support.

Kyle · 31 Oct 2019

So the strange thing is is that a week ago before a recent Windows Update these hangs started I had no issues whatsoever. I've had 14GB RAM (3x4GB + 1x2GB) for a year or two and I've never had any actual issues with my memory. Granted, some of my previous BSODs blamed memory management/memory corruption, but I've tested each RAM stick multiple times and all tests have passed with no issues. System integrity is sound, as per the results from sfc /scannow and check disk.

Screenshots below.

Application Hangs (result in complete system hang)-cmd_3z2waahofv.png

Application Hangs (result in complete system hang)-cmd_adak8oasfj.png

Application Hangs (result in complete system hang)-cmd_djw6eachmy.png

Application Hangs (result in complete system hang)-cmd_uaateerjtr.png

Application Hangs (result in complete system hang)-cmd_xnmioeekqt.png

Note: I did perform these tasks in order as per zbook's response.

PoW32kWatchdog-20191012-0218.dmp: LiveKernelReports.zip - Google Drive

Driver Easy has been uninstalled.

SSD and External Drive F scanned with Chkdsk, reports nothing wrong. That being said, HD Tune does report my External Drive F with a temperature violation(?) and bad sectors. (But drive seems fine)

Application Hangs (result in complete system hang)-dllhost_uyqclaxcao.png

Application Hangs (result in complete system hang)-hdtunepro_0r3xvpamih.png

Application Hangs (result in complete system hang)-hdtunepro_3fholpmqyo.png

Application Hangs (result in complete system hang)-hdtunepro_gxgkc4drmf.png

Application Hangs (result in complete system hang)-hdtunepro_m0h54og9pb.png

Application Hangs (result in complete system hang)-hdtunepro_qvkeaibkky.png

Event Viewer log: Event Viewer - Chkdsk log.zip

joeandmarg0 · 31 Oct 2019

Are there any entries In Reliability History which could be related to this issue?

Kyle · 31 Oct 2019

joeandmarg0 said:

Are there any entries In Reliability History which could be related to this issue?

When you say "Reliability History", to what are you referring?

joeandmarg0 · 31 Oct 2019

In the bottom left search box,start typing in Reliability History after the first two or three letters,the application should appear at the top.Just left click on it to start it and you will see the page.The contents will give you any relevant info,via View Tech Details.If there any red flags,it is better to begin with the earlier one,the later flags could be because of the domino effect.

zbook · 31 Oct 2019

1) When available post images of steps #14, #16, and HD Tune full error scans for all drives

2) When running chkdsk there are multiple switches.
There are some that are superficial and quick and others that are deep and slower.

3) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

4) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

5) Run HD Sentinel: (free or trial edition)
Hard Disk Sentinel - HDD health and temperature monitoring
Hard Disk Sentinel - HDD health and temperature monitoring
Post images of each of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance

6) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

Kyle · 31 Oct 2019

There are many things in Reliability History, too many to screenshot. It shows a log that states Windows didn't shut down properly but doesn't show any other details. Application crashes, etc. but again don't show much information. Also every time I chkdsk and run those commands, no issues were found.

Application Hangs (result in complete system hang)-cmd_jtsfynnmwr.png

windowsreliability.zip