Tweaking.com Support Forums
Main Forum => General Computer Support => Topic started by: Lady on June 02, 2019, 03:53:16 am
-
Hello everyone,
On Friday, while doing my monthly system image and data backup I experienced a BSOD. This happened while Macrium was making a system image on one of my external HDs.
The last time I experienced a BSOD was almost a year ago. I asked about it on a Dutch forum but different and unclear answers got me confused and then I received nasty responses, so I left. :omg:
I must tell you that I have been having suspicions about this particular HD, it's a Western Digital My Passport Mobile 2Tb, 20 months old. It's just my intuition that has been telling me for a while now that there's something wrong with it. The only "proof" I have is that on this HD it seems to take much longer to make a system image by Windows. So I already checked it for errors through the Properties > Options in Windows Explorer. That came out okay. Can you tell me of other ways to check and repair the HD? Before I format it, lol. I just checked the two Western Digital HDs with Defraggler and they showed 46 and 39% defragmentation so a defrag is in order. But I don't suppose that would cause a BSOD?
Could it be the software of Macrium? Is it known to crash pcs while making these images?
Could it be the driver on the external HD? The Device Manager shows a yellow exclamation mark on all external devices (USB sticks and HDs.) I'm not familiar (yet) with dealing with drivers, but ready to learn. :cheesy:
I also looked at the Windows Application Log Files in Disk Management around the time the BSOD happened, but there was only one warning with an Execution Service. Here is a snip of the logs. I saw the BSOD just before 9 p.m.
It's a lot of information, I realize that, but maybe it will help you find out what went on.
Here is the WhoCrashed report. I tried to get the BSOD Collection file from Sysnative but somehow it gave an error message.
As always, very grateful you are there. :cheesy:
Lady
System Information (local)
--------------------------------------------------------------------------------
Computer name: USER-PC
Windows version: Windows 7 Service Pack 1 , 6.1, build: 7601
Windows dir: C:\Windows
Hardware: p7-1423w, Hewlett-Packard, Foxconn, 2ADA
CPU: GenuineIntel Intel(R) Core(TM) i5-3330 CPU @ 3.00GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 8466694144 bytes (7,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Fri 31-5-2019 20:17:22 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\053119-64974-01.dmp
This was probably caused by the following module: volsnap.sys (0xFFFFF88001B70D6E)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001B70D6E, 0xFFFFF88009A5B7C8, 0xFFFFF88009A5B030)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\volsnap.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Volume Shadow Copy-stuurprogramma
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
-
With the WD HDD plugged in, the trial version of HDSentinel may show up something but there is a more dedicated WD diagnostic utility.
Try either of them -
https://www.hdsentinel.com/hard_disk_sentinel_trial.php
https://www.techspot.com/drivers/driver/file/information/18061/
Windows has its own troubleshooting though which can be found in Win 7 in Control Panel/All Control Panel Items.
Double click on Troubleshooting then on View all.
Click on Hardware and Devices/Advanced and ensure the box for Apply repairs automatically is checked - Next
It may be best to have the WD HDD plugged in for this.
-
I'll try that tomorrow, right now the HD is being defragmented.
But what about the BSOD, do you think it has something to do with the HD?
-
BSODs are usually to do with drivers and your crash report does reference an unknown driver.
If you don't get any more when the HDDs are disconnected then it's most likely to do with the WD HDD.
You can still run the Windows troubleshooter to see what that reports before running the WD utility.
-
I ran the Windows troubleshooter. Among a few other things which weren't applicable it said there was a driver problem with G: which wasn't there. The HD was L:. (I removed all other external devices before doing this.) I did click on apply solution there but nothing happened as far as I could see. It said that it was a Microsoft WPD FileSystem Volume Driver. I'm not sure what all this is about but do I understand correctly that with Windows Portable Device it means the external HD? If so, could this link be helpful?
http://download.cnet.com/Microsoft-WPD-FileSystem-Volume-Driver/3000-2122_4-89013.html
The defrag didn't do much, it went from 39% to 38%. What does that say? Should I do it again or is it better to format the disk and start all fresh?
I started the WD Drive Utilities which I saw I had on board in the WD folder. See screenshot. This is how it looks like. It's in Dutch but I can tell you. The first is check disk status for errors which happened really fast. The second is fast scan disk for serious errors which was completed. The third is an extensive scan on damaged sectors which is still running. I didn't get any reports on the first two scans. Have to find out where they are if there are any.
So I installed HDSentinel which I still have in my Save Downloads folder, like you taught me. :smiley: It says the external HD status is perfect. See screenshot of the overview.
-
For me it's never a good idea to download drivers from 3rd party sources.
HDSentinel shows 93% Health for the Kingston - is this the suspect HDD ?
I don't have a Portable Devices section in my Device Manager (as in the following article), so can't find the Microsoft WPD FileSystem Volume Driver on my Win 7 x64 Home laptop.
https://appuals.com/fix-wpd-filesystem-volume-driver-code-10-or-yellow-exclamation-mark/
My Seagate external drive is listed in Disk drives.
I'm not sure if a sfc /scannow may resolve that but you can uninstall it in Device Manager and then click on Action/Scan for hardware changes where Windows should reinstall it.
However, create a restore point before removing anything.
Can you open Device Manager - click on View/Show hidden devices and check for any other yellow alerts, but post a screenshot of your Device Manager.
-
The Kingston is the SSD. See screenshot.
Can I remove HD Sentinel again to save the number of days or do you want any more additional information from it?
I just performed a defrag analysis via command prompt and it says that the WD HD has 4% fragmentation and need not be defragmented. So which one do I trust? Defraggler's or Windows's outcome?? That is a huge difference, 38 or 4%.
Just in case, I looked it up and I have a 2 year warranty on the HD. Bought it on Oct. 23, 2017.
I'm getting confused now, Tom. I read through the article. Solution 3 is about reinstalling the WPD Filesystem Volume Driver manually. Now I have 4 of these drivers under Portable Devices (Dutch: Draagbare apparaten) but the WD HD is under Disk Drives (Schijfstations) highlighted. See screenshot. This HD has password protection with hardware encryption.
I opened the Properties of the WD HD there. It says it works correct. I see two drivers under Details. See screenshots.
Another thing I thought about: I used a hub to connect the external HDs to while making the backups. I know a hub has its own driver, right? Could that one be the culprit? I know hubs can be very unstable, although this one, an Anker, is supposedly a good one.
What I don't understand is why the WD HD is under Disk Drives but the Windows error message was about the Volume Driver and they are under Portable Devices. So can you please explain this situation to me in the most basic way? Does the WD HD has its own driver or does Windows install a driver of its own on the HD? I may be saying crazy things but I'm way out of my league here.
-
Some 3rd party defrag programs can give anomalous results - although I've tried a 3rd party one in the past, I prefer to just use Windows own defrag program or the cmd prompt.
I don't think I've checked the fragmentation on my external HDDs but have used the cmd defrag /c to manually defrag my internal HDD which is what Windows does when auto checking all drives.
WPD stands for Windows Portable Devices and is a Windows driver to sync portable devices to the computer.
I think the reason why I don't have that in my Win 7 laptop is because it has AMD graphics and the South Bridge aspect of those drivers looks after the USB side of things.
It could very well be the hub that is causing the problem.
Try plugging in a HDD directly into the USB port and then go into Device Manager to see if you now get a WPD driver that doesn't have a yellow alert.
-
Many of these WD drives use a controller chip between the SATA connection and the drive interface, this requires specific drivers (WD Smartware/SES?). It may also be set to auto-encrypt.
Should *something* go wrong with the controller, firmware, password, 'drivers' etc. all Windows-based tools will 'see' is a block of encrypted data, nothing can access the real data stored.
Take a little time to look at the topics on the WD portable 'support' site: https://community.wd.com/c/wd-external-drives/wd-portable-drives
Capacity
4TB, 3TB, 2TB, 1TB
Interface
USB 3.0 / USB 2.0 compatible
Additional Details
- Auto backup with included WD Backup software
- Password protection with hardware encryption
- 3-year limited warranty
Package Includes
- My Passport hard drive
- USB 3.0 cable
- WD Discovery™ software for WD Backup™, WD Security™ and WD Drive Utilities™
- Quick install guide
-
Device Manager gives the HDD Properties as working fine - the yellow alerts are on the WPD drivers and Windows troubleshooter lists the WPD drivers as being at fault.
-
Thank you, satrow, for your suggestion. I now agree with Boggin that it's not the HD itself.
This is what I'm going to do: when I have some time I'll remove the hub and plug in one of the devices attached to it and check its WPD driver and if it's signalled in Device Manager I'll perform solution 3. How about that, Boggin?
-
Yes, you will need to uninstall those 4 with the yellow alert, but you could uninstall those 4 and reboot, then plugging directly in an ext. HDD would reinstate the WPD driver for each ext. HDD.
I forgot to add earlier that yes, you can uninstall HDSentinel to preserve the clock on it.
-
Contact me when you upload the data collected by the Sysnative app., I'd like to take a look at it.
-
@satrow I keep getting this error message from Sysnative. See screenshot. It says that the file version is not compatible with my Windows version, 32 or 64 bits. It's really strange, I never had any problem getting the Sysnative report. Just download it, execute it and fine. So I don't know what that is about.
@boggin Tom, how do I know which devices are meant with these 4 drivers?
-
I'll see what I can find out about that error message.
Use Explorer with files and folders unhidden and navigate to C:\Windows\Minidump, copy the files to your Desktop then zip (right-click > Send to > Compressed folder) and upload the resulting zip file.
For a recent snapshot of your PC for further details and comparison of any driver changes, etc, Run MSInfo32, when it opens, click down through each section to ensure all details have loaded (a small number won't load anything), Save that to your Desktop as msinfo.nfo, then zip (as above) and attach it here.
-
What sysnative app is that ?
-
@satrow I just tried the Sysnative App again but same error.
Here are the two zip files you requested. I must say I'm entering into whole new territory here! Another Expotition! :cheesy: But it's good, I'm learning again.
Before I made the msinfo I connected the hub again which I disconnected last night to try out devices. I thought maybe you can check out its functioning with the msinfo.
Indeed, I now see in the msinfo the 4 WPD drivers under problem devices... The Ralink I think is uninstalled because I have a LAN connection and was advised to disconnect the Wifi to not have both running.
I'm sorry, the msinfo is in Dutch. Cannot help that.
@boggin Yesterday before shutting down I disconnected the hub and uninstalled all 4 drivers. Now I connected the two WD HDs (My Passport) directly to the USB port and in Device Manager I see that nothing happened to the WPD drivers. See screenshot. So does that mean that the 4 signalled drivers do not refer to the WD HDs? If so, then the HDs are fine? I will add more devices and see when a WPD driver will get installed. It's not my MP3 player, not my phone. Just now I connected the 3.0 hub on which the WD HD was connected when the BSOD happened and this time I got the popup saying the drivers have been installed. The hub has 4 connectors, is this the one I see in Device Manager? The 4 WPD drivers are still uninstalled. So where do they belong to? I think I need some Drivers 101, lol.
Sysnative for BSOD collection:
https://www.sysnative.com/blogs/download/sysnativebsodcollectionapp-exe/
-
It looks like those WPD drivers have been reinstalled as I thought they would be.
Try creating a system image onto the HDD you thought was a bit slow to see if there's any improvement.
Did you try that Sysnative app before or after the WPD drivers were reinstalled ?
I'll ask again - what is that Sysnative app ?
-
Tom, it's the Sysnative BSOD Dump + System File Collection App: https://www.sysnative.com/forums/threads/blue-screen-of-death-bsod-posting-instructions-windows-10-8-1-8-7-vista.68/
Indications are that it can currently only be downloaded correctly via IE11, other browsers get a truncated download, it's being investigated.
Lady, MSInfo shows that the wdcsam64_prewin8.sys, the WD SAM driver that allows access to your ext. drive, isn't loading currently, whereas a quick look at the minidump with BlueScreenView shows that it was loaded during the session which crashed:
-
Tom, I tried to show with the screenshot, but it's in Dutch, that the WPD drivers aren't being signalled anymore but all 4 of them are still uninstalled. The right-click popup says "inschakelen" meaning "install", so right now they're uninstalled. That's why I asked for what devices they are intended.
Satrow: I think you found something significant, lol. I have no idea what that means or what I should do. Is that the culprit?
-
Go into Device Manager/View/Show hidden devices then click on Action/Scan for hardware changes to see if that completes the install.
Failing that, right click on each and select Update driver and to search online to see what that reports.
I have a WPD driver on my AMD Win 10 laptop but it must now be part of Windows as MS slipped in an update for it on the 28th May.
-
Basically, I think it means you've lost access to that drive, the WD drivers aren't loading, W7's troubleshooter/Device Manager are trying to load incorrect drivers because they're not getting through to the Ext. drive controller now.
-
I performed the Action/Scan already without results. Before we continue with that, Tom, let's try what satrow is saying.
But since you, satrow, now say that it's the malfunctioning driver of the Western Digital HD, if I understand correctly, how do I check that? I connected it this morning and could open it. Doesn't that mean the driver is fine again? I really don't know what I'm talking about, hahaha. Trying to keep up with you guys. :cheesy:
-
Try to open the drive via Explorer again, if it's successful (you can see/read your files), run the MSInfo routine again and upload the .nfo zip so I can, hopefully, see what's loading it.
-
Here is the new msinfo file.
-
Hardware section gives what looks like the correct details for L:, no WD drivers loading (wdc_sam inactive, manual start), 4x WD utilities running plus 4 associated modules loaded - wait, https://www.sysnative.com/drivers/driver.php?id=wdcsam64.sys (note the lack of _ underscore)
'Our' wdcsam64_prewin8.sys (from the crash dump) is dated 16/04/2008 09:39:08, could this be a renamed version of the 'bad' driver listed below?
Name wdcsam64.sys
Info Western Digital External Drive RAID Manager
2008 driver version has known BSOD issues in Windows
Source http://support.wdc.com/product/download.asp or
SES driver update: http://wdc.custhelp.com/app/answers/detail/search/1/a_id/5419#
I suspect a collection of the latest WD drivers/software for your specific drive will be needed before an uninstall all-reboot-reinstall routine.
Thoughts Tom?
-
Well according to that article the SES drivers should have already been installed, but you could create a restore point and download afresh from that website.
Drivers can become corrupt for whatever reason.
When I decided to buy ext. HDDs I opted for Seagate because I remembered reading adverse reports about WD - they seem to be more complex than what should be necessary.
-
Well according to that article the SES drivers should have already been installed, but you could create a restore point and download afresh from that website.
They are installed but not loading since the crash.
Drivers can become corrupt for whatever reason.
No indications from either the crash dump or from MSInfo that any drivers are corrupt.
When I decided to buy ext. HDDs I opted for Seagate because I remembered reading adverse reports about WD - they seem to be more complex than what should be necessary.
I recall writing (at least) one and some of them are.
-
Does Event Viewer have anything recorded for when you plug in an ext. HDD ?
-
Where should I be looking in Eventviewer, Tom? Under System or Application?
When I had to buy new external HDDs years ago I changed from Seagate to WD because Shane recommended them over Seagate. I must say up till now I have had no issue whatsoever with either brand. The wonderful feature of the WD My Passport is the hardware encrypted password protection, so I feel very safe using them.
So in my own words: do I understand correctly when I say that the drivers of the WD HD are fine but that they are not being loaded after the crash? And what caused the crash, do you know now?
Something else I noticed. I now have both WD HDs connected, I have a white and a black one. The HD in question - the white one - keeps flickering its led-light in like a second interval whereas the black one shows no led activity. It's obvious but I have to say it: I haven't been reading/writing on either of them since I turned on the desktop. So this shows to me that the WD is in a constant activity. Maybe trying to get the drivers?
-
Anything would probably be under Errors in Event Viewer.
Whenever I plug in the ext. HDD I use for system images on my Win 7 machine, I get about 5 Disk Event ID 11 errors which appear to have no effect on the system image being created as I've recovered with them as a test.
If drivers aren't loading then it would be under Errors I would expect to see something.
I would just check things with the suspect HDD.
Why drivers should load for one and not the other, I don't understand, but if this is specific to this drive then I would expect something to have been recorded in Event Viewer.
Reliability history may also have something.
EDIT - I forgot to add that plugging the same HDD into a Win 10 machine produces no such errors.
-
Test them individually between reboots and plugged directly into the rear ports. From Device Manager's Properties sheet for the drives, report back on which drivers they're using.
The 'difficult' drive looks like it's being read incorrectly by the troubleshooter and Device Manager, rare but it can happen after corruption - likely the drive's firmware. Logging's likely to give spurious data/results because of that.
-
You could try running WD's Data Diagnostics for Windows on the HDD but also with the HDD plugged in, in Device Manager right click on it and select Uninstall.
Click on Action/Scan for hardware changes where it should reinstall its drivers.
You can either do that in Disk Drives or in the USB section where you will need to find which one it is using.
Have you also tried using a different cable ?
WD Diagnostics - https://support.wdc.com/downloads.aspx?p=3
-
I clicked Uninstall in Device Manager and did Action/Scan for hardware changes (on the WD HD).
I downloaded the WD SES Driver.
I downloaded the WD Diagnostics. That looks a LOT better than the WD Drive Utilities that came with the HD. It's now running an extended test. See screenshot. Will report. The SMART status already says Pass, that's a good sign, isn't it?
And a screenshot of the Device Manager's Properties sheet for the WD HD.
A basic question: why can't I remove all firmware from the HD and re-install it? Just like formatting to replace corrupt data.
-
Certainly looks better, are the new SES drivers installed?
It might be possible to clear the drive so that it bypasses the WD drivers/SES/Encryption, so it behaves like a standard ext. drive, I'll look into that later, unless Tom finds the time before I get back.
-
Certainly looks better, are the new SES drivers installed?
I don't know how to check that.
It might be possible to clear the drive so that it bypasses the WD drivers/SES/Encryption, so it behaves like a standard ext. drive, I'll look into that later, unless Tom finds the time before I get back.
I'm not sure if I understand this correctly, but I definitely don't want to lose the encryption.
-
Reliability history will tell you which drivers were successful or not in installing.
-
This is what my reliability monitor looks like. I guess this is what you mean. I don't see anything that looks like a driver.
Please don't forget my system is in Dutch and I've never dealt with any of these things before.
-
No, that's the reliability monitor.
Go Start - start to type reliability and press enter when View reliability history comes up.
It may have red crosses or an i for info for certain days.
Click on any day where you have these and more info will come up in the bottom pane and clicking on the blue tech details link will produce more info.
-
DriverView (http://www.nirsoft.net/utils/driverview.html) will show the loaded drivers, for 3rd party drivers like these, set it to hide MS drivers (some MS drivers are created 'on the fly', they'll show as unknown but can be ignored, eg. dump_?????.sys), View > Hide Microsoft drivers:
-
Nothing is given with reliability in Start.
I have an urgent matter at hand now. I got a popup saying C: was full. I did disk cleanup to free 412 Mb so I could continue. This is really odd. I know C: is very full, I believe the other day I saw it had 5 Gb left. It's an SSD with only Windows 7 on it. I tried to find out how to decrease that volume but didn't know how. A year ago when I had the last BSOD someone told me that it was a driver issue but we couldn't solve it (probably the same thing as we're dealing here with) and in that process someone said that my system partition on C: was almost twice as large as his Windows 8.1 professional. I went through all the programs installed but couldn't free much space there and I don't believe that the programs total more than 100 Gb. I just checked: I have 190 programs occupying 7,5 Gb disk space.It must be something else that takes up so much space. Tom, you know how I clean up the pc each month for my system image backup. So it cannot be the usual clutter.
I made screenshots of the popup warnings but they failed. I have a screenshot of disk management. I remember that one of the warnings said that it happened while something was being written to C:. What I noticed this morning while checking Windows logs > application for errors of the WD HD was that there was an enormous number of the same information and warning. These two (information and warning) show 3 times a minute since I started up the desktop. So that should tell you something, I hope. See screenshot and details. I disconnected the faulty WD HD but these two things continue to come up in the logs up till this moment. So something weird is going on now. Hope you can help me out. Maybe a reboot could fix it and it's just a glitch but first I'd like to hear your comment.
-
I edited my last post several times.
-
I can't really understand what that Code 10 refers to.
Yes, I noticed earlier you only had 5GB free space left in C: and wondered if that could cause problems.
You can free up about 6GB by turning off Hibernate.
Run a cmd prompt as an admin and enter powercfg -h off
Can you also check you see how much space is being taken up by the restore points.
Go Start - type appwiz.cpl and press enter when it comes up.
This will open Programs and Features and when you scroll to the bottom you will see where it totals the number of programs and how any GBs used.
Running Disk Cleanup as an admin will also remove obsolete Windows Updates, but you may have to check its box to include those in the clean up.
-
"This device cannot start. Try upgrading the device drivers for this device. (Code 10)" (https://support.microsoft.com/en-us/help/310123/error-codes-in-device-manager-in-windows)
-
What do you get when you type view reliability history ?
Have you freed up any space yet ?
-
A picture might help:
-
You can free up about 6GB by turning off Hibernate.
Run a cmd prompt as an admin and enter powercfg -h off
I did that.
Can you also check you see how much space is being taken up by the restore points.
I don't know where to find that, I can only see there are 9 restore points.
Go Start - type appwiz.cpl and press enter when it comes up.
This will open Programs and Features and when you scroll to the bottom you will see where it totals the number of programs and how any GBs used.
I don't see it iin Programs and Features on the bottom. I already mentioned it in my last post, I found it in WiseProgramUninstaller. I have 190 programs occupying 7,5 Gb disk space. So that is not much.
Running Disk Cleanup as an admin will also remove obsolete Windows Updates, but you may have to check its box to include those in the clean up.
I wrote that I did disk cleanup, including the Windows Updates.
Re the WD HD: I connected it to my laptop and ran the WD Diagnostic tool, quick scan. It immediately gave an error, saying too many bad sectors. See screenshot. The same with the extended scan. Then I returned to the desktop, connected it there and for the first time there was the popup that the driver had been installed!! I ran the WD Diagnostic tool quick scan and that came out perfect. I don't know how to get the scan report to show you but I made a screenshot so you can see part of it. Now the WD HD doesn't flicker anymore. The led light is constant. BUT I hear and feel the HD inside running, although I closed down Explorer and everything that could make it run. That shouldn't be, right? I will now start an extended scan, but that scan takes many hours. I hope I'll get it finished by tonight. I also changed the cable, same.
Thanks, Tom, for your quick assistance. This was a scary moment. <3
-
@satrow
Especially for you, satrow, Driver View. :cheesy:
I had a quick glance because I have to run, but here are the screenshots. I think I highlighted the right one. :artist:
Oh, and I finally found the Action Center. But nothing seems to be out of the ordinary, no warnings.
-
Second post re the available disk space of C:
I raised the amount of free space on C: to 35 Gb or 31% by removing all content of the Library (mostly of Pictures) which I use to store stuff temporarily but which had become totally cluttered because I didn't have time to process things. I moved it to the internal HD partition D:. 31% free space is quite enough, I guess, for C: to function properly, isn't it?
Still these strange two information and warning logs about code 10 have continued up to this point. But I found out something about that. Check the screenshots, 3 in a row. These 3 keep repeating. That must mean something is going wrong with the Prey program. Although it's not a device (code 10 @satrow), to make sure, I logged into the Prey program and logged out again. Or maybe there was something going wrong at their end and they solved it just now. I'll check the logs tomorrow.
Restore points: there are 10 restore points. The last one, which is not in the picture, is of June 7 when I downloaded the SES driver. I found out the different ways to remove them. Shall I remove all restore points but the last one? Look at the list, how strange is that? I make a restore point every month when I make my system image backup. Where are they? There is even still one of 2015, which is crazy. CCleaner only gives the last 3, so that's not helpful. So I have two options: clearing them all, or all but the last one. Clearing them all but the last one also deletes shadow copies I read. That term is new to me. Is that safe? Maybe the shadow copies of so many years are cluttering up the disk space?? I must say, in the past I have tried using restore points in crisis situations but it hardly ever worked and I have my system image backup now. :artist:
Re the WD HD: it passed both tests, quick and extended. See screenshot. Can you see whether the driver is correct now? The WD HD is quiet now, the led light is flickering again. The light should be out when not in use. So it's still not ok.
Hope you're still with me. :cheesy:
-
Have you thought of contacting WD about sending it back under warranty ?
-
Yes, but I don't know what to tell them when their Diagnostic tool says it's fine. Maybe you can help me with phrasing that.
A driver question (I'm learning :smiley:): with DriverView open I connected WD HD and the driver appeared. Then I connected the other WD HD, the black one, but no second WD driver appeared. Is that okay? Does that mean that the same driver is used for both HDs?
I still have those four WPD file system volume drivers. They're on uninstall mode. Should I install them? They're not in use now, are they? Haven't found any portable device of mine yet which uses one of them. Then they were used to get the WD HD running like satrow said, is that correct?
How is the WD HD driver doing right now? I see in DriverView that it is installed on the WD HD but is it loading correctly now? I finally was able to get the Sysnative App report. See attachment. So maybe you can see what really caused the BSOD and we can rule out the hub? I noticed that the Sysnative App report is the same as the msinfo report. Can you tell me where to look for that driver, so I can learn how to check that. I looked through it but I cannot see it.
The black WD HD is quiet and its led light is on constantly. I think I saw that incorrectly earlier, that I thought it should be out in rest. The white WD HD's led light is also on continuously, sometimes it flickers and the HD inside is running which still says there's something very wrong. I can still access the files on it, so there's no problem.
Can you or satrow please tell me what you think actually caused the BSOD? Was it the hub or the WD HD driver? Or was the hub unstable upon which the WD HD driver crashed and the system shut down? I think it's best that I connect the ext. HDs directly to the USB port next time I make system image backups, right?
I just checked the Windows logs > Applications and those three Prey logs are there again all the time. Should I do something about that? Prey is a program which locates your devices when lost or stolen. But since I have a VPN I don't think they can be found anymore, hahaha. So should I uninstall Prey and see if those logs disappear?
About the C: disk space: how much space do the Windows7 operating system files take up? To check if there's something wrong there.
Tom, could you please answer the questions I asked in my last post? Some are important, like the restore point/shadow copies one.
Excuse my many questions. We're dealing with several issues at the same time and I felt taxed with all this new info and I'm trying hard to get my head around all of it.
-
In the past I have occasionally turned off system protection which has removed all restore points and then the greyed out volume shadow copies in Device Manager.
Retaining just your last restore point, you could still go into Device Manager and uninstall/delete the greyed out volume shadow copies.
Win 7 requires 20GB of space.
I'll leave the sysnative report to satrow as it's in Dutch, but he'll be aware of what each log refers to.
As for contacting WD, you could ask them why the HDD light flickers and continues to run when it isn't in use and that may point them to something we aren't aware of.