10 BSOD in 24 hours

Page 5 of 8 FirstFirst ... 34567 ... LastLast

  1. Posts : 32,885
    windows 10 professional version 1607 build 14393.969 64 bit
       #41

    Please run these switches /b /v.


    Make a new restore point:
    Create System Restore Point in Windows 10



    For the black background see this link:
    Black background behind Folder icons in Windows 10
      My Computer


  2. Posts : 34
    Windows 10
    Thread Starter
       #42
      My Computer


  3. Posts : 32,885
    windows 10 professional version 1607 build 14393.969 64 bit
       #43

    When available please upload a new V2.
      My Computer


  4. Posts : 34
    Windows 10
    Thread Starter
       #44

    System restore point created

    - - - Updated - - -

    What exactly is the V2 log collector? First reference I see to it is post #13, step 23a, but it just says to use it. Are you saying to trigger a BSOD and post the dump?
      My Computer


  5. Posts : 32,885
    windows 10 professional version 1607 build 14393.969 64 bit
       #45

    The log collectors are V2 and DM.
    They can be run at any time.
    BSOD - Posting Instructions

    For any BSOD:

    a) run the V2 log collector to collect new log files

    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 > post a separate share link into the thread using one drive, drop box, or google drive
      My Computer

  6. axe0's Avatar
    Posts : 14,628
    Windows 10 Pro
       #46

    adriswindow said:
    Okay, thank you guys. This drive is nearly brand-new, purchased probably a month or so ago. Is it unusual that it would have bad blocks so soon? Should I contact the manufacturer and ask them to replace it?
    It's not unusual, but it's unexpected. Some drives can go for 10 years and be like they're brand new, others go bad within a few months. Time is not a determining factor to say when something is going bad or not, time is rather a generic indicator saying that once in a while it's a good idea to check up on the health (S.M.A.R.T.) of a drive to ensure it's still going smoothly. I realize I'm saying this like it's quite easy, but some vendors have custom attributes in the health that as far as I know most programs do not know what they mean. So one of the main things to look out for are current pending sectors and reallocated sector count, current pending sectors should be zero (run multiple chkdsk scans if needed to lower this) and the reallocated sector count's data should not exceed the threshold.
    10 BSOD in 24 hours-image.png
      My Computers



  7. Posts : 34
    Windows 10
    Thread Starter
       #47

    Okay, V2 is running, and I'll check out that other info @axe0 a bit later. :)

    It would seem Macrorit isn't working on my 6tb HD. I plugged it into my old laptop, left it to run, came back several hours later to find no progress. Unplugged it, plugged it into a different USB port, and now it seems to be stuck exactly how it was when I found it. 00:46 elapsed, 2.3gb/min, 0%, no further progress and no estimated time remaining. Drive is working fine though, I can still access it and open the files on it.

    10 BSOD in 24 hours-6tb.jpg

    - - - Updated - - -

    Disregard the last post. I double-checked which USB input was the 3.0, plugged it into that one, and now it's running fine at 10gb/second.

    Here's the new V2:

    DESKTOP-EH76GAR-(2020-05-23_18-36-28).zip - Google Drive

    - - - Updated - - -

    HP Support Assistant found a handful of updates. Installed all those, including the BIOS update.

    10 BSOD in 24 hours-ss16.jpg

    Some of them don't seem to want to install, for whatever reason. Tried twice and get this same result.

    10 BSOD in 24 hours-ss17.jpg

    Anyways, I'm hopeful now that I can run my video editor without BSOD! I'll play around with it for a while and see what happens, then report back. Fingers crossed

    - - - Updated - - -

    Still having issues. This time, I'm able to open Premiere Pro, but when I go to export my 4k timelapse (file > export) the program immediately crashes. It also crashed with a 1080p video. This is generally the point where I would get BSOD - as soon as Premiere would stop responding, BSOD would hit. Now there's no BSOD, so I guess that's an improvement. I tried making a new project, instead of using one of my previous ones, and this time it let me pull up the export dialog. But then gave me the following error report:

    10 BSOD in 24 hours-ss19.jpg

    Any idea where to go from here?

    - - - Updated - - -

    I should also mention that all of my Adobe Creative Cloud programs (including Premiere) are completely up-to-date.
      My Computer


  8. Posts : 32,885
    windows 10 professional version 1607 build 14393.969 64 bit
       #48

    The last BSOD in the new V2 was on 5/20.
    Today is 5/23 so that is approximately 3 days without BSOD while drives were tested.


    Uninstall and reinstall Adobe Premier Pro.
    If there are recurrent problems with this software please open a new thread in this forum room:
    https://www.tenforums.com/software-apps/


    That is normal for HP Support Assistant and other HP software (softpaq download manager, image assist) to suggest drivers that cannot be installed.


    For drive testing you can run HD Tune and Sea Tools for Windows.
    If there are any problems with questionable results you can run Macrorit (surface or error scan) and Crystal Disk standard edition (SMART).


    Find a driver replacement for Netwtw08.sys
    Intel(R) Wireless-AC 9560 160MHz
    Uninstall and reinstall the driver from the HP website.
    Perform Windows updates after installing the driver.
      My Computer

  9. axe0's Avatar
    Posts : 14,628
    Windows 10 Pro
       #49

    It appears Windows has caught up with the drive testing
    Code:
      2020-05-22T23:50:22.185		Volume F: (\Device\HarddiskVolume8) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.
      2020-05-22T23:51:55.885		Volume F: (\Device\HarddiskVolume9) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.
      2020-05-23T03:09:06.423		The IO operation at logical block address 0x97977000 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:10:33.746		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:10:36.557		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:10:39.411		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:10:42.263		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:10:45.110		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:10:47.963		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:10:50.791		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:10:53.644		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:11:14.310		The IO operation at logical block address 0x9799a000 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:12:41.767		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:12:44.580		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:12:47.434		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:12:50.247		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:12:53.057		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:12:55.869		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:12:58.723		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:13:01.536		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:13:38.542		The IO operation at logical block address 0x97e18800 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:15:06.212		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:15:09.279		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:15:12.379		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:15:15.468		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:15:18.523		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:15:21.603		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:15:24.647		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:15:27.745		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:15:48.458		The IO operation at logical block address 0x97f7ec00 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:17:16.246		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:17:19.291		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:17:22.380		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:17:25.468		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:17:28.513		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:17:31.602		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:17:34.691		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:17:37.780		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:17:58.929		The IO operation at logical block address 0x98271400 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:19:27.102		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:19:30.146		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:19:33.203		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:19:36.247		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:19:39.291		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:19:42.336		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:19:45.381		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:19:48.403		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:20:08.614		The IO operation at logical block address 0x98563800 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:21:36.414		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:21:39.459		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:21:42.548		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:21:45.634		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:21:48.725		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:21:51.739		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:21:54.832		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:21:57.859		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:22:18.527		The IO operation at logical block address 0x98856800 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:23:46.182		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:23:49.351		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:23:52.473		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:23:55.638		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:23:58.818		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:24:01.928		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:24:05.096		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:24:08.207		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:35:34.373		The IO operation at logical block address 0xa1961c00 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:37:02.599		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:37:05.643		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:37:08.721		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:37:11.787		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:37:56.534		The IO operation at logical block address 0xa1bbac00 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:39:13.395		The IO operation at logical block address 0xa1bc5c00 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:39:57.017		The IO operation at logical block address 0xa1bcc800 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:41:24.856		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:43:33.148		The IO operation at logical block address 0xa1ecf000 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:56:00.243		The IO operation at logical block address 0xa83a7c00 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:57:28.004		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:57:30.639		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:57:33.272		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:57:35.978		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:57:38.699		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T03:58:32.344		The IO operation at logical block address 0xa85f1800 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T04:19:23.914		The IO operation at logical block address 0xb7a5b400 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T04:20:51.641		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:20:54.408		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:20:57.175		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:20:59.942		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:21:02.702		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:21:05.475		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:21:08.241		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:21:11.008		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:21:40.412		The IO operation at logical block address 0xb7b57000 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T04:23:07.765		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:23:10.607		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:23:13.376		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:23:16.142		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:23:18.909		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:23:21.752		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:23:24.520		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T04:23:27.363		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T11:47:36.663		The IO operation at logical block address 0x1df932000 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T11:49:04.049		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T11:49:06.838		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T11:49:09.638		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T11:49:12.427		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T11:49:15.216		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T11:49:18.005		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T11:49:20.793		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T11:49:23.594		The device, \Device\Harddisk1\DR5, has a bad block.
      2020-05-23T16:57:46.744		An error was detected on device \Device\Harddisk1\DR5 during a paging operation.
      2020-05-23T16:57:46.744		An error was detected on device \Device\Harddisk1\DR5 during a paging operation.
      2020-05-23T16:57:46.744		An error was detected on device \Device\Harddisk1\DR5 during a paging operation.
      2020-05-23T16:57:46.744		An error was detected on device \Device\Harddisk1\DR5 during a paging operation.
      2020-05-23T16:57:46.744		An error was detected on device \Device\Harddisk1\DR5 during a paging operation.
      2020-05-23T16:57:46.744		An error was detected on device \Device\Harddisk1\DR5 during a paging operation.
      My Computers


  10. Posts : 34
    Windows 10
    Thread Starter
       #50

    zbook said:
    The last BSOD in the new V2 was on 5/20.
    Today is 5/23 so that is approximately 3 days without BSOD while drives were tested.


    Uninstall and reinstall Adobe Premier Pro.
    If there are recurrent problems with this software please open a new thread in this forum room:
    https://www.tenforums.com/software-apps/


    That is normal for HP Support Assistant and other HP software (softpaq download manager, image assist) to suggest drivers that cannot be installed.


    For drive testing you can run HD Tune and Sea Tools for Windows.
    If there are any problems with questionable results you can run Macrorit (surface or error scan) and Crystal Disk standard edition (SMART).


    Find a driver replacement for Netwtw08.sys
    Intel(R) Wireless-AC 9560 160MHz
    Uninstall and reinstall the driver from the HP website.
    Perform Windows updates after installing the driver.
    Okay, I will do this. Thank you so much for your help!
    axe0 said:
    It appears Windows has caught up with the drive testing
    Code:
      2020-05-22T23:50:22.185		Volume F: (\Device\HarddiskVolume8) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.
      2020-05-22T23:51:55.885		Volume F: (\Device\HarddiskVolume9) needs to be taken offline to perform a Full Chkdsk.  Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.
      2020-05-23T03:09:06.423		The IO operation at logical block address 0x97977000 for Disk 1 (PDO name: \Device\000000c0) was retried.
      2020-05-23T03:10:33.746		The device, \Device\Harddisk1\DR5, has a bad block.
    What does this mean exactly? Windows has recognized that the issue was with the external drive?
      My Computer


 

Related Threads
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 09:49.
Find Us




Windows 10 Forums