BSOD For The Past Few Weeks - No Apparent Pattern

[oldchili]

I've gotten BSOD for the past few weeks. At first I thought it was due to the drivers for my graphics card, but I wiped the drivers clean and installed an older version to no avail. I still get BSOD every now and then. There's no apparent pattern - at least none that I can see. Sometimes it happens when I'm browsing, reading a PDF file with Adobe Acrobat, playing music on iTunes, etc.

I've attached the necessary files. Any help is truly appreciated.

 

[Northernsoul55]

Hi,

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
[COLOR=red]BugCheck 7A,[/COLOR] {fffff6fc4000c888, ffffffffc0000185, 1e8bd1860, fffff88001911748}
GetPointerFromAddress: unable to read from fffff80003703278
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc4000c888, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 00000001e8bd1860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88001911748, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
 
ERROR_CODE: (NTSTATUS) 0xc0000185 - [COLOR=red]The I/O device reported an I/O error.[/COLOR]
DISK_HARDWARE_ERROR: [COLOR=red]There was error with disk hardware[/COLOR]
BUGCHECK_STR:  0x7a_c0000185
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System

Firstly you need to remove the loopback activation entries you have used for Adobe:

127.0.0.1                   activate.adobe.com
127.0.0.1                   practivate.adobe.com
127.0.0.1                   192.150.14.69
127.0.0.1                   192.150.18.101
127.0.0.1                   192.150.18.108
127.0.0.1                   192.150.22.40
127.0.0.1                   192.150.8.100
127.0.0.1                   192.150.8.118
127.0.0.1                   209-34-83-73.ood.opsource.net
127.0.0.1                   3dns-1.adobe.com
127.0.0.1                   3dns-2.adobe.com
127.0.0.1                   3dns-3.adobe.com
127.0.0.1                   3dns-4.adobe.com
127.0.0.1                   3dns.adobe.com
127.0.0.1                   activate-sea.adobe.com
127.0.0.1                   activate-sjc0.adobe.com
127.0.0.1                   activate.wip.adobe.com
127.0.0.1                   activate.wip1.adobe.com
127.0.0.1                   activate.wip2.adobe.com
127.0.0.1                   activate.wip3.adobe.com
127.0.0.1                   activate.wip4.adobe.com
127.0.0.1                   adobe-dns-1.adobe.com
127.0.0.1                   adobe-dns-2.adobe.com
127.0.0.1                   adobe-dns-3.adobe.com
127.0.0.1                   adobe-dns-4.adobe.com
127.0.0.1                   adobe-dns.adobe.com
127.0.0.1                   adobe.activate.com
127.0.0.1                   adobeereg.com
127.0.0.1                   crl.verisign.net
127.0.0.1                   CRL.VERISIGN.NET.*
127.0.0.1                   ereg.adobe.com
127.0.0.1                   ereg.wip.adobe.com
127.0.0.1                   ereg.wip1.adobe.com
127.0.0.1                   ereg.wip2.adobe.com
127.0.0.1                   ereg.wip3.adobe.com
127.0.0.1                   ereg.wip4.adobe.com
127.0.0.1                   hl2rcv.adobe.com
127.0.0.1                   practivate.adobe.*
127.0.0.1                   practivate.adobe.ipp
127.0.0.1                   practivate.adobe.newoa
127.0.0.1                   practivate.adobe.ntp

There is also evidence of many memory errors and HDD failures in your logs:

[COLOR=red]3709 errors : !Ntfs[/COLOR] (fffff88001911000-fffff88001911fff)

1. Test your memory:

I would firstly try re-seating the RAM, ensure they are free from dust, and seated properly.
Then run memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Tip

Run these tests overnight, pay particular attention to #3 in tutorial if errors occur

2. Run SFC to check the integrity of all Windows 7 system files:

• Click on Start > Type in search cmd
  Right-click cmd after results are displayed and Run as Administrator
  Type SFC /scannow at the prompt
  (Note: There is a space between SFC and /scannow)

:ar: SFC Tutorial

   Note

Select option two. If any problems are found, run the scan 3 times and immediately
reboot the computer after each scan.

3. Also run chkdsk in an elevated command prompt in order to check for file system errors
and bad sectors on your HDD:

• Click on Start>Type in search cmd
• Right click cmd and Run as Administrator
• At the command prompt please type: chkdsk /f/r
  (There is a space between chkdsk and /f/r)

:ar: Chkdsk Tutorial

4. If chkdsk cannot repair the HDD, then test with Seatools:
:ar: SeaTools | Seagate

cheers

Dave