Problem Devices:
Code:
Universal Serial Bus (USB) Controller PCI\VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00\4&108ABD8A&0&00E4 The drivers for this device are not installed.
Universal Serial Bus (USB) Controller PCI\VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00\4&DDEC341&0&00E1 The drivers for this device are not installed.
Make sure you get the drivers from ASUS - Motherboards- ASUS P8P67 through OS: Windows 7 64bit under USB.
Also, it does not appear all Windows updates have been installed. Make sure you install all Windows updates including optional updates but excluding driver updates through Windows updates. Driver updates should be obtained from the manufacturer of the driver or from your motherboard support site.
Code:
-
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\Yeoman\Yeoman BSOD seven forums (second zip)\Windows_NT6_BSOD_jcgriff2\032912-14289-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e64000 PsLoadedModuleList = 0xfffff800`030a8650
Debug session time: Thu Mar 29 04:44:46.289 2012 (UTC - 6:00)
System Uptime: 0 days 3:32:54.476
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff88003310000, 0, fffff800033307f4, 0}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PfpFlushBuffers+294 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88003310000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800033307f4, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003112100
fffff88003310000
FAULTING_IP:
nt!PfpFlushBuffers+294
fffff800`033307f4 488b4d00 mov rcx,qword ptr [rbp]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff880087988a0 -- (.trap 0xfffff880087988a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000006007
rdx=fffff8a0033db178 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033307f4 rsp=fffff88008798a30 rbp=fffff88003310000
r8=0000000000000001 r9=0000000000000717 r10=fffff8a0033d4000
r11=fffff8a0033da578 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!PfpFlushBuffers+0x294:
fffff800`033307f4 488b4d00 mov rcx,qword ptr [rbp] ss:0018:fffff880`03310000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e8d25c to fffff80002ee0d40
STACK_TEXT:
fffff880`08798738 fffff800`02e8d25c : 00000000`00000050 fffff880`03310000 00000000`00000000 fffff880`087988a0 : nt!KeBugCheckEx
fffff880`08798740 fffff800`02edee6e : 00000000`00000000 fffff880`03310000 00000000`00002900 fffffa80`07aef000 : nt! ?? ::FNODOBFM::`string'+0x456cf
fffff880`087988a0 fffff800`033307f4 : 00000000`00000656 fffffa80`00000716 00000000`00000000 fffffa80`08a8ae48 : nt!KiPageFault+0x16e
fffff880`08798a30 fffff800`03351e80 : fffffa80`0adcab01 00000000`00000080 fffffa80`06cef040 fffff800`03067da8 : nt!PfpFlushBuffers+0x294
fffff880`08798ad0 fffff800`0317af7a : ffffffff`ff676980 fffffa80`0adcab60 fffff880`08798c70 fffffa80`0adcab60 : nt!PfTLoggingWorker+0xe0
fffff880`08798c00 fffff800`02ed19c6 : fffff800`03055e80 fffffa80`0adcab60 fffff800`03063cc0 fffff880`01266384 : nt!PspSystemThreadStartup+0x5a
fffff880`08798c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PfpFlushBuffers+294
fffff800`033307f4 488b4d00 mov rcx,qword ptr [rbp]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!PfpFlushBuffers+294
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2
FAILURE_BUCKET_ID: X64_0x50_nt!PfpFlushBuffers+294
BUCKET_ID: X64_0x50_nt!PfpFlushBuffers+294
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\Yeoman\Yeoman BSOD seven forums (second zip)\Windows_NT6_BSOD_jcgriff2\032412-29484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e18000 PsLoadedModuleList = 0xfffff800`0305c650
Debug session time: Sat Mar 24 06:28:41.842 2012 (UTC - 6:00)
System Uptime: 0 days 2:41:44.028
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffffffffffffff, 2, 1, fffff80002ec5932}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffffffffffffff, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ec5932, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c6100
ffffffffffffffff
CURRENT_IRQL: 2
FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`02ec5932 48890a mov qword ptr [rdx],rcx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: MsMpEng.exe
TRAP_FRAME: fffff88003d1a3a0 -- (.trap 0xfffff88003d1a3a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003d1a5e0
rdx=ffffffffffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ec5932 rsp=fffff88003d1a530 rbp=fffff88003d1a5c0
r8=0000000000000000 r9=0000000000000000 r10=fffffa8006bfe4b0
r11=fffff800030c9ac0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KxWaitForLockOwnerShip+0x12:
fffff800`02ec5932 48890a mov qword ptr [rdx],rcx ds:0202:ffffffff`ffffffff=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e942e9 to fffff80002e94d40
STACK_TEXT:
fffff880`03d1a258 fffff800`02e942e9 : 00000000`0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03d1a260 fffff800`02e92f60 : 00000000`00000000 fffffa80`0a0d6b60 ffffffff`fffffd80 fffffa80`0182cbe0 : nt!KiBugCheckDispatch+0x69
fffff880`03d1a3a0 fffff800`02ec5932 : 00000000`00000000 00000000`00000001 fffffa80`06cefc68 00000000`00000001 : nt!KiPageFault+0x260
fffff880`03d1a530 fffff800`02ea46cd : fffffa80`0182cbe0 00000000`00000000 fffff880`03d1a5c0 fffffa80`06cefb60 : nt!KxWaitForLockOwnerShip+0x12
fffff880`03d1a560 fffff800`02ec6ee7 : 00000000`00000000 fffff680`00038eb8 00000000`00000000 00000000`00000001 : nt!MiInsertPageInFreeOrZeroedList+0x55d
fffff880`03d1a670 fffff800`02ec6137 : 00000000`00000000 fffff680`00038fb0 fffffa80`09ee9b30 00000000`00000000 : nt!MiDeletePteRun+0x4ed
fffff880`03d1a820 fffff800`02e814bf : fffffa80`00000000 00000000`07370fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`03d1a9e0 fffff800`02e93fd3 : ffffffff`ffffffff 00000000`027fe720 00000000`027fe6e8 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`03d1aae0 00000000`773514fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`027fe658 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773514fa
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`02ec5932 48890a mov qword ptr [rdx],rcx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KxWaitForLockOwnerShip+12
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2
FAILURE_BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12
BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12
Followup: MachineOwner
---------
- Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Antivirus Software... Drivers...
- Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
When you have a chance, test for Windows corruption (not likely given this is a fairly fresh install, but sometimes installation DVDs can be faulty) and hardware problems:
I realize these are a lot of steps to do in your limited time, so do the best you can. Report back as you proceed, and whatever pace works for you, I'll be checking on the thread as you go, even if it takes a few weeks or more.