HP Omen 15-DC1000NS DRIVER_POWER_STATE_FAIL  

Dear all,

Since a couple of months I am constantly finding my laptop rebooted when I leave it for a while. It usually happens in idle. It does not matter it is connected to an external screen or using its own screen.

The computer has around 8 months and I dont know if I should just send it back to HPE with RMA.

Three different windows installations, a lot of NVIDIA drivers tested and the problems are still the same.

Attached the html exported from Bluescreenview.

I hope you guys can shed some light.

Thanks!

See:
BSOD - Posting Instructions

MrPepka said:

See:
BSOD - Posting Instructions

My bad MrPepka.

Here's the link with the logs gathered:

Dropbox - IAGOMEN-(2020-02-09_00-02-59).zip - Simplify your life

Kind regards

1. Run Driver Verifier Manager through type "verifier" in search bottom
2. Select "Create custom settings (for code developers)"
3. Tick all standard settings and 3 additional settings (force pending i/o request, irp logging and kernel synchronization delay fuzzing)
4. Select "Select driver names from a list"
5. Tick all 3rd party drivers
6. Apply changes and reboot computer

Hi suprimaso,

Welcome to the BSOD forum.

New computers should not have BSOD.
Typically they should be RMA.
The steps below are for troubleshooting and may be useful for the fix or the RMA.

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) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

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

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

14) Open Ccleaner > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

15) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)

16) re-install the Nvidia GPU driver from the HP website
https://support.hp.com/us-en/drivers...80?sku=5QR88EA


Display Driver Uninstaller Download version 18.0.2.2 (or newer version if available)
Official Display Driver Uninstaller DDU Download

Display Driver Uninstaller: How to use - Windows 7 Help Forums
Display Driver Uninstaller: How to use - Windows 7 Help Forums

Download Drivers | NVIDIA
Download Drivers | NVIDIA

17) Download and Install HP UEFI hardware diagnostics
(this typically creates a new partition)

18) Power on the computer repetitively clicking F2

19) Run the HP UEFI hardware diagnostics in system > extensive > loop until error overnight > in the AM if it has made two or more loops click esc > run GPU component tests > using a camera or smartphone camera take pictures of the tests performed and the results > post images into the thread

Code:

07/02/2020 20:44	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffff8d857c26d010
P3: fffff806277ebc2c
P4: ffffffffc000009a
P5: 4
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020720-8218-01.dmp
\\?\C:\Windows\TEMP\WER-10328-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34AC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34BD.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34DB.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34DC.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_116_69f7a3e457371027ba519cd2d778d94ceb916b_00000000_cab_b04d9418-278b-4279-a02d-fdd98803c6f3

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2e16c3b2-9a59-44a6-8fc6-9989a4f61038
Report Status: 2051
Hashed bucket: 
Cab Guid: 0
07/02/2020 20:44	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 116
P2: ffff8d857c26d010
P3: fffff806277ebc2c
P4: ffffffffc000009a
P5: 4
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020720-8218-01.dmp
\\?\C:\Windows\TEMP\WER-10328-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34AC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34BD.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34DB.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34DC.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_116_69f7a3e457371027ba519cd2d778d94ceb916b_00000000_b04d9418-278b-4279-a02d-fdd98803c6f3

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2e16c3b2-9a59-44a6-8fc6-9989a4f61038
Report Status: 4
Hashed bucket: 
Cab Guid: 0
29/01/2020 18:07	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 119
P2: 2
P3: ffffffffc000000d
P4: ffffa6025047f860
P5: ffff840ae20cd030
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\012920-8828-01.dmp
\\?\C:\Windows\TEMP\WER-11015-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3846.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3856.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3865.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3876.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_119_e313e2605ed9cc7d1bdb7024fe1d68aa6906750_00000000_cab_cb0f4e11-0172-488d-b5b1-fe3b387bf51d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 016438fb-e542-42b5-ac65-c5d294cbcfc2
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
29/01/2020 18:07	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 119
P2: 2
P3: ffffffffc000000d
P4: ffffa6025047f860
P5: ffff840ae20cd030
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\012920-8828-01.dmp
\\?\C:\Windows\TEMP\WER-11015-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3846.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3856.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3865.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3876.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_119_e313e2605ed9cc7d1bdb7024fe1d68aa6906750_00000000_cb0f4e11-0172-488d-b5b1-fe3b387bf51d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 016438fb-e542-42b5-ac65-c5d294cbcfc2
Report Status: 4
Hashed bucket: 
Cab Guid: 0
02/02/2020 14:50	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffff838c7c884060
P4: ffffa18e99e7f7b0
P5: ffff838c8594c9a0
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020220-9140-01.dmp
\\?\C:\Windows\TEMP\WER-13109-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F89.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F8A.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FA8.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FA9.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_76b837326676b0649b56ec211c6a70a3deb6939_00000000_cab_4aac0b07-fd3d-41a0-b5a3-c14dadf121c3

