Windows 8 Disk errors but disks test good?

NormAtHome · Aug 18, 2013

While I'm not getting BSOD's, I think that the problems I'm having may come under debugging so I'm posting here. Please excuse me if there's a more appropriate forum for this.

Three or four months ago I put together a new system with these specs:

Intel Core i7-3820 3.6Ghz Cpu
Asus Sabertooth X79 Socket 2011
Corsair CMT16GX3M4X2133C9 Dominator 16GB Memory Kit
OCZ ZX 850Watt PSU
Asus GTX 570 Video Card
2 - 2GB Western Digital Black Edition Hard Drives
Corsair H100i Closed Loop CPU Cooler
Pioneer DVD Burner
Patriot XT 16GB Flash Drive Installed for ReadyBoost

it had been running fine for several months although I noticed that despite being a performance machine Windows Explorer and Explorer type file operations seemed incredibly slow. If I switched directories the circle would spin for 5 to 10 seconds before producing a listing or if I deleted a file or directory again it would take far longer that the same operation on any of my Windows 7 machines. I have three systems using Asus socket 1366 motherboards, two of which run Windows 7 Ultimate and one is my server running Server 2008 R2 x64. I had seen some people complaining about slow Explorer / slow file operations in Windows 8 on Microsoft's site and in most cases turning off Windows Defender or adjusting what disks and directories are being indexed fixed the problem for them but didn't seem to make any difference in my case.

So I've been living with this for a couple months and just in the last few days I've seen a big increase in sluggishness and when I'm playing a high def movie from my data drive it would hangup for as long as a couple minutes before continuing.

So I looked in the system log and I'm seeing dozens if not hundreds of disk related errors such as:

The IO operation at logical block address 78ae7e00 for Disk 1 was retried
The IO operation at logical block address 45bb61d8 for Disk 1 was retried
The IO operation at logical block address 46092740 for Disk 1 was retried
A corruption was discovered in the file system structure on volume Boot. The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x9000000000009. The name of the file is "<unable to determine file name>"
A corruption was discovered in the file system structure on volume boot. The exact nature of the corruption is unknown. The file system structures need to be scanned online.

I've updated to the latest Intel chipset drivers 9.4.0.1022 and the latest Asus bios for the Sabertooth x79 version 1402.

In terms of disk testing, there's a problem with the latest Seatools bootable CD and I think it has something to do with either the EFI bios or it just doesn't recognize the hard drive controller on this motherboard since it boots but can't find any hard drives. I alternately installed Seatools for Windows and so far both hard drives have passed the SMART test and the short test and I'm running the long test on them right now and so far it looks good. The long test on disk 1 just finished and it passed.

One thing that I find odd is that I'm also trying to trouble shoot issues with another system in this thread here:
http://www.eightforums.com/bsod-crashes-debugging/29831-new-system-having-assorted-bsods.html#post268955
and I was also seeing disk errors such as this "The IO operation at logical block address 7d40 for Disk 1 was retried". I would find it hard to believe that both systems have bad hard drives, or that the hard drive controller on the motherboard of both is no good given that these systems are totally different one being AMD and using an AMD chipset and the other being Intel and using the x79 chipset. The only thing they really have in common is that they both use Western Digital Black Edition hard drives (the AMD uses the 1TB version and my Intel uses the 2TB version) and that they both run Windows 8 and they both have LogmeIn installed. (Although I fail to see how logmein could cause any disk errors)

There actually appears to be some evidence that there is a Windows 8 bug, several people have had the same issue which I found in this thread:
The IO operation at logical block address for Disk 0 was retried. - Microsoft Community
in one case someone said that by switching their SATA mode from ahci to ATA the problem went away. Another person mentioned that updating their chipset drivers fixed the problem. Yet another person who had this problem with an SSD said that updating their bios fixed it.

Even though there's no BSOD's, I've attached the diagnostics file and admin events list in the hope that it may provide some clue, I'd appreciate any input.

Thanks,

- Norm

usasma · Aug 21, 2013

I don't see that diagnostics file or the admin events list uploaded.

Does Disk1 contain the volume Boot? If not, then try disconnecting Disk1 to see if that improves things. You also may want to run CHKDSK /R /F on the disk that volume Boot is on.

