BSOD random 0xF4, no dumps; stuck on "initializing disk"

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 7,050
    Windows 10 Pro
       #11

    The first log of C showed some corruption but got resolved, the second chkdsk on partition C was to validate that it was truly resolved.
    If a second chkdsk still shows problems after the first chkdsk fixed problems, then it indicates the HDD failing.

    TBH, a failing HDD wouldn't be surprising, because a combination of 0x7A and 0xF4 BSOD crashes usually results in HDD related problems. Being it
    - a bad motherboard connection,
    - bad or loose cables,
    - SSD firmware issues,
    - a failing HDD or
    - file system corruption,
    where a failing HDD is mostly occuring.
      My Computer


  2. Posts : 59
    Windows 7 Professional x64
    Thread Starter
       #12

    awesome - thanks axe0. i'll let you know if i see BSOD again!
      My Computer


  3. Posts : 59
    Windows 7 Professional x64
    Thread Starter
       #13

    darnit - BSOD'd again. I've been waiting for over an hour in the hopes that it'll create a dump, but no joy... any suggestions for what to look into next? Memtest86+ shows no errors...
    Last edited by luckycharms; 27 Jan 2017 at 04:45.
      My Computer


  4. Posts : 7,050
    Windows 10 Pro
       #14

    Memtest86+ is not worth it if you don't intend to let it run for 8 passes
      My Computer


  5. Posts : 59
    Windows 7 Professional x64
    Thread Starter
       #15

    ok... should i let it run for 8 passes, or is there something more likely you think i should look into before that? any thoughts greatly appreciated...

    mem stick info attached...
    Last edited by luckycharms; 27 Jan 2017 at 08:18.
      My Computer


  6. Posts : 7,050
    Windows 10 Pro
       #16

    You'll want to remove either of the memory sticks while troubleshooting.
      My Computer


  7. Posts : 59
    Windows 7 Professional x64
    Thread Starter
       #17

    Haven't run memtest again yet, will do so, but wanted to share a couple more bsod's meantime. Both are 0x7A, one for win32k.sys and one for srv.sys. Not sure if this gives any more clues...
      My Computer


  8. Posts : 59
    Windows 7 Professional x64
    Thread Starter
       #18

    ran sfc /scannow and found corruption of autochk.exe. let's see if this fixes anything...

    Code:
    2017-01-31 14:44:58, Info                  CSI    0000035d [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"autochk.exe" from store
      My Computer


  9. Posts : 7,050
    Windows 10 Pro
       #19

    Recommendation is to replace the HDD.
      My Computer


  10. Posts : 59
    Windows 7 Professional x64
    Thread Starter
       #20

    The sfc /scannow fix of autochk.exe did not fix the BSOD (as you suspected).

    To test the HDD hypothesis, I ran the computer all night with the HDD removed, and got no BSOD. That supports your hunch of an HDD cause (even though smart and chkdsk showed no issues; reminder that C is SSD and D is HDD). The HDD cable is 3rd party, and had to be scrunched a bit to fit, so I'm wondering if it's faulty. I will try replacing it.

    I'm clearly trying to avoid the "replace HDD" recommendation, as that's $, and I'm also a bit confused as to why the HDD would work no problem in the previous system, show no chkdsk or smart issues (the SSD was the one with chkdsk issues), yet be problematic. There are no firmware updates for it.

    One thought: the BIOS is set to manage drives with "Intel RAID". When I switch to AHCI, the system won't boot, or gets a blue screen upon boot (I forget which). I know there's a bunch online about switching to AHCI in Windows, driver installs, etc, if I really wanted to make AHCI work. My question is: could this RAID vs ACHI configuration in the BIOS have anything to do with the BSODs?

    Thanks again, will continue to update.
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  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 12:22.
Find Us