BSOD becoming more frequently

[ibeleaf]

So far I have gotten BSOD the last 4 days straight and my boot times have been insanely long (~5 min).

Other information:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 4105

Additional information about the problem:
BCCode: 7a
BCP1: FFFFF6FC40053C80
BCP2: FFFFFFFFC0000185
BCP3: 00000000640DBBE0
BCP4: FFFFF8800A790000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\081614-87469-01.dmp
C:\Users\Gurneet\AppData\Local\Temp\WER-277510-0.sysdata.xml

 

[Arc]

Upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

___________________________________________

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

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

 

[ibeleaf]

Attached. If theres anything else that is needed please let me know. I would like to resolve this before I go back to school

 

[Arc]

Sorry to say, but it might not be that easy.

Based on the crash dump report, I am suspecting a disc failure there.

ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error. 
 DISK_HARDWARE_ERROR: [COLOR=Red]There was error with disk hardware[/COLOR]

First of all, you test your HDD using Seatools (It is Samsung, but Seatools tests them all).

http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html
​

Take both the short test and the long test.

Let us know the result.

 

[ibeleaf]

Well this is lame. I ran the short test and it passed. I let the long one run and went away from the laptop, only to come back stating "A disk error occurred Press Ctrl+Alt+Del to reRecovery". I do so but I get the same message. Can't boot...

 

[Arc]

Check if the disc is detected in the BIOS or not. If not, open the computer. Re-seat the SATA and power cables. Apply the SATA cable in another unused SATA port on the motherboard. Also, if possible, change the SATA cable.

If still the disc error occurs, or 0x7A or 0xF4 BSODs continue to occur, you have to get a new HDD.