Your BSoD System File Collection and health reports are not complete, re-upload the complete files requested. The Event Logs are very useful in these type of crashes, they will help us to identify to actual cause.
Blue Screen of Death (BSOD) Posting Instructions
When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.
What size and how many RAM cards do you have?
You have two Western Digital hard drives, add them to your 'System Specs'. If we have a complete list of your system components it will help us to analyze the cause of the crashes.
Run the WD Lifeguard test on each of your HDDs. Quick Test first, if it passes then run the Extended Test.
Data Lifeguard Diagnostic for Windows
Are you running the 'Intel SSD Toolbox' on your SSD?
If not, it's recommended to run it minimum of once a week, download and run it.
Intel® Solid-State Drive Toolbox
If you already have it, check the version number, update it if it is not the newest version.
I have not read anything saying running a HDD diagnostic program on a SSD is bad or causes any problems, but I have never seen it recommended. It's recommended to run SSD diagnostic programs on SSDs.
Use Intel SSD Toolbox and first run the 'Quick Diagnostic Scan' if it passes then run the 'Full Diagnostic Scan'.
Post the results.
You should run Disk Check, as recommended, as you have done and it passed. This indicated the current file system is not corrupted.
Post a snip of your Device Manager > Disk Drives > right click any drive > properties > Driver tab
Should look like this:
View attachment 245980
Post a snip of your Device Manager > IDE ATA/ATAPI controllers > right click the 'Intel' listing > properties > Driver tab
Should look like this, with a different driver version:
View attachment 245982
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Is this your motherboard?
Gigabyte GA-EP45-UD3P
If this is correct, what version is the board? 1.0, 1.1 or 1.6?
There is no EU45-UD3P as listed in your 'System Specs'.
The latest Intel Matrix Storage Manager controller driver listed for the above board is v.8.9.0.1023 date: 2009/08/11.
Your iaStor driver date is Jun 05 2009, which is older than the driver above.
This version will not allow the SSD trim function to work, the first version to allow trim was 9.6.0.1014, over time your SSD will become 'dirty' and quite possibly corrupt.
Install the
Intel® Rapid Storage Technology version 11.2.0.1006
The Intel RST drivers after v11.2.0.1006 and up to v11.6.0.1030 (these versions have been removed from the Intel site) are known to have issues with some systems, so use v11.2.0.1006.
There is a new release, v11.7.0.1013, due to some of the previous version problems I recommend to wait until it has been tested before using it.
The 'dump_iaStor.sys' driver listed in a previous post is a separate driver used only for Crash Dump reports and is not the same iaStor driver used by the OS.
The last four crashes, oldest first:
Code:
STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes: Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack.
GetPointerFromAddress: unable to read from fffff80002f07220
Probably caused by : memory_corruption
If the error status is 0xC000000E, it means the disk subsystem has experienced a failure
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
DISK_HARDWARE_ERROR: There was error with disk hardware
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_4096
Followup: memory_corruption
This is indicating the Page File on your SSD/HDD was corrupt.
By default the page file will be on your SSD, have you moved the page file to one of the hard drives?
Memory is also indicated above, it may need to be tested again, likely when info in the RAM was sent to the page file on the SSD/HDD it became corrupt there and when it was returned to the RAM it caused an error.
Running the SSD diagnostic tests and the HDD diagnostic tests will help to find if that is indeed the cause.
The last three crashes are all the same:
Code:
STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION
A process or thread crucial to system operation has unexpectedly exited or been terminated.
Several processes and threads are necessary for the operation of the system; when they are terminated (for any reason), the system can no
longer function.
IMAGE_NAME: csrss.exe - Client/Server Runtime Subsystem, or csrss.exe, is a component of the Microsoft Windows NT operating system that provides the user mode side of the Win32 subsystem and is included in Windows 7. It is critical to system operation; therefore, terminating this process will result in system failure.
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
DEFAULT_BUCKET_ID: [COLOR="Red"]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR]
FAILURE_BUCKET_ID: X64_0xF4_IOERR_VRF_IMAGE_csrss.exe
2: kd> !process fffffa8009c99b30 3
GetPointerFromAddress: unable to read from fffff80002f0c000
PROCESS fffffa8009c99b30
SessionId: none Cid: 0250 Peb: 7fffffd7000 ParentCid: 023c
DirBase: 20bd72000 ObjectTable: fffff8a000f98180 HandleCount: <Data Not Accessible>
Image: csrss.exe
VadRoot fffffa8009d2dc20 Vads 81 Clone 0 Private 2644. Modified 58985. Locked 0.
DeviceMap fffff8a000007e50
Token fffff8a000f99060
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 166888
QuotaPoolUsage[NonPagedPool] 30768
Working Set Sizes (now,min,max) (3538, 50, 345) (14152KB, 200KB, 1380KB)
PeakWorkingSetSize 7586
VirtualSize 77 Mb
PeakVirtualSize 100 Mb
[COLOR="red"]PageFaultCount 15867[/COLOR]
MemoryPriority BACKGROUND
BasePriority 13
CommitCharge 2821
*** Error in reading nt!_ETHREAD @ fffffa8009defb60
These three crashes were blamed on csrss.exe a Windows driver/process, which are usually not to blame, this was the last thing the debuggar has seen and it couldn't find the actual cause so it blames csrss.exe.
Other information is pointing to a page file fault, so the above recommendations should resolve this issue.
These are 'Verifier Enabled Crashes' disable Driver Verifier.
Driver Verifier - Enable and Disable
Let us know if you have any questions.
