Random BSOD error, usually OxOOOOOOOE

menace9 · 17 Sep 2013

Can anyone help me with this, I get the BSOD every so often and from nothing in particular, sorry i cant give the exact error code but it is usually ending in OE or 7E
I get locked out most times, but after I run window 7 repair from disk it will work after.
Anyway I have attached the file from SF_diagnosis

Arc · 17 Sep 2013

It is HDD related issue.

Code:

ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

It is obtained from event logs ....

Event[14152]:
Log Name: System
Source: atapi
Date: 2013-09-16T23:02:28.350
Event ID: 11
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: dennis-PC
Description:
The driver detected a controller error on \Device\Ide\IdePort2.

In that case, we should try the HDD in another port at first. Also, try Western Digital Data Lifeguard to test the HDD.

Also, Post a screenshot of your HDD using CrystalDisc Info.
______________________________________________________________________
BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc500902d8, ffffffffc0000185, 2e196880, fffff8a01205b000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36c1a )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc500902d8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 000000002e196880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a01205b000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002949742 to fffff800028d6b80

STACK_TEXT:  
fffff880`02fcdf58 fffff800`02949742 : 00000000`0000007a fffff6fc`500902d8 ffffffff`c0000185 00000000`2e196880 : nt!KeBugCheckEx
fffff880`02fcdf60 fffff800`028fd91f : fffffa80`01acb840 fffff880`02fce0d0 fffff800`02b11600 fffffa80`01acb840 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`02fce040 fffff800`028e41b9 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`02fce110 fffff800`02940426 : 00000000`00000000 fffff8a0`1205b000 fa8003a6`16f00400 00000000`00000000 : nt!MmAccessFault+0x1399
fffff880`02fce270 fffff800`02b78e8b : fffffa80`03a61670 00000000`00000000 00000000`0008c081 fffffa80`03a61670 : nt! ?? ::FNODOBFM::`string'+0x2a8e0
fffff880`02fce340 fffff800`028a410b : fffffa80`03a616f0 00000000`00000000 fffffa80`03a616f0 fffffa80`03a616f0 : nt!MiSegmentDelete+0x7b
fffff880`02fce380 fffff800`028a4832 : 00000000`00000000 00000000`00000011 00000000`00000000 fffff880`0125ac00 : nt!MmPurgeSection+0x71b
fffff880`02fce470 fffff880`012c67ef : fffffa80`048c5a40 00000000`00000000 00000000`00000000 fffffa80`00000000 : nt!CcPurgeCacheSection+0x172
fffff880`02fce4e0 fffff880`013c65d2 : fffffa80`022c64d0 fffffa80`024eb180 00000000`00000000 fffff880`013c6501 : Ntfs!NtfsFlushVolume+0x5cf
fffff880`02fce610 fffff880`0131cad8 : fffffa80`01efa488 fffffa80`024eb180 fffffa80`024eb180 fffffa80`024eb030 : Ntfs!NtfsPerformSurpriseRemoval+0x32
fffff880`02fce660 fffff880`0131d7ec : fffffa80`022c64d0 fffff880`02fce7e8 fffff880`02fce7f0 00000000`00000001 : Ntfs!NtfsCommonPnp+0x7eb
fffff880`02fce740 fffff880`010c5bcf : fffffa80`01efa4d0 00000000`00000000 fffff880`02fce801 fffffa80`022c64d0 : Ntfs!NtfsFsdPnp+0x1f0
fffff880`02fce7e0 fffff880`010c46df : fffffa80`0352da40 00000000`c00000bb fffffa80`0352da00 fffffa80`01efa010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`02fce870 fffff800`02b449e1 : fffffa80`0352da40 fffff880`02fce988 00000000`c00000bb fffffa80`01efa010 : fltmgr!FltpDispatch+0xcf
fffff880`02fce8d0 fffff800`02cc36c1 : fffffa80`01a68900 fffffa80`024eb030 fffffa80`01b253f0 fffffa80`01a68900 : nt!IopSynchronousCall+0xe1
fffff880`02fce940 fffff800`02cbe098 : fffff880`02fceb00 fffffa80`01a68900 00000000`0000030a 00000000`00000308 : nt!IopRemoveDevice+0x101
fffff880`02fcea00 fffff800`02cc3207 : fffffa80`01b253f0 00000000`00000000 00000000`00000003 00000000`00000373 : nt!PnpSurpriseRemoveLockedDeviceNode+0x128
fffff880`02fcea40 fffff800`02cc3320 : 00000000`00000000 fffff8a0`0a945d00 fffff8a0`07ff3aa0 fffff880`02fceb98 : nt!PnpDeleteLockedDeviceNode+0x37
fffff880`02fcea70 fffff800`02d53cbf : 00000000`00000002 00000000`00000000 fffffa80`01b253f0 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`02fceae0 fffff800`02d5487c : fffff880`02fcecb8 00000000`00000000 fffff8a0`033e5c00 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0x6cf
fffff880`02fcec20 fffff800`02c3da1e : 00000000`00000000 fffffa80`01a31ad0 fffff8a0`0a945d10 00000000`00000001 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`02fcec50 fffff800`028e0261 : fffff800`02b43868 fffff8a0`0a945d10 fffff800`02a7c2d8 fffffa80`018a2040 : nt! ?? ::NNGAKEGL::`string'+0x551ab
fffff880`02fcecb0 fffff800`02b74bae : 440c6c03`c8200280 fffffa80`018a2040 00000000`00000080 fffffa80`0186d380 : nt!ExpWorkerThread+0x111
fffff880`02fced40 fffff800`028c78c6 : fffff880`009e8180 fffffa80`018a2040 fffff880`009f2f40 0360c208`0080009a : nt!PspSystemThreadStartup+0x5a
fffff880`02fced80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+36c1a
fffff800`02949742 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+36c1a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb06cd

