Screen goes black on A/C power

sims

New Member
Local time
8:26 PM
Posts
15
Thread starter
Hey all,

First time poster

I have been experiencing a stubborn issue with my laptop while I am playing a certain game. Whenever I launch the game, it works fine without any issues as long as I am using the laptop battery. As soon as I plug in the power cable into the laptop, the screen crashes. The laptop screen turns black, but the game sounds can still be heard, so the game is still running.

I am not able to pull up service manager, or minimize the game window or anything else. So I am forced to do a hard reset on the laptop.

Note, this is only happening with this game. I can play other games on AC power with no notable problems.

Things I have tried so far, and did not work:

-Reinstall the game (did this maybe 5-6 times)

-Reinstall windows

-Adjusted the screen resolution & dropped the screen frequency from 144hz to 60hz

-Updated all NVIDIA drivers to the latest, and updated BIOS

-Changed the power settings to match the same settings when the battery is used

-Started the game on battery mode, and then once loaded, I plug in the cable

-Run the game in compatibility mode (tried windows 8, windows 7)

-Reinstalled DirectX

My Laptop specs:
  • Processor: Intel i7 - 8750H CPU @ 2.2GHz
  • Installed Ram: 16 GB
  • System type: 64bit
  • Graphics card: NVIDIA GeForce RTX 2070 with Max-Q design
  • DAC Type: Integrated RAMDAC
  • Display Memory (VRAM): 8GB
  • Approx Total Memory: 16GB
  • Display Monitor: 1920x1080p 144Hz
  • Windows version: 21H1
Game requirements:
  • Windows 7/8/10. (32 or 64 bit)
  • 8 GB disk space available to use.
  • At least 512 MB ram memory, more is better.
  • Video Card that supports DirectX 9 and Shader Model 3.0

As you can see, the game requirements are very basic. Please help! I have nothing else I can think of that might work. I really hope this is not a hardware issue.
 
Windows Version
21H1

My Computer

System One

  • Operating System
    Windows 10

johngalt

Well-known member
WQ Insider
Member
VIP
Local time
8:26 PM
Posts
620
Location
3rd Rock
Hi, @sims, and Welcome to the Windows Questions forums!

First thing that I can think of - have you checked the games settings, namely display / video settings, to make sure it is not set to try to load some particular setting that may cause your video card to overheat? You could try reducing the settings down a tier (particularly the VSync - try enabling it, if disabled, or if enabled, lower the max framerate) and then see if it makes a difference.

It really sounds like the game is trying to force the card to exceed the limitations of your screen, and thus it blanks out. Even if the system requirements are low, doesn't mean that in game it can't still be cranked up to seemingly ludicrous settings.

BTW, what game is it? Also, do your fans ramp up when loading hte game and then enabling the AC power? If not, maybe try manually ramping them up also if you really want to leave your settings as they are in-game.
 

My Computer

System One

  • Operating System
    Windows 10 Pro X64
    Computer type
    PC/Desktop
    Manufacturer/Model
    The Beast Model A (homebrew)
    CPU
    AMD Ryzen 9 3950X
    Motherboard
    MSI MEG X570 GODLIKE
    Memory
    4 * Corsair Vengeance 32 GB 3600 MHz
    Graphics Card(s)
    eVGA GeForce GTX 970 SSC ACX 2.0 (04G-P4-3979-KB)
    Sound Card
    Realtek® ALC1220 Codec
    Monitor(s) Displays
    2 * Lenovo LT2323pwA Widescreeen @ 1920*1080
    Hard Drives
    3x Sabrent Rocket PCIe Gen4 NVMe M.2 1 TB SSD (SB-ROCKET-NVMe4-1TB)
    SanDisk Ultra SDSSDHII-960G-G25 960 GB SATA III SSD
    Crucial MX100 CT256MX100SSD1 256GB SATA III SSD
    2 * Seagate Barracuda 7200.12 ST31000528AS 1TB 7200 RPM (Old storage)
    PSU
    PC Power & Cooling’s Silencer Series 1050 Watt, 80 Plus Platinum
    Case
    Fractal Design Define 7 XL Dark ATX Full Tower Case
    Cooling
    NZXT KRAKEN Z73 73.11 CFM Liquid CPU Cooler + Air (3 * 140mm fans from case)
    Keyboard
    SteelSeries Apex Pro Wired Gaming Keyboard
    Mouse
    Logitech MX Master 3 Wireless Laser Mouse(shared)
    Internet Speed
    AT&T Lightspeed Gigabit duplex
    Browser
    Nightly|Chrome|Canary|Edge+ (Chromium) (in all 4 flavors)
    Antivirus
    Windows Defender + MB 4

