BlueScreen of Death

Hello and welcome to SF :) .

The single dumps file in the attached zip doesn't show much apart from a I/O Error which is storage related.

Code:

BugCheck F4, {3, fffffa8009fa82e0, fffffa8009fa85c0, fffff8000317d0d0}

Code:

0xC0000006 STATUS_IN_PAGE_ERROR    The instruction at 0x%08lx referenced memory at 0x%08lx.
The required  data was not placed into memory because of an I/O error status of  0x%08lx.

Other bugchecks were recorded in the system even log which are also storage related;

Code:

STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR

Code:

Usual causes:  Memory, Paging file corruption, File system, Hard drive,
Cabling, Virus infection, Improperly seated cards,
BIOS, Bad motherboard, Missing Service Pack

Code:

0x0000007a (0xfffff6fb40000148, 0xffffffffc000000e, 0x0000000002b5a884, 0xfffff68000029000)
0x0000007a (0xfffff6fc400075c0, 0xffffffffc000000e, 0x00000000963e4860, 0xfffff88000eb8630)
0x0000007a (0xfffff6fc5000c988, 0xffffffffc000000e, 0x000000019b04f880, 0xfffff8a001931000)
0x0000007a (0xfffff6fc4005b160, 0xffffffffc000000e, 0x000000008d081be0, 0xfffff8800b62c000)
0x0000007a (0xfffff6fc4005b5b8, 0xffffffffc00000c0, 0x0000000195ba3be0, 0xfffff8800b6b7000)
0x0000007a (0xfffff6fb800083f8, 0xffffffffc000000e, 0x00000000687f6880, 0xfffff7000107fff8)
0x0000007a (0xfffff6fb80000000, 0xffffffffc000000e, 0x00000000545a3880, 0xfffff700000000a0)
0x0000007a (0xfffff6fb41fffd90, 0xffffffffc000000e, 0x000000020994b884, 0xfffff683fffb2000)
0x0000007a (0xfffff6fc5038c660, 0xffffffffc000000e, 0x00000001bf80e880, 0xfffff8a0718cc800)
0x0000007a (0xfffff6fc50027458, 0xffffffffc00000c0, 0x0000000205b7e880, 0xfffff8a004e8b620)
0x0000007a (0xfffff6fc4000a8c8, 0xffffffffc000000e, 0x0000000031d28860, 0xfffff88001519ca8)

By looking at the second parameter we can tell the NTstatus code:

Code:

0xC000000E STATUS_NO_SUCH_DEVICE    A device that does not exist was specified.

Code:

0xC00000C0 STATUS_DEVICE_DOES_NOT_EXIST    This device does not exist.

Being that your PC is an OEM not much details are available of core components like the motherboard,
but i do see it's quite old now, 775 socket which leads me to believe that there might be an incompatibility
with SSD's.

Please follow the steps described in this quote:

writhziden said:

• If you have an SSD, make sure the following are up to date:
  
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.

Then scan your PC for infections:

• Download TDSS-Killer and scan for rootkits.
• Download Windows Defender Offline and scan for other types of infections.
• Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

When did the issues start?

Post back with the results :).

• SanDisk Support - SSD Firmware.

Thanks for the feedback :) .

Upon further investigation I found many entries in the system even log about paging errors
regarding Harddisk2 & Harddisk1, but mainly Harddisk2;

Code:

Event[33203]:
  Log Name: System
  Source: Disk
  Date: 2013-10-01T07:12:14.853
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ezunkwelle
  Description: 
The driver detected a controller error on \Device\Harddisk2\DR2.

Code:

Event[28648]:
  Log Name: System
  Source: Disk
  Date: 2013-09-19T10:45:03.980
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ezunkwelle
  Description: 
The driver detected a controller error on \Device\Harddisk1\DR1.

Code:

Event[30684]:
  Log Name: System
  Source: Disk
  Date: 2013-09-26T07:23:21.485
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Ezunkwelle
  Description: 
An error was detected on device \Device\Harddisk2\DR2 during a paging operation.

Code:

Model    Generic External USB Device
Media Type    External hard disk media
Size    465.76 GB (500,105,249,280 bytes)
Partition    Disk #1, Partition #0

Code:

Model    ST310005 28AS USB Device
Media Type    External hard disk media
Size    931.51 GB (1,000,202,273,280 bytes)
Partition    Disk #2, Partition #0

How are the drives connected?
Are they connected directly to the motherboard USB ports at the back?
What is their power source?
How old are the drives?

Please test the disks.

   Warning

The Following Method Should NOT Be Performed On An SSD!

Testing the HDD:

1. Perform a Disk Check | Disk Check
2. Then Post the results following | THIS METHOD
3. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

If SeaTools For DOS does not recognize the drive;
Boot into the BIOS using the *Fxkey.
Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
Set it to IDE then save and exit usually by pressing the F10 key.
Now boot into SeaTools and it should detect the drives.
Start the Long Test and let it run.
Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
and change the SATA setting back to what it was in the first place.

• *Popular BIOS access keys.

Thanks for the update :) .
What did Seatools had to say about them?
Have you had any crashes since post #3?

It's my pleasure :) .
I don't understand one thing though.
Why is your SATA mode set to Raid when you only have one SATA interface (internal) drive?
Please post a screenshot of Disk Management.

• Disk Management - Post a Screen Capture Image

Thanks :)
My method of handling this kind of situation would be don't touch anything unless it proves to be the issue.
As long as the PC is stable after completing the steps above no need to change anything else,
leave Seatools for now as well.

Leave this thread open for a couple of days and see how things are going :) .
Be sure to update in a week or so.