Solved BSOD 0x0000007a possibly related to HDD issue?

[dalmacietis]

Hello,

so recently I've been getting a BSOD every other day (3 total). It is usually during some heavy activity like playing a game. I also recently got a new HDD that seems to disconnect sometimes (suddenly doesn't show up in Windows Explorer or Disk Management).

So what could be the cause of the BSODs? And is it related to the HDD issue?

 

[ICIT2LOL]

Hello dalmacietis now the dump files have five blue screens listed and the last has an error that is supposedly caused by a Windows update - difficult to say what to do about it (other than try a system restore). But there is a message to say there is a hard drive problem too.

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

[COLOR="red"]DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR]

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80002ced0f2 to fffff80002c77400

STACK_TEXT:  
fffff880`031a11c8 fffff800`02ced0f2 : 00000000`0000007a fffff6fc`40007f70 ffffffff`c0000185 00000000`35b48860 : nt+0x6f400
fffff880`031a11d0 00000000`0000007a : fffff6fc`40007f70 ffffffff`c0000185 00000000`35b48860 fffff880`00fee93c : nt+0xe50f2
fffff880`031a11d8 fffff6fc`40007f70 : ffffffff`c0000185 00000000`35b48860 fffff880`00fee93c ffffffff`ffffffff : 0x7a
fffff880`031a11e0 ffffffff`c0000185 : 00000000`35b48860 fffff880`00fee93c ffffffff`ffffffff 00000000`c0000185 : 0xfffff6fc`40007f70
fffff880`031a11e8 00000000`35b48860 : fffff880`00fee93c ffffffff`ffffffff 00000000`c0000185 fffffa80`00000000 : 0xffffffff`c0000185
fffff880`031a11f0 fffff880`00fee93c : ffffffff`ffffffff 00000000`c0000185 fffffa80`00000000 fffff880`00fee93c : 0x35b48860
fffff880`031a11f8 ffffffff`ffffffff : 00000000`c0000185 fffffa80`00000000 fffff880`00fee93c fffff800`02c9f9c9 : ataport+0x1e93c
fffff880`031a1200 00000000`c0000185 : fffffa80`00000000 fffff880`00fee93c fffff800`02c9f9c9 fffffa80`09cec108 : 0xffffffff`ffffffff
fffff880`031a1208 fffffa80`00000000 : fffff880`00fee93c fffff800`02c9f9c9 fffffa80`09cec108 fffffa80`09cec100 : 0xc0000185
fffff880`031a1210 fffff880`00fee93c : fffff800`02c9f9c9 fffffa80`09cec108 fffffa80`09cec100 fffffa80`06762040 : 0xfffffa80`00000000
fffff880`031a1218 fffff800`02c9f9c9 : fffffa80`09cec108 fffffa80`09cec100 fffffa80`06762040 fffffa80`00a11d80 : ataport+0x1e93c
fffff880`031a1220 fffffa80`09cec108 : fffffa80`09cec100 fffffa80`06762040 fffffa80`00a11d80 00000000`00002000 : nt+0x979c9
fffff880`031a1228 fffffa80`09cec100 : fffffa80`06762040 fffffa80`00a11d80 00000000`00002000 fffff6fc`40007f70 : 0xfffffa80`09cec108
fffff880`031a1230 fffffa80`06762040 : fffffa80`00a11d80 00000000`00002000 fffff6fc`40007f70 ffffffff`ffffffff : 0xfffffa80`09cec100
fffff880`031a1238 fffffa80`00a11d80 : 00000000`00002000 fffff6fc`40007f70 ffffffff`ffffffff 00000000`00000000 : 0xfffffa80`06762040
fffff880`031a1240 00000000`00002000 : fffff6fc`40007f70 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : 0xfffffa80`00a11d80
fffff880`031a1248 fffff6fc`40007f70 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 fffffa80`07a71070 : 0x2000
fffff880`031a1250 ffffffff`ffffffff : 00000000`00000000 00000000`00000000 fffffa80`07a71070 fffff800`02eb7540 : 0xfffff6fc`40007f70
fffff880`031a1258 00000000`00000000 : 00000000`00000000 fffffa80`07a71070 fffff800`02eb7540 fffffa80`00a11d80 : 0xffffffff`ffffffff


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport+1e93c
fffff880`00fee93c 4053            push    rbx

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  ataport+1e93c

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  [COLOR="Red"]ataport.SYS[/COLOR]

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:wrong_symbols

FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner

So I might suggest you check the cables to the drive make sure they are connected firmly at the board and drive ends before we launch into drive tests etc

 

[dalmacietis]

Thanks for the reply!

Yes checking the cables was the first thing I did when I saw the HDD disconnect problem (maybe a week or two ago). I haven't seen it disconnect since, but it had happened infrequently anyways.

I also had another bluescreen yesterday (logs attached).

I could try a system restore, but which restore point do I choose? I have restore points due to critical Windows updates at 27/02/2017 and 20/02/2017 and some other restore points, too.

 

[torchwood]

Well the last time updates ran properly was in October, so the restore point would have to be prior to then.

Possible that you have a Virus, or had, thats not been properly cleared, suggest you run
Eset on line scan
(dissable MSE, updating BUT not started?)



Roy

 

[ICIT2LOL]

Ok mate there is a dump linked to an update and as those are hard to track at least for me I suggest you go with what Roy ha suggested and there are other scans that can be used if the Eset doesn't find anything.

 

[dalmacietis]

I tried to do the eset scan, but after about 2 hours it was interrupted by a bluescreen. After that bluescreens were getting more frequent (every 2 hours or so) and now the hard drive I suspected as faulty has an automatic chkdsk at startup (which it fails after 1% of verifying files, I didn't manage to read the whole text), and if I try to skip the chkdsk, the drive can't be found in disk manager.

So I suspect that drive really was the problem. I'll let you know if I get any more bluescreens and do the eset scan just in case.

 

[ICIT2LOL]

Ok mate now sounds like the hard drive is probably heading south so I would be very inclined to get the data backed up now and if it fails completely then there are ways of retrieving data (not all) from it.

Maybe it is worth a test on it anyway while the machine is still running
SeaTools for DOS and Windows - How to Use

Now you can do this via a bootable stick too see this article
How To Create Bootable USB Disk For Seagate SeaTools For DOS | Megaleecher.Net