Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD witn new SSD intel 520 0xF4 and 0x7a


13 Mar 2014   #1

Windows 7 Ultimate x64
 
 
BSOD witn new SSD intel 520 0xF4 and 0x7a

Received as a present a brand new SSD Intel 520 180GB.
Tried to install Win 7 Ult x64 and Win 7 Pro x64 from different discs. Have the same errors, sometimes 0x000000F4, sometimes 0x0000007a. It happened during installation updates from MS or when I surfing via FireFox.
Contacted Intel support, they advised download different programs to fix the register. Today they ask me contact to microsoft, because it looks like problem with OS. 8=(
Before this I used Win XP x64, Win 7 Pro x64, and Win 7 Ult x64 on this PC on different HDDs without any BSOD.
Also during one day I used this SSD on Lenovo T520 without BSOD.
May I ask about help?
I will provide any information that you need.

What was done:
1. Read this forum 8=)
2. Update firmware of Motherboard and SSD.
3. Installed several times different version of Windows 7 from a different discs (different release).
4. Installed Intel Solid-State Drive toolbox. Full diagnostic scan - everything is OK.
5. Installed RegCure Pro, program fixed some system problems.
6. Contacted Intel support - they did not help at all 8=(
7. Memtest86+ - 5 passes, everything is OK.




Attached Files
File Type: zip debug-HP-Thu_03_13_2014_205403_52.zip (484.1 KB, 4 views)
My System SpecsSystem Spec
.

14 Mar 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

There is no crash dump in the uploaded zip.

But a stop 0x7A accompanied by a stop 0xF4 is nothing but storage failure.

If the SSD is within warranty, claim for a replacement.
My System SpecsSystem Spec
14 Mar 2014   #3

Windows 7 Ultimate x64
 
 

Thank you Arc for quick respond. It just happened again after I installed critical windows updates.
stop 0xF4
May I ask you check it?
Intel representative do not answer yet about replacement 8=(


Attached Files
File Type: zip debug-HP-Fri_03_14_2014_105933_99.zip (529.4 KB, 2 views)
My System SpecsSystem Spec
.


14 Mar 2014   #4
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800b18fb30, fffffa800b18fe10, fffff80002f967b0}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800b18fb30, Terminating object
Arg3: fffffa800b18fe10, Process image file name
Arg4: fffff80002f967b0, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa800b18fb30

IMAGE_NAME:  csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`05ff5e38 fffff800`0301fab2 : 00000000`000000f4 00000000`00000003 fffffa80`0b18fb30 fffffa80`0b18fe10 : nt!KeBugCheckEx
fffff880`05ff5e40 fffff800`02fcaabb : ffffffff`ffffffff fffffa80`0b19eb50 fffffa80`0b18fb30 fffffa80`0b18fb30 : nt!PspCatchCriticalBreak+0x92
fffff880`05ff5e80 fffff800`02f4a674 : ffffffff`ffffffff 00000000`00000001 fffffa80`0b18fb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`05ff5ed0 fffff800`02c90e53 : fffffa80`0b18fb30 fffff800`c0000006 fffffa80`0b19eb50 00000000`01f30e80 : nt!NtTerminateProcess+0xf4
fffff880`05ff5f50 fffff800`02c8d410 : fffff800`02cdc82f fffff880`05ff6a38 fffff880`05ff6790 fffff880`05ff6ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`05ff60e8 fffff800`02cdc82f : fffff880`05ff6a38 fffff880`05ff6790 fffff880`05ff6ae0 00000000`77495a38 : nt!KiServiceLinkage
fffff880`05ff60f0 fffff800`02c91242 : fffff880`05ff6a38 00000000`01f70000 fffff880`05ff6ae0 00000000`774a1664 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`05ff6900 fffff800`02c8fdba : 00000000`00000000 00000000`77495a3b fffffa80`0b18fb01 00000000`01f70000 : nt!KiExceptionDispatch+0xc2
fffff880`05ff6ae0 00000000`774c8f56 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`01f315a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774c8f56


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xf4_ioerr_image_csrss.exe

FAILURE_ID_HASH:  {183378f4-a174-8cab-8ad7-e5d860a58439}

Followup: MachineOwner
---------
Stop 0xF4's does not provide much info in the crash dumps, but that is a storage failure. If you get a stop 0x7A again, it will document the storage failure properly.

Can you post a screenshot of all your SSD and HDDs using CrystalDiskInfo - Software - Crystal Dew World
My System SpecsSystem Spec
14 Mar 2014   #5

Windows 7 Ultimate x64
 
 

Now I have only one attached SSD.
Please check the result of CrystalDickInfo for SSD and HDD.


Attached Thumbnails
BSOD witn new SSD intel 520 0xF4 and 0x7a-intel_crystaldiskinfo-5.6.2.png   BSOD witn new SSD intel 520 0xF4 and 0x7a-hdd_crystaldiskinfo-5.6.2.png  
My System SpecsSystem Spec
14 Mar 2014   #6

Windows 7 Ultimate x64
 
 

One more BSOD after I added HDD and restarted PC.


Attached Files
File Type: zip debug-HP-Fri_03_14_2014_122706_21.zip (552.4 KB, 2 views)
My System SpecsSystem Spec
15 Mar 2014   #7
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

The same stop 0xF4 continues here.
Code:
BugCheck F4, {3, fffffa800ae87b30, fffffa800ae87e10, fffff80002fce7b0}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

Followup: MachineOwner
---------
Change the SATA cables. Apply the discs to other unused ports on the motherboard. And test the HDD using Seatools.
SeaTools for DOS and Windows - How to Use

Let us know the results.
My System SpecsSystem Spec
15 Mar 2014   #8

Windows 7 Ultimate x64
 
 

Thank you Arc for help. My mistake, I forgot to show that I change cables...
More info:
Old HDD was on SATA1 and works without any questions.
SSD was with SATA data cable. I connected the SSD to SATA2 (SATA power cable from PC, SATA data cable from SSD set) - sometimes had BSOD. Changed all cables between HDD and SSD (I mean SSD on SATA1 and HDD on SATA2) - still sometimes had BSOD. Leave only SSD on SATA1 (HHD is not attached to power and data SATA) - still sometimes had BSOD. I have 2 more SATA ports - SATA3 with DVD and empty SATA4, and one SATA data cable between DVD and SATA3. What Have I do? I will test my HDD, but do not see any reason to do it, because I have BSOD without attached HDD.
My System SpecsSystem Spec
15 Mar 2014   #9
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

If the SSD causes BSODs irrespective of cables and ports, nothing else is there but it is, to blame for the BSODs.

I would say what I said in post #2. If the SSD is within warranty, claim for a replacement.

But, one last thing ... does it BSOD if the HDD only is attached?
My System SpecsSystem Spec
15 Mar 2014   #10

Windows 7 Ultimate x64
 
 

I think I had BSOD on this PC with this HDD once, it was some years ago.
I asked Intel representative about replacement, still do not have answer. Before they answered on all my emails once per day. Last suggestions was to contact Microsoft and HP representatives 8=)
My System SpecsSystem Spec
Reply

 BSOD witn new SSD intel 520 0xF4 and 0x7a




Thread Tools



Similar help and support threads for2: BSOD witn new SSD intel 520 0xF4 and 0x7a
Thread Forum
Solved Spontaneous BSODs, 0x7A and 0xF4 following 0xDEADDEAD BSOD Help and Support
Solved 0xF4/0x7A BSOD Issues while Gaming BSOD Help and Support
0xF4, 0x7B, 0x7A BSOD with new SSD, leaning towards motherboard? BSOD Help and Support
Random BSOD, error 0x7a BSOD Help and Support
BSOD 0x7A and more (inpagefile) BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:47 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33