win 7 crashes

samar

New member
Joined
May 18, 2013
Posts
4
Hi!

My laptop started crashing about a week ago. I haven't installed any new programs but I think that some updates were installed. The data collection app for BSODs had some error in it when I ran it but it did make the zip file. I appreciate any help you can give me. Thanks in advance!
 

Attachments

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: fffff6fc500fd508, lock type that was held (value 1,2,3, or PTE address)
Arg2: [COLOR="#FF0000"]ffffffffc0000185[/COLOR], error status (normally i/o status code)
Arg3: 000000006a439880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a01faa1085, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

We have a 0x7A bugcheck which is caused by kernel data not being read back into memory from the hard disk.

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

An I/O error occurred and the dump file is blaming the hard disk. This dump file is consistent so it certainly seems like a bad drive.

Code:
fffff880`02a18328 fffff800`0313e752 : 00000000`0000007a fffff6fc`500fd508 ffffffff`c0000185 00000000`6a439880 : [COLOR="#0000FF"]nt!KeBugCheckEx[/COLOR] [COLOR="#800080"]//This is our actual BSOD crash function[/COLOR]
fffff880`02a18330 fffff800`030f291f : fffffa80`0774d760 fffff880`02a184a0 fffff800`03306600 fffffa80`0774d760 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`02a18410 fffff800`030d91b9 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000002 : [COLOR="#FF0000"]nt!MiIssueHardFault+0x28b[/COLOR] [COLOR="#800080"]//generating the actual hardfault and trying to bring the memory in from the disk[/COLOR]
fffff880`02a184e0 fffff800`030c9cee : 00000000`00000000 fffff8a0`1faa1085 00000000`00000000 00000000`00010000 : [COLOR="#FF0000"]nt!MmAccessFault+0x1399[/COLOR] [COLOR="#800080"]//it couldn't find the memory[/COLOR]
fffff880`02a18640 fffff880`09a0604f : fffff8a0`03fa77a0 fffff8a0`0d8e1ed0 00000000`ffffffff 00001f80`01010801 : [COLOR="#FF0000"]nt!KiPageFault+0x16e[/COLOR] [COLOR="#800080"]//page fault where pageable memory was accessed[/COLOR]
fffff880`02a187d0 fffff8a0`03fa77a0 : fffff8a0`0d8e1ed0 00000000`ffffffff 00001f80`01010801 fffff8a0`064ea000 : [COLOR="#FF0000"]EX64+0x604f[/COLOR] [COLOR="#800080"]//norton anti virus driver[/COLOR]
fffff880`02a187d8 fffff8a0`0d8e1ed0 : 00000000`ffffffff 00001f80`01010801 fffff8a0`064ea000 fffff8a0`064f9000 : 0xfffff8a0`03fa77a0
fffff880`02a187e0 00000000`ffffffff : 00001f80`01010801 fffff8a0`064ea000 fffff8a0`064f9000 0000f412`00000000 : 0xfffff8a0`0d8e1ed0
fffff880`02a187e8 00001f80`01010801 : fffff8a0`064ea000 fffff8a0`064f9000 0000f412`00000000 00000000`00000000 : 0xffffffff
fffff880`02a187f0 fffff8a0`064ea000 : fffff8a0`064f9000 0000f412`00000000 00000000`00000000 00000000`00000040 : 0x00001f80`01010801
fffff880`02a187f8 fffff8a0`064f9000 : 0000f412`00000000 00000000`00000000 00000000`00000040 00000000`0000019e : 0xfffff8a0`064ea000
fffff880`02a18800 0000f412`00000000 : 00000000`00000000 00000000`00000040 00000000`0000019e 00000000`00000000 : 0xfffff8a0`064f9000
fffff880`02a18808 00000000`00000000 : 00000000`00000040 00000000`0000019e 00000000`00000000 fffff8a0`0d8e1ee8 : 0x0000f412`00000000

Normally whenever I see norton in the callstack I usually ask the OP to remove it as it's very problematic, however I don't believe it is the cause as this I/O error is consistent and the IRQL is below DPC/Dispatch level.

Code:
2: kd> [COLOR="#008000"]!irql[/COLOR]
Debugger saved IRQL for processor 0x2 -- [COLOR="#800080"]0[/COLOR] ([COLOR="#800080"]LOW_LEVEL[/COLOR])

Therefore, because pageable memory can be accessed and brought into memory from the disk when it's been paged out at this IRQL I see this as a hardware fault.

Can you run a disk check on your C drive.
Run chkdsk /f /r from the elevated command prompt by typing cmd in the start menu.

I'd also recommend running SeaTools DOS

SeaTools for DOS | Seagate
 
Thanks for the quick reply! I ran chkdsk but I don't know if it did anything because I had to run it before windows started. I also tried running SeaTools DOS but after I burned the ISO file to a CD it did not boot at the beginning from the CD. I checked from BIOS that the boot order is optical drive first. If the laptop crashes again, would you recommend buying a new harddisk and re-installing windows?
 
It sounds like a motherboard issue if the optical drive isn't booting.
Keep trying SeaTools.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top