windows freeze DELL XPS15

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

and

Code:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\crashdump

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.

Spectrum said:

Hi Carl,

Given that your system is completely locking up and not producing a crash dump, we'll need to force a system crash when it hangs.

1.) CrashOnLCtrlTildeTilde.reg - When merged with your registry it will trigger a bugcheck when you hold left control and tap tilde twice.

2.) ActiveCrashDump.reg - This will set your default crash dump type to "Active" which will give us more information about what is going on with your system during the hang.


Once your system hangs, try to force a crash with left ctrl tilde tilde. After a reboot you should see a new memory.dmp in C:\Windows. Compress that file and upload it to your preferred cloud hosting site, and post a link here.

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

Spectrum said:

Hi Carl,


My system froze. I forced a crash with CTRL~~. The screen went to the BSOD for about two seconds and then the system rebooted. No .DMP file was created.

Thoughts?
Given that your system is completely locking up and not producing a crash dump, we'll need to force a system crash when it hangs.

1.) CrashOnLCtrlTildeTilde.reg - When merged with your registry it will trigger a bugcheck when you hold left control and tap tilde twice.

2.) ActiveCrashDump.reg - This will set your default crash dump type to "Active" which will give us more information about what is going on with your system during the hang.


Once your system hangs, try to force a crash with left ctrl tilde tilde. After a reboot you should see a new memory.dmp in C:\Windows. Compress that file and upload it to your preferred cloud hosting site, and post a link here.

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

zbook said:

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.


Attachment 152100