Have you looked for misbehaving explorer.exe add-ons? Use ShellExView - Shell Extension Manager For Windows and disable all non-Microsoft extensions to see if that fixes the problem.
Have you seen if it's a DPC Latency issue (just a guess on my part): How to Diagnose and Fix High DPC Latency Issues with WPA (Windows Vista/7/8) - Sysnative Forums
Have you tried a Process Monitor capture to see what the system is doing when it slows down (these logs are very, very large!): Process Monitor
Another guess is to run DISM (aimed at the "scanned online" portion of the last error message):

Code:
Then please run the following DISM commands to see if there's any problems with the system (from an elevated (Run as administrator) Command Prompt). Press Enter after each one:

Code:

Dism /Online /Cleanup-Image /ScanHealth

Code:

Dism /Online /Cleanup-Image /CheckHealth

If the problem is fixable, you can use this command to repair it (from an elevated (Run as administrator) Command Prompt). Press Enter after typing it:

Code:

Dism /Online /Cleanup-Image /RestoreHealth

From this article: Repair a Windows Image

You can also run sfc.exe /scannow from an elevated (Run as administrator) Command Prompt to check for further corruption.

The actual error that you're seeing says that the operation was retried. With just 3 errors, I'd suspect that there was a subsequent Information event that stated it was tried/retried successfully (but haven't looked at any other systems for this myself). I'd imagine that it would take many, many of these errors in order to see a significant decrease in performance (a freeze) - so I wonder if this is a symptom of the problem, or if it's unrelated?

Booting from disk on a UEFI system is a bit trying at times.
If it's an OEM system that came originally w/Win8, then try disabling Secure Boot and enabling anything like "Legacy boot". I have no experience with loading Win8 on a system with UEFI other than OEM systems.
At work (on BIOS systems) we usually switch from AHCI to SATA/ATA/Legacy/etc in order to run Seatools on systems that don't see the hard drive (I prefer the in Windows test or a test in Windows PE/RE- as I wonder about damage to the boot stuff if I accidentally boot with AHCI not enabled - so I don't use it myself).

