Windows 10: Windows 10 randomly crashing

Hi.
First off if I'm posting this in the wrong section, I'm sorry, but I'm in a bit of a rush.
Windows 10 has been crashing on me constantly and it's even worse since it's not a blue screen, so I don't have a code to go off of or anything. After doing more research I've learned that some people refer to them as "system hangs". When it happens everything just stops working, but I can move my mouse around and at first, I thought if I just waited a while everything would start working again, but I waited a full hour for nothing. This has forced me to reinstall Windows to just update to the latest version and for a while that did help, but it has started crashing again and again and I have no idea why. Some people say it's a driver issue, others say it has to do with my hard disk not always running (really don't understand that one) and then Microsoft straight up told me it was because I didn't get a certain update.

I have no idea what to do about this, nor do I know what could be causing this, the only thing I really know is when to expect it. After a good 10-15 minutes of normal use, my C: drive will just skyrocket to 100% for no reason, I could just be on the normal desktop with nothing open and it will just jump and I've looked at my processes and nothing is making use of that much disk usage.

If I need to post all the parts of my system, let me know and I'll edit this post.


Not sure if this has anything to do with it, but when it crashed today I hadn't really shut my computer down for 2-3 days, I usually just put it to sleep.

:)

 

win 10 freezing and apps crashing

win 10 loads normally but then randomly crashes programs or freezes

 

Bsod with "Ättempted execute of noexecute memory"

Hello, so for the past weeks i have been having problems with my PC.

It randomly restarts, freezes or doesn't boot. But sometimes it crashes with said bsod.

I have reinstalled windows 10 completely, i have done the windows memorycheck, i am out of options.

If it is required, i can give you the minidump it generated.

This PC atm is a timebomb, it crashes totally randomly, but most noticeable during the startup period and 15 min after that. After that it might work for 1-4 hours with no issues before it crashes again.

 

This is a log collector that we use in the bsod forum. It will collect many logs and if there are any mini dumps it should collect them too.
BSOD - Posting Instructions - Windows 10 Forums
After running the DM log collector create a zip and post it into the thread.

 

Got it.
https://my.mixtape.moe/cgxegb.zip
Here you go.

 

The likely problem is either the graphics driver or the video card or both as the event log displayed that the video card stopped responding and recovered and the windows error reporting displayed bugcheck 141.

Bug Check 0x141: VIDEO_ENGINE_TIMEOUT_DETECTED
This indicates that one of the display engines failed to respond in timely fashion.

Perform the following steps:
1) Open administrative command prompt and type of copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) 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
6) Please indicate whether you had been or are currently using Ccleaner or any other cleaning software.
7) In the left lower corner search type clean > open disk cleanup > click OK > look for system error memory dump files > make sure this is unchecked
8) In the left lower corner search type system > open system control panel > on the left pane click advanced system settings > on the advanced tab in startup and recovery click settings > post an image into the thread
Take Screenshot in Windows 10 General Tips Tutorials
9) The BIOS: Version/Date American Megatrends Inc. F1, 3/3/2017 > update to F4
GA-A320M-HD2 (rev. 1.0) | Motherboard - GIGABYTE

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) So please make sure your files are backed up.
13) Please make a backup image with Macrium:

Macrium Software | Macrium Reflect Free:
Macrium Software | Your Image is Everything
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 best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the mothervboard manufacturer's website or from the Nvidia website.

The motherboard manufacturer's web site is preferred.

If you use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.
Official Display Driver Uninstaller DDU Download
Display Driver Uninstaller Download version 17.0.7.2
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA


