BSOD at least twice a month - uncertain cause

zbook · 21 Feb 2019

1) During the troubleshooting process please make these changes to the startup and recovery system failure settings:
a) uncheck the box to overwrite any existing file
b) check the box to disable automatic deletion of memory dumps when disk space is low
c) after the above changes > post an image into the thread

2) Download and install Sea Tools for Windows:
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows | Seagate Support US

3) Run Sea Tools for Windows on the non SSD drives
Post images into the thread for results of SMART and long generic testing

4) Find a flash drive that you can format ( > or = 8 GB)

5) Create a bootable Windows 10 iso:
Download Windows 10 ISO File | Tutorials
Download Windows 10

LeoBloom · 23 Feb 2019

Please see the link for requested items: SR and SeaTools - Album on Imgur

In Startup and Recovery: the "Disable automatic deletion" was already checked. I unchecked "Overwrite any existing file" just now

The FreeAgent Go drive failed twice (out of 2 runs). SMART data was not available for this drive

zbook · 23 Feb 2019

1) Find a flash drive that you can format ( > or = 8 GB)

2) Create a bootable windows 10 iso:
Download Windows 10 ISO File | Tutorials
Download Windows 10

3) Perform an in place upgrade repair:
Repair Install Windows 10 with an In-place Upgrade | Tutorials

Steps for an in place upgrade repair:
a) Power on the computer
b) Open file explorer
c) Insert the Windows 10 iso into any USB port
d) Identify the windows 10 iso within file explorer
e) launch setup or setup.exe
f) follow the text and images in this link:
Repair Install Windows 10 with an In-place Upgrade | Tutorials

4) After the windows 10 in place upgrade repair the windows settings will need to be modified again.

Open startup and recovery system failure:
a) uncheck automatically restart
b) make sure that write debugging information is set to automatic memory dump
c) for dump file uncheck overwrite any existing file
d) check the box to disable automatic deletion of memory dumps when disk space is low

5) The HD Tune and Sea Tools were not able to perform SMART on the external seagate HD.

6) Download and install Speecy:
Download Speccy | Find your computer specs, free!

7) Open Speecy > click storage > scroll to the Seagate HD > see if it is able to find SMART

8) The SMART is predictive technology.

9) The drive has already failed Sea Tools long generic.

10) See if you can find an alternative external hard drive.

11) Make a backup image using Macrium:
Macrium Software | Your Image is Everything

12) Save the Macrium backup image to another disk drive or to the cloud.

13) Make a brand new restore point:
Create System Restore Point in Windows 10 | Tutorials

14) Please backup all of the important files on the external drive.

LeoBloom · 24 Feb 2019

In regards to the in-place upgrade; may I select "Keep personal files and apps" or do I have to select "keep personal files only"

Link for Seagate HD SMART data from Speccy: SMART Seagate HD - Album on Imgur

I could stop using the External HD since I already have an internal HD that I could back everything up to if you believe the external HD may be responsible for BSOD given Long Generic test Fail

zbook · 25 Feb 2019

For the in place upgrade repair please keep personal files and applications.

This should allow you to fix any problems with the operating system and reset windows settings to default.

The same Windows version would not fix deeper problems in the registry.

This is a trial and error step for the reported loss of memory dumps.

The registry can sometimes be fixed with an in place upgrade repair when there is a completed upgrade (1809 > 1903 etc.)

So if problems are not fixed with an 1809 to 1809 in place upgrade repair (fixes operating system) it is likely that there is a registry or application problem.

Another method that could be tried is a reset save files but this requires the re-installation of drivers and applications.

For the Seagate external HD:

a) If the external drive is under warranty please contact seagate.
If it is not under warranty see if they have a forum or free support.
America | Seagate US

b) Backing up the files is the most important step.
Then you have more flexibility with additional troubleshooting steps.

c) There are some in Ten Forums that have a lot of experience repairing HD.
Any test can have false positives.
It's a Seagate HD and the Sea Tools had a failed long generic test.

The Sea Tools for Windows was not able to perform SMART however and Speecy was able to perform SMART.

Consider opening a new thread in the General or Hardware forum with title:
Failed long generic but pass SMART external HD

See if you can test the drive using another computer to see whether it has the same results.

The Sea Tools software has repair options and there may be someone in the other forum that has used this feature.

LeoBloom · 25 Feb 2019

In-place upgrade has been completed. Of note, I didn't have to change any of the Startup and Recovery settings - the settings were not reset to default. It was ultimately the same (latest) stable version of windows 10 (build 1809).

The SeaGate drive is old and I have copied everything I needed from it. I will disconnect it from the computer for the time being and see if it helps in regards to BSODs

Should I do anything else at this point or just monitor for further BSOD?

zbook · 25 Feb 2019

For infrequent BSOD there is a tool that can be used to find misbehaving drivers and malfunctioning hardware.

The tool, Windows driver verifier, can be run for 48 hours.
Misbehaving drivers can be identified in the debugging.
After the last BSOD it can be run for an additional 36 hours.
Then the tool is discontinued and this completes the troubleshooting.

Before using the tool:
a) backup all important files to another drive or the cloud
b) Make sure that there is an up to date backup image of all important files
Macrium Software | Your Image is Everything
c) Make a brand new restore point:
System Restore Windows 10 | Tutorials
d) Read this link on the tool and make sure that you understand how to turn off or recover from using the tool after each BSOD:
BSOD Crashes and Debugging - Windows 10 Forums

There are customized settings for the tool.
Test all non-Microsoft drivers simultaneously.
The testing will start with 3 simultaneous customized tests as displayed in the link.

Over time the testing may increase to approximately 19 simultaneous tests and that will be communicated in the thread.

The computer may become sluggish and the boots may become slow while using the tool.

The computer can be placed in typical use while using the tool with the understanding that at any time there could be a BSOD.

After each BSOD:
a) Run the BETA log collector and post a new zip into the 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

LeoBloom · 28 Feb 2019

So I tried to run Driver Verifier according to the instructions provided on this link:
Using Driver Verifier to identify issues with Drivers - Windows 7 Help Forums

I got an immediate BSOD upon reboot - I was not able to get into safe mode.

After a couple of BSODs, Windows managed to self repair and I am able to use it again

Attached is the beta collector zip

Link to MEMORY.zip: Dropbox - MEMORY.zip

philc43 · 28 Feb 2019

The mini-dump file shows that Driver Verifier detected a problem with the ctxva51.sys driver. This is a Citrix Virtual Adaptor driver. Can you identify it and either update it or remove if it is not something you use.

Code:

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002004, Code Integrity Issue: The image contains a section that is not page aligned.
Arg2: ffffdd8dd72f32b8, The image file name (Unicode string).
Arg3: fffff8018faa01f0, The address of the section header.
Arg4: fffffe8982b4d220, The section name (UTF-8 encoded string).

FAULTING_IP: 
ctxva51+1f0
fffff801`8faa01f0 2e7465          hnt je  ctxva51+0x258 (fffff801`8faa0258)


1: kd> lmvm ctxva51
Browse full module list
start             end                 module name
fffff801`8faa0000 fffff801`8faaa000   ctxva51    (no symbols)           
    Loaded symbol image file: ctxva51.sys
    Image path: \SystemRoot\System32\drivers\ctxva51.sys
    Image name: ctxva51.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Jan 27 17:47:11 2010 (4B607C1F)
    CheckSum:         0000BECC
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

LeoBloom · 28 Feb 2019

Unfortunately, Citrix is required for my work. It is currently in the most updated state

Is it worthwhile to re-try Driver Verifier without checking Citrix drivers to test?