zbook

Active Member
Member
VIP
Local time
7:26 PM
Posts
244
Please indicate the laptop:
manufacturer
model

Open the website for the manufacturer > support > enter product or serial number or model > drivers > post a URL / link
 

My Computer

System One

  • Operating System
    Windows 10

sims

New Member
Local time
8:26 PM
Posts
15
Thread starter
First thing that I can think of - have you checked the games settings, namely display / video settings, to make sure it is not set to try to load some particular setting that may cause your video card to overheat? You could try reducing the settings down a tier (particularly the VSync - try enabling it, if disabled, or if enabled, lower the max framerate) and then see if it makes a difference.
I checked the VSync setting, it was already switched off. I put the setting on and gave it a try, but it has no effect. The screen goes black once I plug in the charger. The game is Wartale (Online MMORPG). I've installed it on an old (9-10yr old laptop) Dell XPS and it works fine on power and on battery.

Please indicate the laptop:
manufacturer
model

Laptop is HP Omen 15-dc1027tx
 

My Computer

System One

  • Operating System
    Windows 10

iko22

Active Member
Member
VIP
Local time
1:26 AM
Posts
136
Location
South West England
Does the issue occur only when the game is run in Full Screen mode? Can it run satisfactorily in Windowed mode?
 

My Computer

System One

  • Operating System
    Windows 10

sims

New Member
Local time
8:26 PM
Posts
15
Thread starter
Does the issue occur only when the game is run in Full Screen mode? Can it run satisfactorily in Windowed mode?

Yeah I tried running it windowed, but the screen still blacks out when the laptop is on charge. The funny thing is, when its running in window mode, and if I pull up the browser or anything else while the game is in the background, the screen is fine and I can do anything. Once I Alt+tab back to the game, the screen goes black.

Yesterday I was messing around and went to device manager and disabled the graphics card from there, and launched the game while plugged in. The game launched fine, but barely playable as it was very laggy...
 

My Computer

System One

  • Operating System
    Windows 10

iko22

Active Member
Member
VIP
Local time
1:26 AM
Posts
136
Location
South West England
It is not immediately obvious what is the underlying cause, however there are several setting you might like to check:

Power Plan settings (Windows setting) - is the Power Plan set to Balanced, Power Saver, High Performance or Custom? If the Power Plan is a Custom Plan, then check the Maximum and Minimum processor states in the Advanced Power Plan settings.

Game Mode settings (Windows 10 setting) - The default setting is On. This is a Windows 10 setting that is supposed to optimise your computer for your game, however some people report that the computer works better with Game Mode switched Off. Another potential issue could be that the computer does not recognise your game as a game, and so the Game Mode does not switch on when it is supposed to. In that case you may need to turn on Game Mode for an Individual Game.

GPU scaling (Nvidia control panel setting) - GPU scaling automatically adapts the game screen ratio to the actual screen ratio of your monitor. The drawback is that the scaling requires a higher processing power. Switching off may free up resources. Also check the in-game aspect ratio settings match your monitor, if there are any.

I would try the GPU scaling first as it is the least complicated and most obvious candidate.
 

My Computer

System One

  • Operating System
    Windows 10

sims

New Member
Local time
8:26 PM
Posts
15
Thread starter
Thanks for the reply iko22

Power Plan settings (Windows setting) - is the Power Plan set to Balanced, Power Saver, High Performance or Custom? If the Power Plan is a Custom Plan, then check the Maximum and Minimum processor states in the Advanced Power Plan settings.
Power plan is set to High performance. I checked the advanced settings for the power plan & the max processor state is 100% and the min is 5%

