repost - random BSOD, now pc died completely

Dear forum

My pc died :/ Now I only see this message for split of a second. So I have recorded the booting on mobile camera and made screenshot from that movie. This is what I see. Any suggestions please ? I dont need to save any HDD files, the thing is I dont know what is causing the BSOD and why it now crashed absolutely :/

If you need more informations look into my dropbox. There are some DMP files generated while pc was running plus zipped file folder from SF diagnostic tool.

https://www.dropbox.com/sh/jv1jns1bv...Ec-Ki33IEz3IYa

Thank you very much !

Hello and Welcome to sevenForums.
I have had a look at your Files, and i have found what i believe to be the issue.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc40069660, ffffffffc000009d, 128778be0, fffff8800d2cc000}

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

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

2: 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: fffff6fc40069660, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: 0000000128778be0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8800d2cc000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

LAST_CONTROL_TRANSFER:  from fffff80002d07752 to fffff80002c94bc0

STACK_TEXT:  
fffff880`0351d708 fffff800`02d07752 : 00000000`0000007a fffff6fc`40069660 ffffffff`c000009d 00000001`28778be0 : nt!KeBugCheckEx
fffff880`0351d710 fffff800`02cbb91f : fffffa80`0ab3bbc0 fffff880`0351d880 fffff800`02ecf540 fffffa80`0ab3bbc0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`0351d7f0 fffff800`02ca21b9 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff 00000000`00000001 : nt!MiIssueHardFault+0x28b
fffff880`0351d8c0 fffff800`02cc86e0 : 00000000`00000001 fffff880`0d2cc000 fffffa80`043a1b00 fffff6fc`40069638 : nt!MmAccessFault+0x1399
fffff880`0351da20 fffff800`02cc88d0 : fffffa80`043a1b50 00000000`00000001 fffffa80`00000000 fffff800`02cc570b : nt!MiInPageSingleKernelStack+0x134
fffff880`0351db30 fffff800`02cc885f : 00000000`00000000 00000000`00000001 fffffa80`03c8d5f0 00000000`00000080 : nt!MmInPageKernelStack+0x40
fffff880`0351db90 fffff800`02cc85a4 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03c8d500 : nt!KiInSwapKernelStacks+0x1f
fffff880`0351dbc0 fffff800`02f3073a : f7edffff`5ffffcff cbffbfee`b5f7f27e bf0cf7e7`feffffff ff5fffff`fffff3fe : nt!KeSwapProcessOrStack+0x84
fffff880`0351dc00 fffff800`02c858e6 : fffff880`009e5180 fffffa80`03cb2040 fffff880`009effc0 fffffeff`ff3ffbff : nt!PspSystemThreadStartup+0x5a
fffff880`0351dc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+36c1a
fffff800`02d07752 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:  531590fb

IMAGE_VERSION:  6.1.7601.18409

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

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

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7a_c000009d_nt!_??_::fnodobfm::_string_+36c1a

FAILURE_ID_HASH:  {5d587c54-4ed0-03fb-8499-e454d2876eb8}

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

So basically if we look at parameters of the Bugcheck, we can see that indicated in Parameter 2, we have the error code ffffffffc000009d, this error code means: 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.

Please can you check all the connections in your computer, especially the HDD and Sata leads.
If this fails to resolve your issue, we can do further test on your PC.

Only disassemble it if you feel comfortable as doing this will void your warranty.

Okay and has the BSOD came around again?

Okay so the Clean install should have sorted it out.

But to make sure its not an error with the actual harddrive please run:

SeaTools for Windows | Seagate

sandtrooper said:

ok, I have downloaded seatools software but I am unsure which test to run. I started long generic test. It should end in about 3 hours. I will post the result.

Brilliant keep us posted.