Windows 7 [BSOD] Happens Randomly, Could it Be Samsung HD204UI HDDs?

[dan7u]

I suspect it may be the 2/3rd HDDs. They are Samsung 204UI rain in RAID 0 and seem be slow to detect after a crash. See dumps & files.

Link Removed

 

[kemical]

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


Use !analyze -v to get detailed debugging information.


BugCheck F4, {3, fffffa8009d50b30, fffffa8009d50e10, fffff80002f8c460}


Probably caused by : wininit.exe


Followup: MachineOwner

Hi,

all your dmp files are the same pointing to either bad drivers, RAM or malware.

Please run a scan of malwarebytes as it's search and destroy is one of the best:

Malwarebytes : Free anti-malware download

Test your RAM individually so errors aren't confused with either stick. Also test for at least 7/8 passes.

Memtest86+ - Advanced Memory Diagnostic Tool

Just to check your HDD is ok (RAID 0) run a chkdsk.

Also this link is for your motherboard etc, please use it to update your drivers to the latest versions:

Link Removed

Please post any new dmp files after completing the above.

 

[usasma]

At work we run diagnostics on every system that we take in for repair (before we even start working on it). At a minimum, please run the free diagnostics here: Link Removed. For more in-depth diagnostics, please run those listed here: Link Removed

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.
10 Nov 2012 - I'm seeing an upswing in SSD errors - but most appear due to older storage controller drivers. I strongly suggest NOT using storage controller drivers that don't date from 2012 (if none are available, don't connect an SSD to that controller)

IMO this appears to be a hard drive issue - involving both memory access errors and the NTFS file system.
I'd assume it was the SSD, but please check any other hard drives (internal and external) with diagnostics: Link Removed

Your Intel Rapid Storage Technology (RST) storage drivers date from 2011, please update to the latest 2012 version available at Link Removed

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

iaStor.sys Fri May 20 12:52:24 2011 (4DD69C48)
Intel Storage drivers
Link Removed

EtronXHCI.sys Thu Aug 4 18:00:24 2011 (4E3B1678)
Etron USB 3.0 Extensible Host Controller Driver
Link Removed

EtronHub3.sys Thu Aug 4 18:00:28 2011 (4E3B167C)
Etron USB 3.0 Extensible Hub Driver
Link Removed

Please un-install this one:
AppleCharger.sys Tue Nov 1 22:46:00 2011 (4EB0AEE8)
GIGABYTE On/Off Charge driver. See here for details - Link Removed [br]May cause BSOD on Win7 systems - uninstall to test
Link Removed



Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Sat Dec 15 01:28:30.226 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121412-6988-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:42:57.038[/B]
Probably caused by :[B]wininit.exe[/B]
BugCheck [B]F4, {3, fffffa8009ddfb30, fffffa8009ddfe10, fffff80002f94460}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000003, Process
Arg2: fffffa8009ddfb30, Terminating object
Arg3: fffffa8009ddfe10, Process image file name
Arg4: fffff80002f94460, Explanatory message (ascii)
PROCESS_NAME: [B]wininit.exe[/B]
BUGCHECK_STR:  0xF4_c0000005
FAILURE_BUCKET_ID: [B]X64_0xF4_c0000005_IMAGE_wininit.exe[/B]
CPUID:        "Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz"
MaxSpeed:     3100
CurrentSpeed: [B]3093[/B]
  BIOS Version                  F10
  BIOS Release Date             02/23/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z68MA-D2H-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  9 04:42:32.790 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120912-10342-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:10:49.070[/B]
Probably caused by :[B]wininit.exe[/B]
BugCheck [B]F4, {3, fffffa8009de6b30, fffffa8009de6e10, fffff80002fda460}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000003, Process
Arg2: fffffa8009de6b30, Terminating object
Arg3: fffffa8009de6e10, Process image file name
Arg4: fffff80002fda460, Explanatory message (ascii)
PROCESS_NAME: [B]wininit.exe[/B]
BUGCHECK_STR:  0xF4_c0000005
FAILURE_BUCKET_ID: [B]X64_0xF4_c0000005_IMAGE_wininit.exe[/B]
CPUID:        "Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz"
MaxSpeed:     3100
CurrentSpeed: [B]3093[/B]
  BIOS Version                  F10
  BIOS Release Date             02/23/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z68MA-D2H-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  2 01:59:02.258 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120112-8096-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:50:50.070[/B]
Probably caused by :[B]wininit.exe[/B]
BugCheck [B]F4, {3, fffffa8009d56b30, fffffa8009d56e10, fffff80002f98460}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000000003, Process
Arg2: fffffa8009d56b30, Terminating object
Arg3: fffffa8009d56e10, Process image file name
Arg4: fffff80002f98460, Explanatory message (ascii)
PROCESS_NAME: [B]wininit.exe[/B]
BUGCHECK_STR:  0xF4_IOERR
FAILURE_BUCKET_ID: [B]X64_0xF4_IOERR_IMAGE_wininit.exe[/B]
CPUID:        "Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz"
MaxSpeed:     3100
CurrentSpeed: [B]3093[/B]
  BIOS Version                  F10
  BIOS Release Date             02/23/2012
  Manufacturer                  Gigabyte Technology Co., Ltd.
  Product Name                  Z68MA-D2H-B3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Sat Dec 15 01:28:30.226 2012 (UTC - 5:00)**************************
intelppm.sys       Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys        Fri Mar 19 12:18:18 2010 (4BA3A3CA)
pbfilter.sys       Thu Oct 14 21:39:45 2010 (4CB7B0E1)
iaStor.sys         Fri May 20 12:52:24 2011 (4DD69C48)
EtronXHCI.sys      Thu Aug  4 18:00:24 2011 (4E3B1678)
EtronHub3.sys      Thu Aug  4 18:00:28 2011 (4E3B167C)
Rt64win7.sys       Tue Aug 23 09:55:41 2011 (4E53B15D)
RTKVHD64.sys       Tue Aug 30 05:24:37 2011 (4E5CAC55)
[B]AppleCharger.sys   Tue Nov  1 22:46:00 2011 (4EB0AEE8)[/B]
IntcDAud.sys       Tue Dec  6 06:23:07 2011 (4EDDFB1B)
igdkmd64.sys       Thu Jan  5 22:36:45 2012 (4F066C4D)
MpFilter.sys       Thu Aug 23 19:03:14 2012 (5036B6B2)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  9 04:42:32.790 2012 (UTC - 5:00)**************************
ssudbus.sys        Thu Jul 26 21:15:16 2012 (5011EBA4)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[dan7u]

Might take me a few weeks, but I'll try all this. I'm not convinced its the SSD, as when I disconnected the (2) Samsung HDDs, the problem went away.

 

[usasma]

Since it stops when you remove the other hard drives - then it's most likely the other hard drives (rather than the SSD).
Start with the hard drive diagnostics and go from there.