BSOD Stop 0x000000F4 Windows 7 SP1 Professional x64 Sony SVE14121CLB

[mccra]

Hi Guys,

I'm receiving continuously: "A problem has been detected and Windows has been shut down to prevent damage to your computer. A process or thread crucial to system operation has unexpectedly exited or been terminated.

Technical Information:
STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA800868EB30, 0xFFFFFA80086EE10, 0xFFFFF80002FC47B0)

Computer details

Notebook: Sony SVE14121CLB
Windows 7 Professional 64 bits with SP1
HDD: 250 GB

Technical Background:

1 - OS original in this notebook was Windows 8 where the message error happened a lot times
2 - No hardware installed
3 - We did downgrade from Windows 8 to Windows 7 and the message errors happens again ...
4 - I ran a lot Antivirus / AntiSpyware tools and not infected
5 - I ran with often MEMTEST and no errors
6 - All drivers are installed correctly

I'm attaching for you DUMP files from today 4/20/2014:

First Dump URL:
**************/download/milky82h197bh19/042014-14898-01.dmp

Second DUMP URL:
**************/download/z1uv8a2fg69fdui/042014-15319-01.dmp

Third DUMP URL:
**************/download/e1ir7sxvsr9ta16/042014-17955-01.dmp

MEMORY.DUMP URL:
**************/download/25ewnv1sluq4s2k/MEMORY.rar

Really appreciate your help and guidance with the next steps. If I'm missing some file, log or whatever that you need please feel free to request and I'll look and upload asap.

Thanks a lot,
Regards!

 

[mccra]

replace ************** by mediafire . com

 

[koolkat77]

Please follow the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[mccra]

Attached .ZIP

Thanks,

 

[mccra]

Now information attached following the instructions,

Thanks a lot,
Regards

 

[koolkat77]

Bugcheck F4 and 7A are Storage (Hard Drive) related.

Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Mon Apr 21 06:35:37.734 2014 (UTC + 6:00)
System Uptime: 0 days 0:05:25.889
BugCheck F4, {3, fffffa800868eb30, fffffa800868ee10, fffff80002fc47b0}
Probably caused by : wininit.exe
BUGCHECK_STR:  0xF4_IOERR
PROCESS_NAME:  wininit.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Mon Apr 21 02:59:01.352 2014 (UTC + 6:00)
System Uptime: 0 days 0:02:35.507
BugCheck F4, {3, fffffa8008782b30, fffffa8008782e10, fffff80002fc67b0}
Probably caused by : csrss.exe
BUGCHECK_STR:  0xF4_IOERR
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sun Apr 20 09:41:01.778 2014 (UTC + 6:00)
System Uptime: 0 days 1:01:09.933
BugCheck F4, {3, fffffa8008195b30, fffffa8008195e10, fffff80002fd27b0}
Probably caused by : csrss.exe
BUGCHECK_STR:  0xF4_c0000005
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sun Apr 20 08:22:31.051 2014 (UTC + 6:00)
System Uptime: 0 days 0:03:51.206
BugCheck F4, {3, fffffa8007f5fb30, fffffa8007f5fe10, fffff80002fce7b0}
Probably caused by : wininit.exe
BUGCHECK_STR:  0xF4_c0000005
PROCESS_NAME:  wininit.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sun Apr 20 08:00:21.569 2014 (UTC + 6:00)
System Uptime: 0 days 0:03:07.724
BugCheck F4, {3, fffffa8008164b30, fffffa8008164e10, fffff80002f7a7b0}
Probably caused by : wininit.exe
BUGCHECK_STR:  0xF4_c0000005
PROCESS_NAME:  wininit.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sun Apr 20 04:47:30.271 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:26.426
BugCheck 1000007E, {ffffffffc0000006, fffff80002c76795, fffff8800352ad18, fffff8800352a570}
Probably caused by : hardware_disk
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sat Apr 12 05:05:28.356 2014 (UTC + 6:00)
System Uptime: 1 days 14:43:13.242
BugCheck 7A, {fffff6fc4001d3f8, ffffffffc000000e, d421be0, fffff88003a7f000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36c1a )
BUGCHECK_STR:  0x7a_c000000e
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Post a screenshot of your Hard Drive(s) using Crystal Disk Info software:

• CrystalDiskInfo - Software - Crystal Dew World

Run a Hard Drive test:

• http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Scan with Kaspersky TDSSKiller:

• Anti-rootkit utility TDSSKiller

ESET online scanner:

• Free Online Virus Scanner | ESET

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Reduce items at start-up:

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot:

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Post back results.

 

[mccra]

Attaching HDD Screen using CrystalDiskInfo

SeaTools for Windows: Hitachi HTS543232A7A384

- ALL TEST PASS

 

[mccra]

I will run Disk Check the next time, because my hard drive is in use, so now I'm download TDSSKiller Kaspersky, I'll post the results once completed

 

[mccra]

TDSSKiller Kaspersky: No Threats found

 

[mccra]

Eset Scan = No Threads found

 

[mccra]

Disk Check done, no errors, completed successfully, CCLEAR applied.

I'll keep posted if new BSOD happens.

Thanks,

 

[mccra]

Unfortunately today I got other BSOD with the same code of error (F4). Once I started I had the following popup

"Windows has recovered from an unexpected shutdown"

Problem Details:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 13322

Additional information about the problem:
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA800852DB30
BCP3: FFFFFA800852DE10
BCP4: FFFFF80002F847B0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\042614-15600-01.dmp
C:\Users\Vale\AppData\Local\Temp\WER-37440-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I'm attaching dmp and WER-37440-0.sysdata.xml files

Thanks,

 

[koolkat77]

Follow....

The caution indication can be converted to good using CrystalDiscInfo. Click on the caution Button, you will get another window ....

In the resulting window, there are three sliders in the left. Drag them to the ultimate left, and notice the values at the right side are converting to zeros.

Now click the apply button, and notice that the caution is gone.