Computer Crashes

Hi,

Lately, (as in the past few days now) my laptop has been crashing with blue screen error reports. I used WhoCrashed to check the dump files to see what the crashes were from and this is the results I received:

Code:

On Wed 2/27/2013 10:53:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini022713-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x4709) 
Bugcheck code: 0x7A (0xFFFFFFFFC022F784, 0xFFFFFFFFC0000185, 0xFFFFFFFFAF882860, 0xFFFFFFFF8BDE1324)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Wed 2/27/2013 10:53:11 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!KeRaiseIrqlToSynchLevel+0x70) 
Bugcheck code: 0x7A (0xFFFFFFFFC022F784, 0xFFFFFFFFC0000185, 0xFFFFFFFFAF882860, 0xFFFFFFFF8BDE1324)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Wed 2/27/2013 2:25:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini022613-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x99EE8) 
Bugcheck code: 0x7A (0xFFFFFFFFC025A0B0, 0xFFFFFFFFC0000185, 0x3C001880, 0xFFFFFFFF9682C8E6)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Mon 2/25/2013 9:27:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini022513-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x5063) 
Bugcheck code: 0x50 (0xFFFFFFFFFF80600C, 0x1, 0xFFFFFFFFA7835063, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Here are the specs for my computer:

windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T5800 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3217256448 total
VM: 2147352576, free: 1956999168
Graphics Card: Nvidia Geforce 9600M GT

Any insight as to the steps I could take to hopefully stop these crashes?

Thanks

 

Welcome to MG's :major

Judging by the above, it's probably hardware-related, memory being most likely, use MemTest86+ (the auto-installer for USB is probably easiest), boot the laptop from it and test for 7+ runs (overnight or while you are at work/school is best).

Can you copy the dumps to your Desktop, zip and attach them please?

 

Here are the files.

I shall run a Memtest as soon as I'm able to. I have speculated that it might possibly be a memory issue, but was subconsciously putting that thought to the back of my mind. I just hope that my CD drive will be nice to me and read the CD I burn the iso to. (I would use the USB but my flash drive decided to break on me. Just my luck eh? haha)

 

Looks like problems with the page file, disk or disk controller, backup all vital data

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: c022f784, lock type that was held (value 1,2,3, or PTE address)
Arg2: c0000185, error status (normally i/o status code)
Arg3: af882860, current process (virtual address for lock type 3, or PTE)
Arg4: 8bde1324, 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

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: c025a0b0, lock type that was held (value 1,2,3, or PTE address)
Arg2: c0000185, error status (normally i/o status code)
Arg3: 3c001880, current process (virtual address for lock type 3, or PTE)
Arg4: 9682c8e6, 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

Run chkdsk /r /f on the hard drive, after the reboot/check, run SFC/SCANNOW 3 times, this should patch any broken/missing System files.


This one's less 'easy' to translate:

Code:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ff80600c, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: a7835063, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 831306d8
Unable to read MiSystemVaType memory at 831112e0
 ff80600c 

FAULTING_IP: 
win32k!ldevLoadInternal+70
a7835063 897004          mov     dword ptr [eax+4],esi

MM_INTERNAL_CODE:  0

 

Alright. Thankfully I have my most important data already backed up on my desktop.

I just burned Memtest to a disc so after chkdsk and sfc runs I'll do the memtest.

If this indeed is hardware failure, is there anything that you could recommend be done to ensure this type of thing doesn't happen in the future? I'd really hate for a similar situation to be done to my desktop.

Thanks

 

Most of the time hardware failure is just due to old age or parts wearing out.

About all you can do to extend the life of your hardware is to keep it cool and avoid use as much as possible. Although this does defeat the purpose of having a computer.

If you treat hardware as something that will break every 5 years or so and you decide to focus on the integrity of your data you will be better off. Make sure you back up everything and a good mantra for this is if you don't have the data in three separate locations then it doesn't exist, but for home use two copies is probably enough.

 

Sounds reasonable. The laptop is going on 3 years now and has had it pretty rough due to siblings neglecting it as well as a dead battery. I regularly clean out my desktop both data and hardware wise so hopefully it will last a lot longer.