Solved BSOD when Backing up HDD using EaseUs

[gopher22]

While performing a System Backup using the latest EaseUs ToDo Backup software (version 9.1) I am experiencing a BSOD (KERNAL_DATA_INPAGE_ERROR) each time the app has run for several hours. Before I initiate the backup, I kill all un-necessary apps and background stuff and I disconnect from the Internet.

Here are some of my laptop specs.

Host Name: VAIOVGNZ
OS Name: Microsoft Windows 7 Professional
OS Version: 6.1.7601 Service Pack 1 Build 7601
Original Install Date: 4/3/2013, 5:52:14 AM
System Manufacturer: Sony Corporation
System Model: VGNZ790DLX
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 23 Stepping 10 GenuineIntel ~2801 Mhz
BIOS Version: INSYDE R4044M3, 11/10/2009
Hard Drive: HGST HTS721010A9E630 (1000.20 GB)
Total Physical Memory: 4,027 MB
Available Physical Memory: 2,056 MB
Virtual Memory: Max Size: 8,121 MB
Virtual Memory: Available: 5,511 MB
Virtual Memory: In Use: 2,610 MB
Page File Location(s): C:\pagefile.sys

I have BlueScreenView installed and yesterday’s Memory Dump highlighted NTOSKRNL.EXE. In todays dump both NTOSKRNL.EXE and CDD.DLL were highlighted.

Today I changed my Paging File from a fixed size value of 4096 MB to Automatically Managed just in case it was causing the problem.

After browsing earlier today for BSOD issues in the forum, I downloaded and installed the SF Diagnostic tool and created the files ready for zipping and upload. Before I send them, I am going to run the backup again and see if I am still getting a BSOD and will report back later.

If I need to upload any reports which is preferred? SF Diagnostic Tool or the DM Log Collector, There may be some redundancy.

Thanks in advance.

 

[axe0]

Both folders normally contain the same data, so it doesn't really matter but it is prefered to upload the DM Log Collector reports

 

[whs]

Here are some suggestions for fixes.

HP PCs - Blue Screen Error: KERNAL_DATA_INPAGE_ERROR | HP® Customer Support

 

[axe0]

Yep, those are causes of a 0x7A (not all usual causes are there), but with some there is a culprit
1. It often happens that the virus scanner used is the cause.
2. Usually difficult, the user isn't aware of all the drivers that could trigger the crash.
3. A failing hard drive doesn't have to have bad sectors, you'll need to look at the S.M.A.R.T. attributes too

This (and some more reasons) is why we need dumps.

 

[gopher22]

I tried again this morning after disconnecting from the internet and shutting down all malware apps and a few others that run in the background. All was in vain, the backup failed after about 45 minutes; same BSOD as before.

I have attached a zip file after running DM Log Collector. I await a cure with bated breath.

Thanks.

 

[axe0]

Unfortunately this isn't a cure, only a diagnostics test to confirm the suspected cause.
Looking at the dump argument 2 has value 0xC0000185 which is indicative of a i/o error what could mean a hard drive problem, or the cable or the motherboard.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

1. Short Drive Self Test
2. Short generic
3. Long generic

If the short generic fails, no need for the long generic.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
[COLOR="Red"]If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.[/COLOR]
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc5009f3a0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffff[COLOR="red"]c0000185[/COLOR], [COLOR="red"]error status (normally i/o status code)[/COLOR]
Arg3: 0000000019bb2820, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a013e743c6, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

 

[gopher22]

Thanks axe0 for the prompt response.

I ran CHKDSK /R the other day but it did not find any problems. It did find some bad sectors a few months ago but it fixed them and there have been no known issues since then until I tried to clone the drive in readiness for replacing it with an identical HDD. Each attempt fails.

I will run chkdsk /r again tonight and will run Sea Tools and HD Tune which I have in my "tool box" today. I will post the results. Replacing the HDD in this laptop requires major surgery unlike my two Dells where it only requires the removal of two screws then it slides out of a slot in the side of the case.

Later.

 

[axe0]

Just to let you know, chkdsk /r recovers data from the bad sectors and marks the bad sectors so the system knows what sectors are bad. Depending on a SMART attribute, which shows how many bad sectors your hard drive can hold without problems, it may or may not give problems now.

 

[gopher22]

Here is a copy of the latest Chkdsk and SeaTools results, and I have attached JPGs of HD Tune Benchmark, Health and Error Scan. As you can see we have a problem. I will need to open up the laptop (uggghh) and check the cabling before committing to replacing the HDD with an identical spare that I have sitting on my desk.

+++++++++++++++++
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.

CHKDSK is verifying files (stage 1 of 5)...
380928 file records processed.
File verification completed.
3687 large file records processed. 0
bad file records processed. 2 EA
records processed. 40 reparse
records processed. CHKDSK is verifying
indexes (stage 2 of 5)...
468364 index entries processed.
Index verification completed.
0 unindexed files scanned. 0
unindexed files recovered. CHKDSK is
verifying security descriptors (stage 3 of 5)...
380928 file SDs/SIDs processed.
Cleaning up 88 unused index entries from index $SII of file 0x9.
Cleaning up 88 unused index entries from index $SDH of file 0x9.
Cleaning up 88 unused security descriptors.
Security descriptor verification completed.
43719 data files processed.
CHKDSK is verifying Usn Journal...
36874736 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
380912 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
127636363 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.

976657407 KB total disk space.
465396172 KB in 303644 files.
198988 KB in 43720 indexes.
432 KB in bad sectors.
516363 KB in use by the system.
65536 KB occupied by the log file.
510545452 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
127636363 allocation units available on disk.

