Windows 10: windows freeze DELL XPS15

The only way to enable manually initiat crashes is through editing the registry. It's creating two keys, you can always remove them later. There is nothing magical about this registry edit at all.

If you'd like to edit it yourself, following Microsoft's official documentation:

Forcing a System Crash from the Keyboard | Microsoft Docs

As for crash dumps not being produced, it's likely because your pagefile is too small, it should be a little more than the total amount of RAM you have if you are using a complete memory dump.

 

...I double click on your files and they automatically change the registry? What is the best way to remove these changes after I am done diagnosing?

I have had my pagefile set to 8500 MB and I have 8GB of RAM and I could not get a dump file to be created. Can you think of anything else that would keep the dumpfile from happening?

Thanks

 

Just double click the CrashOnLCtrlTildeTilde.reg file, it looks like you are comfortable changing your dump type so just go to that settings page again and switch it to Automatic (complete is fine, but it will be the entire size of RAM rather than just your current RAM used).

To undo the changes that CrashOnLCtrlTildeTilde.reg makes, open regedit and delete the following keys:

Code: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\kbdhid\crashdump[/quote] and
Code: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\crashdump[/quote]

 

On your attachment, go down and select small memory dump. That will limit the size of the file and put them in a minidump folder.

You can create a crash dump from Task Manager properties tab. Right click for the options. It does seem to be limited to specific processes so if it can help I will let the others make that determination.

It would be nice to know what was running your drive at 50% in your Task Manager listing.

 

His computer is freezing, we will need a lot more information than a mini dump. He also can't really create a crash dump of the system via task manager.

 

A dump via the task manager is solely from the selected process and won't help anything.

 

Spectrum,

How does this approach differ from using the Driver Verifier method someone previously mentioned?

Thanks for all your help.

 

Typing the key command causes the kernel to bugcheck, thus dumping physical memory to the pagefile where it will turn into a crash dump on your next boot. This will save the current state of what is going on in your computer, so we can hopefully see what is causing the complete system hang you are experiencing.

Driver verifier performs several tests for correctness as well as stresses drivers to hopefully determine which driver is to blame for pathological behavior.

 

Please post an updated zip: BSOD - Posting Instructions - Windows 10 Forums

 

My system froze. I forced a crash with CTRL~~. The BSOD screen came up for about 2 seconds and then the system rebooted. No .DMP was created.

Thoughts?

 

See if you can post an updated zip: BSOD - Posting Instructions - Windows 10 Forums

 

See attached.

The DMP file in there is from 8/30 and was created as I was experimenting with the CTRL~~ process. It is not related directly to one of my freezes.


DESKTOP-MBCUAVH-Tue_09_05_2017_191702_14.zip

 

In the logs were file drive problems.
There were also hibernation failures.


Open administrative command prompt and type or copy and paste:

1) powercfg.exe /hibernate off
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) 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
5) In the left lower corner search type reliability and post an image into the thread.
6) Download and install Whocrashed:
Resplendence Software - WhoCrashed, automatic crash dump analyzer
7) Above analyze click on tools > crash dump test > type: ACCEPT
8) After the dump click analyze > post a report into the thread.




Code: Event[2081]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-06-30T11:07:49.968 Event ID: 16 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-MBCUAVH Description: Windows failed to resume from hibernate with error status 0xC000009A.[/quote] Code: Event[1124]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-06-29T13:38:56.956 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-MBCUAVH Description: Windows failed fast startup with error status 0xC00000D4.[/quote] Code: Event[1589]: Log Name: System Source: volmgr Date: 2017-06-29T14:19:27.985 Event ID: 49 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-MBCUAVH Description: Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.[/quote] Code: Event[9221]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-07-31T21:11:13.589 Event ID: 140 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-MBCUAVH Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume9.(The I/O device reported an I/O error.)[/quote] Code: Event[16372]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-09-04T21:58:26.923 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-MBCUAVH Description: {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\karl\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost.[/quote] Code: Event[16261]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-09-04T16:12:49.829 Event ID: 98 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-MBCUAVH Description: Volume F: (\Device\HarddiskVolume9) requires an Online Scan. An Online Scan will automatically run as part of the next scheduled maintenance task. Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.[/quote]

 

Thanks for the reply.
(1) My 'F' drive is a detachable USB drive.
(2) The page file error is old...I have since enlarged my page file to make it larger than 8GB
(3) Could you explain what "dism /online /cleanup-image /restorehealth" does or direct me to an online resource that would explain it to me.

 

There are many dism commands. The dism command above will check the integrity of the operating system. It is a backup in case sfc /scannow in unable to complete or finds integrity violations that it cannot fix.