Windows 10: Corruption of display, Windows 10 Insider 17063, HP EliteBook G3 1040

1) Download and install the latest HP UEFI diagnostics: version 6.5
HP PC Hardware Diagnostics | HP® Official Site
2) This evening power on the computer and repetitively click the F2 key.
3) Run the HP UEFI diagnostics in loop until failure mode overnight
4) If there is a failure the testing will abort and display an error code.
5) If the loop until failure has made at least 2 runs click the keyboard escape key and confirm the pass results in the log.
Post the results of the HP UEFI diagnostics into the thread.

 

Argghhhhh. I ran the test all night, and like an idiot I hit the power button the laptop this morning (as I do every morning, but the screen were switched off rather than in sleep mode) before checking the test results *Sad. However, before I went to bed it had completed 6 rounds of the extended test with no issues.

 

1) Power on the computer > repetitively click the F2 key > navigate to the BIOS UEFI log > check the results > report into the thread.

2) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Speccy - System Information - Free Download
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer


3) Run this log collector and post a zip into the thread for troubleshooting:
log collector v2-beta06.zip

 

1) - I did - like a fool I powered off the machine before I got the results, but for the 6 times that it ran through the test before I went to bed last night, all had passed. I will need to run more test, but that will have to be this evening/tomorrow.

2) - OK, will do shortly

3) - OK , will do shortly

 

2) Done, core temps ideal around 44 deg C
3) See attached. Please remember that the latest HP provided Intel 550 drive is installed but disabled, thus the GPU.txt file shows and error.
HPELITEBOOK (05-01-2018 11 23).zip

 

Not in my experience, there are plenty of people on here messing with Laptop Graphics drivers and end up having considerable problems.
I get no problems yet only use Windows updates for Graphics drivers, which installs a suitable version of Intels iGPU driver, currently on mine .4549
There is a lesson there, though most won't like that.

Also the manufacturer no longer supplies driver updates, even the manufacturer specific stuff comes via Windows updates.

Preview (insider) versions of Windows are test versions so asking people to fix problems is basically not on as it's Microsoft who ultimately must fix the insider version of Windows. You are the unpaid tester, send the info to MS.

 

@Helmut Not sure if I fully agree with you here. Yeah, the insider builds are preview/test OS, but if there is an issue, is the resolution to that issue to simply start again with no thought as to diagnosis? I certainly have already posted on the Feedback pages of the insider program, but this will not usually lead to a direct response from MS. I am looking for alternatives to a global "switch it off an on again" type fix, and given this is a test build, messing with internals of the OS is probably OK and indeed maybe desirable (which is a part of the reason for running the test builds in the first place). To revert to a previous state certainly wouldn't be my first course of action in any diagnostic process, although this is exactly what I would expect from first line HP support.

@zbook and @freebooter were kind enough to lend their insight albeit most of this I have already tried, so I was looking to collective knowledge to gain a better understanding as to what might be the cause, and potentially the resolution, of the issue. As a final last step, resetting the OS may be the only solution left, but I don’t believe we are there yet, and I think it is useful to continue the troubleshooting further at this stage.

 

Although some driver updates can be obtained through Windows update, this is by no means exhaustive. Unfortunately, there are far too many different pieces of hardware available for Windows to cover them all! You should always check with the hardware manufacturer first when looking for an updated driver. When downloaded direct from the hardware maker, you'll know the driver is both valid and the most recent for the hardware.

Often new graphics card drivers are made available through Windows update but, in my experience, it is better to download them from the manufacturer’s website. Although Microsoft tests the updates before they are released with numerous computer configurations, you may have issues after running an update. Usually these problems are caused by other software programs, a unique computer or software configuration, or third-party drivers.

 

For all test /steps please post images into the thread.
If there are any problems posting images please use one drive or drop box share links.

Take Screenshot in Windows 10 General Tips Tutorials

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) powercfg.exe /hibernate off
6) 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

7) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

8) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread

9) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
9a) > on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
9b) > on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread

10) In the left lower corner search type services > open windows error reporting service > scroll to the startup type column > right click > left click on properties > post an image into the thread

11) Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
http://www.resplendence.com/whocrashed6) Click analyze > look for dead or deaddead in the results > post the results into the thread

12) Run the DM log collector after all of the above steps and post a zip into the thread:BSOD - Posting Instructions - Windows 10 Forums
BSOD - Posting Instructions - Windows 10 Forums

