Problem Devices:
Code:
Cisco AnyConnect VPN Virtual Miniport Adapter for Windows x64 ROOT\NET\0000 This device is disabled.
Security Software:
Code:
msmpeng.exe c:\program files\microsoft security client\antimalware\msmpeng.exe 924 8 200 1380 3/22/2012 12:50 PM 3.0.8402.0 12.48 KB (12,784 bytes) 4/27/2011 5:21 PM
nissrv.exe c:\program files\microsoft security client\antimalware\nissrv.exe 4824 8 200 1380 3/22/2012 12:54 PM 3.0.8402.0 281.52 KB (288,272 bytes) 4/27/2011 5:21 PM
msseces.exe c:\program files\microsoft security client\msseces.exe 2892 8 200 1380 3/22/2012 12:51 PM 2.1.1116.0 1.37 MB (1,436,736 bytes) 6/15/2011 2:35 PM
system idle process Not Available 0 0 Not Available Not Available Not Available Not Available Not Available Not Available
Code:
-
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\Kingston\BSODDmpFiles\gbrethen\Windows_NT6_BSOD_jcgriff2\032212-30560-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 (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c4f000 PsLoadedModuleList = 0xfffff800`02e93650
Debug session time: Thu Mar 22 11:49:44.144 2012 (UTC - 6:00)
System Uptime: 0 days 16:55:02.767
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff9fec084da68, 0, fffff96000176d97, 5}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!zzzLockDisplayAreaAndInvalidateDCCache+127 )
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: fffff9fec084da68, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff96000176d97, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efd100
fffff9fec084da68
FAULTING_IP:
win32k!zzzLockDisplayAreaAndInvalidateDCCache+127
fffff960`00176d97 488b4058 mov rax,qword ptr [rax+58h]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: Rainmeter.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800ae717e0 -- (.trap 0xfffff8800ae717e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff9fec084da10 rbx=0000000000000000 rcx=fffff900c084db50
rdx=fffff900c02031f8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000176d97 rsp=fffff8800ae71970 rbp=00000000ffffffff
r8=0000000000000000 r9=0000000000000215 r10=fffffa8006705810
r11=fffff8800ae718e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
win32k!zzzLockDisplayAreaAndInvalidateDCCache+0x127:
fffff960`00176d97 488b4058 mov rax,qword ptr [rax+58h] ds:4100:fffff9fe`c084da68=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c76c1f to fffff80002ccbd40
STACK_TEXT:
fffff880`0ae71678 fffff800`02c76c1f : 00000000`00000050 fffff9fe`c084da68 00000000`00000000 fffff880`0ae717e0 : nt!KeBugCheckEx
fffff880`0ae71680 fffff800`02cc9e6e : 00000000`00000000 fffff9fe`c084da68 fffff900`c0203100 fffff900`c1d56260 : nt! ?? ::FNODOBFM::`string'+0x43d41
fffff880`0ae717e0 fffff960`00176d97 : 00000000`00000000 fffff900`00000000 00000200`00000764 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0ae71970 fffff960`0017ae01 : fffff900`c2c37090 fffff900`c2c37010 fffff8a0`00000000 0000002c`00000000 : win32k!zzzLockDisplayAreaAndInvalidateDCCache+0x127
fffff880`0ae719c0 fffff960`0017a28e : fffff960`003c6340 00000000`00000000 fffff960`00000000 fffff800`00000001 : win32k!zzzBltValidBits+0x365
fffff880`0ae71ac0 fffff960`001dee41 : 00000000`00000001 00000000`00000001 00000000`00000007 fffff960`00000000 : win32k!xxxEndDeferWindowPosEx+0x1f2
fffff880`0ae71b80 fffff960`001beac1 : 00000000`00000000 fffff880`0ae71ca0 00000000`00000000 fffff960`001c183d : win32k!xxxSetWindowRgn+0x99
fffff880`0ae71bd0 fffff800`02ccafd3 : fffffa80`06b23060 00000000`0001037a 00000000`00000027 00000000`00000000 : win32k!NtUserSetWindowRgn+0x95
fffff880`0ae71c20 00000000`769fb55a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0018dca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x769fb55a
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!zzzLockDisplayAreaAndInvalidateDCCache+127
fffff960`00176d97 488b4058 mov rax,qword ptr [rax+58h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k!zzzLockDisplayAreaAndInvalidateDCCache+127
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4f2b63bd
FAILURE_BUCKET_ID: X64_0x50_win32k!zzzLockDisplayAreaAndInvalidateDCCache+127
BUCKET_ID: X64_0x50_win32k!zzzLockDisplayAreaAndInvalidateDCCache+127
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\gbrethen\Windows_NT6_BSOD_jcgriff2\032012-75379-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 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02a53000 PsLoadedModuleList = 0xfffff800`02c8fe70
Debug session time: Tue Mar 20 12:26:34.210 2012 (UTC - 6:00)
System Uptime: 0 days 5:57:51.129
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa9007a29f50, 1, fffff80002acb234, 5}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceExclusiveLite+54 )
Followup: MachineOwner
---------
0: 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: fffffa9007a29f50, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002acb234, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfa0e0
fffffa9007a29f50
FAULTING_IP:
nt!ExAcquireResourceExclusiveLite+54
fffff800`02acb234 f0480fba696000 lock bts qword ptr [rcx+60h],0
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800b929810 -- (.trap 0xfffff8800b929810)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a3160b0 rbx=0000000000000000 rcx=fffffa9007a29ef0
rdx=fffff8a016dee901 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002acb234 rsp=fffff8800b9299a0 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000001 r10=fffff8800b929ab8
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl zr na po nc
nt!ExAcquireResourceExclusiveLite+0x54:
fffff800`02acb234 f0480fba696000 lock bts qword ptr [rcx+60h],0 ds:fcf0:fffffa90`07a29f50=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b41ed1 to fffff80002ac3540
STACK_TEXT:
fffff880`0b9296a8 fffff800`02b41ed1 : 00000000`00000050 fffffa90`07a29f50 00000000`00000001 fffff880`0b929810 : nt!KeBugCheckEx
fffff880`0b9296b0 fffff800`02ac162e : 00000000`00000001 fffffa90`07a29ef0 00000000`07ca4c00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x408fb
fffff880`0b929810 fffff800`02acb234 : fffff880`0b9299b6 00000000`00000001 ff000000`00000000 fffffa80`00000000 : nt!KiPageFault+0x16e
fffff880`0b9299a0 fffff880`01218353 : 00000000`c00000d8 fffff8a0`16dee940 fffffa80`0b0ffcf0 fffff800`02a98274 : nt!ExAcquireResourceExclusiveLite+0x54
fffff880`0b929a10 fffff880`012d9e50 : fffff8a0`16dee940 00000000`00000080 00000000`00000000 fffffa80`07c6a180 : Ntfs!NtfsAcquireExclusiveFcb+0x73
fffff880`0b929a60 fffff880`01247e57 : 00000000`00000000 fffff8a0`14892df0 00000000`00000000 00000000`00000080 : Ntfs!NtfsAcquireAllFiles+0xc4
fffff880`0b929ab0 fffff880`013822d5 : fffffa80`0b0ffcf0 fffffa80`07c6a180 00000000`00000000 fffffa80`07c6a180 : Ntfs!NtfsCheckpointForVolumeSnapshot+0x117
fffff880`0b929b40 fffff880`0120d4d7 : fffffa80`0b0ffcf0 fffffa80`07cfac10 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonDeviceControl+0x344
fffff880`0b929c60 fffff800`02d62726 : 00000000`00000000 fff1109d`fff11000 00000000`00000001 fffff800`02abb3c7 : Ntfs!NtfsFspDispatch+0x4a7
fffff880`0b929d40 fffff800`02aa1ac6 : fffff800`02c3ce80 fffffa80`0a316060 fffff800`02c4ac40 fffff880`012182b4 : nt!PspSystemThreadStartup+0x5a
fffff880`0b929d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExAcquireResourceExclusiveLite+54
fffff800`02acb234 f0480fba696000 lock bts qword ptr [rcx+60h],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!ExAcquireResourceExclusiveLite+54
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ec7a284
FAILURE_BUCKET_ID: X64_0x50_nt!ExAcquireResourceExclusiveLite+54
BUCKET_ID: X64_0x50_nt!ExAcquireResourceExclusiveLite+54
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...
- Same as 1.
Thanks to Dave76 for help understanding possible causes.
We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.
If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.
- If you are overclocking any hardware, please stop.
- Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
- Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
- Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
If you swap any memory components, follow these steps for ESD safety:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.
Also, go into your BIOS and post all Voltages (CPU, RAM, NB, IMC, etc.) and all RAM settings (timings, frequency, etc.)
Thanks to Dave76 for help learning RAM Stability
Quote