Game Mode settings (Windows 10 setting) - The default setting is On. This is a Windows 10 setting that is supposed to optimise your computer for your game, however some people report that the computer works better with Game Mode switched Off. Another potential issue could be that the computer does not recognise your game as a game, and so the Game Mode does not switch on when it is supposed to. In that case you may need to turn on Game Mode for an Individual Game.
I didnt know about this, I switched it off.

GPU scaling (Nvidia control panel setting) - GPU scaling automatically adapts the game screen ratio to the actual screen ratio of your monitor. The drawback is that the scaling requires a higher processing power. Switching off may free up resources. Also check the in-game aspect ratio settings match your monitor, if there are any.
I think this actually helped! I managed to launch the game while the power cable was connected and played for a good 20-30 mins before the screen went black again, but the game was still running I could hear the sound. This time I noticed the laptop was hot, it seems the fans are not able to keep up with the cooling? I placed a cooling pad under the laptop and tried again, but it didn't help.
 

My Computer

System One

  • Operating System
    Windows 10

zbook

Active Member
Member
VIP
Local time
7:26 PM
Posts
244
Download and install:
HP Diagnostics UEFI version 8.1.0

Plan to run the tests overnight:

Power on the computer > repetitively click F2 or F10 to open the HP UEFI diagnostics > click extensive > click loop until error > the next day if there were two or more loops > click esc > take pictures > post images of the tests performed with results > run component tests as needed (many are interactive) (run all graphic tests) > post images into he thread
 

My Computer

System One

  • Operating System
    Windows 10

johngalt

Well-known member
WQ Insider
Member
VIP
Local time
8:26 PM
Posts
620
Location
3rd Rock
Thanks for the reply iko22


Power plan is set to High performance. I checked the advanced settings for the power plan & the max processor state is 100% and the min is 5%


I didnt know about this, I switched it off.


I think this actually helped! I managed to launch the game while the power cable was connected and played for a good 20-30 mins before the screen went black again, but the game was still running I could hear the sound. This time I noticed the laptop was hot, it seems the fans are not able to keep up with the cooling? I placed a cooling pad under the laptop and tried again, but it didn't help.

Yup, that's why I suggested manually ramping up your fans. The GPU Scaling and the GPU overheating are two increasingly common problems.

EDIT: Added the following:

To ramp up your fans, you may need a 3rd party utility to do so. The reason I say may is that there may be a utility already installed with your system from HP that accomplishes this without the need to install another app - but, TBH, I'd still go with either of the below mentioned apps (assuming there is a dedicated GPU-specific fan) because, although it seems their focus is overclocking your video cards, in fact, I've only ever used both of them to manually set he fan speeds for my graphics cards. Also, with this being a laptop, the fans fare system fans, not fans directly on a GPU (almost always, with a vew few distinct exceptions), so using the native HP app may be the only option that you have, unless you happen to have a dedicated fan for the laptop GPU.

If you do happen to have dedicated gpu fan(s) in your system, apps like MSI Afterburner or eVGA Precision X1 should work well - I've used Precision X1 and it works perfectly fine even if you don't own an eVGA graphics card, and I'm currently using MSI Afterburner with my eVGA Discrete GPU on my system. Of course, mine is a desktop system, not a laptop, and, again, these are got hte GPU dedicated fans only.
 
Last edited:

My Computer