*************************************************
Looking at both topics, there's not even a similarity in the storage controllers.
That leaves (as you've stated) - Win8, W-D Black HDD's, and LogMeIn

To rule out LogMeIn - you've gotta uninstall it to see if that fixes things. Use something like TeamViewer temporarily (if needed).
To rule out the HDD's - you'll have to install Win8 on another (non-Black edition) hard drive - preferably a non-Western Digital drive and see if that stops the problems. If using 2 of them, then disconnect the other one while testing.
To rule out Win8 - you'll have to install another OS (?Win7?) and see if that stops the problems.

I lean towards blaming LogMeIn because it's the easiest to test and it has older drivers. These drivers work in the kernel space and can (fairly easily) interfere with other drivers/kernel components.

NormAtHome · Aug 21, 2013

I'm sure I attached those files, sorry I don't know what happened. I've attached them to this message.

usasma · Aug 22, 2013

Only 1 W-D drive (1 tB in size) is showing in the Components...Storage...Disks section of MSINFO32.

MSINFO32 shows lot's of Critical Live Kernel Events. 5 or so were Event ID 41's (Windows doesn't know why it shut down) occurring over the last month
MSINFO32 also shows a number of different BSOD codes.
The memory dumps show 4 different codes out of 4 memory dumps.
These are symptomatic of low-level issues, with hardware problems being the most likely

Admin Event Viewer logs:
-There are @BrandName errors on this system also - are you sure this is the correct Event Viewer Admin log?
-Lot's of Quickbook errors. Are you running Quickbooks from a network share?
-Lot's and lot's of Printer installation errors. Please remove the printer from the system (and uninstall it's drivers/software) to see if that helps.
-Many Hyper-V errors. I'm not well-versed at this. I'd suggest turning off the Hyper-V feature in Windows to see if that helps. Hyper-V drivers are also present in the memory dumps - it may be possible to get some further info by running Driver Verifier (verifier.exe) - please use the standard settings and verify ALL drivers (it may slow the system down while running).

Out of 4 memory dumps there were 4 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

You can get a head start on the hardware diagnostics if you'd like - they are located here: Hardware Diagnostics

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

lmimirr.sys Tue Apr 10 18:32:45 2007 (461C108D)
RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
http://www.carrona.org/drivers/driver.php?id=lmimirr.sys

lmimirr2.dll Tue Apr 10 18:32:46 2007 (461C108E)
LogMeIn Remote Access driver
http://www.carrona.org/drivers/driver.php?id=lmimirr2.dll

LMIRfsDriver.sys Mon Jul 14 12:26:56 2008 (487B7E50)
RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
http://www.carrona.org/drivers/driver.php?id=LMIRfsDriver.sys

AsUpIO.sys Mon Aug 2 22:47:59 2010 (4C57835F)
ASUS hardware monitoring software related
http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys

ASUSFILTER.sys Tue Sep 20 11:46:33 2011 (4E78B559)
ASUS USB Hub filter driver
http://www.carrona.org/drivers/driver.php?id=ASUSFILTER.sys

AiChargerPlus.sys Wed Apr 18 21:17:35 2012 (4F8F67AF)
Asus Charger Driver [br] Likely BSOD cause - haven't seen recently (15Jan2013)
http://www.carrona.org/drivers/driver.php?id=AiChargerPlus.sys

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Thu Aug  1 02:06:54.021 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\080113-30498-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16628.amd64fre.win8_gdr.130531-1504
System Uptime:[B]0 days 9:40:07.707[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )[/B]
BugCheck [B]1E, {ffffffffc0000005, fffff8038be66df5, 0, ffffffffffffffff}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8038be66df5, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]0x1E_c0000005_R_nt!ExpInterlockedPopEntrySListFault16[/B]
  BIOS Version                  1708
  BIOS Release Date             04/10/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 30 23:47:00.343 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\073013-29811-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16628.amd64fre.win8_gdr.130531-1504
System Uptime:[B]0 days 0:01:24.039[/B]
Probably caused by :[B]Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B]
BugCheck [B]19, {3, fffff8a0029f0af0, 0, fffff8a0029f0af0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000019]BAD_POOL_HEADER (19)[/url]
Arguments: 
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff8a0029f0af0, the pool entry being checked.
Arg3: 0000000000000000, the read back flink freelist value (should be the same as 2).
Arg4: fffff8a0029f0af0, the read back blink freelist value (should be the same as 2).
BUGCHECK_STR:  0x19_3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 30 23:44:38.006 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\073013-24414-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16628.amd64fre.win8_gdr.130531-1504
System Uptime:[B]0 days 7:19:20.701[/B]
Probably caused by :[B]Pool_Corruption ( nt!ExDeferredFreePool+4da )[/B]
BugCheck [B]139, {3, fffff88005b10750, fffff88005b106a8, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000139]KERNEL_SECURITY_CHECK_FAILURE (139)[/url]
Arguments: 
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff88005b10750, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff88005b106a8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x139_3_nt!ExDeferredFreePool[/B]
  BIOS Version                  1708
  BIOS Release Date             04/10/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 26 08:01:21.998 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\072613-32058-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16628.amd64fre.win8_gdr.130531-1504
System Uptime:[B]0 days 15:40:41.698[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiSystemServiceExit+24b )[/B]
BugCheck [B]1, {7fbeb8d118a, 0, ffff0000, fffff8800b82fb80}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000001]APC_INDEX_MISMATCH (1)[/url]
Arguments: 
Arg1: 000007fbeb8d118a, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 00000000ffff0000, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff8800b82fb80, Call type (0 - system call, 1 - worker routine)
BUGCHECK_STR:  0x1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID: [B]0x1_SysCallNum_11cd_nt!KiSystemServiceExit[/B]
  BIOS Version                  1708
  BIOS Release Date             04/10/2013
  Manufacturer                  To be filled by O.E.M.
  Product Name                  To be filled by O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Thu Aug  1 02:06:54.021 2013 (UTC - 4:00)**************************