13) Open device manager > click view > show hidden devices > expand all rows > look for any row with an icon that is a yellow triangle with a black exclamation mark > post an image into the thread
13a) Post an image of display adapters > right click on Intel HD graphics 520 > left click properties > post an image of each of the tabs

14) In the left lower corner type: services > open services desktop application > post an image of the Intel services
14a) Right click on Intel HD Graphics control panel services > left click properties > post an image into the thread.

Take Screenshot in Windows 10 General Tips Tutorials


These were displayed as Problem Devices:

Code: Shrew Soft Virtual Adapter ROOT\VNET\0000 This device is disabled.[/quote] Code: Intel(R) HD Graphics 520 PCI\VEN_8086&DEV_1916&SUBSYS_80FA103C&REV_07\3&11583659&0&10 This device is disabled.[/quote]


Code: Event[987]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2017-12-24T23:59:48.189 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: HPElitebook Description: The driver \Driver\splitcam_hd_driver failed to load for the device ROOT\MEDIA\0001.[/quote] Code: Event[3019]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2018-01-02T10:48:07.900 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: HPElitebook Description: Windows failed fast startup with error status 0xC0280018.[/quote] Code: Event[5457]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2018-01-04T15:51:38.886 Event ID: 16 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: HPElitebook Description: Windows failed to resume from hibernate with error status 0xC0280018.[/quote] Code: Event[5941]: Log Name: System Source: Service Control Manager Date: 2018-01-04T16:03:58.840 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: HPElitebook Description: The Intel(R) HD Graphics Control Panel Service service failed to start due to the following error: The system cannot find the file specified.[/quote] Code: Event[6054]: Log Name: System Source: Service Control Manager Date: 2018-01-04T16:05:10.831 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: HPElitebook Description: The igfxCUIService2.0.0.0 service failed to start due to the following error: The system cannot find the file specified.[/quote] Code: Event[2035]: Log Name: System Source: Application Popup Date: 2017-12-30T18:16:27.433 Event ID: 26 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: HPElitebook Description: Application pop-up: Windows - Bad Image : Exception Processing Message 0xc000007b Parameters 0x7ff885551c08 0xffffffffc0000428 0x7ff885551c08 0x7ff885551c08[/quote] Code: Event[723]: Log Name: System Source: Microsoft-Windows-DriverFrameworks-UserMode Date: 2017-12-21T09:27:11.064 Event ID: 10111 Task: User-mode Driver problems. Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: HPElitebook Description: The device NXP NearFieldProximity Provider (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.[/quote] Code: Event[910]: Log Name: System Source: Microsoft-Windows-DriverFrameworks-UserMode Date: 2017-12-23T17:52:21.574 Event ID: 10111 Task: User-mode Driver problems. Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: HPElitebook Description: The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.[/quote] Code: Event[964]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-12-24T23:59:39.987 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: HPElitebook Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote] Code: Event[3049]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2018-01-02T10:48:10.553 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: HPElitebook Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote] Code: Event[3643]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2018-01-04T10:47:55.909 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: HPElitebook Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote] Code: Event[6525]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2018-01-05T09:41:36.755 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: HPElitebook Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote]

 

@zbook, FWIW, after running through SFC and DISM checks, I re-enabled the Display driver and I was back to a working system!!! TBH, I should have run through this from my own knowledge but like all things, you forget, so thank for helping me to remember. However for completeness, I thought I would run through the other element you suggested.
Some comments about the previous test results:


· The two driver picked up as have issues are correct and fine. The Shrew Soft VPN driver only become enabled when the VPN is active, and of course the HP 550 graphic driver was disabled because of the issues
· Unexpected crashes, some of these started occurring when the driver started experiencing issue, however, other are caused by hard shut downs (I kind of expect SOME issue on a pre-release OS).
· Some of the other crashes are more worry somesome

Whilst SFC found some issue, these were relatively innocuous (I remover Pester modules for build PowerShell tests as I installed a later version), and there was one missed .NET DLL.

Steps 1-6:

Code: Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. PS C:\WINDOWS\system32> sfc /scannow Beginning systemscan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios. 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 /restorehealth Deployment Image Servicing and Management tool Version: 10.0.17063.1000 Image Version: 10.0.17063.1000 [==========================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. Volume label is Windows. Stage 1: Examining basic file system structure ... 953600 file records processed. File verification completed. 7916 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 16687 reparse records processed. 1099968 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 16687 reparse records processed. Stage 3: Examining security descriptors ... Security descriptor verification completed. 73185 data files processed. CHKDSK is verifying Usn Journal... 37571488 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 479784639 KB total disk space. 428344812 KB in 553824 files. 284340 KB in 73186 indexes. 0 KB in bad sectors. 1085623 KB in use by the system. 65536 KB occupied by the log file. 50069864 KB available on disk. 4096 bytes in each allocation unit. 119946159 total allocation units on disk. 12517466 allocation units available on disk. PS C:\WINDOWS\system32> powercfg.exe /hibernate off PS C:\WINDOWS\system32>[/quote] I'll post the rest in due corse

 

Step 7:




8:







9a:



9b:




10:




11: Your link is incorrect, I should simply be Resplendence Software - WhoCrashed, automatic crash dump analyzer




12:
HPELITEBOOK-06_01_2018_174834_78.zip

13:
No devices with warinings
13a:
Remember, I have now re-enable this driver and all is functional




14:




15:





Last point of note. I re-ran the UEFI on board diagnostics over night, all System tests, Exhaustive, this completed 15 time with no errors.

 

For post #24 make the following changes:
1) Ccleaner > un-check memory dumps, windows logs
2) System failure > un-check automatically restart
3) Windows error reporting > change to automatic, click start, ok, reboot

4) The notebook computer is a little over clocked.
"Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz"
MaxSpeed: 2500
CurrentSpeed: 2592


5) Please return everything to stock.
If there is any turbo boost type software please uninstall it during the troubleshooting.

6) Run Prime95 - Stress Test Your CPUPrime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
Prime95 - Stress Test Your CPU Performance Maintenance Tutorials
7) Record maximum temperatures and duration of testing.
8) Aim for testing > 3 hrs and abort testing as needed for freezing, temperature changes (see link)
9) Please use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 General Tips Tutorials


10) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
11) Aim for testing for 1 hour.
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test Performance Maintenance Tutorials
12) All of these test should be done with the bios reset and no over clocking.
13) For each of the above tests please record maximum temperatures.
14) And please make sure that you use the Microsoft snipping tool to post images of each into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

 

1 -3 Done.

4 - However, I don't believe this system has been intentionally overclocked.

 

5 - No Turbo boost software of any description running. No modification ( that I am aware of) to BIOS

6: Will run tonight

 

I ran Prime95 last night very late, and left it, however, I don't think it made it more that 10 minutes before the system crashed. I came in today and the system had slept, but as soon I I work it, it green screened with a System Execution Exception. Annoyingly, I have run Who Crashed but no valid dump files were found. Looking at some of the logs, I noted that an application I use to provide virtual Web Camera crashed (Split Camera), which also show as giving an error previously, so I have removed this for now.

WRT the CPU system clock speed, after the crash I looked in BIOS to see if there were any settings that might affect this. The only things that I could see that might be a cause were:

• Advanced -> System options -> Turbo Boost (Enabled)
• Advanced -> System options -> Turbo Boost on DC (Disabled)
• Advanced -> Built in Device Options -> Boost Converter (Enabled)

Just in case, I reset the BIOS setting to factory defaults but these setting were not affected. TBH Turbo Boost should be enabled by default, so this is OK (as it only allows for temporary increase in clock speed), although I have no idea what Boost Converter is.

FWIW, the only settings that were altered by resetting the BIOS to factory defaults were the virtualisation technology settings (which I have re-enabled), and a Power Management setting (which I have not).

I then rebooted into a normal Windows session, such sown a few system tray applications, and re-ran Prime95, This time I watched the test on and off for the next few hours, and all was fine:

During the test and according to CPUID, you could see the CPU core frequency flit between its rated value (2495 GHz) and the speed you saw in the System Info file (2595 GHz), although nod of the screen show below show the higher frequency. When at idle, the frequency is higher still (up to 3095 GHz), although CPU temp is a lot lower. This, I believe is simply a natural behaviour of TurboBoost technology on Intel CPUs.

CPU temps hit a maximum of 86 deg C according to CPUID, although I did not see them above 83 deg C.















I will run the GPU stress test shortly