System One

  • Operating System
    Windows 10 Pro X64
    Computer type
    PC/Desktop
    Manufacturer/Model
    The Beast Model A (homebrew)
    CPU
    AMD Ryzen 9 3950X
    Motherboard
    MSI MEG X570 GODLIKE
    Memory
    4 * Corsair Vengeance 32 GB 3600 MHz
    Graphics Card(s)
    eVGA GeForce GTX 970 SSC ACX 2.0 (04G-P4-3979-KB)
    Sound Card
    Realtek® ALC1220 Codec
    Monitor(s) Displays
    2 * Lenovo LT2323pwA Widescreeen @ 1920*1080
    Hard Drives
    3x Sabrent Rocket PCIe Gen4 NVMe M.2 1 TB SSD (SB-ROCKET-NVMe4-1TB)
    SanDisk Ultra SDSSDHII-960G-G25 960 GB SATA III SSD
    Crucial MX100 CT256MX100SSD1 256GB SATA III SSD
    2 * Seagate Barracuda 7200.12 ST31000528AS 1TB 7200 RPM (Old storage)
    PSU
    PC Power & Cooling’s Silencer Series 1050 Watt, 80 Plus Platinum
    Case
    Fractal Design Define 7 XL Dark ATX Full Tower Case
    Cooling
    NZXT KRAKEN Z73 73.11 CFM Liquid CPU Cooler + Air (3 * 140mm fans from case)
    Keyboard
    SteelSeries Apex Pro Wired Gaming Keyboard
    Mouse
    Logitech MX Master 3 Wireless Laser Mouse(shared)
    Internet Speed
    AT&T Lightspeed Gigabit duplex
    Browser
    Nightly|Chrome|Canary|Edge+ (Chromium) (in all 4 flavors)
    Antivirus
    Windows Defender + MB 4

sims

New Member
Local time
8:26 PM
Posts
15
Thread starter
Download and install:
HP Diagnostics UEFI version 8.1.0

Plan to run the tests overnight:

Power on the computer > repetitively click F2 or F10 to open the HP UEFI diagnostics > click extensive > click loop until error > the next day if there were two or more loops > click esc > take pictures > post images of the tests performed with results > run component tests as needed (many are interactive) (run all graphic tests) > post images into he thread
Ok so I did this overnight, and attached the files from the system test. It seems all tests have passed without any issues. I also did one component test on the VRAM.
 

Attachments

  • SystemDiags.pdf
    155.7 KB · Views: 4
  • SystemDiagsCeeHistory.pdf
    58.1 KB · Views: 4

My Computer

System One

  • Operating System
    Windows 10

sims

New Member
Local time
8:26 PM
Posts
15
Thread starter
To ramp up your fans, you may need a 3rd party utility to do so. The reason I say may is that there may be a utility already installed with your system from HP that accomplishes this without the need to install another app - but, TBH, I'd still go with either of the below mentioned apps (assuming there is a dedicated GPU-specific fan) because, although it seems their focus is overclocking your video cards, in fact, I've only ever used both of them to manually set he fan speeds for my graphics cards. Also, with this being a laptop, the fans fare system fans, not fans directly on a GPU (almost always, with a vew few distinct exceptions), so using the native HP app may be the only option that you have, unless you happen to have a dedicated fan for the laptop GPU.

If you do happen to have dedicated gpu fan(s) in your system, apps like MSI Afterburner or eVGA Precision X1 should work well - I've used Precision X1 and it works perfectly fine even if you don't own an eVGA graphics card, and I'm currently using MSI Afterburner with my eVGA Discrete GPU on my system. Of course, mine is a desktop system, not a laptop, and, again, these are got hte GPU dedicated fans only.
Thanks for the explanation. A silly question but, how can I tell if my system has a dedicated fan for graphics card? It most likely does not have one specifically for the graphics card, but I am wondering if there is a way to tell, or do I have to open the laptop up and visually check?
 

My Computer

System One

  • Operating System
    Windows 10

johngalt

Well-known member
WQ Insider
Member
VIP
Local time
8:26 PM
Posts
620
Location
3rd Rock
No, no need to open the laptop - the owner's manual should tell you, or you could simply download MSI afterburner and install it - it should tell you if there is a configurable fan.

Be sure to first explore adjusting how hte system fans run, changing them ot active, or aggressive, to blow when temps get warm, as opposed to when hot, at least when on A/C power.
 

My Computer

