BSOD 0x7A, seemingly random

Page 1 of 3 123 LastLast

  1. Posts : 11
    Windows 7 Home Premium 64bit
       #1

    BSOD 0x7A, seemingly random


    So for the past few days, I have been utterly plagued by this BSOD, sometimes my computer freezes at startup, then startup repair does nothing, a chkdsk will find files fix them but then BSOD anyways. There is no consistency, except that there is a limited time before the BSOD and I ran for about 6 hours in normal windows without one (I restarted) and 12+ hours in safe mode (I restarted). Steps I have taken from threads I have read on this forum:

    1) Memtest86+ runs perfectly fine for ~8 hours.
    2) SeaGate SeaTool - all basic tests passed
    3) Chkdsk /f - found errors, repaired them
    4) CCleaner - registry cleanup
    5) SFC /scannow - run 3 times with restarts in between
    6) Configure windows to save minidumps - note: there are none that I can find
    7) Malwarebytes full scan - clean
    8) AntiVirus (Symantec Endpoint) Full Scan - clean
    9) Uninstall Intel Rapid Storage Technology
    10) Stop any overclocking (I only overclocked my GPU, I also disabled XMP on my RAM)
    11) Disk Defrag

    This leads me to believe it may be a driver or a program. I can't figure it out. This DOES NOT happen coming out of hibernation/sleep.

    EDIT: I (as far as I can remember) get 0x7A Kernel_Inpage_Data_Error, usually if it doesn't flash by it says ntfs.sys
      My Computer


  2. Posts : 11
    Windows 7 Home Premium 64bit
    Thread Starter
       #2

    Help?
      My Computer


  3. Posts : 26,869
    Windows 11 Pro
       #3

    Theblaze973, unfortunately, you have no dump files, which is what we use to debug with. Either your computer did not create them or your use of cleaning tools deleted them which many will do by default, unless those items are deselected.

    What seems obvious, is check disk finds errors when there should be none. Yet it keeps finding them. BSODs mentions NTFS file system. The problem, just from your description lies somewhere between the ram and your hard drive. At least that is the first place I would look. Memtest must be run for 8 complete passes before it runs a complete test. It won't run 8 complete passes in 8 hours. Norton is a cause of BSODs. You said you ran sfc /scannow for 3 times with reboots in between, but never said what the results were. So, if you would, please configure your computer for small memory dumps. Make sure you have a C:Windows Minidump folder. if not, create one. Dump Files - Configure Windows to Create on BSOD

    Create a system restore point System Restore Point - Create

    Next enable Driver Verifier

    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
       Information

    What is Driver Verifier:
    It puts stress on the drivers, and therefore it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.


    How we know that DV is enabled:
    It will make the system bit slow and sluggish.
       Warning

    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there are no Restore points, make a System Restore Point manually before enabling DV.


       Tip





    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  4. Posts : 11
    Windows 7 Home Premium 64bit
    Thread Starter
       #4

    Is there anything that would clean dumps without me running manually? I have not run any cleaning tools after the last few BSODs and my configuration (as per instructions found a few days ago) is below. Would RAM randomly have issues after only a year of use? When I first got it I did a 30 hour Memtest with no errors.

    Result of SFC /scannow, the first one found and fixed corrupted files, the second and third didn't. and I just ran a fourth (after another BSOD today) with no errors. I'm going to run Memtest again (for longer) and report back. I don't see a point in pushing my system to BSOD (with DV) if it isn't logging anything. am obviously missing something.

      My Computer


  5. Posts : 26,869
    Windows 11 Pro
       #5

    There is nothing in Windows that would automatically clean out dump files. Disk Cleanup would, if that option was checked as would CCleaner, but they both have to be run manually. If you have any of those Windows optimizers or other utilities that run automatically, they probably would and should be removed from your system anyway. they cause more problems than they solve. If you have McAfee or Norton installed, they might and they are both causes of BSODs in themselves. There are special removal tools for them, but it is very difficult to remove them in any case.

    As far as the ram, I really can't say except that ram will occasionally go bad for unknown reasons. With the error reports I saw and what you described, I would look at the hard drive again too as well as Windows Updates. There were references to the NTFS file system and your reports of windows scanning the disks is in many cases a warning of a hard drive going bad.

    Driver Verifier is supposed to make your system crash so the dump will catch the offending driver. It would be best to make sure your system will create dump files before enabling it.
      My Computer


  6. Posts : 11
    Windows 7 Home Premium 64bit
    Thread Starter
       #6

    Memetest86+ 8 passes ~10 hours no errors. More BSODs, no minidumps still. It says on the BSOD that it is collecting data, then initializing then physical memory dump complete. Anyways, new errors:

    0x7A once, then Chkdsk (It said something about a sector then my computer restarted and it ran againw tih no errors), then 0xF4 twice, then:

    Stop c000021a {Fatal System Error}
    Verification of a Knowndll failed. System thread has terminated with code:
    0xC0000222 (0x4a5a450 0x0)

    Then two more 0xF4s. Then my computer would not boot (in safe mode it froze at CI.dll). Then Startup repair failed to do anything twice. Then it said fixing disk errors and then my computer booted into safe mode.

    I think I'm going to initiate an RMA with WD unless I can get minidumps working.
      My Computer


  7. Posts : 26,869
    Windows 11 Pro
       #7

    If you still have driver verifier enabled, disable it. You may have to boot your Installation DVD or the repair CD. Restore to a previous point, which you should have created before enabling DV. See Option 2 System Restore

    you may also want to run Western digital's diagnostic test data Lifeguard for DOS WD Support / Downloads / SATA & SAS / WD Black instructions are there

    If that won't work, use Seatools SeaTools for DOS | Seagate

    Whichever one you can get to work, run the short and the long test.
      My Computer


  8. Posts : 11
    Windows 7 Home Premium 64bit
    Thread Starter
       #8

    Screen just goes blank when I run the WD program from DOS. Following the WD instructions.

    SeaTools for DOS can't find my HDD.
      My Computer


  9. Posts : 26,869
    Windows 11 Pro
       #9

    There is no reason it should do that. Do you see anything to begin with? Your graphics should work just fine, just like in BIOS. The hard drive is not being used and the drivers are not being used. What happens when you boot from the CD?
      My Computer


  10. Posts : 11
    Windows 7 Home Premium 64bit
    Thread Starter
       #10

    I was just putting in the CD now.

    Following the Instructions for installation disc. It did not find my OS installation so I can't do a restore (which I did make/verify).
      My Computer


 
Page 1 of 3 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 09:56.
Find Us