I have been getting these wierd crashes. Can someone analize my crash dump file?

[Shawn]

I have been randomly getting blue screens. What's weird though is that it never happens when I'm using the computer. I'll go to bed and I'll wake up and my computer has been restarted. It tells me that it recovered from an error but it doesn't give me a driver name or anything. I am using Windows Vista x64.

Here is the crash dump. Maybe someone here can shed some light on the problem.

 

[Shawn]

Crashed again. This time no information.

The previous system shutdown at 2:40:15 PM on 6/11/2007 was unexpected.

When I got home it was stuck on the bios screen saying "No system disk". I had to turn off the power and turn it back on to get it to boot. WTF!?!

 

[Shawn]

ttt

 

[Allanv]

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\abm\Desktop\Mini060807-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16386.amd64fre.vista_rtm.061101-2205
Kernel base = 0xfffff800`01c00000 PsLoadedModuleList = 0xfffff800`01d99e90
Debug session time: Fri Jun 8 12:06:26.247 2007 (GMT+1)
System Uptime: 1 days 9:55:25.124
Loading Kernel Symbols
....................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 77, {1, 478b5824448905c0, 0, fffff9800fc64960}

Probably caused by : memory_corruption ( nt!MiInPageSingleKernelStack+2b9 )

Followup: MachineOwner
---------

1: kd> ;!analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: 0000000000000001, (page was retrieved from disk)
Arg2: 478b5824448905c0, value found in stack where signature should be
Arg3: 0000000000000000, 0
Arg4: fffff9800fc64960, address of signature on kernel stack

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


ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1

BUGCHECK_STR: 0x77_1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_RC

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001c98689 to fffff80001c4e250

STACK_TEXT:
fffff980`012e1b78 fffff800`01c98689 : 00000000`00000077 00000000`00000001 478b5824`448905c0 00000000`00000000 : nt!KeBugCheckEx
fffff980`012e1b80 fffff800`01c987c1 : fffffa80`064e5330 fffff980`012e1ca0 00000000`00000000 fffffa80`064e5330 : nt!MiInPageSingleKernelStack+0x2b9
fffff980`012e1c80 fffff800`01c986ef : fffff800`01c73230 fffffa80`03999430 00000000`00000000 00000000`00000080 : nt!MmInPageKernelStack+0x41
fffff980`012e1ce0 fffff800`01c732c4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInSwapKernelStacks+0x1f
fffff980`012e1d10 fffff800`01ee199b : 00010000`00003960 00000000`005a0070 00010000`0000061b 01c6fe48`3a1cd401 : nt!KeSwapProcessOrStack+0x94
fffff980`012e1d50 fffff800`01c34b86 : fffff800`01d49880 fffffa80`039cbbb0 fffff800`01d4eb80 fffff980`012e8ce0 : nt!PspSystemThreadStartup+0x5b
fffff980`012e1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiInPageSingleKernelStack+2b9
fffff800`01c98689 cc int 3

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4549b6c6

SYMBOL_NAME: nt!MiInPageSingleKernelStack+2b9

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x77_1_nt!MiInPageSingleKernelStack+2b9

BUCKET_ID: X64_0x77_1_nt!MiInPageSingleKernelStack+2b9

Followup: MachineOwner
---------


looks like if i read it correctly the HDD is going bad...

 

[Shawn]

ack! anyway to tell which drive? would this be the OS drive?

 

[Allanv]

the OS drive by the look of it, but i would wait until someone who can read a bugcheck better than me pops in and gives you a final answer..

 

[Shawn]

Ok, thanks. The crashes only seem to happen when I am running bittorant and have a lot of things downloading at once. My downloads are saved to a separate partition on the same drive.

 

[RebateMonger]

Originally posted by: Shawn
Crashed again. This time no information.

In my experience, if there's no crash dump (and Windows is set to provide one), it's often because there's a problem with the hard drive system (controller, cable, drives, drivers).

 

[Shawn]

I did a thorough hard drive test with WD Diagnostics and the drive checks out ok. I also ran Memtest86 and my memory checks out ok too.

 

[Allanv]

try utoorent see if it works any better and stops the crashes but i still suspect something amiss