PC Freeze on Heavy use/streaming w/ Gaming  

Hi all,

I have being suffering a slew of issues with my fairly new PC (12 months old). First off, I was getting multiple BSODs fairly regularly - usually there would either happen on startup or shutdown and then randomly during use, but not during gaming or intensive operations.

The BSODs were a mixture of:
CRITICAL_PROCESS_DIED
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
PAGE_FAULT_IN_NONPAGED_AREA
SYSTEM_SERVICE_EXCEPTION

N.B I still have these dump files from the crashes before the windows reinstall, if they are at all useful?

On the guidance of the IT support from the place I bought the PC, I reinstalled windows. This seemingly fixed the BSOD issue. However, just before I did this reinstall I started getting full PC freezes

When these freezes happen I am almost always playing a demanding game on screen 1 whilst watching YT video on fullscreen on the screen 2, or having just finished playing a game, the freeze will happen when streaming a video fullscreen (rare). The audio 'locks up' on whatever sound was being broadcast right that second and sounds like a lawnmower, the fans go like clappers, then the PC will restart. I do not actually see the BSOD screen when this happens. This has now been continuing fairly regularly (with more frequency even) since the fresh windows install. I have tried the below steps:

- remove all USB devices
- driver verifier
- monitoring all hardware temps (RAM getting to about 50, is this OK?)
- clean windows install
- SFC scan and DISM /Online /Cleanup-Image /RestoreHealth
- memtest86 - no errors
- DDU uninstall in safe mode then reinstall display drivers - this was the most promising step - it gave me hope and seemingly stopped the restarts for about 36 hours, with lots of stress testing. But then they reappeared, albeit in a slightly different fashion - see below.
- update RealTek PCIe GbE family controller driver - I haven't tested if this fixed it because I only just did this after some googling mentioned that this might fix the the last BSOD I had (DPC watchdog violation) when it was crashing during YT vids

Before I DDU'd and reinstalled the driver, I could recreate the issue by running a 3D mark benchmark or by playing a demanding game (BF1) and also having Chrome open whilst on YT or Netflix, i.e. viewing a video fullscreen on the 2nd screen. Once I realised I could recreate it by putting the PC under stress I figured it was a hardware issue. I then read about the reliability monitor and checked it. This is where I saw the LiveKernelEvent errors 117 and 141. Here is a screencap of the logs but I'm sure your Log Collector will have this information. All but one of the hardware errors in this example is 141.

Imgur: The magic of the Internet < here are screens of the reliability monitor.

After running DDU and putting the new driver in, whilst the freeze is the same audio lockup nightmare coupled with the fans and the restart, the PC will then restart and all I will see is a command prompt screen with the flashing input "_" on the screen. I will then have to restart and the PC will boot normally BUT my windows display HDR will have turned back on AND the display settings will have reset on the game I was playing whilst the crash happened (BF1). This has happened in both the crashes since the DDU 'fix'. There is also nothing in the reliability monitor other than 'windows was not properly shut down', and no minidump file being created.

I've included my V2 log, I hope someone can make sense of this. My gut says hardware but I am praying that's not the case.

Thank you!

OS Version: 20H2 (OS Build 19042.804)

DESKTOP-I61RQPE-(2021-02-25_22-24-08).zip

Update BIOS - MSI Global
Check in Windows Update if there any updates of system
Update AMD chipset driver - https://www.amd.com/en/support/chips...ocket-am4/b450
Install HP printer drivers - https://support.hp.com/pl-pl/drivers...series/8954253

MrPepka said:

Update BIOS - MSI Global
Check in Windows Update if there any updates of system
Update AMD chipset driver - https://www.amd.com/en/support/chips...ocket-am4/b450
Install HP printer drivers - https://support.hp.com/pl-pl/drivers...series/8954253

Thanks for looking at this - I've downloaded these drivers (apart from the HP printer one, that was already installed) and will test this today.

- - - Updated - - -

MrPepka said:

Update BIOS - MSI Global
Check in Windows Update if there any updates of system
Update AMD chipset driver - https://www.amd.com/en/support/chips...ocket-am4/b450
Install HP printer drivers - https://support.hp.com/pl-pl/drivers...series/8954253

No joy I'm afraid, seemed to be running fine - got a good few hours of gaming + streaming on 2nd screen without issue which made me think it might be resolved, but just crashed again when I opened BF1 again. Updated log attached but no BSOD, just hard restart as per the last few freezes.

Again, the windows display HDR has randomly turned back on. I'll just leave it on this time I guess.

DESKTOP-I61RQPE-(2021-02-27_23-10-27).zip

Hi Zbook,

thank you for your help.

1. see Memory.dump file here (0.98gb!)
2. Logs ZIP download here and TUNEUP output below:

Code:

###########################################################
# The following commands will be run in sequence.         #
# The first 5 will take quite a while to run, be patient. #
###########################################################

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

chkdsk /scan

wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot
wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType

