what's new? Windows 7 crashing

Hi guys, I have a new windows 7 installation that has been crashing regularly. I posted a dump files to the forum but I did it in the wrong place. Please have a look at my info and let me know what the problem could be. I'm new at debugging winodws so perhaps my info is not the most appropriate. please let me know what should I do better. Just in case I posted the newest dump file.

generally the crushes happen when i leave the computer for an hour or so. I come back and I see the computer has rebooted.

am7555 said:

Hi guys, I have a new windows 7 installation that has been crashing regularly. I posted a dump files to the forum but I did it in the wrong place. Please have a look at my info and let me know what the problem could be. I'm new at debugging winodws so perhaps my info is not the most appropriate. please let me know what should I do better. Just in case I posted the newest dump file.

generally the crushes happen when i leave the computer for an hour or so. I come back and I see the computer has rebooted.

Hi am and welomce

This dump had two proximate causes. Memory and the ntfs.sys file

I would
Run a system file checker to verify and repair system files.
To run type cmd in search>right click and run as admin>
SFC /SCANNOW

Let us know the result at the end of the SFC.

Then I would download and run memtestx86 for several hours

Hope this helps and if you get any more BSOD's upload the dumps so we can narrow it down

Thanks

Ken J+


\
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\111609-17893-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c18000 PsLoadedModuleList = 0xfffff800`02e55e50
Debug session time: Mon Nov 16 20:29:39.081 2009 (GMT-5)
System Uptime: 0 days 1:35:49.829
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {c08a2, 0, 0, 0}

Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )

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

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

NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000000c08a2
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x24

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff88001243e95 to fffff80002c89f00

STACK_TEXT:
fffff880`031405f8 fffff880`01243e95 : 00000000`00000024 00000000`000c08a2 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03140600 fffff880`01243ae8 : 00000001`00000000 00000000`00000000 00000000`00000000 00000080`00000000 : Ntfs!NtfsPagingFileIo+0x155
fffff880`03140700 fffff880`00dac23f : fffffa80`075f7b20 fffffa80`075f7780 fffffa80`075df310 00000000`00000000 : Ntfs! ?? ::FNODOBFM::`string'+0x9e89
fffff880`031407b0 fffff880`00daa6df : fffffa80`050669a0 fffffa80`075f7780 fffffa80`05066900 fffffa80`075f7780 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`03140840 fffff800`02c7ba52 : fffffa80`075f77a0 fffffa80`03a18070 00000000`00000043 fffff880`009e8180 : fltmgr!FltpDispatch+0xcf
fffff880`031408a0 fffff800`02c7bd55 : 00000000`00000000 00000000`00000000 fffff880`031409a0 00000000`00000000 : nt!IoPageRead+0x252
fffff880`03140930 fffff800`02ca4da4 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`02c981ed : nt!MiIssueHardFault+0x255
fffff880`03140a00 fffff800`02c7e848 : 00000000`00000001 fffff6fc`40053d90 fffffa80`056fdb00 fffff880`0317bcd0 : nt!MmAccessFault+0x11c4
fffff880`03140b60 fffff800`02c7ea34 : fffffa80`06f0db60 00000000`00000000 fffffa80`00000000 00000000`00000000 : nt!MiInPageSingleKernelStack+0x134
fffff880`03140c70 fffff800`02c7e9cf : 00000000`00000000 00000000`00000001 fffffa80`0396c890 00000000`00000080 : nt!MmInPageKernelStack+0x40
fffff880`03140cd0 fffff800`02c7e66c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0396c800 : nt!KiInSwapKernelStacks+0x1f
fffff880`03140d00 fffff800`02f2d166 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x84
fffff880`03140d40 fffff800`02c68486 : fffff800`02e02e80 fffffa80`03a01040 fffff800`02e10c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03140d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
Ntfs!NtfsPagingFileIo+155
fffff880`01243e95 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: Ntfs!NtfsPagingFileIo+155

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f

FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsPagingFileIo+155

BUCKET_ID: X64_0x24_Ntfs!NtfsPagingFileIo+155

Followup: MachineOwner

EDIT: might want to addionally do the suggetions below by TG.

Ken
---------