Analysis symbol: 
Rechecking for solution: 0
Report Id: 879eb524-3f46-4bf3-a40f-f9505f7be06d
Report Status: 2051
Hashed bucket: 
Cab Guid: 0
02/02/2020 14:50	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffff838c7c884060
P4: ffffa18e99e7f7b0
P5: ffff838c8594c9a0
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020220-9140-01.dmp
\\?\C:\Windows\TEMP\WER-13109-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F89.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F8A.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FA8.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FA9.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_76b837326676b0649b56ec211c6a70a3deb6939_00000000_4aac0b07-fd3d-41a0-b5a3-c14dadf121c3

Analysis symbol: 
Rechecking for solution: 0
Report Id: 879eb524-3f46-4bf3-a40f-f9505f7be06d
Report Status: 4
Hashed bucket: 
Cab Guid: 0
28/01/2020 19:32	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffff8c81545d4060
P4: ffff8a026c45f7b0
P5: ffff8c815aea88a0
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\012820-8906-01.dmp
\\?\C:\Windows\TEMP\WER-14187-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER442D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER442E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER444C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER445D.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_199e90289a141ed75ddfc5f4bba7699cd5b9c098_00000000_cab_0f43676e-2e26-4385-b6ac-5978492e71ec

Analysis symbol: 
Rechecking for solution: 0
Report Id: e04f334f-8797-4f19-a006-27664e7e3e1f
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
28/01/2020 19:32	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffff8c81545d4060
P4: ffff8a026c45f7b0
P5: ffff8c815aea88a0
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\012820-8906-01.dmp
\\?\C:\Windows\TEMP\WER-14187-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER442D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER442E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER444C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER445D.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_199e90289a141ed75ddfc5f4bba7699cd5b9c098_00000000_0f43676e-2e26-4385-b6ac-5978492e71ec

Analysis symbol: 
Rechecking for solution: 0
Report Id: e04f334f-8797-4f19-a006-27664e7e3e1f
Report Status: 4
Hashed bucket: 
Cab Guid: 0
08/02/2020 18:56	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffff8e8fd304d060
P4: fffffc054526f7b0
P5: ffff8e8fd8b7b060
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020820-8187-01.dmp
\\?\C:\Windows\TEMP\WER-12171-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BB1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BC1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BE0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BF0.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_39b5e090b0ded96c848fd71427262455e59622_00000000_cab_9f0d4f6a-92b5-4b53-a308-37963e669527

Analysis symbol: 
Rechecking for solution: 0
Report Id: f73d69da-1aab-4d73-b75b-57057aa8556c
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
08/02/2020 18:56	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffff8e8fd304d060
P4: fffffc054526f7b0
P5: ffff8e8fd8b7b060
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020820-8187-01.dmp
\\?\C:\Windows\TEMP\WER-12171-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BB1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BC1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BE0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BF0.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_39b5e090b0ded96c848fd71427262455e59622_00000000_9f0d4f6a-92b5-4b53-a308-37963e669527

