Solved Random BSODs relating to disk issues (0x07a and 0x0fa)

[Proverbs]

Hello everyone!

For the past week or so, I have been having seemingly random BSODs. Here is a pic of the ones I have received:

I have not noticed any connection between my actions and the crashes. As I said, they seem fairly random. Everything I have looked up about these error codes seems to point to a disk issue.

What Ive tried:
sfc /scannow - "...found corrupt files but was unable to fix some of them."
Booting from install disk and running sfc - "..system repair pending which requires reboot to complete." I have tried multiple reboots, and tried to clear the "pending" change. Nothing.
Disk Clean up of temp files - got some extra SSD space? :huh:
Ran SMART disk test (Both from SEAGATE, and CrystalDiskInfo) - The C: drive had no issues.
Ran Chkdsk /R /P (I cant remember which flags, it was check and repair) - 0 Issues found on disk

Additional info:
I have my main install of windows on the C: drive. The C: drive is a SSD. I have a 2nd, 3rd, and 4th install of Windows (x1 Vista, x2 7) on my E:, F:, and G: drive, respectively. These are all HHDs that I have been meaning to cleanup for a while now, but just haven't gotten around to. :shock:

Any help is appreciated.

Thanks,
Tanner

 

[Laith]

Hiya and welcome to SevenForums!rb:

BugCheck 7A, {fffff6fc400099c8, ffffffffc000000e, 19e3e4860, fffff88001339dc4}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
GetPointerFromAddress: unable to read from fffff800030c3278
Probably caused by : memory_corruption
[CODE]MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption

[/CODE]

BugCheck F4, {3, fffffa8008dedb10, fffffa8008deddf0, fffff800031cbe20}

Probably caused by : wininit.exe

BugCheck 7A, {fffff8a0115cda60, ffffffffc000000e, 1dd8d5860, fffff960001536e0}

Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+1436e0 )

BugCheck F4, {3, fffffa8008436b10, fffffa8008436df0, fffff800031dee20}

Probably caused by : csrss.exe

BugCheck 116, {fffffa8009386010, fffff8800522c6ac, ffffffffc000009a, 4}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9336ac )

This the first time i've seen such detailed infomation on an memory corruption. Anyways

There's an 0xF4 which can mean several things. It might be the HDD that is failing, some viruses or the RAM.

But i'm certain that it is the RAM. Run MemTest86+ for 8 passes. It must be MemTest86+. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run sfc /scannow and chkdsk /r.

Install the latest updates from Windows Update.

Run Display Driver Uninstaller(DDU)
Make sure you tick the Uninstall C:/AMD and C:/NIVIDA folders while you are in DDU when you are done running DDU install your graphics driver again. This is the guide for DDU: http://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html

The RAM is failing very very very heavy. That's what i think at least.

 

[Proverbs]

Thank you, Laith! I will start running these tests tonight after work, and post back the results when I can.

 

[Laith]

Okay, sounds good and no problem!

 

[Proverbs]

So, I removed the RAM from my motherboard, gave everything a good air dusting, and re-seated the RAM. After that, I let Memtest86+ run for 9 passes. It found 0 errors. I think this has probably fixed my issue.

Sfc /scannow still won't fix some of the corrupt files, but I will try and fiddle with that a bit. I'll wait and see if I receive any other BSODs. If I haven't had any in a few days, I will come back and mark this thread as solved!

Thanks again, Laith!

 

[Laith]

No problem! It is my duty to help!

It must be the disk because 0xF4s are commonly most related to viruses and disks.