Code: Event[1118]: Log Name: System Source: Display Date: 2017-11-01T21:15:09.749 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-IEFR6F0 Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: 11/3/2017 05:49 Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 1d7134c7-133b-4c00-8254-cd18643424b3 Problem signature: P1: 141 P2: ffffb582ed2204a0 P3: fffff8094a7b6478 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20171102-2249.dmp \\?\C:\Windows\TEMP\WER-101818734-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAF78.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAF78.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAFA8.tmp.txt \\?\C:\Windows\Temp\WERE9E2.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_45d4c90da3d1632212871e5154c9b51d6cef5d6_00000000_cab_25d1eb96 Analysis symbol: Rechecking for solution: 0 Report Id: 56443bf1-0233-4e75-bef1-c29cbcc1c111 Report Status: 268435456 Hashed bucket:11/5/2017 00:44 Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 34cd7341-7c05-4b12-a464-905c3fe13f98 Problem signature: P1: 141 P2: ffffb582e0c4b1a0 P3: fffff8094a7b6478 P4: 0 P5: 201c P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20171104-1743.dmp \\?\C:\Windows\TEMP\WER-256287015-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB115.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB125.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB145.tmp.txt \\?\C:\Windows\Temp\WERD4FA.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_7da8e3d41a5a2c16b650542ba11f99f197875f_00000000_cab_13c2d6dd Analysis symbol: Rechecking for solution: 0 Report Id: 7b77b6b5-54ae-4f58-b7a7-e19d5ebe1dc0 Report Status: 268435456 Hashed bucket: 11/2/2017 04:15 Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: fbd7a618-d0db-47ec-ab15-ff7d3615a092 Problem signature: P1: 141 P2: ffffb582e13bb4a0 P3: fffff8094a7b6478 P4: 0 P5: 15fc P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20171101-2115.dmp \\?\C:\Windows\TEMP\WER-9763375-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6D2.tmp.txt \\?\C:\Windows\Temp\WER367D.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_8f5a3fcc3c2bbfba364854ce692715dfdf7a87_00000000_cab_1d113841 Analysis symbol: Rechecking for solution: 0 Report Id: 7dba800e-57e2-46cb-a513-5ab0d62eb142 Report Status: 268435456 Hashed bucket:[/quote]

 

No idea how to spoiler stuff, but here are the results of my scan (Kinda messed up the second one, don't pay attention to that)

>Microsoft Windows [Version 10.0.16299.19]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning 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 /clean-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Image Version: 10.0.16299.19


Error: 87

The clean-image option is unknown.
For more information, refer to the help by running DISM.exe /?.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Image Version: 10.0.16299.19

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is Kabuto.

Stage 1: Examining basic file system structure ...
235776 file records processed.
File verification completed.
3671 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
160 reparse records processed.
314100 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
160 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
39163 data files processed.
CHKDSK is verifying Usn Journal...
38237760 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

234428415 KB total disk space.
64213888 KB in 188751 files.
118436 KB in 39164 indexes.
0 KB in bad sectors.
348731 KB in use by the system.
65536 KB occupied by the log file.
169747360 KB available on disk.

4096 bytes in each allocation unit.
58607103 total allocation units on disk.
42436840 allocation units available on disk.

C:\Windows\system32>

I don't use any cleaner programs at all.

Here's my Startup and Recovery stuff: https://i.imgur.com/2UCVcVO.png

I'm downloading the BIOS update right now and after it finishes, I'll reset it.

 

In startup and recovery settings un-check automatic restart.
This will enable you to view the BSOD window.
Sometimes along with the bugcheck you may be able to see the misbehaving driver.
If you see one then record it.
If there are any new bsod please post a new zip:
BSOD - Posting Instructions - Windows 10 Forums

 

Alright, if it crashes again I'll make sure to post the log here.
Updating the BIOS and changing the settings to default went pretty smooth and so far I haven't had any issues.
If it doesn't crash in 3 days, I'll consider this resolved.

Thank you so much for your help, this has been a massive headache.

 

Your welcome.
After bios update and Nvidia driver replacement it is wait and see.


If you open task manager and have high CPU, Memory, or Disk that may require additional troubleshooting.
The first step would be clean boot to see if there is any change.
The next step would be safe mode.
If the issues disappears with the current bios and driver changes then you again will wait and see.

There were additional drivers on the Gigabyte website that came out in 2017.
So run through all the drivers including the chip set drivers to update all drivers.