Analysis symbol: 
Rechecking for solution: 0
Report Id: f73d69da-1aab-4d73-b75b-57057aa8556c
Report Status: 4
Hashed bucket: 
Cab Guid: 0
07/02/2020 19:37	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffff968fcbc8a060
P4: ffff95015d267c00
P5: ffff968fd2c3f0f0
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020720-7859-01.dmp
\\?\C:\Windows\TEMP\WER-11796-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A2A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A2B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A49.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A4A.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_92e4b258c9ccfdf0bba79bf26c14eb548b9a9c31_00000000_cab_607f5340-3f1c-4656-8b3e-8f9fd06db817

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6a52a020-e78e-4a3a-bb26-ca44d169fb93
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
07/02/2020 19:37	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffff968fcbc8a060
P4: ffff95015d267c00
P5: ffff968fd2c3f0f0
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020720-7859-01.dmp
\\?\C:\Windows\TEMP\WER-11796-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A2A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A2B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A49.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A4A.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_92e4b258c9ccfdf0bba79bf26c14eb548b9a9c31_00000000_607f5340-3f1c-4656-8b3e-8f9fd06db817

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6a52a020-e78e-4a3a-bb26-ca44d169fb93
Report Status: 4
Hashed bucket: 
Cab Guid: 0
02/02/2020 11:49	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffff9988c3ac6060
P4: ffffae0de4a3f7b0
P5: ffff9988cab84010
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020220-9156-01.dmp
\\?\C:\Windows\TEMP\WER-13171-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FD7.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FD8.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FF7.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4007.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_c4cfcb91124b4b1ea20ff9d28fae92e60fcef45_00000000_cab_467855b1-a082-4559-a2f6-b764cff460e1

Analysis symbol: 
Rechecking for solution: 0
Report Id: 00b7c2a2-20c9-49dd-b937-cade061b0c85
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
02/02/2020 11:49	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffff9988c3ac6060
P4: ffffae0de4a3f7b0
P5: ffff9988cab84010
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020220-9156-01.dmp
\\?\C:\Windows\TEMP\WER-13171-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FD7.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FD8.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3FF7.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4007.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_c4cfcb91124b4b1ea20ff9d28fae92e60fcef45_00000000_467855b1-a082-4559-a2f6-b764cff460e1

Analysis symbol: 
Rechecking for solution: 0
Report Id: 00b7c2a2-20c9-49dd-b937-cade061b0c85
Report Status: 4
Hashed bucket: 
Cab Guid: 0
01/02/2020 18:20	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffffcc8fea076060
P4: fffffe03baa6f7b0
P5: ffffcc8feee05010
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020120-9156-01.dmp
\\?\C:\Windows\TEMP\WER-13734-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4371.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4372.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4390.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER43A1.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_5318b1c829ee624589890880d2f47671cfe771_00000000_cab_9db24be6-1259-4821-adfc-d78815117664

Analysis symbol: 
Rechecking for solution: 0
Report Id: f7da1c3b-b527-460c-abcd-142632eb021b
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
01/02/2020 18:20	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffffcc8fea076060
P4: fffffe03baa6f7b0
P5: ffffcc8feee05010
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020120-9156-01.dmp
\\?\C:\Windows\TEMP\WER-13734-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4371.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4372.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4390.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER43A1.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_5318b1c829ee624589890880d2f47671cfe771_00000000_9db24be6-1259-4821-adfc-d78815117664

Analysis symbol: 
Rechecking for solution: 0
Report Id: f7da1c3b-b527-460c-abcd-142632eb021b
Report Status: 4
Hashed bucket: 
Cab Guid: 0
02/02/2020 18:16	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffffda0421283060
P4: fffff609c322f7b0
P5: ffffda042a6a3820
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020220-9125-01.dmp
\\?\C:\Windows\TEMP\WER-13671-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER419C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER41AD.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER41BC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER41CC.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9f_fb48a6b2a31b2fe24a2b708f39e9715fb867846_00000000_cab_e517a127-e8ec-42ec-8c53-bf38b09cc3e2