System One

  • Operating System
    Windows 10 Pro X64
    Computer type
    PC/Desktop
    Manufacturer/Model
    The Beast Model A (homebrew)
    CPU
    AMD Ryzen 9 3950X
    Motherboard
    MSI MEG X570 GODLIKE
    Memory
    4 * Corsair Vengeance 32 GB 3600 MHz
    Graphics Card(s)
    eVGA GeForce GTX 970 SSC ACX 2.0 (04G-P4-3979-KB)
    Sound Card
    Realtek® ALC1220 Codec
    Monitor(s) Displays
    2 * Lenovo LT2323pwA Widescreeen @ 1920*1080
    Hard Drives
    3x Sabrent Rocket PCIe Gen4 NVMe M.2 1 TB SSD (SB-ROCKET-NVMe4-1TB)
    SanDisk Ultra SDSSDHII-960G-G25 960 GB SATA III SSD
    Crucial MX100 CT256MX100SSD1 256GB SATA III SSD
    2 * Seagate Barracuda 7200.12 ST31000528AS 1TB 7200 RPM (Old storage)
    PSU
    PC Power & Cooling’s Silencer Series 1050 Watt, 80 Plus Platinum
    Case
    Fractal Design Define 7 XL Dark ATX Full Tower Case
    Cooling
    NZXT KRAKEN Z73 73.11 CFM Liquid CPU Cooler + Air (3 * 140mm fans from case)
    Keyboard
    SteelSeries Apex Pro Wired Gaming Keyboard
    Mouse
    Logitech MX Master 3 Wireless Laser Mouse(shared)
    Internet Speed
    AT&T Lightspeed Gigabit duplex
    Browser
    Nightly|Chrome|Canary|Edge+ (Chromium) (in all 4 flavors)
    Antivirus
    Windows Defender + MB 4

zbook

Active Member
Member
VIP
Local time
7:26 PM
Posts
244
Please upload results after running V2:


There is a log in the BIOS for HP UEFI hardware diagnostics.
Power on > repetitively click F2 or F10 > take a picture > upload an image
 

My Computer

System One

  • Operating System
    Windows 10

sims

New Member
Local time
8:26 PM
Posts
15
Thread starter
Please upload results after running V2:
There is a log in the BIOS for HP UEFI hardware diagnostics.
Power on > repetitively click F2 or F10 > take a picture > upload an image

Here is the logs from V2 attached and the image of the UEFI hardware diagnostics
 

Attachments

  • DESKTOP-3THLKJL-(2021-06-10_18-34-40).zip
    1.4 MB · Views: 4
  • UEFI diagnostics.jpeg
    UEFI diagnostics.jpeg
    150 KB · Views: 7

My Computer

System One

  • Operating System
    Windows 10

zbook

Active Member
Member
VIP
Local time
7:26 PM
Posts
244
The logs displayed a recent BSOD.

1) Open administrative command prompt (ACP) 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) wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
12) wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
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) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
14) re-install the Nvidia GPU driver from the Nvidia website
15) make sure that you check the clean install box and if available install the physx driver.

Display Driver Uninstaller Download version 18.0.3.5 (or newer version if available)

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

Download Drivers | NVIDIA


Code:
nvlddmkm.sys Thu May 27 12:07:47 2021 (60AFEE03)
 
Last edited:

My Computer

System One

  • Operating System
    Windows 10

sims

New Member
Local time
8:26 PM
Posts
15
Thread starter
Hi zbook, here is the copy / paste of the above steps.

Microsoft Windows [Version 10.0.19043.1052]
(c) Microsoft Corporation. All rights reserved.

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 found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1052

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\system32> dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1052

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

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.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
549888 file records processed.
File verification completed.
Phase duration (File record verification): 5.85 seconds.
5776 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.48 milliseconds.

Stage 2: Examining file name linkage ...
187 reparse records processed.
793572 index entries processed.
Index verification completed.
Phase duration (Index verification): 13.71 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 1.29 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.54 milliseconds.
187 reparse records processed.
Phase duration (Reparse point and Object ID verification): 3.73 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 32.71 milliseconds.
121843 data files processed.
Phase duration (Data attribute verification): 0.97 milliseconds.
CHKDSK is verifying Usn Journal...
39878208 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 178.57 milliseconds.

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

