Solved repost - random BSOD, now pc died completely

[sandtrooper]

faulty HDD caused BSOD on dell xps 15z

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/jv1jns1bvdfnkve/AABSMwzgdjTEc-Ki33IEz3IYa

Thank you very much !

 

[HarriePateman]

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

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

Use !analyze -v to get detailed debugging information.

[COLOR="Blue"]BugCheck 7A, {fffff6fc40069660,[COLOR="Red"] ffffffffc000009d[/COLOR], 128778be0, fffff8800d2cc000}[/COLOR]

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

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="Blue"]KERNEL_DATA_INPAGE_ERROR (7a)[/COLOR]
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, 0[COLOR="blue"]xC000009D[/COLOR] 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:
------------------


[COLOR="blue"]ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED[/COLOR]

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.

 

[sandtrooper]

Hi HarriePateman

Thank you very much for response.

I can try dissasemble the notebook. I watched some tutorials how to do it. It does not seem difficult, however I cannot tell right now If I will be able to touch both ends of the HDD cable. I will try it and write what I have found.

 

[HarriePateman]

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

 

[sandtrooper]

Ok, I have found no problem regarding the connection of HDD. It sits there tightly. But because of known "magic" I just pulled it out, blowed some air to connectors and put it in. I have also put out RAM and changed the slots. (two physical pieces there). I have also formatted and installed new Windows again (using the cd included with the notebook)

 

[HarriePateman]

Okay and has the BSOD came around again?

 

[sandtrooper]

Well so far no BSOD, but if you look into my dropbox folder, there is screenshot of BSOD that appeared at the very first start. I was not able to boot to Windows, after the screen with Windows 7 logo animation with text "Windows loading" or something like that, this BSOD appeared. I have formated HDD installed new fresh copy of Win7 and it was ok for may be 2 weeks. Then those random BSOD started to appear, from which I have dmp files in my dropbox folder too. Sometimes Windows generated message after restart that it has recovered from serious error with these texts:

12:56 5. 7. 2014
Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7601.2.1.0.768.3
  Locale ID: 1051
Additional information about the problem:
  BCCode: 7a
  BCP1: FFFFF6FC40069660
  BCP2: FFFFFFFFC000009D
  BCP3: 0000000128778BE0
  BCP4: FFFFF8800D2CC000
  OS Version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1
Files that help describe the problem:
  C:\Windows\Minidump\070514-21450-01.dmp
  C:\Users\sandtrooper\AppData\Local\Temp\WER-111946-0.sysdata.xml
Read our privacy statement online:
  [URL="http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409"]Windows 7 Privacy Statement - Microsoft Windows[/URL]
If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt
 
Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7601.2.1.0.768.3
  Locale ID: 1051
Additional information about the problem:
  BCCode: f4
  BCP1: 0000000000000003
  BCP2: FFFFFA8007F3D620
  BCP3: FFFFFA8007F3D900
  BCP4: FFFFF80002F89270
  OS Version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1
Files that help describe the problem:
  C:\Windows\Minidump\070114-22666-01.dmp
  C:\Users\sandtrooper\AppData\Local\Temp\WER-177029-0.sysdata.xml
Read our privacy statement online:
  [URL="http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409"]Windows 7 Privacy Statement - Microsoft Windows[/URL]
If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

And then it came to the point with BSOD in my first post and I was unable to start pc at all. I fear it will come back, but I will have to wait and see what will happen. Do you think it is solved for now ?

 

[HarriePateman]

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]

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.

 

[HarriePateman]

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.

 

[sandtrooper]

I did two different tests. Here is a copy of log from the seatools. Hopefully it was only bad cable contacts. So you think I should be ok ? Anyway thank you very much for your time that you did look on my dmp files and tried to find the cause!! I really appreciate it !!

*plus I have done, before the complete crash, test with memtest software, where I have passed 16 times (I forgot to mention it)

--------------- SeaTools for Windows v1.2.0.10 ---------------
10. 7. 2014 19:16:51
Model: ST9750420AS
Serial Number: 6WS1AFCC
Firmware Revision: 0002DEM1
Long Generic - Started 10. 7. 2014 19:16:51
Long Generic - Pass 10. 7. 2014 21:40:42
Identify - Started 10. 7. 2014 21:57:43
Short DST - Started 10. 7. 2014 21:59:27
Short DST - Pass 10. 7. 2014 22:01:31

 

[HarriePateman]

yeah it probably was the Cables. Hey no worries!

Welcome to seven forums!

 

[sandtrooper]

Hi, i just wanted to add that I finally replaced HDD. Because BSOD kept comming, but you still helped me to find out that it is something with hdd so good job with your help and thank you ! problem solved !

 

[HarriePateman]

No worries mate, Glad i could help!

Stay around if you have an interest in computers