Seemingly random BSODs, different reasons multiple occurences per day

[essenbe]

Ok, no problems, just let me know.

 

[tizbad2k]

Just an update to keep you posted.

No crashes for the last couple of days, but this could be a placebo effect situation.

Chkdsk has checked the file systems on all my partitions and made corrections where necessary (C: had some issues that were resolved). I have not had the time to check for bad sectors on all the drives, I did schedule it for C: and it may have done so though it was not apparent to me while it was checking. I still see errors in windows error reporting that appear quite often, but they dont lead to crashes. If you like I can post the msinfo32 file, or I could wait till the next crash happens.

 

[essenbe]

Why not wait for the next crash and just run the BSOD Posting Instructions again and upload it. Maybe your good luck will continue and that won't be necessary.

 

[tizbad2k]

Update:

Had two recent BSODs and also had WMC crash a few times. One of my drives complained about impending failure and then disappeared entirely from disk management.

 

[essenbe]

This is what the dumps say

0xfffff88003185800
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a00676cb60 rbx=0000000000000000 rcx=fffff8a00666cb60
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800129b9ab rsp=fffff88003185990 rbp=0000000000000000
 r8=fffffa800843b388  r9=0000000000000000 r10=fffff80002e4d000
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
[COLOR=red]Ntfs!NtfsFullDeleteLcb+0xbb[/COLOR]:

NTFS is the file system on the hard drives

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
[COLOR=red]BugCheck 1000007E[/COLOR], {ffffffffc0000005, fffff80002e882ca, fffff8800318c318, fffff8800318bb70}
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireFastMutex+1a )
Followup: MachineOwner

That code is almost always a Storage Problem. That coupled with the Hard Drive warning you received is most likely most, if not all, of your problem.

 

[tizbad2k]

Once again, thank you for your help.

As I had mentioned earlier, the HD in question has disappeared from disk management, and seatools cannot see it either. Im certain that it is still plugged in, because I was scanning it (which required a forced dismount), then I had to reboot and then it was no longer there (either partition in explorer, and disk was missing in disk management).

What should I do to try to prevent these types of issues in the future? I have a good UPS that the computer is hooked up to, so I dont think its power supply problems (unless the internal power supply is having issues). I have had two disk failures in the last 6 months and both have been seagate drives between 3-4 years old. They are primarily used for storage so its not like I read/write from them often.

Also is there anything I can do to try to revive the drive? The data is backed up, but it might be nice to see if its possible to fix/refresh the drive (using spinrite? with which I have no experience).

I guess I could unplug the drive and see if the BSODs return.

 

[essenbe]

There are no tools I am aware of that can access a drive unless it is seen by Windows. When the drive was being scanned, did you stop the scan? If so, that could be an issue. If the drive can't be seen, most likely it is dead, if you can get it to be seen you can recover data several ways.

http://www.sevenforums.com/tutorials/93347-copy-paste-windows-recovery-console.html
http://www.sevenforums.com/tutorials/287439-emergency-kit-save-your-files-dead-os.html