249416758 KB total disk space.
105911664 KB in 421926 files.
238564 KB in 121844 indexes.
0 KB in bad sectors.
665482 KB in use by the system.
65536 KB occupied by the log file.
142601048 KB available on disk.

4096 bytes in each allocation unit.
62354189 total allocation units on disk.
35650262 allocation units available on disk.
Total duration: 21.09 seconds (21090 ms).

C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-3THLKJL\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home Single Language|C:\\Windows|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-3THLKJL\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home Single Language|C:\\Windows|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


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


C:\Windows\system32>wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
Updating property(s) of '\\DESKTOP-3THLKJL\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP-3THLKJL"'
Property(s) update successful.

C:\Windows\system32>wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\Windows\system32>bcdedit /enum {badmemory}

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

C:\Windows\system32>
 

My Computer

System One

  • Operating System
    Windows 10

sims

New Member
Local time
8:26 PM
Posts
15
Thread starter
13) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
14) re-install the Nvidia GPU driver from the Nvidia website
15) make sure that you check the clean install box and if available install the physx driver.
Ok, I've re-installed the graphics drivers once again, but I did not get the check for step 15 above.
 

My Computer

System One

  • Operating System
    Windows 10

zbook

Active Member
Member
VIP
Local time
7:26 PM
Posts
244
First scannow:
Code:
Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow:
Code:
Windows Resource Protection did not find any integrity violations.


BSOD can be missed when automatic restart is checked.
The above commands modified the default settings so that automatically restart is unchecked.
If there is a recurrent BSOD it is now more likely you will see: :(



Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
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.
a) Record the maximum temperature and post the maximum temperature into the thread.
b) Record the test duration and post the uninterrupted test duration into the thread.
c) Aim for testing 1 hour.
d) Use the Microsoft snipping tool to post images into the thread.

Take Screenshot in Windows 10 Windows 10 General Tips Tutorials



Code:
6/5/2021 9:26 AM    Windows Error Reporting    Fault bucket 0x113_19_nvlddmkm!unknown_function, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 4cc56fa6-5caf-4b43-b2e0-4be0557754d3

Problem signature:
P1: 113
P2: 19
P3: 1
P4: 10de
P5: 1f50
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\060521-9968-01.dmp
\\?\C:\Windows\TEMP\WER-41765-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE04D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE05E.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_113_f2acb13865f772d03ca39936e4f6dcecad77824_00000000_cab_a1af0b52-eff7-480d-ae4c-cc4ee25fe73d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 45406daf-10fd-4ed6-bd5c-e63f2874c341
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0


Code:
6/3/2021 6:16 PM    Windows Error Reporting    Fault bucket BAD_DUMPFILE, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 66b776d0-4268-4060-817e-c9c27fb80223

Problem signature:
P1: 141
P2: ffffb88377a24050
P3: fffff80561356f64
P4: 0
P5: 2838
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210603-1352.dmp
\\?\C:\Windows\TEMP\WER-381703-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE065.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE075.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE074.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE094.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_a0adf372958593365521143f7e383ebaa956089_00000000_cab_9b9eec8c-e152-4b65-96ac-761980765346

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9b9eec8c-e152-4b65-96ac-761980765346
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
6/3/2021 9:41 AM    Windows Error Reporting    Fault bucket BAD_DUMPFILE, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 7844706b-168d-44bd-96ad-00b71bb4f370

Problem signature:
P1: 141
P2: ffff96080d963010
P3: fffff8003ea16f64
P4: 0
P5: 128c
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210603-1340.dmp
\\?\C:\Windows\TEMP\WER-263906-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER13E2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER13F3.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER13F4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1404.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_c4bacec0e4ec58b65d4babd33b21aca243423e_00000000_cab_20b1ce41-d73c-41a8-be00-b419277cda11

Analysis symbol: 
Rechecking for solution: 0
Report Id: 20b1ce41-d73c-41a8-be00-b419277cda11
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
6/4/2021 9:06 PM    Windows Error Reporting    Fault bucket BAD_DUMPFILE, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: c2944122-4675-49f1-9225-6112c2b0fbf5