Analysis symbol: 
Rechecking for solution: 0
Report Id: 32cb946b-9bda-4451-9d36-946ffe8bdd66
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
02/02/2020 18:16	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 9f
P2: 3
P3: ffffda0421283060
P4: fffff609c322f7b0
P5: ffffda042a6a3820
P6: 10_0_18363
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\020220-9125-01.dmp
\\?\C:\Windows\TEMP\WER-13671-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER419C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER41AD.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER41BC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER41CC.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9f_fb48a6b2a31b2fe24a2b708f39e9715fb867846_00000000_e517a127-e8ec-42ec-8c53-bf38b09cc3e2

Analysis symbol: 
Rechecking for solution: 0
Report Id: 32cb946b-9bda-4451-9d36-946ffe8bdd66
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Code:

Name	NVIDIA GeForce RTX 2060
PNP Device ID	PCI\VEN_10DE&DEV_1F11&SUBSYS_8574103C&REV_A1\4&1197EB17&0&0008
Adapter Type	GeForce RTX 2060, NVIDIA compatible
Adapter Description	NVIDIA GeForce RTX 2060
Adapter RAM	(1,048,576) bytes
Installed Drivers	C:\Windows\System32\DriverStore\FileRepository\nvhmi.inf_amd64_b56324ae3c3b6bd9\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvhmi.inf_amd64_b56324ae3c3b6bd9\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvhmi.inf_amd64_b56324ae3c3b6bd9\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvhmi.inf_amd64_b56324ae3c3b6bd9\nvldumdx.dll
Driver Version	26.21.14.4219
INF File	oem23.inf (Section051 section)
Colour Planes	Not Available
Colour Table Entries	4294967296
Resolution	1920 x 1080 x 143 hertz
Bits/Pixel	32
Memory Address	0xBB000000-0xBBFFFFFF
Memory Address	0x90000000-0x9FFFFFFF
Memory Address	0xA0000000-0xA1FFFFFF
I/O Port	0x00004000-0x0000407F
IRQ Channel	IRQ 4294967274
I/O Port	0x000003B0-0x000003BB
I/O Port	0x000003C0-0x000003DF
Memory Address	0xA0000-0xBFFFF
Driver	C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVHMI.INF_AMD64_B56324AE3C3B6BD9\NVLDDMKM.SYS (26.21.14.4219, 22.20 MB (23,276,960 bytes), 08/02/2020 17:22)

Code:

nvlddmkm.sys Tue Dec 24 00:30:38 2019 (5E01CCAE)

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell Installing PowerShell - PowerShell | Microsoft Docs

PS 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.
PS C:\Windows\system32> dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.592

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.
PS C:\Windows\system32> dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.592

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\Windows\system32> chkdsk /scan
The type of the file system is NTFS.

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

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

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

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

249397247 KB total disk space.
66940796 KB in 119136 files.
81268 KB in 31355 indexes.
0 KB in bad sectors.
269663 KB in use by the system.
65536 KB occupied by the log file.
182105520 KB available on disk.

4096 bytes in each allocation unit.
62349311 total allocation units on disk.
45526380 allocation units available on disk.
PS C:\Windows\system32> wmic recoveros set autoreboot = false
Updating property(s) of '\\IAGOMEN\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.
PS C:\Windows\system32> wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\IAGOMEN\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.
PS C:\Windows\system32> wmic recoveros get autoreboot
AutoReboot
FALSE

PS C:\Windows\system32> wmic recoveros get DebugInfoType
DebugInfoType
7

PS C:\Windows\system32> bcdedit /enum {badmemory}
Invalid command line switch: /encodedCommand
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.
PS C:\Windows\system32>


Attachment 266274

