BSOD after waking from sleep

a135rt6, welcome to SF :).

Both bugchecks indicate an issue with the storage:

Code:

CRITICAL_OBJECT_TERMINATION (f4)
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.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8006e3db30, Terminating object
Arg3: fffffa8006e3de10, Process image file name
Arg4: fffff800031d30d0, Explanatory message (ascii)

Code:

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.

Code:

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

-====================================================-

Code:

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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa80050307c8, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Code:

ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

• 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.

-------------------

Code:

  Log Name: System
  Source: cdrom
  Date: 2013-08-18T17:17:34.837
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: user-PC
  Description: 
The device, \Device\CdRom0, has a bad block.

This was logged numerous times in the Event Viewe and indicates a failing CD-ROM drive / controller.

-====================================================-



Testing the HDD:

1. Perform a Disk Check | Disk Check
2. Then Post the results following | THIS METHOD
3. Download SeaTools for Windows 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 the page).

Post back with the results!

Your PC appears to be overheating often!

Code:

  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2013-08-19T20:39:36.718
  Event ID: 88
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: N/A
  User Name: N/A
  Computer: user-PC
  Description: 
The system was hibernated due to a critical thermal event.
Hibernate Time = ?2013?-?08?-?19T19:39:36.718808600Z             
ACPI Thermal Zone = ACPI\ThermalZone\THRM             
_HOT = 373K

Download Speccy and Post a Screenshot of the summary window under two conditions.

1. Normal use for 30 minutes.
2. Strees Tessting With Prime95, Keep a close eye in the temperatures don't let it exceed 80°! If it does STOP the test and shutdown the PC in a safe manner using the Shut Down option in the start menu.

Well that must be it, if not than a big part of the issue.

How old is the laptop? thermal pads, like anything, degrade over time.
Most BIOSs these days have an option to set a fan profile, i.e. Silent / Normal.
Check and see if yours offers this option.

you can also purchase a cooling-mat for it and see if it helps, making sure that the air vents
doesn't look like this picture I took today would go a long way.

Attachment 282560

Any developments?