Problem signature:
P1: 141
P2: ffffe10ca7c1c010
P3: fffff8059bb76f64
P4: 0
P5: 104c
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210603-2341.dmp
\\?\C:\Windows\TEMP\WER-607890-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER54AC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER54BC.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER54BF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER54DF.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_9ac2294a86a2a31178cb9ba9ce9c2bfbf219d14_00000000_cab_a97abe86-abfc-463c-9791-2d7d0b20e589

Analysis symbol: 
Rechecking for solution: 0
Report Id: a97abe86-abfc-463c-9791-2d7d0b20e589
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
6/3/2021 9:46 AM    Windows Error Reporting    Fault bucket BAD_DUMPFILE, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: de7cce17-cac2-4b8e-8a32-ad91fb1da4d9

Problem signature:
P1: 141
P2: ffffa3061e348010
P3: fffff805973c6f64
P4: 0
P5: 558
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210603-1345.dmp
\\?\C:\Windows\TEMP\WER-300234-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA1F9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA1FA.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA1FB.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA21B.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_9c55cf2664e3b8db6cff53ce7f72274aa9c78f2_00000000_cab_5322f7fd-1953-47e8-9da6-6e6083e2ea17

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5322f7fd-1953-47e8-9da6-6e6083e2ea17
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0


Code:
6/3/2021 9:36 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 47a98560-3d28-478a-9cc0-4e2d089e9101

Problem signature:
P1: 117
P2: ffffe486b553a460
P3: fffff8007f3f6f64
P4: 0
P5: 558
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210603-1335.dmp
\\?\C:\Windows\TEMP\WER-348140-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C8F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C9F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5CA2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5CB3.tmp.txt
\\?\C:\Windows\Temp\WER7C55.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_c3973caa94f994152ff0c2a56840ff82605ddb54_00000000_cab_d2ba770a-a5e4-4158-a7dc-87f95f35e751

Analysis symbol: 
Rechecking for solution: 0
Report Id: d2ba770a-a5e4-4158-a7dc-87f95f35e751
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0


Code:
6/3/2021 9:25 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 3330bacd-ac66-4469-b1c3-a625aa0a3ee0

Problem signature:
P1: 141
P2: ffff958b50e65010
P3: fffff80563bb6f64
P4: 0
P5: 3638
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210603-1325.dmp
\\?\C:\Windows\TEMP\WER-519895906-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8D0.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8D3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E4.tmp.txt
\\?\C:\Windows\Temp\WER8285.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_89519e841b23ce9432d68668c31c68b80014fd_00000000_cab_85729919-39c9-4900-95c3-6a655ce208df

Analysis symbol: 
Rechecking for solution: 0
Report Id: 85729919-39c9-4900-95c3-6a655ce208df
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
6/5/2021 11:35 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: d0357b58-c564-4290-b18b-8cea6d2f1c6a

Problem signature:
P1: 141
P2: ffff9406ea7c2220
P3: fffff80485b07f64
P4: 0
P5: 1918
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210605-1535.dmp
\\?\C:\Windows\TEMP\WER-7808562-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3601.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3612.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3613.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3633.tmp.txt
\\?\C:\Windows\Temp\WER5E5A.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_1fbe2af7f3d034ffead994763ea9040b63be58e_00000000_cab_7f761c02-398b-4f92-926c-af8ef7ffbf5a

Analysis symbol: 
Rechecking for solution: 0
Report Id: 7f761c02-398b-4f92-926c-af8ef7ffbf5a
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
6/3/2021 7:18 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: d39b6716-9d6a-42be-a1e4-ec8c7a29f630

Problem signature:
P1: 141
P2: ffffc208b2f73050
P3: fffff80658006f64
P4: 0
P5: 2308
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210603-2317.dmp
\\?\C:\Windows\TEMP\WER-3690953-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5FD2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5FD3.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5FD4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5FF5.tmp.txt
\\?\C:\Windows\Temp\WERC13D.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_4097f3c212f28d332acfb1b1f4d53db3f11f17b_00000000_cab_a5ac1dbc-6aac-45e5-91dc-1758b1f3c162

