BSOD when watching YouTube/Taxing my CPU

Page 1 of 2 12 LastLast

  1. Posts : 7
    Win10 Professional v10.0.17763
       6 Days Ago #1

    BSOD when watching YouTube/Taxing my CPU


    Approximately 3-4 times a week I will experience either a BSOD - WHEA_UNCORRECTABLE_ERROR or a screen freeze (mouse and keyboard are completely non-responsive) resulting in a hard reset to restore. This typically occurs while watching random YouTube videos or while playing Cities Skylines or attempting to convert video files. If the PC is idle, there are no issues.

    I've had this PC since 2012 and about 6 months ago updated all the drivers, blew away Win7 and updated to Win10 Pro. At that time I updated my UEFI which should be current. I also diligently run Windows updates, etc.
    I had the pc over-clocked to 4.7 the entire time it was on Win7 and had no issues, but not long after moving to Win10 I started experiencing screen freezes. I've been putting up with this for several months now but it's been very frustrating. Within the last month or so I'll more-often see a BSOD than a screen freeze but it does appear to be random.
    In the pursuit of resolving this issue, I just dropped the over-clocking down to 4.4, but it's just crashed again (converting a MKV to MP4).

    I'm not sure where to start here so any help you can provide would be greatly appreciated. I've attached the required files but can add any others as requested.
    BSOD when watching YouTube/Taxing my CPU Attached Files
      My ComputerSystem Spec

  2. philc43's Avatar
    Posts : 3,823
    64bit Win 10 Pro ver 1809 Build 17763.253 and W10 Insider Build 18312
       6 Days Ago #2

    Hello dpinkis and welcome to the BSOD Forum area

    My personal view is that W10 is more susceptible to BSOD from overclocking and so I would make sure your CPU does not go over the Max turbo boost frequency allowed which is 3.8GHz. Your current setting of 4.4 is still rather high in my opinion.

    At least while troubleshooting please remove any overclock and see if it makes a difference.

    The single BSOD crash dump indicates a hardware error with an internal timing issue which is entirely consistent with overclocking.
      My ComputersSystem Spec


  3. Posts : 22,640
    windows 10 professional version 1607 build 14393.969 64 bit
       6 Days Ago #3

    The logs displayed problems related to the drive including paging errors, possible corruption and bad block.

    Run HD Tune (free edtition): (test all drives)
    https://www.hdtune.com/
    Post images into the thread for results on these tabs:
    a) Health (SMART)
    b) Benchmark
    c) Full error scan

    Open administrative command prompt and type or copy and paste: chkdsk /r /v

    This command may take many hours so plan to run overnight.

    Use the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

    Use the text and images in this thread to find the chkdsk reports in the event viewer > copy and paste > notepad > post share links into the thread using one drive, drop box, or google drive

    There are two log collectors: DM and BETA
    The BETA will eventually replace the DM log collector.
    The BETA log collector will collect more useful files and folders.

    Once the computer environment is no longer overclocked:
    for any BSOD:
    a) Run the BETA log collector and post a zip into this thread
    b) Open file explorer > this PC > C: > in the right upper corner search for C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a separate share link into the thread using one drive, drop box, or google drive

    Code:
    Event[8900]:
      Log Name: System
      Source: Microsoft-Windows-Ntfs
      Date: 2019-01-09T14:43:33.305
      Event ID: 140
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: dpinkis
      Description: 
    The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume6.
    (A device which does not exist was specified.)

    Code:
    Event[8902]:
      Log Name: System
      Source: Ntfs
      Date: 2019-01-09T14:43:34.886
      Event ID: 50
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: dpinkis
      Description: 
    {Delayed Write Failed} Windows was unable to save all the data for the file \$Mft::$BITMAP. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
    Code:
    Event[8372]:
      Log Name: System
      Source: Microsoft-Windows-Ntfs
      Date: 2019-01-08T10:30:18.437
      Event ID: 140
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: dpinkis
      Description: 
    The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{6febb9d1-f863-4780-97a7-a9642ec9a90a}, DeviceName: \Device\HarddiskVolume10.
    (A device which does not exist was specified.)
    
    Event[8373]:
      Log Name: System
      Source: Microsoft-Windows-Ntfs
      Date: 2019-01-08T10:30:18.439
      Event ID: 140
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: dpinkis
      Description: 
    The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume11.
    (A device which does not exist was specified.)
    Code:
    Event[1768]:
      Log Name: System
      Source: Disk
      Date: 2018-10-19T17:23:32.800
      Event ID: 7
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: dpinkis
      Description: 
    The device, \Device\Harddisk2\DR3, has a bad block.
    Code:
    Event[1685]:
      Log Name: System
      Source: Disk
      Date: 2018-10-18T12:32:15.768
      Event ID: 7
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: dpinkis
      Description: 
    The device, \Device\Harddisk2\DR2, has a bad block.
      My ComputerSystem Spec

  4. philc43's Avatar
    Posts : 3,823
    64bit Win 10 Pro ver 1809 Build 17763.253 and W10 Insider Build 18312
       6 Days Ago #4

    @zbook You are referring to bad blocks picked up back in October 2018 which will have no connection to the BSOD. You also refer to recent drive problems but do not specify which drive - in fact you can clearly see that they are not the system drive and the events were at times not related to the crash.
      My ComputersSystem Spec


  5. Posts : 22,640
    windows 10 professional version 1607 build 14393.969 64 bit
       6 Days Ago #5

    The possible corruption problems reported in the logs were in January.
    The paging errors I/O retried, bad blocks were older.
    Maybe the OP can comment on whether the chkdsk fix and recover had been ran or whether the drive was replaced.
    The recent bugchecks were 124. There were older BSOD with different bugchecks (A and D1)
    Last edited by zbook; 6 Days Ago at 15:37.
      My ComputerSystem Spec


  6. Posts : 7
    Win10 Professional v10.0.17763
    Thread Starter
       6 Days Ago #6

    For clarification (and because I forgot):
    For my OS/C Drive I originally had two 250GB SSD's in Raid 0 (Win7 Pro)
    I replaced those with two brand-new Samsung 1TB drives in Raid 0 @10/3/18 (Win10 Pro) (as per Systeminfo.exe).
    I can remove over-clocking and run chkdsk on my PC (after work) but would like to know what the switches represent please? (/r /v)
      My ComputerSystem Spec


  7. Posts : 22,640
    windows 10 professional version 1607 build 14393.969 64 bit
       6 Days Ago #7

    /r Locates bad sectors and recovers readable information. The disk must be locked. /r includes the functionality of /f, with the additional analysis of physical disk errors.

    /v Displays the name of each file in every directory as the disk is checked.

    chkdsk | Microsoft Docs



    C:\WINDOWS\system32>chkdsk /r /v C:
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot
      My ComputerSystem Spec


  8. Posts : 7
    Win10 Professional v10.0.17763
    Thread Starter
       6 Days Ago #8

    I have not yet removed the OC settings in the UEFI, but chkdsk /r /v c: has finished. I keep a lean c:\ so not seeing the need to export this and posting directly:




    Checking file system on C:
    The type of the file system is NTFS.

    A disk check has been scheduled.
    Windows will now check the disk.

    Stage 1: Examining basic file system structure ...
    Cleaning up instance tags for file 0x5487b.
    Cleaning up instance tags for file 0x548ca.
    Cleaning up instance tags for file 0x54924.
    741888 file records processed.
    File verification completed.
    7758 large file records processed.
    0 bad file records processed.

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

    Stage 3: Examining security descriptors ...
    Cleaning up 3633 unused index entries from index $SII of file 0x9.
    Cleaning up 3633 unused index entries from index $SDH of file 0x9.
    Cleaning up 3633 unused security descriptors.
    Security descriptor verification completed.
    54181 data files processed.
    CHKDSK is verifying Usn Journal...
    Usn Journal verification completed.

    Stage 4: Looking for bad clusters in user file data ...
    741872 files processed.
    File data verification completed.

    Stage 5: Looking for bad, free clusters ...
    447077786 free clusters processed.
    Free space verification is complete.

    Windows has made corrections to the file system.
    No further action is required.

    1899752447 KB total disk space.
    110423132 KB in 202265 files.
    146436 KB in 54182 indexes.
    0 KB in bad sectors.
    871731 KB in use by the system.
    65536 KB occupied by the log file.
    1788311148 KB available on disk.

    4096 bytes in each allocation unit.
    474938111 total allocation units on disk.
    447077787 allocation units available on disk.

    Internal Info:
    00 52 0b 00 b4 e9 03 00 f6 4b 07 00 00 00 00 00 .R.......K......
    24 01 00 00 66 1a 00 00 00 00 00 00 00 00 00 00 $...f...........

    Windows has finished checking your disk.
    Please wait while your computer restarts.
      My ComputerSystem Spec


  9. Posts : 7
    Win10 Professional v10.0.17763
    Thread Starter
       3 Days Ago #9

    More info


    I've stripped all UEFI over-clocking as noted above. I've also uploaded the beta version of the log collector, dated 1-12-19. Please take a look and let me know if there's anything actionable there or if I've missed anything. I haven't had a BSOD since the 10th, but i did find my PC completely shutdown today (1/12) and definitely didn't power down, and my PC is on a reliable UPS (this was prior to removing the OC'ing).
    BSOD when watching YouTube/Taxing my CPU Attached Files
      My ComputerSystem Spec


  10. Posts : 22,640
    windows 10 professional version 1607 build 14393.969 64 bit
       3 Days Ago #10

    For C:

    Windows has made corrections to the file system.

    There was one reboot without clean shut down on 1/12/2018.

    These are seen with:
    a) non-BSOD crashes
    b) BSOD crashes
    c) Manual power off
    etc.


    Code:
    Event[2812]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Power
      Date: 2019-01-12T14:51:09.687
      Event ID: 41
      Task: N/A
      Level: Critical
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: dpinkis
      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.



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

    2) Open Ccleaner (do not install the software if it is not already installed) > on the left pane click on cleaner > click windows tab > scroll down to system and advanced > post an image into the thread

    3) To ensure that there are no improper bios settings please reset the bios.
    4) Sometimes there can be failure to boot after resetting the bios.
    5) Backup the computer files to another drive or to the cloud.
    6) Make a backup image using Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free

    7) And please create a brand new restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    https://www.howtogeek.com/131623/how...bios-settings/
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    4) Run chkdsk /r /v on drive K:
    5) Post a share link for the notepad event viewer report using a share link

    6) Read this link on Windows driver verifier:
    BSOD Crashes and Debugging - Windows 10 Forums

    7) Do not turn on the tool until it is communicated in the thread
    Last edited by zbook; 3 Days Ago at 00:24.
      My ComputerSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