wmic pagefile list /format:list
wmic Computersystem where name="DESKTOP-I61RQPE" get AutomaticManagedPagefile
wmic Computersystem where name="DESKTOP-I61RQPE" set AutomaticManagedPagefile=True
wmic Computersystem where name="DESKTOP-I61RQPE" get AutomaticManagedPagefile

bcdedit /enum {badmemory}


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>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19042.844

[==========================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.19042.844

[==========================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 ...
  673536 file records processed.
File verification completed.
 Phase duration (File record verification): 3.48 seconds.
  8856 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.25 milliseconds.

Stage 2: Examining file name linkage ...
  297 reparse records processed.
  855998 index entries processed.
Index verification completed.
 Phase duration (Index verification): 6.55 seconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 550.84 milliseconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 0.41 milliseconds.
  297 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 3.30 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 16.52 milliseconds.
  91232 data files processed.
 Phase duration (Data attribute verification): 0.27 milliseconds.
CHKDSK is verifying Usn Journal...
  36111712 USN bytes processed.
Usn Journal verification completed.
 Phase duration (USN journal verification): 122.16 milliseconds.

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

 499446783 KB total disk space.
 227861616 KB in 307116 files.
    186876 KB in 91233 indexes.
         0 KB in bad sectors.
    793131 KB in use by the system.
     65536 KB occupied by the log file.
 270605160 KB available on disk.

      4096 bytes in each allocation unit.
 124861695 total allocation units on disk.
  67651290 allocation units available on disk.
Total duration: 10.73 seconds (10733 ms).

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


C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-I61RQPE\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk1\\Partition4"'
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 recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-I61RQPE\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk1\\Partition4"'
Property(s) update successful.

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


C:\Windows\system32>wmic pagefile list /format:list


AllocatedBaseSize=2432
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20210106095911.179409+000
Name=C:\pagefile.sys
PeakUsage=1
Status=
TempPageFile=FALSE




C:\Windows\system32>wmic Computersystem where name="DESKTOP-I61RQPE" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


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

C:\Windows\system32>wmic Computersystem where name="DESKTOP-I61RQPE" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


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

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

C:\Windows\system32>Echo off
   ###################################################################################
   #    How to capture batch file data and post in your thread in the BSOD forum     #
   #                                                                                 #
   #      Batch files and instructions for use in BSOD debugging[Part Two-Four]      #
   #                                                                                 #
   #        Press [V] to visit the above web page for detailed instructions.         #
   #        Press [C] to close this window.                                          #
   ###################################################################################

3. I have turned off fast startup
4. I've created the restore point.
5. I am getting a 'file not found - C:\hiberfile.sys' output.
6. I have read the articles and understand - I've used driver verifier before. I will use the verifier /reset or restore point if it results in a BSOD.

Thanks again.

Please make sure all share links are one drive, drop box, or google drive.


For any BSOD run the V2 log collector to collect new log files


Read these links on Windows driver verifier:

learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool



Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are ran in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with the 3 customized test settings in the Ten Forums link
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified

zbook said:

Please make sure all share links are one drive, drop box, or google drive.

Apologies, here is a gdrive folder with the logs.zip and the minidump file. I will run verifier for the 48 hours and report back.

Thank you again for your time, greatly appreciated.

- - - Updated - - -

See attached V2 log file - the driver causing an error was/is bcbtums.sys - it's a bluetooth usb dongle I use so that I can listen to my wireless headphones.

Should I delete/reinstall the driver? I've read some posts about it suggesting that it's just a bad driver and I should perhaps get another dongle.

Should I continue the verifier but not that driver?

I've not yet downloaded the new files.

For WDV if possible uninstall misbehaving drivers / software and restart the tool to find the next misbehaving driver.
Once there are no longer any BSOD you can reinstall drivers / software.

An alternative method is to reinstall a driver (same, newer, or older) and retest with WDV.

Plan to run the tool for 36 hrs to complete testing of all drivers.

Hi guys, just wanted to give you an update:

I reinstalled the faulty Bluetooth driver but this didn't seem to fix the issue - I was all but resigned to returning the whole PC to the vendor for repair but read that an overheating PSU might be causing a very similar issue on another users PC. So, I took the case apart and air dusted/brush dusted everything - with rubber gloves on mind.

The CPU fans and the liquid cooler all seem to be doing their job fine, they needed a bit of a dusting HOWEVER, the way the case is setup, the PSU is hidden down at the bottom of the case - not only did I not realise this was there (I know, I know, that's a ridiculous thing to not know) but I also subsequently didn't realise just how dusty the PSU air vents at the bottom of the case were. I took a good few millimetres layer of dust off both the rear and underside vents.

I haven't had a crash since, though it's only been 2 days.

I did want to ask, if this is indeed what the problem was and I've been overheating my PSU for about a month now, is that likely to have caused any long-term hardware damage? Have I unwittingly knocked a few years off it's life-span? It's about a year old now, FYI.

I'll report back in a week.