Analysis symbol: 
Rechecking for solution: 0
Report Id: a5ac1dbc-6aac-45e5-91dc-1758b1f3c162
Report Status: 268435556
Hashed bucket: 
Cab Guid: 0
6/5/2021 7:50 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: d4a03b12-561e-45d3-9473-ec003e2f731b

Problem signature:
P1: 141
P2: ffffa207b3acb010
P3: fffff802755d7f64
P4: 0
P5: 2790
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210605-1150.dmp
\\?\C:\Windows\TEMP\WER-38643250-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB620.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB630.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB62F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB650.tmp.txt
\\?\C:\Windows\Temp\WERDC08.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_9fcd21bae58d1b6e4decb2e0a268a4b6b3f1c6_00000000_cab_02f4e345-5f14-4efe-925f-9e15a47254d8

Analysis symbol: 
Rechecking for solution: 0
Report Id: 02f4e345-5f14-4efe-925f-9e15a47254d8
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
6/3/2021 7:31 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: d706a4a0-c1c4-430d-b775-349fceaac010

Problem signature:
P1: 141
P2: ffffb40f1fbed010
P3: fffff80578516f64
P4: 0
P5: 674
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210603-2330.dmp
\\?\C:\Windows\TEMP\WER-154109-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER678A.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER679A.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6799.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER67AA.tmp.txt
\\?\C:\Windows\Temp\WER6E0C.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_6aa9117b10631c65c16c3f6927789dfebb1c865_00000000_cab_74015dfa-23af-426d-b437-5f3a0cc10027

Analysis symbol: 
Rechecking for solution: 0
Report Id: 74015dfa-23af-426d-b437-5f3a0cc10027
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
6/3/2021 7:28 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: d79df539-bcf8-494c-8744-69da3cff2517

Problem signature:
P1: 141
P2: ffffcc035d3ad010
P3: fffff80429b76f64
P4: 0
P5: a20
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210603-2323.dmp
\\?\C:\Windows\TEMP\WER-321718-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF614.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF615.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF616.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF636.tmp.txt
\\?\C:\Windows\Temp\WER67A4.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_777ac86c48dda8b5e144e51c8f965a4d11893b81_00000000_cab_9e988f04-9910-4f27-ba78-fd0f639e7848

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9e988f04-9910-4f27-ba78-fd0f639e7848
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
5/24/2021 8:25 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: e59f4742-8aea-46f3-b0fd-6f7dc384cb6d

Problem signature:
P1: 141
P2: ffffce0c144b5010
P3: fffff8017dfc6f64
P4: 0
P5: 316c
P6: 10_0_19043
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210525-0024.dmp
\\?\C:\Windows\TEMP\WER-3288437-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C79.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C89.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C8A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C9B.tmp.txt
\\?\C:\Windows\Temp\WER70C8.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_7d325569ea335c3ac25c3bc5c1e42415be5fb6_00000000_cab_46b1ed7d-9ec1-4152-a934-467145a7e607

Analysis symbol: 
Rechecking for solution: 0
Report Id: 46b1ed7d-9ec1-4152-a934-467145a7e607
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
 
Last edited:

My Computer

System One

  • Operating System
    Windows 10

sims

New Member
Local time
8:26 PM
Posts
15
Thread starter
Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
a) Record the maximum temperature and post the maximum temperature into the thread.
b) Record the test duration and post the uninterrupted test duration into the thread.
c) Aim for testing 1 hour.
d) Use the Microsoft snipping tool to post images into the thread.
Ok, I lauched FurMark test, and the warning says not to go above 80C temperature otherwise the GPU might get damaged. For my laptop, it took 8mins and it reached 79C, so I had to stop the test, and couldn't go for the full hour. Attached screenshot
 

Attachments

  • FurMark test.jpg
    FurMark test.jpg
    582.6 KB · Views: 2

My Computer

System One

  • Operating System
    Windows 10
Top