You might also want to do a check disk as there is a mention of a disk hardware error in the enclosed DMP file
To do chkdsk
CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows7_BSOD_jcgriff2\082310-28033-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03019000 PsLoadedModuleList = 0xfffff800`03256e50
Debug session time: Mon Aug 23 03:26:39.579 2010 (GMT-4)
System Uptime: 0 days 3:46:35.609
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {20, ffffffffc000009d, fffffa8008dd4078, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c5e0 )
Followup: MachineOwner
---------
5: 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: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa8008dd4078, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
[COLOR=Red][U][I][B]ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000009d[/B][/I][/U][/COLOR]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 1
LAST_CONTROL_TRANSFER: from fffff800030c13fc to fffff80003089740
STACK_TEXT:
fffff880`033d9828 fffff800`030c13fc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`08dd4078 : nt!KeBugCheckEx
fffff880`033d9830 fffff800`03073637 : fffffa80`08dd4010 00000000`c000009d 00000000`00000000 fffffa80`08dd40a8 : nt! ?? ::FNODOBFM::`string'+0x4c5e0
fffff880`033d98f0 fffff800`030660c7 : fffffa80`07935a10 fffffa80`07935a60 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57
fffff880`033d9920 fffff800`03090b9d : fffffa80`07935a10 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`033d99a0 fffff800`0308cd4b : 00000103`0987b801 00000000`00000000 00000000`00000000 fffff880`033d9a50 : nt!KiCommitThreadWait+0x3dd
fffff880`033d9a30 fffff800`03023abf : fffffa80`00000002 fffff880`033d9d20 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
fffff880`033d9ce0 fffff800`0332dc06 : fffffa80`07935a10 00000000`10002000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`033d9d40 fffff800`03067c26 : fffff880`009b2180 fffffa80`07935a10 fffff880`009bd0c0 01ca03ff`7a0c7524 : nt!PspSystemThreadStartup+0x5a
fffff880`033d9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4c5e0
fffff800`030c13fc cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4c5e0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0
BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0
Followup: MachineOwner
---------
Let us know if you need any further help
Ken
