SMART is not the same thing as a surface scan. That's why you want to do a long test.
For Seagates, you need to run Seatools.
https://www.sevenforums.com/tutorial...s-how-use.html
Printable View
SMART is not the same thing as a surface scan. That's why you want to do a long test.
For Seagates, you need to run Seatools.
https://www.sevenforums.com/tutorial...s-how-use.html
Was the Data Lifeguard Diagnostic for Windows only to determine what HD it is? Or is that to also perform checks/fixes? It does seem to show the option to run tests. Is that part of the process?
Is that instead or in addition to the test on that UBCD5 thread?Quote:
You need to run the DLG for Windows to diag the USB WD hard drives.Quote:
Was the Data Lifeguard Diagnostic for Windows only to determine what HD it is? Or is that to also perform checks/fixes?
The link I posted was for the WINDOWS version Seatools. Again, you'd need to run Seatools for Windows to diag the USB drive.
UBCD5 would be used for INTERNAL hard drives.
I checked for Events and got another bunch of errors since I reconnected my EHD. The mention is now
An error was detected on device \Device\Harddisk4\DR7 during a paging operation.
So, Disk 4 again, but DR7 (no idea what that means).
However, I still didn't have a BSOD despite allllllllll those errors!
Ah OK. I had not gotten that. So at this point, I am done with the UBCD, correct?Quote:
UBCD5 would be used for INTERNAL hard drives.
So I select the drive and choose to Run the test from there?Quote:
You need to run the DLG for Windows to diag the USB WD hard drives.
And for the Seagate one, I will run the SeaTools for Windows. Correct?
So all those tests can be done through Windows and no need to boot and go through the BIOS?
Uh, so get started on those diags. If a drive shows any errors, you can stop the test. At that point, you'll want to copy data off of the bad drive.
For now, you're done with UBCD5. The bootable/DOS version probably won't be able to see the USB drives. That's why I said to use the Windows version.
You still want to do the short test first, then the long test. If the short test fails, you don't need to run the long test.
Ran the Seam Tools for Windows, and it recognizes all the drives (internal and external) EXCEPT the Seagate one! Yet, I see it in Windows Explorer.
Strange. Anyway, start with the WD drives. Disconnect the drives that you are NOT scanning.
OK first run on the Fantom drive (WD), I get:
Quick Test on Drive 4 did not complete!
Status code = 07 (Failed read test element), Failure checkpoint = 97 (unknown Test)
SMART self-test did not complete on drive 4!
>> I guess this might mean that this is the Drive 4 that was showing so many errors since 2 days in the Event Viewer.
Any point in running the long test?
So that drive is bad for sure. I'd still run diags on the other drives.Quote:
If the short test fails, you don't need to run the long test.
Since the Sea Tool does not seem to see the Seagate drive, can I use the DLG for that? Or what else can I do for that one specific drive?
I tried uninstalling and reinstalling the Sea Tools and I get the same thing.
Interestingly, DLG sees it no problem.
Interestingly, there is NO error since I disconnected that "big" EHD that was problematic.
I still have not scanned the Seagate one.
DLG might be able to see the Seagate drive, but it won't be able to SCAN it. That why I said you needed Seatools.
Did you try plugging the Seagate into a different USB port?
In any case, you'll want to copy the data off of the "bad" hard drive ASAP.
Yeah, that is what i thought.Quote:
DLG might be able to see the Seagate drive, but it won't be able to SCAN it. That why I said you needed Seatools.
I have tried all 4 USB ports I have on the front and the Sea Tool still does not "see" it.Quote:
Did you try plugging the Seagate into a different USB port?
Should I try on a different computer?
Definitely a next step!Quote:
In any case, you'll want to copy the data off of the "bad" hard drive ASAP.
Reading the help for Sea Tool, it reads this:
"SeaTools may not find or access hard disk drives when CMOS is set to "none" for those drives."
I don't know what CMOS is or if it is something that I am experiencing. What is that? Could that be the problem?
What about the BACK USB ports? Otherwise, yes you could take it to another computer and scan it there.Quote:
I have tried all 4 USB ports I have on the front and the Sea Tool still does not "see" it.
The CMOS (BIOS settings) is for INTERNAL drives, not USB.
Tried 3 USB from the back. Same thing.
Could it have something to do with the fact that it WAS an internal hard drive just put in an enclosure and now used as an External?
I set it up on the laptop, and Sea Tools still does not see it.
I doubt it. It's more likely that Seatools doesn't like the hard drive controller in the enclosure. Another option would be to take the Seagate out of the enclosure and connect it to an internal SATA port.Quote:
Could it have something to do with the fact that it WAS an internal hard drive just put in an enclosure and now used as an External?
If you're not seeing more errors in Event Viewer, then the priority should be getting data off of the "bad" drive.
Oh, you are talking surgery now! Yikes.Quote:
I doubt it. It's more likely that Seatools doesn't like the hard drive controller in the enclosure. Another option would be to take the Seagate out of the enclosure and connect it to an internal SATA port.
I have NO CLUE what that would mean and I suspect it will make my computer out of order for the time of that process, right? I might look into doing that on a "spare" computer we have. But i would need detailed instructions. (I will only be able to do that later today as i am leaving for a few hours).
At this point, I think you should focus on getting the data off of the "bad" drive.
Another idea would be to take the Seagate out of its current enclosure, and then put it into another one.
Another 4 hours later and still ZERO error with the "bad" drive disconnected.
I did install that CrystalDisk Info, and it showed that untested drive as being fine. I do have access to install it into another computer, as an internal drive. How would I do that? Guide me and I'll follow. If you feel it is needed.
For the "bad" drive, everything is already backed up so I just have to get another one and transfer. So that should be "taken care of".
I said that CrystalDiskInfo was for the SSD.
At this point, I think we've found the culprit. Leave the "bad" drive disconnected and hopefully it won't BSOD again.
If you really want to test the Seagate, I suggest you get a techie friend to help you locally.
https://www.wikihow.com/Install-a-SATA-Drive
Bad news. It rebooted overnight, and NO EHD was connected. After I woke up this morning, I was hoping it was a normal Windows update but it wasn't. I checked Event Viewer and sure enough, there were a few errors including critical ones. This is what the errors say:
Error 2:57 am: The previous system shutdown at 2:53:06 AM on 9/29/2019 was unexpected. (strangely, there was NO error at or around 2:53)
Critical: 2:56 (yes, it is listed AFTER the previous one): The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Error: 3:25 am: The previous system shutdown at 3:02:19 AM on 9/29/2019 was unexpected. (there was no error at or around 3:02)
Critical: 3:24 am: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Error: 3:25 am: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800b5a3b00, 0xfffffa800b5a3de0, 0xfffff80003bb1930). A dump was saved in: C:\windows\MEMORY.DMP. Report Id: 092919-41808-01.
Error: 3:29 am: The browser service has failed to retrieve the backup list too many times on transport \Device\NetBT_Tcpip_{CE792E5A-B025-48E8-9CFF-55903EF956CE}. The backup browser is stopping.
Critical: 5:59 am: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Error: 6:00 am: The previous system shutdown at 5:36:32 AM on 9/29/2019 was unexpected. (again, nothing listed around that time)
Error: 6:00 am: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800b5e0b00, 0xfffffa800b5e0de0, 0xfffff80003b67930). A dump was saved in: C:\windows\MEMORY.DMP. Report Id: 092919-44085-01.
This is the point when I got up and started the computer. After I found out it was an error and not a Windows update, I decided to open Outlook (so, nothing else was really open). The computer froze. Didn't respond to the mouse, to the keyboard. I thought it was just "waking up" and being slow but then, I got that BSOD within 5 minutes of having the computer open. This time, the errors read:
Error: 7:46 am: The previous system shutdown at 7:41:37 AM on 9/29/2019 was unexpected. (nothing listed at that time)
Error: 7:46 am: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800b01ab00, 0xfffffa800b01ade0, 0xfffff80003bb7930). A dump was saved in: C:\windows\MEMORY.DMP. Report Id: 092919-38922-01.
Critical: 7:46: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
So, doesn't that bring us back to square one, since the suspected culprit (might have been accessories to the issue) couldn't be the cause of those errors?
And I thought it was solved :(
Chatting with my son (who knows a bit more than me about tech issues, although he is not a tech person per say), we looked at various information from the EventViewer and BlueScreenView, and noticed a few things:
- in the BlueScreenView, many will have one of these messages:
"The problem seems to be caused by the following file: ntoskrnl.exe"
"The problem seems to be caused by the following file: Ntfs.sys"
"The problem seems to be caused by the following file: partmgr.sys"
and once
"The problem seems to be caused by the following file: ACPI.sys"
- the Crash Address always shows: " ntoskrnl.exe+93ca0 " no matter what the problem was pointing to.
Does that mean anything?
Those Event Viewer errors don't really point to anything specific. You'd want to look at the events that happened just before the shutdown. Check the Application and System sections.
It would be better if you could at least post a screenshot of Bluescreenview again. Just the file names isn't enough.
Sure. Here are the last two.
From the log of BlueScreenView, there were 2 shutdowns overnight, then one at 7:45 when I had just came to the computer, and another time, this afternoon.
Attachment 15183
Attachment 15185
As far as the EventViewer information, I found no error in the Application logs that match what "just happened before". All the errors listed are after, which is why I was listing them above. The BSOD happened at 3:23, 5:58, 7:45 and 12:59.
For the 3:23 crash,
there is no entry in the Application log between 3:01 and 3:25 (not even at the time of the BSOD)
In the System log, there is no entry between 3:02 and 3:24.
For the 5:58 crash,
In Application, nothing between 5:09 and 6:00
In System, nothing between 5:28 and 5:59
For the 7:45 crash
In the Application, nothing entered between 7:40 and 7:47
In the System, nothing entered between 7:40 and 7:46
For the 12:59 crash, there are 3 entries related to Outlook, about one minute before:
The store C:\Users\User_2\AppData\Local\Microsoft\Outlook\[email protected] is being reconciled with the indexer for the following reason: The store was last opened on a different machine.
The store C:\Users\User_2\AppData\Local\Microsoft\Outlook\[email protected] is being reconciled with the indexer for the following reason: The store was last opened on a different machine.
The store C:\Users\User_2\AppData\Local\Microsoft\Outlook\[email protected] is being reconciled with the indexer for the following reason: The store was last opened on a different machine.
>>> looking closely, I see three emails that are gmail and integrated with my Outlook. Nothing about the direct emails.
In System, nothing between 12:53 and 1:01
Hmm. Still getting the same error.Quote:
BTW, 0x0000007a KERNEL_DATA_INPAGE_ERROR for partmgr.sys is the one that makes me suspect the HD.
0x000000f4 critical_object_termination also seems like a drive or memory issue.
What is the exact model of SSD? Did you install the latest firmware?
You said that Memtest86+ passed, right?
It is a KingstonQuote:
What is the exact model of SSD?
I didn't install it myself so I can just assume the tech did itQuote:
Did you install the latest firmware?
I'll have to go back through this thread. I did one Memory test but don't think it was Memtest86+. Can you point me to how to do that?Quote:
You said that Memtest86+ passed, right?
Kingston is the brand, not the model. Firmware is specific to the model. The Kingston SSD tool should tell you which firmware you have and if there is an update available.
Don't assume anything. If you didn't ask for it, the tech probably didn't do it.
If you didn't run Memtest86# from UBCD5, what memtest did you run?
UBCD5 Guide post #3
http://discussions.virtualdr.com/sho...oot-CD-5-Guide
Ok.. back to the notes, yes it was the Memtest86 that I did.
Post #29
Post #18Quote:
Memory test is ok.
Quote:
Now, I also downloaded the Kingston SSD Manager. When I start it, what am I looking for? There is a Health overview and it shows that everything is fine. Is that all it takes to run a diagnostic test on it?
The Kingston SSD tool says "No firmware update available".Quote:
Kingston is the brand, not the model. Firmware is specific to the model. The Kingston SSD tool should tell you which firmware you have and if there is an update available.
Hmm. You could try running CHKDSK. There are other possible fixes like updating drivers on this link:
https://www.minitool.com/data-recove...age-error.html
1. Restart Computer
Already done (more than once!)
2. Fix Kernel Data Inpage Error with CHKDSK
I get this:
"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)"
Do I need to restart the computer to complete that task?
Or am I doing something wrong?
3. Run Memory Diagnostics Tool for a RAM Check
I'll have to wait, since that needs a restart again. Is it supposed to take long? (just trying to do those test while I still have work to do on the computer)
4. Run Antivirus Scan to Fix Kernel Data Inpage Error
I did Window Defender and Malwarebytes scan; came out clean.
5. Check System Log to Fix 0x0000007a Kernel Data Inpage Error
It says "check if there are any error messages that may cause the Kernel Data Inpage Error." How do I check that? Or did I already do that when compiling those messages above?
6. Update Device Drivers
All the drives were up-to-date.
7. Uninstall Incompatible Software
I have removed any "new" software that had been installed (for testing purpose) in the last month
8. Run sfc /scannow to fix Kernel Data Inpage Error
Doing it now. No idea how long it will take. - Done. Everything is fine.
9. Check Hardware and IDE/SATA Cable Connections
I could disconnect the printer and see. All the EHD are currently disconnected.
10. Reboot Windows in Safe Mode
If I do, I can't work on my computer. How long would it need to stay like that to "test" if that fixed the issue? In the past, although I have had 3 BSOD in one day, I also had 2 full days without any. I can't really leave the computer in Safe Mode for days.
9. Check Hardware and IDE/SATA Cable Connections
I could disconnect the printer and see. All the EHD are currently disconnected.
I just realized that the printer is connected through Wi-fi so guess this point was already addressed as everything was already disconnected.
3. Run Memory Diagnostics Tool for a RAM Check
I'll have to wait, since that needs a restart again. Is it supposed to take long? (just trying to do those test while I still have work to do on the computer)
Ran the test and no error was found.
2. Fix Kernel Data Inpage Error with CHKDSK
YES. You cannot run CHKDSK on your Windows drive from within Windows.Quote:
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)"
Do I need to restart the computer to complete that task?
5. I've already been telling you to check Event Viewer
6. Update Device Drivers
How did you check for updates? Did you actually look up drivers for each device? Checking through Device Manager doesn't count. I didn't see any obvious drivers to update from the BSODs or Event Viewer, though.
10. I don't think Safe Mode will really help.
We've already gone through the most obvious things. That's why I posted the list of other things to try.
You didn't say the make/model of your motherboard. 0x0000007a KERNEL_DATA_INPAGE_ERROR is usually related to disk, so you might want to update the chipset drivers.
Do you have any apps open when it BSODs? Keep apps closed and see if you still get errors.
Done overnight. No report anywhere? It was restarted this morning, after the test. Nothing showing.Quote:
YES. You cannot run CHKDSK on your Windows drive from within Windows.
Yes, that is what I was doing through Device Manager. I had also tried to do that manually, for the graphic card, my pen tablet, monitor, everything I could identify in the Device Manager, and then going to the manufacturer's site. I could not find any update for any of them.Quote:
6. Update Device Drivers
How did you check for updates? Did you actually look up drivers for each device? Checking through Device Manager doesn't count. I didn't see any obvious drivers to update from the BSODs or Event Viewer, though.
Aspire M5811Quote:
You didn't say the make/model of your motherboard. 0x0000007a KERNEL_DATA_INPAGE_ERROR is usually related to disk, so you might want to update the chipset drivers.
I checked the driver for the chipset and the last update is 2009. Is it worth redownloading? No update is more recent than 2010.
What do you call an app? I do have some regular processes in the background, but as far as common programs open when it happens, aside from that one time when I had ONLY opened EventViewer and nothing else, I have usual programs I work with daily (Outlook, Notepad++, PaintShop Pro, Skype, Chrome, and such). Nothing different than before I got those issues.Quote:
Do you have any apps open when it BSODs? Keep apps closed and see if you still get errors.
Looks like that has an Intel H57 chipset, but I don't see an updated driver on the Intel support site.Quote:
Aspire M5811
An app is an application. The only one that had errors was Outlook?
Most of the time, the 0x0000007a KERNEL_DATA_INPAGE_ERROR is a disk or memory problem. It's possible that it could be a motherboard issue. You could check the motherboard for bad caps.
https://www.badcaps.net/index.php