Problem Devices:
Code:
Marvell 91xx Config ATA Device IDE\PROCESSORMARVELL_91XX_CONFIG_____________________1.01____\6&10E1F5B8&0&1.1.0 The drivers for this device are not installed.
Universal Serial Bus (USB) Controller PCI\VEN_1033&DEV_0194&SUBSYS_50071458&REV_03\4&38482B95&0&0038 The drivers for this device are not installed.
Install the drivers for the above devices.
Antivirus Software? I would recommend installing either or the Run a full scan on your system with the security software once it is installed and updated.
Possible out of date drivers:
Code:
Rt64win7 fffff880`03e6a000 fffff880`03e9c000 Thu Feb 26 02:04:13 2009 (49a65b0d) 000361a5 Rt64win7.sys
GEARAspiWDM fffff880`03eb8000 fffff880`03ec5000 Mon May 18 06:17:04 2009 (4a1151c0) 000159b4 GEARAspiWDM.sys
Update Rt64win7.sys your Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC from Realtek
GEARAspiWDM.sys (this driver rarely is a problem unless iTunes or a CD/DVD program is causing crashes)
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\mkiriti\Windows_NT6_BSOD_jcgriff2\031212-30061-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`0309be50
Debug session time: Mon Mar 12 06:08:28.580 2012 (UTC - 6:00)
System Uptime: 0 days 17:00:39.446
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {20, ffffffffc000009d, fffffa800594b078, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c830 )
Followup: MachineOwner
---------
2: 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: fffffa800594b078, 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:
------------------
ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000009d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 1
LAST_CONTROL_TRANSFER: from fffff80002f07bec to fffff80002ecff00
STACK_TEXT:
fffff880`03108828 fffff800`02f07bec : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`0594b078 : nt!KeBugCheckEx
fffff880`03108830 fffff800`02eb9e67 : fffffa80`0594b010 00000000`c000009d 00000000`00000000 fffffa80`0594b0a8 : nt! ?? ::FNODOBFM::`string'+0x4c830
fffff880`031088f0 fffff800`02eac92f : fffffa80`03a12b60 fffffa80`03a12bb0 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57
fffff880`03108920 fffff800`02ed725d : fffffa80`03a12b60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`031089a0 fffff800`02ed354b : 00000103`05aca901 00000000`00000000 fffff800`00000000 fffff880`03108a50 : nt!KiCommitThreadWait+0x3dd
fffff880`03108a30 fffff800`02e68a8f : fffffa80`00000002 fffff880`03108d20 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
fffff880`03108ce0 fffff800`03173166 : fffffa80`03a12b60 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`03108d40 fffff800`02eae486 : fffff880`02d64180 fffffa80`03a12b60 fffff880`02d6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03108d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+4c830
fffff800`02f07bec cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4c830
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c830
BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c830
Followup: MachineOwner
---------
I suspect this is due to the missing Marvell controller.
Also, install all Windows updates once you get all device drivers installed/updated. I noticed you only have 15 updates installed and have not yet installed Service Pack 1...
Quote