1st was BSOD DPC watchdog violation 2nd was OSOD 3rd didn't happen after closing youtube when foreshadowing occurred seems like a driver issue but it won't let me access the info on my end so hopefully you guys are better at this than i am
BSOD watching youtube in BSOD Crashes and Debugging
Hello everyone. I have the blue screen problem (Dpc_watchdog_violation) only when I watch video on youtube. Not during video on VLC nor twich.tv... Only with youtube, and with every browser. I think I have all my driver up to date (but I can make...
BSOD while watching YouTube videos in BSOD Crashes and Debugging
Hello. Had some BSOD while watching YouTube. And sometimes I go to sleep while watching videos and by the morning I notice the PC had reset. Cannot say if BSOD or an unexpected update, but most likely BSOD. Actually, my no-break's battery has...
BSOD while watching a youtube video in BSOD Crashes and Debugging
Hello. System specs: CPU: I5-4690k RAM: Kingston Fury 2x4GB MOBO: Z97-D3H GPU:R9 280x PowerColor PSU: NZXT Hale v2 Browser: Google Chrome OS: Windows 10 x64
Solved BSOD playing PoE and watching youtube in BSOD Crashes and Debugging
Hello, I recently updated to windows 10 and have been getting BSODS alot more frequently than before. It's the good old driver_IRQL_not_less_or_equal (some letters that I cant remember). I suspect that it's my network card thats causing it. I use...

Tags for this Thread

Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:13.
Find Us