FAILURE_BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+36c1a

BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+36c1a

Followup: MachineOwner
---------

menace9 · 18 Sep 2013

Hey thanks Arc,
I kind of thought it was my HDD, but wern't really too sure...anyway here the Data Lifeguard reports first that it fixed the errors, then the second time it didnt and the third it did!
Attached is the Crystal disc info. (not shizuku edition).

ICIT2LOL · 18 Sep 2013

Hmm menace mate that is a fairly old drive what about swapping it out -clone it to a new one - SSD?

I notice you have three AV's listed too any reason? The Housecall is ok but I would be looking at disabling at least either Avast or Emisoft..

Arc · 18 Sep 2013

ICit2lol said:

Hmm menace mate that is a fairly old drive what about swapping it out -clone it to a new one - SSD?

I notice you have three AV's listed too any reason? The Housecall is ok but I would be looking at disabling at least either Avast or Emisoft..

I reassamble both the statements, in a different way :)

Replace your HDD. Do a clean reinstall on the new one following Clean Reinstall - Factory OEM Windows 7. Dont use any other antivirus than that is suggested in post 13 thereto.

menace9 · 18 Sep 2013

Ha,ha ICit2lol, yep I have a pretty old drive, I am not really a gamer or heavy user as such , neither am i the sort of person to upgrade because those so called experts say..if it still meets my needs, then I am ok!
I got three AV's on because I couldnt decide what one to get rid of, so kept them all cos there was no visible signs of drain on my resources.

Arc, no problem, I was avoiding changing my HDD cos it was quite reliable til a few weeks ago, but if I have to there's no problem...I have an issue with MSE, I noticed it was always doing something and I was a bit suspicious, heard lots of other people had similar stories so got rid of it.paranoid, maybe., but microsoft have a record for stuff like that.

Anyway...thanks guys...

Arc · 18 Sep 2013

About MSE, I can say one thing. Here on SevenForums, we have a large number of top tech enthuciasts who use MSE over a very long time without any issue, and they (including me) recommend it as we have a support of our experience to believe that it does do the job perfectly, and never puts any kind of pressure on the system, which all the rest does.

Still, as an user you can choose your stuff at your own. All are good (except McAfee and AVG) .... but never use more than one of those programs. It will make the system totally unprotected in turn.

menace9 · 02 Oct 2013

Hi guys
Quick update that i wanted to share with you and probably to help others out if they had the same problems as me!

Ok, well after I read this I decided to just let my drive die, before I bought a replacement, after all I was just surfing the web, watching the odd videos and a bit of downloading...nothing too HDD heavy.
Friday it finally went and i couldnt get past the BSOD with my usual tricks, so I gave up and started looking for a new drive, but I noticed from my Windows 98 days I had a program called HDD regenerator and I found a recent copy for Windows 7, so I spent the day doing a few scans and repairing bad sectors, then the next day a full regeneration.
When I booted all was great and running smooth and all it took was a weekend and HDD Regenerator, saved me a few quid and a lot of time....Here is my report from Crystal disk

Thanks to everyone again for helping

Arc · 02 Oct 2013

Good news.

Let us know how it is going, after say an week.

menace9 · 17 Oct 2013

Update:
Generally all is ok, but on occasion can seem a bit slow...I know Hdd reg is just a temporary fix and am just grateful for the extended disc life.

I ran an old version of Data lifeguard (found on Ultimate Boot Disc) when it became just a bit too sluggish, as I noticed the newer one I downloaded seemed to crash my windows after Hdd Regenerator