Help with Blue Screens/Minidump

[tfoster]

I keep getting random BSOD's. I'm running VISTA Home Premium 64. Here is the output from one of the minidumps:

BugCheck 7A, {fffff6fc40013488, ffffffffc0000185, 329d2880, fffff88002691a80}

When I looked that up on Microsoft's web page, I believe it says to check the cabling or termination on my 'SCSI' drive. I actually have a Wester Digital 3200KS SATA drive, however, I believe Windows reports it as a SCSI. I have tried updating every driver I can think of to no avail. I have downclocked the Dram to 667 and the processor by 200MHz (to 2.6GHz) and still see failures. I have taken the cover off of the case in case it was overheating. Nothing has worked.

I'm hoping there is someone out there who can shed more light on this. I have several minidumps that I could attach, however, they are 265K in size and I do no know if that would be acceptable or not.

What are the chances that a new cable will fix the problem or whether this is a malfunction of the hard drive itself?

Also, I can provide any other system information if that would help diagnose this issue.

Thanks!

Todd

[fizban2]

are you able to get into windows long enough to change the type of dump to full? that would be more helpful to us in resolving your issue

[tfoster]

Absolutely. My system is quite alive and sometimes takes days to fail. It seems to fail quicker when I am accessing the hard drive more (like playing a game or sometimes downloading a file). I'll get in and change the dump type to full and wait for another failure.

Todd

[tfoster]

Just to make sure, my 3 options are:

Small Memory Dump (128KB)

Kernel Memory Dump

Complete Memory Dump

Currently I have everything as a Kernel Memory Dump. However, you would like me to change to a Complete Memory Dump, correct?

Todd

[fizban2]

Just to make sure, my 3 options are:

Small Memory Dump (128KB)

Kernel Memory Dump

Complete Memory Dump

Currently I have everything as a Kernel Memory Dump. However, you would like me to change to a Complete Memory Dump, correct?

Todd

correct, set it up to do a complete memory dump, the dump file will be as big as your physical memory, PM me when you have complete dump

[gosh]

Does the blue screen reference a file name? Is this on a clean install or upgrade?

-gosh

[cluberti]

It would help if you could provide even a minidump of this (although a complete dump is infinitely more useful). I'm expecting the module was win32k.sys, Atapi.sys, or Ataport.sys, but if you could post that as well, that'd be great. Note that a STOP 0x7A means that a page (4Kb) of kernel data was requested from the paging file to map back into RAM, and it could not be read into memory - this generally means bad RAM (the page was corrupt when written to the disk from RAM earlier, or the write operation from the disk to the RAM location failed) or a bad hard disk controller or a bad hard disk (failed to read the section of the pagefile on disk where the page to be remapped into RAM was supposed to be located).