Frequent BSODs - BCCode=f4/03


  1. Posts : 3
    Windows 7 Professional 32bit
       #1

    Frequent BSODs - BCCode=f4/03


    I am at my wits end with this problem. I am an experienced PC person who has built many machines before but I never had this much trouble diagnosing a problem.

    New build using MSI H55M-E33 mobo, core i3, 4GB Gskil (all new) and a 3-5 yr old WD 160 GB drive. Windows 7 Pro, fresh install (coexists with Ubuntu 10.04).

    Basically, NO applications installed. Machine will randomly and frequently BSO, usually with BCCode=f4, BCP1=03. Reboots, works for a while, then same thing happens.

    I have already substituted the memory and PSU from another working machine. No help.

    Attachment with files as instructed attached.
      My Computer


  2. Posts : 3
    Windows 7 Professional 32bit
    Thread Starter
       #2

    Is anyone going to reply to this? I see much new posts with replies, so why no response to this post?
      My Computer


  3. Posts : 5,705
    Win7 x64 + x86
       #3

    I have no idea why others have skipped over your post. I do know that STOP 0xF4 errors are one's that I hate because they are very complicated to troubleshoot. Here's a link to a page with some info on that error: BSOD Index (please check the Usual Causes and the KB articles).

    From the perfmon report - Windows Search terminated abnormally. Have you "tweaked" any settings that relate to Search?

    There are approximately 50-60 updates available after installing SP1. Your system only has 2. Please visit Windows Update and get all available updates.

    Acronis True Image can cause issues with Win7 systems. Just to be sure, please uninstall it while we're troubleshooting.

    From the 1st BSOD (STOP 0x7E), the NT STATUS code of 0xc00000c0 is
    STATUS_DEVICE_DOES_NOT_EXIST

    From the STOP 0xF4 BSOD's, the status is an I/O Error
    So we're looking at hardware here - and IMO the most suspect device is the old W-D hard drive.
    So, please start with these free diagnostics:
    I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link) - Test ALL of the hard drives.

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Resources (read the details at the link)
    There are also free, bootable antivirus disks at this link: Free Online AntiMalware Resources
    Please post back with the results of the tests and we'll see where to go from there.

    BSOD BUGCHECK SUMMARY
    Code:
    
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080211-13540-01.dmp]
    Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
    Debug session time: Tue Aug  2 22:21:32.006 2011 (UTC - 4:00)
    System Uptime: 0 days 0:06:47.052
    PROCESS_NAME:  csrss.exe
    BUGCHECK_STR:  0xF4_IOERR
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    FAILURE_BUCKET_ID:  0xF4_IOERR_IMAGE_csrss.exe
    Bugcheck code 000000F4
    Arguments 00000003 86f59870 86f599dc 82c5ecf0
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    CPUID:        "Intel(R) Core(TM) i3 CPU         540  @ 3.07GHz"
    MaxSpeed:     3070
    CurrentSpeed: 3059
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080211-14258-01.dmp]
    Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
    Debug session time: Tue Aug  2 21:44:38.826 2011 (UTC - 4:00)
    System Uptime: 0 days 0:04:01.247
    PROCESS_NAME:  csrss.exe
    BUGCHECK_STR:  0xF4_IOERR
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    FAILURE_BUCKET_ID:  0xF4_IOERR_IMAGE_csrss.exe
    Bugcheck code 000000F4
    Arguments 00000003 8619fd40 8619feac 82c6ecf0
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    CPUID:        "Intel(R) Core(TM) i3 CPU         540  @ 3.07GHz"
    MaxSpeed:     3070
    CurrentSpeed: 3059
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080211-16005-01.dmp]
    Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
    Debug session time: Tue Aug  2 21:39:44.931 2011 (UTC - 4:00)
    System Uptime: 0 days 0:14:09.367
    PROCESS_NAME:  csrss.exe
    BUGCHECK_STR:  0xF4_IOERR
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    FAILURE_BUCKET_ID:  0xF4_IOERR_IMAGE_csrss.exe
    Bugcheck code 000000F4
    Arguments 00000003 8620ad40 8620aeac 82c51cf0
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    CPUID:        "Intel(R) Core(TM) i3 CPU         540  @ 3.07GHz"
    MaxSpeed:     3070
    CurrentSpeed: 3059
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080211-16629-01.dmp]
    Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
    Debug session time: Tue Aug  2 21:24:19.023 2011 (UTC - 4:00)
    System Uptime: 0 days 0:07:23.443
    PROCESS_NAME:  csrss.exe
    BUGCHECK_STR:  0xF4_IOERR
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    FAILURE_BUCKET_ID:  0xF4_IOERR_IMAGE_csrss.exe
    Bugcheck code 000000F4
    Arguments 00000003 86a938d8 86a93a44 82c54cf0
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    CPUID:        "Intel(R) Core(TM) i3 CPU         540  @ 3.07GHz"
    MaxSpeed:     3070
    CurrentSpeed: 3059
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080211-18501-01.dmp]
    Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
    Debug session time: Tue Aug  2 21:16:03.245 2011 (UTC - 4:00)
    System Uptime: 0 days 0:00:30.666
    PROCESS_NAME:  csrss.exe
    BUGCHECK_STR:  0xF4_IOERR
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    FAILURE_BUCKET_ID:  0xF4_IOERR_IMAGE_csrss.exe
    Bugcheck code 000000F4
    Arguments 00000003 86b3fd40 86b3feac 82c5ecf0
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    CPUID:        "Intel(R) Core(TM) i3 CPU         540  @ 3.07GHz"
    MaxSpeed:     3070
    CurrentSpeed: 3059
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080211-18252-01.dmp]
    Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
    Debug session time: Tue Aug  2 20:47:04.590 2011 (UTC - 4:00)
    System Uptime: 0 days 1:52:14.010
    BUGCHECK_STR:  0x7a_c00000c0
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  smss.exe
    FAILURE_BUCKET_ID:  0x7a_c00000c0_nt!MiWaitForInPageComplete+302
    Bugcheck code 0000007A
    Arguments c0604000 c00000c0 a70c8880 c0800000
    BiosVersion = V1.9
    BiosReleaseDate = 09/14/2010
    CPUID:        "Intel(R) Core(TM) i3 CPU         540  @ 3.07GHz"
    MaxSpeed:     3070
    CurrentSpeed: 3059
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  4. Posts : 3
    Windows 7 Professional 32bit
    Thread Starter
       #4

    First of all, thanks for the analysis and reply. Just before I checked for any replies on this thread, I had replaced the older WD drive with a brand new one, installed W7 and, VOILA! No more BSODs!
    What is really puzzling to me is this drive came out of another PC that I thought was working fine, although I did re-partition it before installing into new PC. And I DID run WD diagnostics on the drive 2x and both times no issues were found. I have not run the HD diags you have pointed to.

    So, bottom line is: Problem resolved by changing hard drive!
      My Computer


  5. Posts : 5,705
    Win7 x64 + x86
       #5

    If you ran the W-D DLG, then that should have been good for that drive.
    But there's many things that can happen here.
    There could have been a loose connection (it took me many years of building PC's to get this one right!)
    There could have been a bad cable
    There could have been a "glitch" in the hard drive that wasn't evident all of the time
    There could have been an issue between the hard drive controller (on the mobo) and the hard drive (not likely, but possible).
    But it could also have been software issues - either those that I mentioned, or some that I didn't see.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About 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 05:29.
Find Us