[COLOR=RED][B]lmimirr.sys          Tue Apr 10 18:32:45 2007 (461C108D)[/B][/COLOR]
[COLOR=RED][B]LMIRfsDriver.sys     Mon Jul 14 12:26:56 2008 (487B7E50)[/B][/COLOR]
[COLOR=RED][B]AsUpIO.sys           Mon Aug  2 22:47:59 2010 (4C57835F)[/B][/COLOR]
[COLOR=RED][B]ASUSFILTER.sys       Tue Sep 20 11:46:33 2011 (4E78B559)[/B][/COLOR]
asahci64.sys         Thu Jan  5 00:08:19 2012 (4F053043)
epfwwfpr.sys         Fri Mar 23 12:08:14 2012 (4F6C9FEE)
ehdrv.sys            Fri Mar 23 12:13:29 2012 (4F6CA129)
[COLOR=RED][B]AiChargerPlus.sys    Wed Apr 18 21:17:35 2012 (4F8F67AF)[/B][/COLOR]
GEARAspiWDM.sys      Thu May  3 15:56:17 2012 (4FA2E2E1)
ndisrd.sys           Wed May 30 23:03:33 2012 (4FC6DF85)
nvhda64v.sys         Tue Jul  3 11:25:04 2012 (4FF30ED0)
eamonm.sys           Wed Jul  4 04:07:45 2012 (4FF3F9D1)
lunparser.sys        Wed Jul 25 22:28:26 2012 (5010AB4A)
passthruparser.sys   Wed Jul 25 22:28:35 2012 (5010AB53)
vhdparser.sys        Wed Jul 25 22:28:37 2012 (5010AB55)
Rt630x64.sys         Mon Jul 30 12:03:12 2012 (5016B040)
RTKVHD64.sys         Tue Aug  7 06:49:39 2012 (5020F2C3)
asmtxhci.sys         Mon Aug 20 08:28:15 2012 (50322D5F)
asmthub3.sys         Mon Aug 20 08:28:29 2012 (50322D6D)
AsIO.sys             Wed Aug 22 05:54:47 2012 (5034AC67)
usbfilter.sys        Tue Aug 28 21:27:12 2012 (503D6FF0)
amd_sata.sys         Mon Sep 17 04:40:39 2012 (5056E207)
amd_xata.sys         Mon Sep 17 04:40:43 2012 (5056E20B)
RaInfo.sys           Fri Jan 11 07:19:28 2013 (50F00350)
nvlddmkm.sys         Fri Jan 18 08:22:15 2013 (50F94C87)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 26 08:01:21.998 2013 (UTC - 4:00)**************************
[COLOR=RED][B]lmimirr2.dll         Tue Apr 10 18:32:46 2007 (461C108E)[/B][/COLOR]
[/font]

NormAtHome · Aug 22, 2013

I owe you a sincere apology, I had two sets of these files on my main computer one of which I'd ftp'ed from that AMD system and the other from my new Intel system and I attached the files from the AMD system (again) rather than the files from the Intel.

That was totally my fault.

Norm

usasma · Aug 23, 2013

Not a problem, I do this occasionally myself. It gets sorta embarrassing when I tell someone to remove something that's not even on their system!

Please redo this (the evtx file is much easier to read than the .xml):

Please do the following:
- open Event Viewer (eventvwr.msc)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

J: drive only has about 7% free space. Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance. Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty)

WER section of MSINFO32 shows 4 STOP errors (0x117 and 0x141's) - all involving video drivers - on 6 and 10 Aug 2013.
I'd look at replacing the video drivers and stress testing the video card: Video TDR Timeout - 0x116 + 0x117 - Sysnative Forums

Most errors in the WER section point to crashes in DVDFab (looks to be a couple of hundred errors). I'd remove it until the system has been stabilized. Then, if still needed, I'd install the latest, Win8 compatible version. I've seen delays/lags attributable to these sort of programs - it's even happened to us at work on our work computer.

CorsairLink2 is known to cause problems on some Windows systems. Please uninstall it until the system has been stabilized, then feel free to reinstall the latest, Win8 compatible version.

The suggestions in Post #2 are still valid for your system: http://www.eightforums.com/bsod-cra...sk-errors-but-disks-test-good.html#post269961

Windows 8 Disk errors but disks test good?

NormAtHome

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

NormAtHome

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One

NormAtHome

New Member

My Computer

System One

usasma

Mr. Cranky Pants

My Computer

System One