Very likely, I'm afraid that a new hard drive is going to be necessary since these 0x7a stops are caused by bad blocks and not any software that was installed (or not installed.)
Basically, they're indicative of a physically failing hard drive and any kind of format can not repair that.
If money is a concern, then trying to low level format the hdd and re-installing Windows, of course can be tried. There's nothing wrong with the attempt.
There is a hardware issue though. If it isn't the actual drive itself gone bad, it is the cooling of the laptop itself that has gone bad which is causing the hdd to work in temperatures it doesn't like.
----
To the OP - Please make sure you run that chkdsk command as I've shown to above, in an elevated command prompt. This will repair any hard drive errors that it can.
----
Crash dump output:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\Temp\Rar$DI00.856\082110-18423-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82810000 PsLoadedModuleList = 0x82958810
Debug session time: Sat Aug 21 09:46:45.469 2010 (UTC - 4:00)
System Uptime: 0 days 0:33:37.263
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
......
0: kd> !analyze -v
*******************************************************************************
* *
* 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: c049e8d0, lock type that was held (value 1,2,3, or PTE address)
Arg2: c0000185, error status (normally i/o status code)
Arg3: 346108c0, current process (virtual address for lock type 3, or PTE)
Arg4: 93d1a3cc, 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
BUGCHECK_STR: 0x7a_c0000185