windows freeze DELL XPS15

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:
http://www.resplendence.com/whocrashed
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.

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.

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.

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.)

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.

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.

zbook said:

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:
http://www.resplendence.com/whocrashed
7) Above analyze click on tools > crash dump test > type: ACCEPT
8) After the dump click analyze > post a report into the thread.

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.

zbook said:

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.

If SFC /scannow does not find any errors do you still recommend I run the DISM command?
What information will the "crash dump test" from WHOCRASHED give us?

Thanks

There are some basic preventative maintenance tests that you can run on a regular basis. They are the scannow, restorehealth, and scan. They let you know if there are or are not problems with the operating system or drive files. If you find problems there are additional steps that you can make.
For whocrashed the software has a feature to create a dump and then process the dump. This will indicate whether dumps are or are not being created. Then when the DM log collector has collected all of the logs we can again see what was and was not done.
These are simple methods to check for problems in the computer environment.

zbook said:

There are some basic preventative maintenance tests that you can run on a regular basis. They are the scannow, restorehealth, and scan. They let you know if there are or are not problems with the operating system or drive files. If you find problems there are additional steps that you can make.
For whocrashed the software has a feature to create a dump and then process the dump. This will indicate whether dumps are or are not being created. Then when the DM log collector has collected all of the logs we can again see what was and was not done.
These are simple methods to check for problems in the computer environment.

TXT file attached with the copied and pasted info from the command prompt and the whocrashed report.
Attachment 152247Attachment 152248Attachment 152249

Thanks.

zbook said:

When using the reliability control panel click on each date that displays a red circle with a white x and view the problems. Going forward when you have hangs or freezes use the reliability control panel to see if you can find information about the problems that you are experiencing.

I recently was introduced to this reliability control panel...I have been keeping an eye on it but have not been able to discover anything of note yet.

zbook said:

Whocrashed has confirmed that the computer is capable of producing dump files.

There are methods to unintentionally delete dump files.

In the left lower corner search type: disk and click on disk cleanup > view the boxes that have checks > un-check system error memory dump files
If you use Ccleaner make sure windows > system > memory dumps is un-checked

I am not using ccleaner. The other two settings were already set as you suggested.

zbook said:

Please post the result of step 4 in post #41

They were in the text file in my last post.

zbook said:

And post a current image of startup and recovery settings that were used during the whocrashed dump.

Attachment 152252

zbook said:

Uncheck automatic restart so that you have time to view the bsod window. Sometimes when using Windows driver verifier the malfunctioning driver is displayed in the form *.sys. If you see a misbehaving driver displayed after the stop code, typically driver verifier detected violation, please post the misbehaving driver into the thread.

Have you read the information on using Windows driver verifier?
Have you made a brand new restore point?
Have you made a backup image of the drive?
Do you know the 3 methods to turn off Windows driver verifier?

I will start running driver verifier and see if it will generate any useful information.

The whocrashed results displayed that you created a manual crash on 8/30/2017.
What were the keyboard steps that you made to create the crash?


On Wed 8/30/2017 7:41:41 PM your computer crashed
crash dump file: C:\Windows\Minidump\083017-8234-01.dmp
This was probably caused by the following module: i8042prt.sys (i8042prt+0x9E7A)
Bugcheck code: 0xE2 (0x0, 0x0, 0x0, 0x0)
Error: MANUALLY_INITIATED_CRASH
file path: C:\Windows\system32\drivers\i8042prt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: i8042 Port Driver
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

zbook said:

The whocrashed results displayed that you created a manual crash on 8/30/2017.
What were the keyboard steps that you made to create the crash?


On Wed 8/30/2017 7:41:41 PM your computer crashed
crash dump file: C:\Windows\Minidump\083017-8234-01.dmp
This was probably caused by the following module: i8042prt.sys (i8042prt+0x9E7A)
Bugcheck code: 0xE2 (0x0, 0x0, 0x0, 0x0)
Error: MANUALLY_INITIATED_CRASH
file path: C:\Windows\system32\drivers\i8042prt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: i8042 Port Driver
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

See post #26