Attachment 266275

Attachment 266276

So, shall I install drivers for a Windows version is not the one I am using?

I will end with the rest of the inputs tomorrow! Thank you very much!

For the commands some do work using PS.
The instructions were to use administrative command prompt: bcdedit /enum {badmemory}

For PS run this command: bcedit /enum all

Download and install the driver for Windows 1903:
https://support.hp.com/us-en/drivers...-2?sku=5QR88EA

Then perform Windows updates.

Then run the HP driver and support assistant to check for any additional driver or BIOS updates:
https://support.hp.com/us-en/drivers...-2?sku=5QR88EA

No BIOS / Firmware update were available, I usually have everything up to date.

The cmd that was pending:

PS C:\Windows\system32> bcdedit /enum all

Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {bootmgr}
{4b68e5f2-3f6e-11ea-a10b-c95c8967054c}
{0da11631-3f86-11ea-9eed-806e6f6e6963}
timeout 0

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume4
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-GB
inherit {globalsettings}
default {current}
resumeobject {4b68e5f3-3f6e-11ea-a10b-c95c8967054c}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Firmware Application (101fffff)
-------------------------------
identifier {0da11631-3f86-11ea-9eed-806e6f6e6963}
description USB Drive (UEFI)

Firmware Application (101fffff)
-------------------------------
identifier {4b68e5f2-3f6e-11ea-a10b-c95c8967054c}
device partition=\Device\HarddiskVolume4
description Solid State Disk

Firmware Application (101fffff)
-------------------------------
identifier {fad2cfc9-3f6e-11ea-9076-806e6f6e6963}
description USB Drive (UEFI) - Hard Drive

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 10
locale en-GB
inherit {bootloadersettings}
recoverysequence {4b68e5f5-3f6e-11ea-a10b-c95c8967054c}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {4b68e5f3-3f6e-11ea-a10b-c95c8967054c}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {4b68e5f5-3f6e-11ea-a10b-c95c8967054c}
device ramdisk=[\Device\HarddiskVolume3]\Recovery\WindowsRE\Winre.wim,{4b68e5f6-3f6e-11ea-a10b-c95c8967054c}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-gb
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[\Device\HarddiskVolume3]\Recovery\WindowsRE\Winre.wim,{4b68e5f6-3f6e-11ea-a10b-c95c8967054c}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Resume from Hibernate
---------------------
identifier {4b68e5f3-3f6e-11ea-a10b-c95c8967054c}
device partition=C:
path \Windows\system32\winresume.efi
description Windows Resume Application
locale en-GB
inherit {resumeloadersettings}
recoverysequence {4b68e5f5-3f6e-11ea-a10b-c95c8967054c}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume4
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-GB
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems No

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Local

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {4b68e5f6-3f6e-11ea-a10b-c95c8967054c}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume3
ramdisksdipath \Recovery\WindowsRE\boot.sdi
PS C:\Windows\system32>

The step 19 you mentioned, is not available as diagnostic. I can only perform Memory test (Which passed) and storage and hard disks tests. I cannot perform any "system > extensive > loop until error" diagnostics.

I think I am definetely sending the product to HP for RMA because after so much changes done troubleshooting this issue, it still happens...

Attachment 266316

I think what happens is a physical problem with the GPU. And as you said, having the computer not more than 9 months it makes no sense not send the laptop to HP for replacement.

Thank you very much for your inputs!

I will report back once HP gives me feedback.

You started Driver Verifier as recommended in one of the previous posts?

MrPepka said:

You started Driver Verifier as recommended in one of the previous posts?

Sorry, I missed yours!

I did what you requested of the driver verifier and when I rebooted, well, while closing windows I got a BSOD with Stop Code: SYSTEM_SERVICE_EXCEPTION

It gets stucked at 100% getting the data but it never reboots. I manually press power off and it gives BSOD again.

Now is diagnosing PC... it says it could not repair it... and I exitted the repairing and now I am back in the desktop...