Internal Info:
00 d0 05 00 ea 4c 05 00 6b c4 08 00 00 00 00 00 .....L..k.......
24 1a 01 00 28 00 00 00 00 00 00 00 00 00 00 00 $...(...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts
+++++++++++++++

--------------- SeaTools for Windows v1.2.0.10 ---------------
12/8/2015 12:40:43 PM
Model: HGST HTS721010A9E630
Serial Number: JG40006PG0RTWD
Firmware Revision: JB0OA3B0
Identify - Started 12/8/2015 12:40:43 PM
SMART - Pass 12/8/2015 12:41:55 PM
Short DST - Started 12/8/2015 12:42:25 PM
Short DST - Pass 12/8/2015 12:47:34 PM
Short Generic - Started 12/8/2015 12:59:38 PM
Short Generic - Pass 12/8/2015 1:01:23 PM
Long Generic - Started 12/8/2015 1:06:55 PM
Long Generic - FAIL 12/8/2015 2:05:55 PM
SeaTools Test Code: 6C9AC2A4
Long Generic - Started 12/8/2015 3:34:08 PM
Long Generic - FAIL 12/8/2015 4:36:33 PM
SeaTools Test Code: 6C9AC2A4
Long Generic - Started 12/8/2015 6:35:20 PM
Long Generic Aborted 12/8/2015 6:42:57 PM
Long Generic - Started 12/14/2015 7:14:34 PM
Long Generic Aborted 12/14/2015 7:15:28 PM
Long Generic - Started 12/14/2015 7:15:42 PM
Long Generic - Aborted 12/14/2015 7:15:45 PM
Short DST - Started 1/25/2016 8:03:56 AM
Short DST - Pass 1/25/2016 8:06:56 AM
Long Generic - Started 1/25/2016 8:28:50 AM
Long Generic - FAIL 1/25/2016 9:39:24 AM
SeaTools Test Code: 6C9AC2A4
Identify - Started 1/25/2016 10:02:42 AM
Identify - Started 1/25/2016 10:09:14 AM
Short DST - Started 3/28/2016 2:48:02 PM
Short DST - Pass 3/28/2016 2:50:27 PM
Short Generic - Started 3/28/2016 3:08:53 PM
Short Generic - Pass 3/28/2016 3:10:29 PM
Long Generic - Started 3/28/2016 4:25:57 PM
Long Generic - FAIL 3/28/2016 4:54:09 PM
SeaTools Test Code: 6C9AC2A4

++++++++++++++++

 

[axe0]

My guess is more the hard drive than the cabling, but I could be wrong.

I would besides of the drive problem also check for a BIOS update after the hard drive problem is gone.

 

[gopher22]

I agree axe0, but the cabling is an easy to do check. After the HDD is removed I could re-run the tests on the drive in a docking station attached to one my desktop PCs for comparison purposes. I have copies of all my data on backup drives, lots of them, so if an image I created a long time ago is no good, I could do a clean install of Win 7 Pro. The only downside to this is installing from an OEM disc then having to re-install all the Sony stuff so that everything works like it does now. Wish me luck.

The laptop originally cost about $2,400 equipped with a 320 GB HDD and Vista but I upgraded it to 1 TB and Win 7 Pro a few years ago. I originally purchased it in 2009, wow 7 years, and it is and has been a great laptop and goes everywhere with me. People ask why I don't get rid of it and buy a new one, but is normally runs fine, has a BD DVD burner, HDMI display and lots of other features like a carbon fiber case so is very light and fits easily in a small rolling travel suitcase along with my personal items. I was planning on a replacement for it, but a few years ago SONY sold their Vaio line to a Japanese outfit and closed all of their stores in the USA. But I did discover that the Vaio is back on the market through Microsoft stores with a 1 TB SSD, 16 GB Ram etc and sells for around $3,300 for the top model but there is no optical drive. Comes with Windows 10, errrrr...that is a whole other story.

I will post again with a follow up the the HDD issue, but it may be a few days before I do. Golf gets in the way now and again.

Cheers and thanks very much for all the help.

Peter B.

 

[gopher22]

Today I ran CHKDSK /R again and it found nothing wrong with the HDD. After it had completed and the laptop had restarted, I ran HD Tune again and it showed the same defects as yesterday. So much for MS's CHKDSK and it has been around since DOS release 1, I'm sure.

 

[axe0]

Chkdsk has marked the bad sectors as bad what possibly makes that it can't find them anymore. Although I'm not 100% sure about the procedure of chkdsk.

 

[gopher22]

Hey axe0,

I bit the bullet and took the Vaio VGNZ apart and replaced the HDD with an identical one. Some time ago, I was able to create a one and only clone on the new drive but did not know if it was any good. It was the only successful clone or image I was able to create. Not knowing its viability, it was a chance I had to take. If it worked it meant I would not have to do a clean install...what a pain that would have been.

I restarted the laptop, and a message appeared saying it would need to do a system repair. That took about an hour to complete then it restarted normally. The only thing that did not work was my Outlook 2010, so I simply replaced the pst file with a copy from one of my desktops.

Yesterday I bit the bullet a second time and purchased a brand new VAIO, made in Japan and sold through MS stores. It is a VAIO Z Canvas Signature Edition 2 in 1 PC, 1TB SSD, 16GB Ram, 12.3-inch WQXGA+ 2560 x 1704 IPS touchscreen, Intel Core i7-4770HQ. I will donate my old Vaio to my wife, it is a lot smaller and lighter than the one she has now.

 

[axe0]

Glad to hear you sorted it out

 

[gopher22]

Thanks axe0, I have not had time to checkout every app etc, so if I find any more issues and cannot fix them I will post back. Thanks again for all your help.

PS. New VAIO will be here tomorrow, Friday.